CliQr is now part of Cisco Learn More About Cisco

Install and Configure ServiceNow and CloudCenter


Availability

CloudCenter 4.6 supports the following ServiceNow releases:

  • ServiceNow, Geneva

  • ServiceNow, Helsinki

CloudCenter 4.6 supports the following Integration–CloudCenter releases:

  • Integration–CloudCenter, Release 1.0

  • Integration–CloudCenter, Release 1.1

  • Integration–CloudCenter, Release 1.2

Configure Cisco CloudCenter

To configure the CloudCenter for the ServiceNow Integration, you must follow a multi-step process.

1. Create Custom Action

You  must create a custom action to publish application profiles from Cisco CloudCenter to ServiceNow.
To create a custom action, perform the following procedure in Cisco CloudCenter.

  1. Log into Cisco CloudCenter using administrative privileges.
  2. Select Policies from the left navigation.
  3. Select the Custom Actions tab.
  4. Click Add Custom Action and define the fields as follows:

    Field

    Value

    Name

    Publish to ServiceNow

    Visible to User

    Enabled

    Object

    Application

    Action Type

    Invoke a web service

    Protocol

    HTTPS

    Web Service URL

    <yourServiceNowInstance.com>/api/now/table/x_cqt_cliqr_publish_app_trigger

    Username

    rest.admin (this user will be created in ServiceNow at a later point)

    Password

    Enter the password for the rest.admin user.

    Http Request Type

    POST

    Content Type

    JSON

    Body

2. Create Policies

You must create 3 action policies to propagate the status of the application deployments back to ServiceNow. For each policy, use the common settings and individual policy settings listed below.

To create each new policy, perform the following steps in Cisco CloudCenter.

  1. Select Policies from the left navigation.
  2. Select the Policies tab.
  3. Click on Add Action Policy and define the fields as follows:

    Common Settings

    Field

    Value

    Name

    See the Individual Policy Settings section below.

    Execute For

    Application Deployment

    On Event

    See the Individual Policy Settings section below.

    Action Type

    Invoke a web service

    Protocol

    HTTPS

    Web Service URL

    <yourServiceNowInstance.com>/api/now/table/x_cqt_cliqr_job_status_trigger

    Username

    rest.admin (this user will be created in ServiceNow at a later point)

    Password

    Enter the password for the rest.admin user.

    Http Request Type

    POST

    Content Type

    JSON

    Body

    See the Individual Policy Settings section below.

    Auto Enabled for shared users

    Enabled

    Restrict users from disabling this Policy

    Enabled


    Individual Policy Settings

    Policy

    On Event

    Body

    1. SNOW_job_status_changed

    Status Changed

    2. SNOW_job_deployed

    Deployed

    3. SNOW_job_canceled

    Canceled

     

 

Configure ServiceNow

To configure the CloudCenter-ServiceNow Integration application, you must follow a multi-step process.

1. Download and Install the CloudCenter-ServiceNow Integration Application

To download and install the CloudCenter-ServiceNow Integration application, follow this procedure.

  1. Submit a request to download the CloudCenter-ServiceNow Integration application.

    1. Go to the https://store.servicenow.com website.
    2. Search for Integration - CloudCenter.
    3. Select the Integration - CloudCenter application from the catalog.
    4. Select Contact Seller to obtain approval to download the application.
  2. Install the CloudCenter application in ServiceNow:
    1. Once the application has been approved, using the left filter option, navigate to System Applications > Applications > Downloads > Integration - CloudCenter.
    2. Click All versions.
    3. Select and install the appropriate version.

2. Configure the CloudCenter-ServiceNow Integration Application

