Configuring ServiceNow Extensions

Overview

The integration between Cisco CloudCenter and ServiceNow is provided through a certified, scoped application, called Integration – Cisco CloudCenter, that is available for download from ServiceNow’s app store. This integration enables Cisco CloudCenter users to obtain manager approval for their deployment through ServiceNow, as well as add deployment information to the ServiceNow CMDB.

ServiceNow Version Support

  • ServiceNow Jakarta

  • ServiceNow Kingston

Cisco CloudCenter Version Support

Prerequisites

Verify the following requirements:

  1. That you have downloaded and installed Integration – Cisco CloudCenter, Version 2.2 from store.servicenow.com and ensure that the installation is functional.

  2. That the inbound port to access CloudCenter UI through ServiceNow is open.

Download the Integration Application

To download the integration application, follow this process.

  1. Go to the https://store.servicenow.com website.

  2. Search and select the Integration – Cisco CloudCenter application.

  3. Select Contact Seller to obtain approval to download the application.

  4. Once Cisco approves the application download, the ServiceNow admin will receive an email confirmation. In the email confirmation, click the link to Get the application.

Install the Integration Application

To install the integration application, follow this process.

  1. Once the integration application is approved, use the ServiceNow Filter Navigator and browse to System Applications > Applications > Downloads > Cisco CloudCenter - Integration.

  2. Click All versions.

  3. Select and install the appropriate version (v2.2).

Perform the ServiceNow Configuration

Base Configuration

Using the ServiceNow Filter Navigator, navigate to Cisco CloudCenter > Configuration > Base Configuration.  Configure the parameters as described in the table below.

As an alternative, you can also update these parameters by navigating to System Properties and performing a search for x_cqt_c3*.

Configure Parameters

Configure parameters as listed in the following table, and click Save.

Parameter

Description

Server URL

URL of the CloudCenter Instance, used for API calls.

Tenant Name field on the user record

Field reference on the User Record to identify the tenant to which a user belongs.

MID server name

Name of a pre-configured MID server. Optional.

Retry attempts on communication error

Number of retries to attempt upon any communication error with the CloudCenter instance.

Number of approval reminders after which request will be automatically cancelledThese two configurations only work if you have enabled the C3: Approval Workflow with Reminders setting. Default value is 2 days.

Number of days after which a reminder email is sent if approval is not given

Disable Untrusted SSL Certificates

This procedure is only required if the customer:

  • Is using self-signed CCM certificate for HTTPS encryption. 

  • Has problems authenticating the Owner API credentials.

  1. Using the ServiceNow Filter Navigator, type sys_properties.list and press Enter.  

  2. Update the following two properties.

    1. Search for a property called: com.glide.communications.trustmanager_trust_all and set the value to true.

    2. Search for a property called: com.glide.communications.httpclient.verify_hostname and set the value to false

Configure the API credentials

This step is required to establish communication from ServiceNow to Cisco CloudCenter.  Prior to completing this step, create a user in Cisco CloudCenter with admin credentials – if your environment requires an admin user.  The following CloudCenter settings are required:

  • Username 

  • API key

To configure the API credentials, follow this procedure.

  1. Using the ServiceNow Filter Navigator, navigate to Cisco CloudCenter > Configuration>Owner API Keys.  

  2. Add a new record. 

  3. Click Validate Credentials. Wait for a successful validation.

  4. Once successfully validated, click Submit.

Create an Integration User

In ServiceNow, create a user with an appropriate User ID, for example cloudcenter.integration. Note the User ID and password because this user is later used in Cisco CloudCenter setup process to communicate with ServiceNow. This user's settings should be similar to the settings identified in the following table.

FieldDescription
User ID

cloudcenter.integration – This is only an example!

First nameCloudCenter – This is only an example!
Last nameIntegration – This is only an example!
Passwordcisco-snow – This is only an example!
EmailNot required .
Web service access onlyCheck this box.
Internal Integration UserCheck this box.
Role Assignment

