Step 1

Go to https://partners.dnaspaces.io/ to log in to the Cisco Spaces - Partner Dashboard.

Step 2

Click the Create New App tile under the Partner Apps section.

Step 3

Select Multi Tenant Cloud and click Create.

Step 4

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. (Optional) Under the More Industries section, choose the business segments that the app applies to.

   The options available are listed below:

   • Retail

   • Hospitality

   • Health Care

   • Manufacturing

   • Education

   • Financial Services

   • Venues

   • Workspace

   • Real estate

   • Others

8. (Optional) You can also add the following details:

   Note	The information collected here will be displayed on the App details screen, when you view the App information on the Cisco Spaces - Partner App Center. Please ensure the developer details provided here are up-to-date.

   • Developer Info: Under Developer Info, click Browse to choose the Company Logo and upload the file.

   • Company Name: Enter the Company Name of the App developer.

   • Company Website: Enter the Company Website of the App developer

   • Support Contact: Enter the Support Phone number and Support Email address.

   • Sales Contact: Enter the Sales Phone number and Sales Email address.

   • Phone

   • App Media: You can also add the following info for your app:

     • Screenshots: You can upload Screenshots of your application from your local drive either through Drag & drop or by using Click here to upload.

     • Youtube Video URL: Enter the Youtube Video URL of your app and click Save.

Step 5

Under the Use Cases tab, click the Add a Use Case button to add a use case.

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 6

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 App Dashboard URL. Ensure the URL uses the https:// protocol.

4. Check the OAuth check box.

5. Enter your Client ID.

6. Click Regenerate Secret to generate a Client Secret key. This value is automatically populated the Client Secret field.

7. A default value, https://partners.dnaspaces.io/partner/OAuthValidation, is automatically populated in the Redirect URI field. Specify the OAuth Login URL prefixed with https://.

   Under the OAuth Configuration section, enter the OAuth Login URL, OAuth Token URL, and the App Info URL. These details need to be confirmed and provided by the partner.

   Note

   When your app is ready for submission, replace the Cisco Spaces test authentication site (Trigue) URLs with valid OAuth URLs. If your app does not have an authentication site configured for App activation, then you can choose to use the Cisco test site for testing your app's authentication. For the US domain Cisco Spaces - Partner Dashboard, enter the following details: Client ID: dnaspaces Client Secret Key: c567560ad2e84795a8f16c32586e1f69b78cab02 OAuth Login URL: https://trigue.dnaspaces.io/auth/login. OAuth Token URL: https://trigue.dnaspaces.io/auth/token App Info URL: https://trigue.dnaspaces.io/appInfo Dashboard URL: https://trigue.dnaspaces.io/auth/appLogin For the EU domain Cisco Spaces - Partner Dashboard, enter the following details: Client ID: dnaspaces Client Secret Key: c567560ad2e84795a8f16c32586e1f69b78cab02 OAuth Login URL: https://trigue.dnaspaces.eu/auth/login OAuth Token URL: https://trigue.dnaspaces.eu/auth/token App Info URL: https://trigue.dnaspaces.eu/appInfo Dashboard URL: https://trigue.dnaspaces.eu/auth/appLogin

Step 7

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. In the APP MONITORING section, specify the App Health Check URL, API Health Status URL, and the App Status Page URL in the corresponding fields.

   Note	Use https:// for the app monitoring URLs. When your app is ready for submission, specify valid app monitoring URLs.

   The App monitoring configurations help Cisco Spaces to monitor and report the app health and the partner app uptime status. For more information, see Monitor Partner App Health.

Step 8

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.

     Attention

     The Device Entry event is deprecated and is now replaced by the Device Presence event.

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

     Attention

     The Device Exit event is deprecated and is now replaced by the Device Presence event.

   • Device RSSI Update: This event is sent when a device RSSI is updated.

   • BLE RSSI Update: This event is sent when there is a ping from the BLE device at the location.

   • Profile Update: This event is sent when a device profile is modified. 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 modified. For example, when a location is renamed, moved under a group, or when there is a change to the location's metadata.

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

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

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

   • Device Presence: This event is used to track the life cycle of a device at a location. Events are generated at various points such as 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 active and inactive devices at the location.

   • 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 various points such as 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.

   • Network Status Update: This event is sent to represent the status of the connector and controller.

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

     Attention

     The TelePresence event is deprecated and is now replaced by the WebEx Telemetry event which is the enhanced version of the Telepresence update.

   • WebEx Telemetry: This event is sent when there is telemetry from WebEx devices at the location.

     Note	You need a Cisco Spaces ACT license to utilize this event.

   • Device Association: This event is triggered when a device successfully connects to an SSID (ASSOCIATE) or disconnects from an SSID (DISASSOCIATE). Device details include device ID, location details, SSID, and other information associated with the user.

   Note

   For more information, go to https://developer.cisco.com/docs/cisco-spaces-firehose/api/. 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 9

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

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

   • Check the AWS Kinesis check box to push events to the AWS Kinesis Data Stream.

     • Choose the required AWS Region.

     • Enter the exact stream name used while creating the Data Stream in AWS.

     • Enter the correct AWS Access Key.

     • Enter the correct AWS Secret Key.

   • Check the AWS Kinesis Firehose check box to push event details to the AWS Kinesis Data Firehose.

     • Choose the required AWS Region.

     • Enter the exact stream name used while creating the Delivery Stream in AWS.

     • Enter the correct AWS Access Key.

     • Enter the correct AWS Secret Key.

   • Check the Azure Events Hub check box to channel push events to an Azure Event Hub.

     • Enter the correct Connection String.

   • Check the Google Pub/Sub check box to push events to Google Pub/Sub.

     • Enter the correct Project ID.

     • Enter the correct Topic ID.

   Note	The AWS Secret Key and Connection String fields are now masked while an app is created or being edited.

