Create Single-Tenant Cloud Partner Apps

Step 1

Go to https://partners.dnaspaces.io/home to login to the Cisco Spaces - Partner Dashboard.

Step 2

Click the Create New App tile under the Partner Apps section. For details, refer to the Create Partner Apps section.

The Choose App Type dialog box displays the Multi Tenant Cloud, Single Tenant Cloud, and On-Prem options.

Step 3

Select Single Tenant Cloud.

Step 4

Click Create.

Step 5

The App Center tab displays by default.

1. Choose the desired region. To create, activate, publish and manage app for the Europe region, choose the Europe Region option. Otherwise, choose Rest of the World (Except Europe region) option.

2. Enter a relevant App Name.

3. Enter a relevant App Tagline for your app.

4. Click the Choose File button to select and upload the App Icon image.

5. Enter a relevant App Description.

6. Choose the Primary Industry for the app.

7. Check the relevant check boxes under the More Industries section, if your app is applicable to specific business segments. Retail, Hospitality, Health Care, Manufacturing, Education, Financial Services, Venues, Workspaces, Real estate, and Others.

8. You can include (optional) following details: in the Developer Info, Support Contact, Sales Contact, and App Media sections such as the Company Logo, Company Name, Company Website, Support Contact, Support Email, Sales Phone, Sales Email, Screenshots, and Youtube Video URL.

   • Under the Developer Info section, click Choose File to upload a company logo of the app developer.

   • Enter the Company Name of the app developer, if needed.

   • Enter the Company Website of the app developer, if needed.

   • Under the Developer Info section, click Choose File to upload a company logo of the app developer.

   • Enter the Company Name of the app developer, if needed.

   • Enter the Company Website of the app developer, if needed.

   • Under the Support Contact section, enter the Support Phone number, if needed.

   • Under the Support Contact section, enter the Support Email address, if needed.

   • Under the Sales Contact section, enter the Sales Phone number, if needed.

   • Under the Sales Contact section, enter the Sales Email address, if needed.

   • Under the App Media section, Drag & drop screenshots of your application from your local drive, or click the Click here to upload link to choose and upload screenshots of your app, if needed.

   • Enter the Youtube Video URL and click Save, if you wish to save a video URL of your application.

Step 6

Click on the Use Cases tab.

Step 7

Click the Add a Use Case button if you wish to add one or more use cases.

1. Enter a relevant Use Case Headline.

2. Click the Choose File button to select and upload the Use Case Icon.

3. Enter relevant Use Case Short Description.

4. Enter the optional Use Case Long Description, if any.

5. Enter the optional Compatibility Notes, if any.

6. Choose the relevant Use Case Category. The available options are Analytics, Captive Portal, Marketing & Engagement, Asset Management, Wayfinding, Mapping, and Others. Choose Others if the use case does not belong to any of the available categories.

7. Provide other optional use case options, for the Who is this use case applicable to, What value does this drive for the customer? questions.

8. Optionally, select the appropriate Infrastructure Compatibility options.

9. Optionally, select the upload relevant Screenshots, and Youtube Video URL, if any

10. Click Save to save changes.

11. Click Add Another Use Case button to add additional use cases.

Step 8

Click on the App Tile tab. The App Tile Configuration section displays.

1. Enter a relevant APP Tile Label.

2. Enter the desired App Tile Tagline description.

3. Enter the relevant instructions in the App Activation Instructions window, if needed

Step 9

Click on the Behaviors tab. Enter details in the App Behaviors section, if you wish to support automated sign-up for new customers.

1. The NEW CUSTOMER ONBOARDING section allows you to enter the redirect URL for new customers' sign-up. Enter the redirect URL in the Sign Up URL field.

2. Enter correct address in the Contact Company Info field.

3. To enable customers to view details when they remove/delete the App, enter details in the Delete App Confirmation field. Ensure the URL uses the https:// protocol.

4. The App monitoring configurations help Cisco Spaces to monitor and report the app health and the uptime status. Under the APP MONITORING section, enter the correct link addresses in the App Health Check URL, API Health Status URL, and the App Status Page URL fields. Make sure to use the https:// protocol when entering the App Monitoring URLs. For more information, see Monitor Partner App Health.

Step 10

Click on the Events tab. The available app Events Types and Event Settings are listed.