Add the cloudcenter.integration user to the x_cqt_c3_frame.admin role.

Create a Requester User

In ServiceNow, create a user with an appropriate User ID, for example cloudcenter.requester. This user's settings should be similar to the settings identified in the following table.

FieldDescription
User ID

cloudcenter.requester – This is only an example!

First nameCloudCenter – This is only an example!
Last nameRequester – This is only an example!
Passwordcloudcenter-requester  – This is only an example!
Emailcloudcenter.requester@yourdomain.com  (Required!)
Role Assignment

No roles are required for the cloudcenter.requester user.

Add the ServiceNow cloudcenter.requester user to the role x_cqt_c3_frame.consumer only if this user needs access to ServiceNow CMDB modules related to Cisco CloudCenter.

Manager Assignment

Assign a Manager permission to this user. Create a new ServiceNow user if required.

If a Manager permission is not assigned to this user, the deployment request record in ServiceNow won't be created and the default approval workflow will auto approve each request and no request record will be created in ServiceNow.

Notes:

  1. The Manager permission for the ServiceNow cloudcenter.requester user must also be added to the following two roles:

    • approver_user

    • x_cqt_c3_frame.consumer

  2. A corresponding user account for this user is also created in Cisco CloudCenter (see the Create a CloudCenter User section below) – The CloudCenter user information must be added to the User API Keys table in ServiceNow.

  3. Repeat this process for each CloudCenter user who logs into Cisco CloudCenter for deployments that require ServiceNow approval. 

    If you do not complete this step, even if the deployment is approved in ServiceNow, the response will not be accepted by Cisco CloudCenter and the deployment continues to remain in a pending state.

Perform the Cisco CloudCenter Configuration

Create an Extension

To configure an extension from the CloudCenter UI, follow this procedure.

  1. Navigate to Admin > Extensions and add a new extension or edit an existing extension for your ServiceNow integration.

  2. Add a New Extension and configure the settings as described in the following table.

    FieldDescription
    Extension TypeSelect ServiceNow from the drop-down list.
    Extension NameEnter a unique name for the extension.
    ServiceNow URL

    Enter the URL of the ServiceNow instance being integrated.

    Username

    Enter the User ID of the integration user created in ServiceNow.

    Password

    Enter the password of the integration user created in ServiceNow.


    If your connection is successful, you see the Connected status and the success message at the top of the UI.

Setup Approval Flows

Once the connection is established between CloudCenter and ServiceNow, enable the approval toggle switches for the desired workflows in the CloudCenter UI. 

In the following example, enabling the Initial Deployment will send deployment approval requests to ServiceNow. However, other actions taken by a user such as Stop or Terminate will not require an approval if they are not enabled in the following screenshot.

If the Initial Deployment toggle is not enabled, the deployment's default approval workflow will auto approve each request and no request record will be created in ServiceNow.

Setup CMDB Update

Enable the Send CMDB Update setting if your environment requires it.

By enabling this setting, you authorize the ServiceNow CMDB to be populated with the Cisco CloudCenter deployment information. The following CMDB tables are updated in ServiceNow:

  • Jobs (custom table part of this application)

  • Virtual Machines (out-of-box)

  • Network Adapters (out-of-box)

  • Storage Volumes (out-of-box)

  • IP Addresses (out-of-box)

Associate the ServiceNow Extension to a Deployment Environment

In Cisco CloudCenter, navigate to an existing Environment or create a new Environment. Using the drop-down, select an appropriate ServiceNow Extension to be used for this Deployment Environment.

When a ServiceNow extension is associated to a Deployment Environment, Cisco CloudCenter’s deployment approval toggle switch for this environment is automatically disabled.

Create a CloudCenter User

To ensure that the ServiceNow cloudcenter.requester user can access the CloudCenter UI, follow this procedure. 

  1. In Cisco CloudCenter, create a standard user called cloudcenter.requester.

  2. Ensure that this user is activated and has access to appropriate application profiles, clouds, environments, system tags and policies in your ServiceNow CloudCenter environment.

  3. Note down the username and API Key of this user – The information must be added to the User API Keys table in ServiceNow.