1. In the Pull Channels section, choose among the following options:

   • HTTP: Sends pull channel event details over a streaming HTTP connection.

   • gRPC: Sends pull channel event details over a streaming gRPC call.

   • Websocket: Sends pull channel event details over a streaming Websocket connection.

   Note	For details, visit Pull Channels.

Step 10

Click Create to create the App.

Step 1

Login to the Cisco Spaces - Partner Dashboard.

Step 2

Click on the App Activation Sandbox tile.

Step 3

Click the Get Partner Apps tile under the EXTEND section.

Step 4

Click on the desired app to view the associated details.

Step 5

Click Activate App.

Step 6

Depending on whether you have an account with the Partner, choose the appropriate option under Sign Up & Onboarding and click Continue.

Step 7

Click Accept Permission to continue.

Step 8

Select the locations for which you wish to enable and activate this app. Depending on your selection of events related to IoT services configured during app creation, either the Next or Select & Activate button appears.

• If the Next button appears, go to Step 9.

• If the Select & Activate button appears, go to Step 10.

Step 9

Click Next.

Step 10

Click Select & Activate to activate the App.

Step 11

If the OAuth login authentication integration is implemented by your application, Cisco Spaces retrieves details of the account from your application, and setups a mapping between Cisco Spaces Tenant ID and your account identifier.

Step 12

Your application is now activated. It is added as a panel under Cisco Spaces Home page. Customer can click on this panel to access your application from Cisco Spaces dashboard.

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.

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 Event Types displayed are:

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

     Attention

     The Device Entry event is deprecated and is now replaced by the Device Presence event. The Device Entry event is deprecated and is now replaced by the Device Presence event.

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

     Attention

     The Device Exit event is deprecated and is now replaced by the Device Presence event.

   • 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.

     Attention

     The TelePresence event is deprecated and is now replaced by the WebEx Telemetry event which is the enhanced version of the Telepresence 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.

   • WebEx Telemetry: This event is sent when there is telemetry from WebEx devices at the location.

     Note	You need a Cisco Spaces ACT license to utilize this event.

   • Device Association: This event is sent when a device gets connected at a specified location. Device details include device ID, location details, SSID, and other information associated with the user.

   Note

   For more information, go to https://developer.cisco.com/docs/cisco-spaces-firehose/api/. 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. In the Pull Channels section, choose among the following options:

   • HTTP: Sends pull channel event details over a streaming HTTP connection.

   • gRPC: Sends pull channel event details over a streaming gRPC call.

   • Websocket: Sends pull channel event details over a streaming Websocket connection.

   Note	For details, see the Pull Channels channels section.

Step 12

Click Create to create the App.

Step 1

Log in to the Cisco Spaces - Partner Dashboard.

Step 2

Click on the App Activation Sandbox tile.

Step 3

Click the Get Partner Apps tile under the EXTEND section.

Step 4

Click on the desired app to view the associated details.

Step 5

Click Activate App.

Step 6

Depending on whether you have an account with the Partner, choose the appropriate option under Sign Up & Onboarding and click Continue.

Step 7

Click Accept Permission to continue.

Step 8

Select the locations for which you wish to enable and activate this app in order to receive the Event data and click Next.

Step 9

Select the groups you wish to enable for this app and click Next.

Step 10

Under the Generate App Activation Token section, click Generate to obtain the Activation (JWT) Token.

Step 11

Click Copy Token to copy the displayed Activation Token.

Step 12

Follow the on-screen instructions, in the Activation Instructions section, to activate the app.

Step 13

Click the Activate Single Tenant Cloud App button. The Setup wizard displays.

Step 14

Click Next. The Activate section displays.

Step 15