1. The available Events Types displayed are:

   • Device Entry: This event is sent when a device enters a location.

   • Device Exit: This event is sent when a device has exited a location.

   • Profile Update: This event is sent when a device profile is updated. For example, this event is sent when an end-user provides information in a captive portal.

   • Location Information Change: This event is sent when a location is updated or changed. For example, a location is moved under a group, location is renamed or there is a change to the location metadata.

   • TelePresence: This event is sent when the TelePresence system encounters a people count update.

   • Device Location Update: This event is sent when a device location is updated. If you check the Receive Geo Coordinates option, you will receive the device latitude and longitude coordinates, along with the X and Y coordinates data for the device.

   • App Activation : This event is sent when a customer activates the application.

   • Account Admin Change: This event is sent when a account admin gets added/removed/updated for the partner account.

   • Device Presence: Used to track life cycle of a device at a location. Events are generated at device entry, when a device is inactive for 10 minutes, when a device is active after being inactive or when we determine that the device has exited. These events also provide current count of devices at location (active and inactive).

   • User Presence: Based on available authentication in use and information available from the network, Cisco Spaces can map group multiple devices owned by a user. Events are generated at user entry, when a user is inactive for 10 minutes, when a user is active after being inactive or when we determine that the user has exited. These events also provide current count of user at location (active and inactive).

   • IoT Telemetry: This event is sent when there are telemetry updates from BLE, RFID, and Zigbee IoT devices.

   • IoT User Action: This event is sent when user actions are performed on IoT devices.

   • Device Count: This event is sent when there is a change in the (count) number of devices at the location.

   • Camera Count: This event is sent when there is a change in the aggregated count of people (computed via the Meraki Video Camera) at the location.

   • Raw Camera Count: This event is sent when there is a change in the individual camera count (computed via the Meraki Video Camera) at the location.

   • Network Telemetry: This event is sent at a periodical interval with health and performance telemetries of the location.

   • Location Anchor Update: This event is sent when a new location anchor is added to, updated in, or removed from IoT Services.

   Note

   For more information, see the Event Types section. During app activation, you can now see the groups defined under IoT services. However, these groups are displayed only if you have selected one of the following events: IOT_TELEMETRY IOT_USER_ACTION To manage the groups selected during app activation, in the Activation window, click the Groups tab. Here, you can add or edit the groups. Note For this feature to work, you must enable IoT services for the specified Cisco Spaces account. You must enable IoT services through both the Cisco Spaces Dashboard and the Cisco Spaces - Partner Dashboard for EXTEND accounts in order to use this feature. You can see the groups mentioned above during app activations for activations done through both the Cisco Spaces Dashboard and the Cisco Spaces - Partner Dashboard.

2. Under the Event Settings section, check the desired location option.

   • Under Choose Locations, you can choose to receive the above Event types data for the various location levels specified in the Cisco Spaces - Location hierarchy. The Location hierarchy in Cisco Spaces can be setup to correspond to your business needs and your organizational hierarchy, instead of corresponding only to the physical or geographical business hierarchy.

     In Cisco Spaces, you can set up your business organizational hierarchy by defining the main or the Root Level, which can include one or more Group and Network level. Each Network level may include one or more floors, while each Floor level can include one or more Zones. Access points can be associated with the different zones.

     • Check All Location Types if you wish to make the app available and receive the event data from all the business locations.

     • Check the Location Types option if you wish to make the app available and receive the event data only from specific location types that you choose. Root Level, Groups, Network, Floor, and Zone are the available location types.

       Note

       If you are operating only at specific levels in the location hierarchy, such as only at the Network, Floor or Zone levels, it is highly recommended that you choose to receive Event data only for those specific levels, in order to avoid unnecessary system overheads. Only if you need to process information from all levels in the Cisco Spaces - Location hierarchy, then choose the All Location Types option.

     • Select the desired location types.

     • Some of the event types listed above include the device MAC address in the Event payloads. For the MAC Address Sharing event setting, if you check the Yes option, you will receive the Client MAC addresses along with the associated events details. If you wish to receive MAC Address Sharing details, then you will be responsible for handling the GDPR compliance requirements. However, if you do not adhere to GDPR compliance standards requirements and your business requirement only needs the device ID, then you can use the device ID event type data provided by Cisco Spaces provides with all the device-related events.

     • Some of the event types listed above include the Social Identifier Sharing data in the Event payloads. For the Social Identifier Sharing event setting, if you check the Yes option, you will receive the Social identifier Sharing data along with the associated events details. If you wish to receive Social identifier Sharing details, then you will be responsible for handling the GDPR compliance requirements. However, if you do not adhere to GDPR compliance standards requirements and wish to avoid data privacy issues while handling or storing the Social Identifier Sharing data, then you can choose the No option, which is checked by default.

     • Likely, some Partners may not have their wireless network infrastructure fully set up and configured to receive the above Event types information to analyze the data that is received. To glance and get a quick preview of the typical sample data that is received from the above events, choose the Yes option associated with the Receive Simulation Events option. You will receive sample dummy data from Cisco.

       Note	Data that is provided as part of the Simulation Events is only dummy data. This sample data does not guarantee any interoperability or integrity across any other events or APIs. Simulation data is available only for the US domain.

       Check No if you do not wish to receive dummy simulation events data from Cisco.

   The Permissions and the Location Permissions sections on the right-side displays information on the permission types that will be requested from customers during App activation. the Permissions are based on the event types that you selected. For example: If you wish to collect the MAC address of a device, then the app will request the MAC specific permissions from the Customer. These permissions will be based on the selected events, location, and the privacy configurations.

Step 11

Select the desired Integration Types details on the Integration Details tab.

1. Under the Pull Channels section, check the desired options.

   • Check the HTTP check box to send pull channel events details over a streaming HTTP Connection.

   • Check the gRPC check box to send pull channel events over a streaming gRPC call.

   Note	For details, see the Pull Streaming channels section.

Step 12

Click Create to create the App.