Add User API Keys in ServiceNow

To add the username and the API key for the cloudcenter.requester user in the User API Keys table in ServiceNow, follow this procedure.

  1. In ServiceNow, use the Filter Navigator to navigate to Cisco CloudCenter > Configuration > User API Keys.

  2. Create a new record using the following settings for cloudcenter.requester (this is only an example).

    FieldDecription
    API KeyThe API key of the user cloudcenter.requester from the CloudCenter platform.
    C3 User IDThe username of the user cloudcenter.requester from the CloudCenter platform.
    ServiceNow User is requiredThe user cloudcenter.requester should already created in ServiceNow.

Validate the Configuration

To validate the configuration, perform the following procedure.

  1. Log into Cisco CloudCenter as cloudcenter.requester@yourdomain.com.

  2. Select an Application Profile and initiate a deployment. 

    1. Select the Deployment Environment that is configured for ServiceNow approvals.  If the correct Deployment Environment was selected, you should see the Deployment Pending Approval popup.

  3. In ServiceNow, login with the user account that was setup as the manager for the ServiceNow user, cloudcenter.requester.

  4. In ServiceNow, navigate to My Approvals. You should see a new record with the state Requested.   Click on this record, leave a comment (optional) and approve the request.

  5. In ServiceNow, visually confirm that  the record state changed from Requested to Approved.

  6. In Cisco CloudCenter, check the Deployment state. The state should have changed from Pending Approval to In Progress.

  7. In Cisco CloudCenter, on the Deployment Details page, click on the View Action History link and review the details. You should see the ServiceNow user who approved the request and any comments that were added during the approval.

  8. Once the Application Profile is successfully deployed, the following CMDB modules in ServiceNow should be updated.

    • Jobs

    • Virtual Machines

    • Network Adapters

    • Storage Volumes

    • IP Addresses

Sample Approval Request Payload

The following sample lists a request payload for an approval flow:

{"approvalrequest":{
      "resourceType":"DEPLOYMENT",
      "resourceAction":"DEPLOY",
      "approvalToken":"C3Wi1BejvQTqBcfhI2wqEkRxH8l4SsHvrtmRiYjdmfWCJ54MoBY0IwTIPg2C",
      "approvalIdentifier":872,
      "approvalStatus":"PENDING",
      "deploymentDetails":{
         "initiatorEmailAddress":"initiator@cisco.com",
         "id":1529,
         "name":"kk_may23_3",
         "description":"",
         "jobStatus":"JobPending",
         "currentPredictiveMonthlyCost":32.12,
         "minPredictiveMonthlyCost":32.12,
         "maxPredictiveMonthlyCost":3212,
         "deploymentCost":null,
         "deploymentHours":null,
         "ownerEmailAddress":" initiator@cisco.com",
         "terminateProtection":false,
         "deploymentEnvironment":{
            "id":2,
            "name":"snowapproval"
         },
         "application":{
            "id":68,
            "name":"Centos7",
            "version":"1"
         },
         "ageExtendRequest":{
            "policyName":null,
            "policyId":null,
            "policyType":null,
            "policyLimit":null,
            "extensions":null
         },
         "childJobs":[
            {
               "id":1530,
               "name":"CentOS_1",
               "serviceName":"CentOS",
               "serviceCost":0,
               "cloudFamily":"Vmware",
               "numNodes":1,
               "tier":{
                  "id":69,
                  "name":"CentOS_1"
               },
               "currentPredictiveMonthlyCost":32.12,
               "minPredictiveMonthlyCost":32.12,
               "maxPredictiveMonthlyCost":3212,
               "instance":{
                  "id":1,
                  "type":"m1.small",
                  "name":"m1.small",
                  "hardwareSpec":{
                     "memorySize":1024,
                     "cpu":1,
                     "storageSize":0,
                     "storageCount":0
                  },
                  "description":null,
                  "costPerHour":0.044,
                  "costPerMonth":32.12
               },
               "costDetails":{
                  "nodeHours":null,
                  "billedNodeHours":0,
                  "cloudComputeCost":0,
                  "cloudStorageCost":0,
                  "appRunTimeCost":0,
                  "appServiceCost":0,
                  "nodeCostDetails":[

                  ]
               },
               "virtualMachines":[

               ]
            }
         ]
      },
      "vmDetails":null
   }
}