Paste the Activation Token that you copied, earlier, and the App Launch URL.

Step 16

Click Activate App. The App activation successful message displays.

Step 17

Close the browser window to navigate back to the Partner Dashboard section.

Step 18

Click the App Activation Sandbox.

Step 19

Click the Settings link on the App tile The activate partner app displays under the Partner Apps section.

Step 20

Click Activate to activate the app for that particular partner tenant ID.

Step 21

If required, click New Activation and complete the steps to activate the app for another partner tenant ID.

Step 22

If required, click Remove app to remove the partner app from the dashboard.

Step 1

The customer must copy the Activation Token (JWT) that was generated earlier during the application activation process (in the Cisco Spaces dashboard) and paste it in the partner’s single-tenant cloud application, where the Cisco Spaces connection setup must be configured.

eyJ0eXAiOiJKV1QiLC<XXXXXXXXXXXXXXXXXXXX>SIsImFjdGl2YXRpb25SZWZJZCI6IjBEO
DVBMTQ0QTM0RTRDQ0NBQzFERjkwQzFFNzc0OTQzIiwiY3VzdG9tZXIiOiJUcmlndWUiLCJleHBpcmVzSW4
iOjE1NjE3MDMxMzQyNzEsInRlbmFudElkIjo0MjAsImJhc2VVcmwiOiJodHRwczovL3BhcnRuZXJzLmRld
i1kbmFzcGFjZXMuaW8iLCJwYXJ0bmVyVGVuYW50SWQiOiIwRDg1QTE0NEEzNEU0Q0NDQUMxREY5MEMxRTc3
NDk0MyIsImlhdCI6MTU2MTY5OTUzNCwiZXhwIjoxNTYxNzAzMTM0fQ.n6TenjTHdBw5VHLHO_rk6OpgR8Q0
waU1ynovI_qWOgzcuNw2tqatXTNq6vTOo5vRzAtGRu4zYz34Y33NYA-zoQaTx3krb4fKr8DSmRcQ4xCFrI0
3ZkaZTtfi7uGrd-7TkOfFqPQgsZMLW7_IoYMFhpEunOu3gvijxQ00UYIQhgo

The decoded Activation Token would be similar to the below sample:
{

"appId": "app-31688AFCCAD44F4E9EE7C0CF7DFC993E",

"version": "v1",

"activationRefId": "568850F2CF5A466F8BBA5C895863EE60",

"customer": "Trigue",

"expiresIn": 1559201374033,

"tenantId": 420,

"baseUrl": "https://partners.dnaspaces.io",

"partnerTenantId": "0D85A144A34E4CCCAC1DF90C1E774943",

"iat": 1559201074,

"exp": 1559201374

}

Step 2

The Partner’s single-tenant cloud application must validate the Activation Token by following the below steps:

Step 3

If the token is valid, the partner single-tenant cloud application should invoke the Cisco Spaces App activation API (which returns the API key) to activate the App for the Customer.

App Activation API Endpoint: <base-url>/client/v1/partner/activateSingleTenantCloudApp 
Method: POST 
Content-Type: application/json
Authorization: Bearer <The generated Activation Token>
JSON Payload   
{    
"appId": "<appId extracted from activation token>",
"activationRefId": "<activationRefId extracted from activation token>",
"appDashboardUrl": "<appDashboardUrl to be provided by customer during app activation>"
}

Step 4

Use the apiKey from the response to invoke the partner APIs to receive the events data.

Step 1

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

Step 2

Click the Create New App tile.

Step 3

Click the Create New App tile under the Partner Apps.

Step 4

Select the On-Prem option.

Step 5

Click Create.

Step 6

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 your App screenshots, if needed.

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

Step 7

Click on the Use Cases tab.

Step 8

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 9

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

4. Under the APP Launch Configuration section, you can choose to check the App Launch Link option and provide the App Launch URL or choose the Launch Instructions Notes option and enter the relevant information in the App Launch Instructions Notes window

Step 10

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 11

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.

     Attention

     The Device Entry event is deprecated and is now replaced by the Device Presence event.

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

     Attention

     The Device Exit event is deprecated and is now replaced by the Device Presence event.

   • 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.

     Attention

     The TelePresence event is deprecated and is now replaced by the WebEx Telemetry event which is the enhanced version of the Telepresence 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.

   • WebEx Telemetry: This event is sent when there is telemetry from WebEx devices at the location.

     Note	You need a Cisco Spaces ACT license to utilize this event.

   • Device Association: This event is sent when a device gets connected at a specified location. Device details include device ID, location details, SSID, and other information associated with the user.

   Note

   For more information, go to https://developer.cisco.com/docs/cisco-spaces-firehose/api/. 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 12

Under the Integration Details tab, select the desired Integration Types:

1. In the Pull Channels section, choose among the following options:

   • HTTP: Sends pull channel event details over a streaming HTTP connection.

   • gRPC: Sends pull channel event details over a streaming gRPC call.

   • Websocket: Sends pull channel event details over a streaming Websocket connection.

   Note	For details, go to https://developer.cisco.com/docs/cisco-spaces-firehose/pull-channels/.

Step 13

Click Create to create the App.

Step 1

Log in to the Cisco Spaces - Partner Dashboard.

Step 2

Click on the App Activation Sandbox tile.

Step 3

Click the Get Partner Apps tile under the EXTEND section.

Step 4

Click on the desired app to view the associated details.

Step 5

Click Activate App.

Step 6

Depending on whether you have an account with the Partner, choose the appropriate option under Sign Up & Onboarding and click Continue.

Step 7

Click Accept Permission to continue.

Step 8

Select the locations for which you wish to enable and activate this app in order to receive the Event data and click Next.

Step 9

Select the groups you wish to enable for this app and click Next.

Step 10

Under the Generate App Activation Token section, click Generate to obtain the Activation (JWT) Token.

Step 11

Click Copy Token to copy the displayed Activation Token.

Step 12

Follow the on-screen instructions, in the Activation Instructions section, to activate the app.

Step 13

Click the Activate On Premise App button. The Setup wizard displays.

Step 14

Click Next. The Activate section displays.

Step 15

Paste the Activation Token that you copied, earlier.

Step 16

Click Activate App. The App activation successful message displays.

Step 17

Close the browser window to navigate back to the Partner Dashboard section.

Step 18

Click the App Activation Sandbox.

Step 19

Click the Settings link on the App tile The activate partner app displays under the Partner Apps section.

Step 20

Click Activate to activate the app for that particular partner tenant ID.

Step 21

If required, click New Activation and complete the steps to activate the app for another partner tenant ID.

Step 22

If required, click Remove app to remove the partner app from the dashboard.

Step 1

The Customer must copy the Activation Token (JWT) that was generated earlier during the application activation process (in the Cisco Spaces dashboard) and paste it in the Partner’s On-Prem application, where the Cisco Spaces connection setup must be configured.

eyJ0eXAiOiJKV1QiLC<XXXXXXXXXXXXXXXXXXXX>SIsImFjdGl2YXRpb25SZWZJZCI6IjBEO
DVBMTQ0QTM0RTRDQ0NBQzFERjkwQzFFNzc0OTQzIiwiY3VzdG9tZXIiOiJUcmlndWUiLCJleHBpcmVzSW4
iOjE1NjE3MDMxMzQyNzEsInRlbmFudElkIjo0MjAsImJhc2VVcmwiOiJodHRwczovL3BhcnRuZXJzLmRld
i1kbmFzcGFjZXMuaW8iLCJwYXJ0bmVyVGVuYW50SWQiOiIwRDg1QTE0NEEzNEU0Q0NDQUMxREY5MEMxRTc3
NDk0MyIsImlhdCI6MTU2MTY5OTUzNCwiZXhwIjoxNTYxNzAzMTM0fQ.n6TenjTHdBw5VHLHO_rk6OpgR8Q0
waU1ynovI_qWOgzcuNw2tqatXTNq6vTOo5vRzAtGRu4zYz34Y33NYA-zoQaTx3krb4fKr8DSmRcQ4xCFrI0
3ZkaZTtfi7uGrd-7TkOfFqPQgsZMLW7_IoYMFhpEunOu3gvijxQ00UYIQhgo

The decoded Activation Token would be similar to the below sample:
{

"appId": "app-31688AFCCAD44F4E9EE7C0CF7DFC993E",

"version": "v1",

"activationRefId": "568850F2CF5A466F8BBA5C895863EE60",

"customer": "Trigue",

"expiresIn": 1559201374033,

"tenantId": 420,

"baseUrl": "https://partners.dnaspaces.io",

"partnerTenantId": "0D85A144A34E4CCCAC1DF90C1E774943",

"iat": 1559201074,

"exp": 1559201374

}

Step 2

The Partner’s On-Prem application must validate the Activation Token by following the below steps:

Step 3

If the token is valid, the Partner On-Prem application should invoke the Cisco Spaces App activation API (which returns the API key) to activate the App for the Customer.

App Activation API Endpoint: <base-url>/client/v1/partner/activateOnPremiseApp 
Method: POST 
Content-Type: application/json
Authorization: Bearer <The generated Activation Token>
JSON Payload   
{    
"appId": "<appId extracted from activation token>",
"activationRefId": "<activationRefId extracted from activation token>"
"instanceName": "<Optional parameter, which indicates the location name>" 
}

Step 4

Use the apiKey from the response to invoke the partner APIs to receive the events data.