To configure the CloudCenter-ServiceNow Integration application, follow this procedure.

  1. Enable the Procurement plugin.

    1. Using the filter and navigate to Plugins.
    2. Search for Procurement within the Plugins module.
    3. Locate and activate Procurement - com.snc.procurement.
    4. Once completed, click on Close and Reload Form.
  2. Install the certificate:

    Icon

    If a self-signed certificate is used in Cisco CloudCenter, the certificate must be added in ServiceNow to enable communication

    1. Using the filter and navigate to System Definition > Certificates.
    2. Add a new X.509 certificate using the Trust Store Cert type.
  3. Setup the connection with Cisco CloudCenter:

    Icon

    This step assumes that you have a CloudCenter Manager (CCM) that can communicate with the ServiceNow environment over the network.

    1. Using the filter and navigate to Cloud Marketplace Configuration.
    2. Complete the following required fields under the General Settings section in order to establish a connection with Cisco CloudCenter.

      General Settings

      Additional information

      CCM URL

      Enter the URL of Cisco CloudCenter using the format https://<ciscoCloudCenterURL>.com.

      Username

      Enter the default username cliqradmin or another administrator account from Cisco CloudCenter.

      API Key

      Enter the API key of the administrator account used above. To obtain the API key, login to Cisco CloudCenter. Then navigate to Admin > Users and click on Manage API Key for the account being used.

    3. Once you complete the General Settings section, click Submit. The Cloud Marketplace configuration page will reload and a new section called Cloud and Instance Mapping becomes accessible. Stay on the same page and follow the steps in the next section.

      Icon

      This step is important – If the Cloud and Instance Mapping section is not visible, ServiceNow cannot communicate with Cisco CloudCenter.

  4. Setup Clouds and Instance Mapping.
    1. Complete the following required fields under the Cloud and Instance Mapping section. See screenshot below for reference.

      Cloud and Instance Mapping

      Additional information

      Cloud

      Use the dropdown to select a Cloud. Only Clouds that are enabled in Cisco CloudCenter are selectable.

      Region

      Use the dropdown to select the Region that is enabled in Cisco CloudCenter.

      Instance Mapping

      The order form in the integration application utilizes a simplified approach for users to select an instance size. Use this dropdown to associate an appropriate instance type value for sizes Small, Medium, Large and Extra Large. Additional Clouds can be configured by clicking the plus (plus) icon.

    2. After the Cloud and Instance Mapping section is completed, click the Submit button to save the settings.

  5. Verify Connectivity.
    1. Using the filter to navigate to the Integration: CloudCenter > Test CliQr Connection.
    2. Click Test CliQr Connectivity.
    3. All 3 tests should be successful – as displayed in the following image.
  6. Create the Integration User.
    1. In ServiceNow, create a new user as follows:

      Field

      Value

      User ID

      rest.admin

      First Name

      Rest

      Last Name

      Admin

      Email

      Not required

      Password

      <enter a secure password>

      Web service access only

      Enabled

      Internal integration user

      Enabled

      Roles

      Add the following roles: u_cliqr_admin, procurement_admin, rest_service

  7. Create a Purchase Order (PO). 

    Icon

    To complete the order form within the integration application, a valid PO is required.

     

    1. Using the filter, navigate to Purchase Orders under Procurement > Orders > Purchase Orders.

    2. Create a new Purchase Order as follows:

      Field

      Additional information

      PO Number

      Enter the auto generated number from the Number field.

      Value

      Enter an appropriate value for the Purchase Order.

      Assigned To

      Select any user. We will update this field later to validate the configuration.

      Type

      Select Cloud Marketplace.

  8. Verify your integration by following the items listed in the post configuration checklist

    1. Confirm the following Groups and Roles exist under System Security > Users and Group.

      Group Name

      Roles

      Additional information

      Cloud Marketplace Service Instance Owners

      x_cqt_cliqr.service_instance_owner

      Users part to this group can be owners of the service instance and will also see the Approvals tab on the dashboard. At least one user should belong to this group.

      Cloud Marketplace Consumers

      u_cliqr_requester

      Users must be a part of this group to browse the catalog and accept/reject approval requests. Adding users to this group (along with the CliQr group) creates a user account in Cisco CloudCenter and generates an API key for this user. Confirmed this requirement by navigating to Integration - CloudCenter > User Properties and Integration - CloudCenter > User API Keys.

      CliQr

      rest_service
      procurement_user

      Create a separate group for each Cisco CloudCenter Activation Profile that used for this integration. The first group should be called CliQr. Additional groups (if needed), should be given the name CliQr <activation profile tag>.

    2. Confirm the following Group Properties exists under Integration - CloudCenter > Group Properties.

      Group

      Name

      Value

      Additional information

      CliQr

      activiation_profile

      1

      Use the following format to create additional Group Properties as needed:
      Group: CliQr <activation profile tag>
      Name: activation_profile
      Value: <cliqr_profile_id}>
      The cliqr_profile_id is the ID of the activation profile in Cisco CloudCenter. This is a numeric value such as 1 or 2.  The groups associated activation profile defines the options that group members can see for items in the order guide. Use the API View Activation Profiles to retrieve the ID. If an Activation Profile is not present in Cisco CloudCenter, you will need to create one, as per the instructions in the link provided above.

  9. Confirm the following properties exist under Integration - CloudCenter > Settings > Properties.

    Property Name

    Description

    default_published_app_group

    The default value of this property is Cloud Marketplace Consumers. This is the default group to which the applications published from Cisco CloudCenter will be associated with. If there is no requirement to filter the applications based on user groups, this group should always be set to the default value.

    max_order_quantity

    The order form in the integration application allows users to select the quantity of each application through a dropdown list. Use this comma separated list to configure the dropdown values for the quantity selection. The default value is 1,2,3,4,5.

  10. Confirm the Instance Specs table under Integration - CloudCenter > Data Tables > Instance Specs contains sample data. This data is presented to the user on the order form when selecting an instance size (small, medium, large or extra large).

  11. Optional configuration procedure to enable emails and support MID servers.

    1. Email needs to be enabled for the approval workflow email notifications. Existing ServiceNow installations may already have this configured.

      1. Using the filter, navigate to System Properties > Email Properties (or Email depending on the ServiceNow version)

      2. Confirm that outbound and inbound email sending is enabled.

    2. Support for MID server:

      1. Navigate to MID Server > Capabilities and confirm that the REST, SSH, and SOAP capabilities have been added.

      2. Create the following property under Integration - CloudCenter > Settings > Properties.

        Property name

        Value

        Mid_server_name

        <configured_rest_server_name>