Sample CMDB Update Payload

The following sample lists a update payload for a CMDB flow that is initiated by Cisco CloudCenter:

{
   "id":"1529",
   "resource":"https://<ip_address>:8443/v2/jobs/1529",
   "name":"kk_may23_3",
   "description":"",
   "status":"JobRunning",
   "jobStatusMessage":"",
   "approvalRequestStatus":"",
   "approvalRequestAction":"",
   "startTime":"1527077346620",
   "endTime":"",
   "scheduleEndTime":"",
   "timeZone":"GMT+02:00",
   "favoriteCreationTime":"",
   "cloud":"VMware-DMZ",
   "cloudFamily":"Vmware",
   "cloudDisplayName":"VMware DMZ",
   "deploymentEnvironment":{
      "id":"2",
      "resource":"https://<ip_address>:8443/v1/environments/2"
   },
   "application":{
      "id":"68",
      "version":"1",
      "resource":"https://<ip_address>:8443/v1/apps/68?version=1"
   },
   "actions":[
      "UPDATE_TAGS",
      "MARK_FAVORITE",
      "SUSPEND",
      "TERMINATE",
      "UPGRADE",
      "PROMOTE",
      "MIGRATE",
      "EXPORT_TO_REPO",
      "ON_TERMINATE_PROTECTION"
   ],
   "deploymentEntity":{
      "type":"DEPLOYMENT",
      "id":"757",
      "name":"kk_may23_3",
      "attributes":{
         "status":"Deployed",
         "health":"Healthy",
         "ownerId":"2",
         "containsExternalServices":false
      }
   },
   "terminateProtection":false,
   "hidden":false,
   "favorite":false,
   "benchmark":false,
   "owner":true,
   "ownerEmailAddress":"admin@cliqrtech.com",
   "customActions":[

   ],
   "parentJob":{
      "id":"",
      "resource":""
   },
   "lastUpdatedTime":"1527077478874",
   "bareMetalMachines":[

   ],
   "accessLink":"http://<ip_address>",
   "parameters":{
      "cloudParams":{
         "cloudRegionId":1,
         "instance":"",
         "instanceName":"",
         "nics":[

         ],
         "volumes":[

         ],
         "provisionBareMetal":false,
         "deploymentIsolationTag":"",
         "autoCloudAndInstanceSelection":false,
         "selectionCriteria":"NONE",
         "accountId":"1",
         "rootVolumeSize":"",
         "storage":"",
         "networkTypeName":"",
         "containerVolumes":[

         ],
         "cloudProperties":[
            "<cloud properties array>"
         ]
      },
      "appParams":[
         "<app parameters array>"
      ],
      "globalParams":[
         "<global parameters array>"
      ],
      "tierParams":[

      ],
      "envParams":[
         "<environment parameters array>"
      ],
      "nodeParams":[

      ]
   },
   "virtualMachines":[

   ],
   "externalServiceInstance":null,
   "approvalRequest":{
      "currentDeploymentEnvironment":{
         "id":"2",
         "resource":"https://<ip_address>:8443/v1/environments/2"
      },
      "fromDeploymentEnvironment":{
         "id":"",
         "resource":""
      },
      "initiatingUser":{
         "id":"",
         "resource":"https://<ip_address>:8443/v1/users/2"
      },
      "lastApprovalInitiatingUser":{
         "id":"",
         "resource":"https://<ip_address>:8443/v1/users/2"
      },
      "approvingUser":{
         "id":"",
         "resource":""
      },
      "lastApprovalAction":"Deployment",
      "approvalCategory":"SERVICE_NOW",
      "requestTime":"1527077336000",
      "approvalTime":"",
      "status":"APPROVED",
      "message":""
   },
   "childJobs":[
      {
         "id":"1530",
         "resource":"https://<ip_address>:8443/v2/jobs/1530",
         "dependencies":[

         ]
      }
   ],
   "tags":[
      {
         "id":"1",
         "resource":"https://<ip_address>:8443/v1/systemTags/1"
      },
      {
         "id":"2",
         "resource":"https://<ip_address>:8443/v1/systemTags/2"
      }
   ],
   "policyIds":[

   ],
   "securityProfiles":[

   ],
   "costDetails":{
      "nodeHours":0,
      "billedNodeHours":0,
      "cloudComputeCost":0,
      "cloudStorageCost":0,
      "appRunTimeCost":0,
      "appServiceCost":0,
      "nodeCostDetails":[

      ]
   },
   "windowsJob":false,
   "scalable":false,
   "metadata":[
      {
         "namespace":"",
         "name":"TAG_TWO",
         "value":"USER_DEFINED_TAG",
         "editable":false,
         "required":false
      },
      {
         "namespace":"",
         "name":"TAG_ONE",
         "value":"USER_DEFINED_TAG",
         "editable":false,
         "required":false
      },
      {
         "namespace":"",
         "name":"Name",
         "value":"kk_may23_3",
         "editable":false,
         "required":true
      }
   ]
}

