Cisco Smart+Connected Personalized Spaces Installation Guide

Configuring the Smart+Connected PS

This chapter describes how to configure locations, devices, room types, and adapters in the Cisco Smart+Connected Personalized Spaces (Smart+Connected PS) application through the Cisco Service Delivery Platform (SDP) interface. It also describes how to modify the branding images for the Smart+Connected PS application.

•Configuring Locations

•Configuring Devices

•Configuring Room Types

•Configuring Adapters

•Assigning Roles (groups) to the Application User

•Customizing the Branding Images

Configuring Locations

You need to configure locations from where the users can search for workspaces in Smart+Connected PS. Because the Smart+Connected PS application depends on SDP for location management, you need to access the Location Management module from the web interface of the SDP application.

To access the SDP web application, you need the DNS hostname or the IP addess of the SDP web portal and the port number on which the SDP is configured. The default credentials are superadmin/superadmin. If the default credentials have been updated, then you require the updated credentials.

For detailed information on configuring locations, see the Cisco Service Delivery Platform User Guide.

•Adding Locations

•Editing a Location

•Deleting a Location

Adding Locations

The Smart+Connected PS is used to reserve locations, that are identified as workspaces. When the word `workspace' is used in context of the Smart+Connected PS application, we are referring to location types, such as cubicles and offices.

You need to add locations to the Location Hierarchy tree in the following recommended hierarchical order: Location>Country>State>City>Campus>Floor>Wing>Cubicles. For example,
Cisco, India, Karnataka, Bangalore, Cessna Park, Floor1, Leftwing, Cubicle 15.

To add a new location to the location hierarchy, perform the following steps:

Step 1 Log in to the SDP application.

Step 2 Click the Locations tab.

The Locations page appears. The left pane displays the location hierarchy, and the right pane displays the main content area.

Step 3 Select a location for which you want to add the child location in one of the following ways:

a. Searching for a location:

1. Click in the shortcut tools.

2. In the Search field, enter a location keyword, and click .

The Search Results page appears with the location details.You can select the location for which you want to add the child location.

b. Expanding location hierarchy:

1. Click before a parent location.

If the is not displayed before a parent location, the location does not have any child location.

2. Click a location for which you want to add the child location.

Alternatively, click (Expand Immediate Child Nodes of Selection tool), and click a location for which you want to add the child location.

The following details are displayed for the selected location in the Location Details area:

•Location Type— Type of location under which the selected location has been categorized.

•Location Name—Name of the selected location.

•Parent Location—Parent of the selected location.

•Any custom property that has been setup for the location type.

Step 4 In the main content area, click .

The Add Location page appears. The Parent Location field displays the selected parent location for which you want to add the child location.

Step 5 Enter the following details:

•Location Type—From the Location Type drop-down list, choose the type of the location under which the selected location has to be categorized.

•Location Name— Enter the name of the location. The location name can be alpha-numeric, and you can use a maximum of 500 characters.

Step 6 Click Save to save the location details. The newly added location is displayed in the location hierarchy.

Editing a Location

After adding a location to the location hierarchy, you can modify the location name, property definition, and description.

To modify the existing location details, perform the following steps:

Step 1 On the Locations page, select a location for which you want to modify the location details in one of the following ways:

For more information on how to select a location, perform Step 1 through Step 3 in Adding Locations.

The following details are displayed for the selected location in the Location Details area:

•Location Type— Type of location under which the selected location has been categorized.

•Location Name— Name of the selected location.

•Parent Location—Parent of the selected location.

Step 2 In the right pane, click .

The Edit Location page appears. The Parent Location field displays the selected parent location. The Location Type drop-down list displays the type of the selected location.

Step 3 Modify the following fields as necessary:

•Location Name— Name of the selected location. The location name can be alpha-numeric, and you can use a maximum of 500 characters.

•Edit Location Properties—Property definitions that you defined for the location type during installation of the SDP application. For more information, see the sections "Defining Location Properties" and "Creating Custom Location Types" in the Cisco Service Delivery Platform Installation Guide.

Step 4 Click Save to save the location details.

The modified details are updated and appear in the location hierarchy.

Deleting a Location

To delete a location, perform the following steps:

Step 1 On the Locations page, select a location that you want to delete.

For more information on how to select a location, perform Step 1 through Step 3 in Adding Locations.

The following details are displayed for the selected location in the Location Details area:

•Location Type— Type of location under which the selected location has been categorized.

•Location Name— Name of the selected location.

•Parent Location— Parent of the selected location.

Step 2 In the right pane, click .

After a location is deleted, all the child locations, defined property definitions, and the role and device associations for the location are automatically removed from the SDP application.

Configuring Devices

To avail building system services such as light settings, blinds, dimmer, and air conditioner for locations through the Smart+Connecte PS application, you must configure devices. You must use the SDP interface to access the Device Management module.

•Adding Device Types

•Adding a Device

•Deleting a Devices

Adding Device Types

Device type definitions for some device types (such as light settings, dimmer, and blind) are added as a part of the SDP seed data. For all Smart+Connected PS needed device type definitions (such as Cisco IP Phone, DMP, and Extension mobility), you need to run additional SQL statements. These scripts are to be run against the schema created earlier.

•Adding Device Types in the Oracle Database

•Adding Device Types in the PostgreSQL Database

Adding Device Types in the Oracle Database

To add device types, run the following scripts using any SQL tool:

•SSP_DEVICE_TYPE

--SSP_DEVICE TYPE inserts

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) 

values (44,44,1,'Generic','superadmin',sysdate,'superadmin',sysdate,0);

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) 

values (46,46,1,'Generic','superadmin',sysdate,'superadmin',sysdate,0);

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) 

values (49,49,1,'Generic','superadmin',sysdate,'superadmin',sysdate,0);

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) values 
(50,50,1,'Generic','superadmin',sysdate,'superadmin',sysdate,0);

Recreate sequence with updated start value:

DROP SEQUENCE SSP_DM_PROP_DEF_ID_SEQ;

CREATE SEQUENCE SSP_DM_PROP_DEF_ID_SEQ INCREMENT BY 1 START WITH 10026 MAXVALUE 
999999999999999999999999999 MINVALUE 0 NOCACHE;

•SSP_DM_PROPERTY_DEFINITION

–Extension Mobility properties:

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,44,'mobilityaddress',1,0,'0',null,null,null,100,'0
','1','0','0',1,'superadmin',sysdate,'superadmin',sysdate,44,0);

–IP Phone properties:

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,46,'IP_Port',1,0,'0',null,null,null,100,'0','1','0
','0',1,'superadmin',sysdate,'superadmin',sysdate,46,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,46,'IP_PortCount',1,0,'0',null,null,null,100,'0','
1','0','0',1,'superadmin',sysdate,'superadmin',sysdate,46,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,46,'IP_MACADDRESS',1,0,'0',null,null,null,100,'0',
'1','0','0',1,'superadmin',sysdate,'superadmin',sysdate,46,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,46,'Application_UserName',1,0,'0',null,null,null,1
00,'0','1','0','0',1,'superadmin',sysdate,'superadmin',sysdate,46,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,46,'Application_Password',1,0,'0',null,null,null,1
00,'0','1','0','0',1,'superadmin',sysdate,'superadmin',sysdate,46,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,46,'Audio_Loop',1,0,'0',null,null,null,100,'0','1'
,'0','0',1,'superadmin',sysdate,'superadmin',sysdate,46,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,46,'Audio_Timetoplay',1,0,'0',null,null,null,100,'
0','1','0','0',1,'superadmin',sysdate,'superadmin',sysdate,46,0);

–DMP Properties:

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,49,'TOUCH',1,0,null,null,null,null,0,'0','1','0','
0',1,'superadmin',sysdate,'superadmin',sysdate,49,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,49,'URL',1,0,null,null,null,null,0,'0','1','0','0'
,2,'superadmin',sysdate,'superadmin',sysdate,49,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,49,'Password',1,0,null,null,null,null,0,'0','1','0
','0',3,'superadmin',sysdate,'superadmin',sysdate,49,0);

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(SSP_DM_PROP_DEF_ID_SEQ.nextval,49,'Username',1,0,null,null,null,null,0,'0','1','0
','0',4,'superadmin',sysdate,'superadmin',sysdate,49,0);

Commit;

–Interactive Experience Client (IEC) Properties:

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(10038,51,'MACADDRESS',1,0,null,null,null,null,0,'0','1','0','0',4,'superadmin',sy
sdate,'superadmin',sysdate,10001,0);

Adding Device Types in the PostgreSQL Database

To add device types, run the following scripts using the pgAdmin tool:

•SSP_DEVICE_TYPE

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) values 
(10000,44,1,'Generic','superadmin',CURRENT_DATE,'superadmin',CURRENT_DATE,0);

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) values 
(10001,46,1,'Generic','superadmin',CURRENT_DATE,'superadmin',CURRENT_DATE,0);

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) values 
(10003,45,1,'Generic','superadmin',CURRENT_DATE,'superadmin',CURRENT_DATE,0);

INSERT INTO ssp_device_type 
(device_type_id,device_type_master_id,manufacturer_id,model,created_by,created_dt,upda
ted_by,updated_dt,tenant_id) VALUES 
(10002,49,1,'dmp','superadmin',CURRENT_DATE,'superadmin',CURRENT_DATE,0);

Insert into SSP_DEVICE_TYPE 
(DEVICE_TYPE_ID,DEVICE_TYPE_MASTER_ID,MANUFACTURER_ID,MODEL,CREATED_BY,CREATED_DT,UPDA
TED_BY,UPDATED_DT,TENANT_ID) values 
(50,50,1,'Generic','superadmin',CURRENT_DATE,'superadmin',CURRENT_DATE,0);

Recreate sequence with updated start value:

DROP SEQUENCE SSP_DM_PROP_DEF_ID_SEQ;

CREATE SEQUENCE SSP_DM_PROP_DEF_ID_SEQ START WITH 10026 MAXVALUE 9223372036854775807 
MINVALUE 0 NO CYCLE;

•SSP_DM_PROPERTY_DEFINITION

–Extension Mobility properties:

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10000,44,'mobilityaddress',1,0,null,'',null,null,0,'0','1','0','0',1,'superadmin'
,CURRENT_DATE,'superadmin',CURRENT_DATE,10000,0);

–IP Phone properties:

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10001,46,'IP_MACADDRESS',1,0,null,'',null,null,0,'0','1','0','0',1,'superadmin',C
URRENT_DATE,'superadmin',CURRENT_DATE,10001,0);

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10002,46,'Application_Password',1,0,null,'',null,null,0,'0','1','0','0',2,'supera
dmin',CURRENT_DATE,'superadmin',CURRENT_DATE,10001,0);

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10003,46,'Audio_Loop',1,0,null,'',null,null,0,'0','1','0','0',3,'superadmin',CURR
ENT_DATE,'superadmin',CURRENT_DATE,10001,0);

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10004,46,'Application_UserName',1,0,null,'',null,null,0,'0','1','0','0',4,'supera
dmin',CURRENT_DATE,'superadmin',CURRENT_DATE,10001,0);

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10005,46,'Audio_Timetoplay',1,0,null,'',null,null,0,'0','1','0','0',5,'superadmin
',CURRENT_DATE,'superadmin',CURRENT_DATE,10001,0);

–DMP properties:

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10026,49,'TOUCH',1,0,null,null,null,null,0,'0','1','0','0',1,'superadmin',CURRENT
_DATE,'superadmin',CURRENT_DATE,10002,0);

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10027,49,'URL',1,0,null,null,null,null,0,'0','1','0','0',2,'superadmin',CURRENT_D
ATE,'superadmin',CURRENT_DATE,10002,0);

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10028,49,'Password',1,0,null,null,null,null,0,'0','1','0','0',3,'superadmin',CURR
ENT_DATE,'superadmin',CURRENT_DATE,10002,0);

INSERT INTO ssp_dm_property_definition 
(prop_def_id,prop_group_id,prop_name,prop_data_type_id,prop_constraint_id,prop_def
ault_value,prop_default_string,prop_default_number,prop_default_date,prop_size,req
uired_flag,application_flag,unique_id_flag,secure_flag,prop_order_num,created_by,c
reated_dt,updated_by,updated_dt,device_type_id,tenant_id) VALUES 
(10029,49,'Username',1,0,null,null,null,null,0,'0','1','0','0',4,'superadmin',CURR
ENT_DATE,'superadmin',CURRENT_DATE,10002,0);

–IEC Properties:

Insert into SSP_DM_PROPERTY_DEFINITION 
(PROP_DEF_ID,PROP_GROUP_ID,PROP_NAME,PROP_DATA_TYPE_ID,PROP_CONSTRAINT_ID,PROP_DEF
AULT_VALUE,PROP_DEFAULT_STRING,PROP_DEFAULT_NUMBER,PROP_DEFAULT_DATE,PROP_SIZE,REQ
UIRED_FLAG,APPLICATION_FLAG,UNIQUE_ID_FLAG,SECURE_FLAG,PROP_ORDER_NUM,CREATED_BY,C
REATED_DT,UPDATED_BY,UPDATED_DT,DEVICE_TYPE_ID,TENANT_ID) values 
(10038,51,'MACADDRESS',1,0,null,null,null,null,0,'0','1','0','0',4,'superadmin',CU
RRENT_DATE,'superadmin',CURRENT_DATE,10001,0);

Adding a Device

The following devices are supported by the Smart+Connected PS application:

•Cisco IP Phones

•Blinds

•Lights

•Dimmer

•DMP

•Extension Mobility

•VAV

•IEC

You can add any of these devices to the selected location in the Location Hierarchy tree if they are available at the location. Before adding devices, ensure that the device types are created. You can create a new device type that is supported by SDP by utilizing the device type properties that are shipped along with SDP.

Table 4-1 lists the device properties of the devices that have been added by the Smart+Connected PS scripts.

To add a device, perform the following steps:

Step 1 On the SDP home page, click Devices.

The List of Devices page appears.

Step 2 Select a location in the left pane.

Step 3 Click Add a Device in the right pane.

The Add Device page appears.

Step 4 Select a Device Category.

Step 5 Select the Manufacturer.

Step 6 Select the Model.

Properties of the selected device are displayed when the model is selected in the Add Device Properties box.

Step 7 To select the properties for the device, perform the following steps:

a. Select the property of the device in the Add Device Properties box.

The value box is displayed on the right side.

b. Select or enter the corresponding value.

c. Click Save.

Step 8 Type the name of the device in the Device Name field.

Step 9 Click Save.

The new device is added to the selected location.

Deleting a Devices

To delete a device, perform the following steps:

Step 1 In the SDP home page, click the Devices tab.

Step 2 To view devices in child locations, select the Show devices from child locations check box.

Step 3 In the Location Hierarchy tree, select the location from where you want to delete an associated device. The list of associated devices appear on the right, if available.

Step 4 Select the check box corresponding to the device that you want to delete, and click Delete.

Configuring Room Types

By default, the Office and Cubicle location types are configured as workspaces in the Smart+Connected PS solution. If any other location type is also to be treated as workspaces, then the necessary configuration needs to be done in SSP_PVO_LOCATION_TYPE table.

Table 4-2 displays the LOC_TYPE_ID, which is the location type ID mapping in the SSP_LOCATION_TYPE table that is available in SDP.

Configuring Adapters

•Configuring Adapter Properties

•Configuring the Adapters to a Location

Configuring Adapter Properties

You need to configure the adapter properties for available adapters. The adapter definitions are inserted in the Smart+Connected PS database, when you execute the SDP and Smart+Connected PS database scripts. Adapter configuration needs to be performed in the database by inserting data into the SDP_ADAPTER_PROPERTIES table.

Table 4-3 provides information on the properties of the adapters. These can be used to come up with the SQL scripts that must be run against the database. All these properties are mandatory.

Configuring the Adapters to a Location

The adapters are configured to the specific location by mapping the adapter instance id with the corresponding location in the SDP_ADAPTER_LOCATION_LINK table.

When an adapter is associated to a location, the adapter instances are automatically applied to all the child locations for that location.

See the "Sample Adapter Configurations" section for a sample configuration for the ObixBean mapped to the location ID 10011.

Sample Adapter Configurations

SDP_ADAPTER_DEFN table

This configuration is part of the seed data.

Table 4-4 displays the adapter definition mapped to an adapter definition ID.

SDP_ADAPTER_INSTANCE

Table 4-5 displays the adapter definition ID mapped to an adapter instance ID

SDP_ADAPTER_LOCATION _LINK table

This table allows you to link the adapter instances with a specific location(s).

Table 4-6 displays the adapter instance ID configured to the preferred location

For more information on configuring adapters, refer to the Cisco Service Delivery Platform Installation Guide.

Note If you change values in these tables, then you must restart the application to enable the changes done.

Configuring Services in CUCM

The Smart+Connected PS services appear on the Cisco IP phone only after you configure the Smart+Connected PS URL on the CUCM. It is assumed that the Extension Mobility is enabled for the device and the end-user.Typically, these tasks must be performed by the CUCM Administrator.

To configure the services in the CUCM, perform the following steps:

Step 1 In the browser, enter the CUCM URL.

Step 2 Click Cisco Unified Communications Manager.

The Cisco Unified CM Administration home page appears.

Step 3 new

Step 4 Enter the CUCM administration username and password, and then click Login.

Step 5 Navigate to Device>Device Settings>Phone Services.

Step 6 Click Add New.

To add a new service, perform the following steps:

a. Enter the service name in the Service Name field. For example, SCPS service.

b. Enter the service description in the Service Description field.

c. Enter the service URL in the Service URL field. The format is as follows:

http://<IP Address>:<port number>/ipsapp/pvoipphone.ip

Where the IP Address of Smart+Connected PS server specifies the IP Address of server where the Smart+Connected PS application is running and the port number is the WebLogic server port.

d. From the Service Category drop-down list, choose XML Service.

e. From the Service Type drop-down list, choose Standard IP Phone Service.

f. Select the Enable checkbox.

Step 7 Click Save.

Step 8 Click Device>Phone. The Find and List Phones page appears.

Step 9 From the "Find Phone where" drop-down list, choose Device Name.

Step 10 Choose contains from the drop-down list adjacent to the "Find Phone where" drop-down list.

Step 11 Enter the MAC address of the Cisco IP phone for which you want to subscribe the service.

Step 12 Click Find.

Step 13 Select the Cisco IP phone. The Phone Configuration page appears.

Note Ensure that the Web Access drop-down list displays an enabled value.

Step 14 In the Related Links drop-down list, choose Subscribe/Unsubscribe Services, and then click Go.

Step 15 Select the service name that you have provided in Step a.

Step 16 Click Next.

Step 17 Click Subscribe.

Step 18 Click Reset in the Phone Configuration page. A device reset pop-up appears.

Step 19 Click Reset. The configured service name appears under the Services menu, in the Cisco IP Phone.

Step 20 Subscribe the "SCPS service" for the default Extension Mobility profile or the extension mobility profile of an individual user.

Step 21 Subscribe the "SCPS service" to the Extension Mobility logout profile (if enabled for IP phone).

Assigning Roles (groups) to the Application User

The Smart+Connected PS solution require an application user to be created in CUCM for the following reasons:

•To do an Extension Mobility login on the behalf of an user.

•To push the audio unicast and text messages to the Cisco IP phone.

The application user needs the following privileges minimally to allow the Smart+Connected PS solution to work properly:

•Standard CTI Enabled—This user group, which is required for all CTI applications, allows an application to connect to Cisco CallManager to access CTI functionality.

•Standard CTI Allow Control of All Devices—This user group allows an application to control or monitor any CTI-controllable device in the system.

•Standard EM Authentication Proxy rights -- This user group manages Cisco Extension Mobility authentication rights for application users that interact with Cisco Extension Mobility.

•Standard CCM Admin Users—This grants log-in rights to Cisco Unified Communications Manager Administration. A user with only the Standard CCM Admin Users role can access Cisco Unified Communications Manager Administration but cannot make any changes.

•Standard CCMADMIN Read only— This allows an administrator to view configuration in Cisco Unified Communications Manager Administration page

•Copy of Standard CCM Phone Administration which includes Service URL Page, User Web Page and Phone Services Subscribe.

•Copy of Standard Serviceability named as roles for Web Services which has only SOAP related services as read and write access.

To create and assign a role to an application user, perform the followin steps:

Step 1 In the browser, enter the URL to access the Call Manager application.

Step 2 Click Cisco Unified Communications Manager.

The Cisco Unified CM Administration home page appears.

Step 3 Enter the username and password and click Login.

Step 4 Navigate to User Management > Application User to create application users and assign roles to the application users.

Customizing the Branding Images

The branding images include the logo and the login screen. You can customize the Smart+Connected PS user interface by changing one or both of these images.

To customize the branding images, perform the following steps:

Step 1 Open the scps.war file using any archive utility.

Step 2 Navigate to the images directory and replace the login and the logo images.

Table 4-7 displays the specifications of the branding images.

Note Branding images that you replace must have the same name and resolution as per the specification provided in Table 4-7.

Note You must re-deploy the scps.war file to enable changes to the branding images.