Validate the CloudCenter-ServiceNow Integration

To validate the CloudCenter-ServiceNow Integration application, follow this procedure.

  1. Create Test Users

    1. To verify the installation, create the following test user accounts in ServiceNow. An email address is required to create a user account.

      User Name

      Group Membership

      Description

      consumer.user

      1. Cloud Marketplace Consumers
      2. CliQr

      This test user is used to submit orders.

      serviceOwner.user

      1. Cloud Marketplace Consumers
      2. Cloud Marketplace Service Instance Owners

      This test user is used to approve/reject order requests from an owner perspective.

      financeOwner.user

      1. Cloud Marketplace Consumers
      2. Cloud Marketplace Service Instance Owners

      This test user is used to approve/reject order requests from a finance perspective.

    2. A new purchase order was created in the Create a Purchase Order section above. For that purchase order, update the Assigned To field to the user financeOwner.user.
  2. Publish an Application Profile to ServiceNow
    1. In Cisco CloudCenter, locate an Application Profile under the Applications tab.
    2. Click the dropdown for the application and Share it with all users in the Tenant.
    3. Click the dropdown for the application and select Publish to ServiceNow.
    4. In ServiceNow, navigate to Integration - CloudCenter > Data Tables > Application Profiles. There should be a record that contains the published application.
  3. Place an order:
    1. Navigate to https://<yourServiceNowInstance>.com/cloud-marketplace.
    2. Login as the user consumer.user.
    3. Click on Store.
    4. Select an application from the catalog, configure and submit the order. Make sure to choose serviceOwner.user as the Service Instance Owner and select the PO that is assigned to financeOwner.user.
    5. Login as serviceOwner.user and then as financeOwner.user to approve the request.
    6. Once the order is approved, the order should be deployed based on the provided deployment start date and time.
    7. Browse to the Service Instances tab and confirm the order is in Deployed status.

Additional Notes

Installing the Integration app adds extra fields to the task table. As this is a linear operation, the load time could take a while depending on the existing data in the environment.
 

  • No labels