Sample CMDB Payload for Each Child Job

The following sample lists a update payload for a CMDB child job workflow:

{
   "id":"1530",
   "resource":"https://<ip_address>/v2/jobs/1530?includeNodeDetails=true&includeNodeCostDetails=true&includeTaskDetails=true",
   "name":"CentOS_1",
   "description":"",
   "status":"JobRunning",
   "jobStatusMessage":"",
   "approvalRequestStatus":"",
   "approvalRequestAction":"",
   "startTime":"1527077346897",
   "endTime":"",
   "scheduleEndTime":"",
   "timeZone":"GMT+02:00",
   "favoriteCreationTime":"",
   "cloud":"VMware-DMZ",
   "cloudFamily":"Vmware",
   "cloudDisplayName":"VMware DMZ",
   "deploymentEnvironment":{
      "id":"",
      "resource":""
   },
   "application":{
      "id":"69",
      "version":"1",
      "resource":"https://<ip_address>/v1/apps/69?version=1"
   },
   "actions":[
      "SCALE_UP",
      "SCALE_DOWN",
      "UPDATE_TAGS"
   ],
   "terminateProtection":false,
   "hidden":false,
   "favorite":false,
   "benchmark":false,
   "owner":true,
   "ownerEmailAddress":"admin@cliqrtech.com",
   "customActions":[

   ],
   "parentJob":{
      "id":"1529",
      "resource":"https://<ip_address>/v2/jobs/1529"
   },
   "lastUpdatedTime":"1527077478796",
   "bareMetalMachines":[

   ],
   "accessLink":null,
   "parameters":{
      "cloudParams":{
         "cloudRegionId":1,
         "instance":"m1.small",
         "instanceName":"m1.small",
         "nics":[
            {
               "id":"VM Network",
               "type":"NETWORK",
               "allocationMode":"DHCP",
               "order":1,
               "allocatePublicIp":false,
               "assignIpv6Address":false,
               "properties":[

               ],
               "netId":null
            }
         ],
         "volumes":[

         ],
         "provisionBareMetal":false,
         "deploymentIsolationTag":"",
         "autoCloudAndInstanceSelection":false,
         "selectionCriteria":"NONE",
         "accountId":"1",
         "rootVolumeSize":"",
         "storage":"",
         "networkTypeName":"",
         "containerVolumes":[

         ],
         "cloudProperties":[
            "<cloud properties array>"
         ]
      },
      "appParams":[
         "<parameters array>"
      ],
      "globalParams":[
         "<global parameters array>"
      ],
      "tierParams":[
         "<deployment parameters array>"
      ],
      "envParams":[
         "<environment parameters array>"
      ],
      "nodeParams":[
         {
            "name":"x",
            "value":"100"
         },
         {
            "name":"y",
            "value":"250"
         }
      ]
   },
   "virtualMachines":[
      {
         "id":"4235d810-4c2e-bcc7-12c7-c2967a4743e0",
         "virtualMachineId":"688",
         "privateIpAddr":"<ip_address>",
         "publicIpAddr":"<ip_address>",
         "hostName":"cqjw-e0670ad1f",
         "zone":"Rack-N2-DC",
         "status":"NodeReady",
         "startTime":"1527077362428",
         "endTime":"",
         "agentVersion":"V-4.9.0-2018-04-09T16:03:04Z",
         "nodeNetworkInterfaces":[
            {
               "privateIpAddr":"<ip_address>;fe80::264:ede3:735d:72e3;fe80::7987:a6c7:7d8:9893;fe80::d69:1f63:59ae:1836",
               "publicIpAddr":"<ip_address>",
               "networkDisplayName":"VM Network",
               "interfaceIndex":0
            },
            {
               "privateIpAddr":"172.17.0.1",
               "publicIpAddr":null,
               "networkDisplayName":null,
               "interfaceIndex":1
            }
         ],
         "costDetails":null,
         "nodeSpecs":{
            "numberOfCpus":1,
            "memorySize":1024,
            "storageSize":0,
            "osType":"Linux",
            "memoryUnit":"MB",
            "storageUnit":"GB"
         },
         "volumes":[
            {
               "id":"",
               "name":"",
               "size":0,
               "type":null,
               "iops":0,
               "bootable":true
            },
            {
               "id":"724-2001",
               "name":"Hard disk 2",
               "size":1,
               "type":null,
               "iops":0,
               "bootable":false
            }
         ],
         "taskDetails":[

         ],
         "properties":[

         ]
      }
   ],
   "externalServiceInstance":null,
   "approvalRequest":{
      "currentDeploymentEnvironment":{
         "id":"",
         "resource":""
      },
      "fromDeploymentEnvironment":{
         "id":"",
         "resource":""
      },
      "initiatingUser":{
         "id":"",
         "resource":""
      },
      "lastApprovalInitiatingUser":{
         "id":"",
         "resource":null
      },
      "approvingUser":{
         "id":"",
         "resource":""
      },
      "lastApprovalAction":"",
      "approvalCategory":"",
      "requestTime":"",
      "approvalTime":"",
      "status":"AUTO_APPROVED",
      "message":""
   },
   "childJobs":[

   ],
   "tags":[

   ],
   "policyIds":[

   ],
   "securityProfiles":[

   ],
   "costDetails":{
      "nodeHours":0,
      "billedNodeHours":0,
      "cloudComputeCost":0,
      "cloudStorageCost":0,
      "appRunTimeCost":0,
      "appServiceCost":0,
      "nodeCostDetails":[

      ]
   },
   "windowsJob":false,
   "scalable":true,
   "metadata":[

   ]
}

CloudCenter Actions that trigger ServiceNow CMDB Updates

The following table lists actions that can be triggered after CMDB updates.

CMDB UpdateActions or States
A completed job

If you take one of the following actions:

  • DEPLOY
  • SUSPEND
  • RESUME
  • TERMINATE
  • SCALE_UP
  • SCALE_DOWN
A Managed VM

If you take one of the following actions:

  • TERMINATE
  • START (REBOOT)
  • STOP (POWER-OFF)
  • SYNC VM INFORMATION
  • ATTACH/DETACH VOLUMES
  • CREATE SNAPSHOT
  • RESIZE INSTANCE TYPE
A Managed VM

Is in a NodeNotReachable state.

A JobIs in an Error state.

The Workflows

The following image displays an overview of the integration.

The following image displays the CMDB update workflow:

Optional ServiceNow Update Set

The Cisco provided ServiceNow Update Set, cloudcenter-release-4.9.0-ServiceNow_UI_Update_Setv2.2.xml, is an optional component of the Cisco CloudCenter and ServiceNow integration. It adds Cisco CloudCenter as a category into the ServiceNow Service Portal and provides the ability for a ServiceNow user to use the Service Portal to gain limited access to Cisco CloudCenter through an iFrame.

Prerequisites

To install the optional Update Set component in Cisco CloudCenter and ServiceNow integration, verify the following prerequisites:

  1. Integration – Cisco CloudCenter, version 2.2 (downloaded from store.servicenow.com) must already be installed and functional.

  2. The inbound port to access the CloudCenter UI through ServiceNow must be open.

Download the Update Set

To download the update set, follow this procedure.

  1. Download the following required file for this optional component from software.cisco.com. Be aware that the file name uses the following syntax:

    cloudcenter-release-<release.tag>-ServiceNow_UI_Update_Set_<version .number>.tar
    
    #For example: cloudcenter-release-4.9.0-ServiceNow_UI_Update_Setv2.2.zip
  2. Unzip the file to a local folder.  It should contain one .xml file called Update Set.

Configure ServiceNow

To configure ServiceNow, follow this procedure.

  1. Using the ServiceNow Filter Navigator perform one of the following actions:

    • Navigate to Cisco CloudCenter > Configuration > Base Configuration.  Configure the parameters as described in the table below.
      OR

    • Update the following parameters by navigating to System Properties and search for x_cqt_c3*.

  2. Configure the parameters described in the following table.

    ParameterDescription

    Server URL (External)

    URL of the CloudCenter instance

    Error landing page URL endpoint

    URL of the error page

    Automatically create accounts in CloudCenter

    Select the required value:

    • Yes (default): To create CloudCenter user account when a ServiceNow user with the x_cqt_c3_frame.consumer role attempts to access the CloudCenter UI from ServiceNow.

    • No: For the administrator to manually create CloudCenter user accounts.

Validate the ServiceNow Configuration

To validate the ServiceNow configuration follow this procedure.

  1. Login to ServiceNow as a user with the x_cqt_c3_frame.consumer role.

  2. Verify that Automatically create accounts in CloudCenter is enabled on the Base Configuration page.

  3. Go to the ServiceNow Service Portal by entering https://<ServiceNow_URL>/sp

  4. From the homepage, click Order Something > Browse by Categories > Cisco CloudCenter. Several Cisco CloudCenter catalog items should be visible. 

  5. Click Deploy Applications.The Cisco CloudCenter Application Profiles page should be visible within the ServiceNow header.

  6. Select an Application Profile and initiate a deployment.

  7. Be sure to select the Deployment Environment that is configured for ServiceNow approvals. Verify that the Deployment environment is shared with the user with deployment and manage permissions. If the correct Deployment Environment was selected, you should see the Deployment Pending Approval popup.

  8. Open a private browser session and login to ServiceNow with a user account that has the approver_user role.

  9. Navigate to My Approvals.  You should see a new record with the state Requested.  

  10. Click this record, leave a comment (optional) and approve the Request.

  11. Visually confirm that the record state has changed from Requested to Approved.

  12. Switch back to the previous browser session containing the Cisco CloudCenter UI and check the Deployment state.  The state should have changed from Pending Approval to In Progress.

  13. In ServiceNow, visually confirm that the record state has changed from Requested to Approved.

  14. Once the Application Profile is successfully approved and deployed, the following CMDB modules in ServiceNow should be updated.

    1. Jobs

    2. Virtual Machines

    3. Network Adapters

    4. Storage Volumes

    5. IP Addresses



© 2017-2019 Cisco Systems, Inc. All rights reserved