Installation from ServiceNow Store
Install the Cloudaware CMDB application from the ServiceNow Store, then configure ServiceNow to import Cloudaware CMDB data from the Cloudaware-provided Google BigQuery export.
The application creates Cloudaware-specific tables in ServiceNow and populates them with CMDB data on a scheduled basis.
High-Level Setup Flow
To complete the installation:
- Get the ServiceNow-to-Google credentials from Cloudaware Support.
- Install the Cloudaware CMDB application from the ServiceNow Store.
- Configure JWT-based authorization in ServiceNow.
- Configure and activate the Workflow Studio import flow.
- Verify that Cloudaware data is loaded into ServiceNow.
Prerequisites
Before you begin, make sure you have:
- ServiceNow administrator access.
- ServiceNow IntegrationHub Enterprise Pack activated.
- ServiceNow Workflow Studio installed.
- Access to install applications from the ServiceNow Store.
- Cloudaware-provided credentials:
- Service account email address
- Service account private key
.p12certificate file- Project ID
- Dataset ID
To request the Cloudaware-provided credentials, contact Cloudaware Support at support@cloudaware.com.
Install the Cloudaware CMDB Application
- Log in to the ServiceNow instance.
- Go to System Applications.
- Select Available to Obtain From Store.
- Search for Cloudaware CMDB.
- Open the application details page.
- Click Get and follow the ServiceNow Store installation flow.
Check the Cloudaware CMDB application page in the ServiceNow Store to confirm that the application is compatible with the target ServiceNow instance version.
Configure ServiceNow-to-Google Authorization
Cloudaware provides the credentials required for ServiceNow to authenticate to Google and read Cloudaware export data. Configure the connection before setting up the import workflow.
Create a JWT Key and Certificate
- In ServiceNow, go to All → System OAuth → JWT Keys.
- Click New.
- Fill out the JWT key form:
- Name: Enter a meaningful name, for example,
Google JWT Key. - Signing Key: Enter
notasecret. - Signing Keystore: Click the lookup icon to create a signing keystore.
- Name: Enter a meaningful name, for example,
- In the keystore pop-up, click New.
- Fill out the JWT certificate form:
- Name: Enter a meaningful name, for example,
Google JWT Certificate. - Type: Select Java Key Store.
- Key store password: Enter
notasecret.
- Name: Enter a meaningful name, for example,
- Click the paperclip icon and attach the
.p12certificate file provided by Cloudaware. - Click Submit.
- Return to the JWT key form.
- For Signing Keystore, select the certificate you created.
- Click Submit.
Configure the JWT Provider
- Go to All → System OAuth → JWT Providers.
- Click New.
- Fill out the JWT provider form:
- Name: Enter a meaningful name, for example,
Google JWT Provider. - Signing Configuration: Select the JWT key you created.
- Name: Enter a meaningful name, for example,
- Save the provider.
- Open the provider record.
- Select the Standard Claims tab.
- Add the following claims:
| Claim | Type | Value |
|---|---|---|
iss | String | Service account email address provided by Cloudaware |
sub | String | Service account email address provided by Cloudaware |
aud | String | https://oauth2.googleapis.com/token |
- Click Update.
Configure the OAuth Application Registry
- Go to All → System OAuth → Application Registry.
- Click New.
- Select Connect to a third party OAuth Provider.
- Fill out the form:
| Field | Value |
|---|---|
| Name | A meaningful name, for example, Google JWT |
| Client ID | notneeded |
| Client secret | notneeded |
| Default grant type | JWT Bearer |
| Token | https://oauth2.googleapis.com/token |
| Refresh Token Lifespan | 10 |
- Click Submit.
- Open the generated OAuth entity profile, for example,
Google JWT default_profile. - For JWT Provider, select the JWT provider you created.
- Click Update.
Add the BigQuery OAuth Scope
- Go back to All → System OAuth → JWT Providers.
- Open the JWT provider you created.
- Select the Custom Claims tab.
- Add the following claim:
| Claim | Type | Value |
|---|---|---|
scope | String | https://www.googleapis.com/auth/bigquery.readonly |
- Click Update.
Configure Credentials and Connection Alias
-
Go to All → Connections & Credentials → Credentials.
-
Click New.
-
Select Auth 2.0 Credentials.
-
Fill out the form:
- Name: Enter a meaningful name, for example,
Google JWT Credentials. - OAuth Entity Profile: Select the OAuth entity profile created earlier.
- Name: Enter a meaningful name, for example,
-
Click Update.
-
Click Get OAuth Token to test the connection.
-
Go to All → Connections & Credentials Aliases.
-
Click New.
-
Set the alias to
Google JWT. -
Save the alias.
-
In the alias record, create a new HTTP(S) connection.
-
Fill out the connection form:
- Name: Enter a meaningful name, for example,
Google JWT Connection. - Credential: Select
Google JWT Credentials. - URL builder: Select this checkbox.
- Host: Enter
bigquery.googleapis.com.
- Name: Enter a meaningful name, for example,
-
Click Submit.
Configure the Import Workflow
Configure Workflow Studio to populate the Cloudaware import settings and run the scheduled CI import.
- Go to All → Workflow Studio.
- Open Flows.
- Select Update Import Settings and Fields Mapping.
- Click Test → Run test.
Run Update Import Settings and Fields Mapping once after installation. This prepares the import settings and field mapping records used by the data import workflow.
- Return to the list of flows.
- Sort the list by Updated in descending order.
- Open Import All CI Data from Cloudaware.
- In Trigger, configure a scheduled trigger.
- Select Scheduled.
- Set the schedule to run daily at the preferred time.
The recommended import frequency is once per day unless Cloudaware Support provides different guidance for your environment.
- In Actions, open Set Flow Variables.
- Set the required variables:
| Variable | Value |
|---|---|
| Connection Alias | The connection alias configured earlier, for example, Google JWT |
| Cloudaware Import Settings Table | Use the auto-populated system table value |
| Cloudaware Import Fields Mapping Table | Use the auto-populated system table value |
| Project Id | Import Project ID provided by Cloudaware |
| Dataset Id | Import Dataset ID provided by Cloudaware |
- Click Done.
- Save and activate the workflow.
- Allow time for the first import to complete.
Created Tables
The application creates system tables for import configuration and application tables for Cloudaware CI data.
System Tables
| Label | Table name |
|---|---|
| Cloudaware CI | x_ca_cmdb_ci |
| Cloudaware CMDB Schema | x_ca_cmdb_schema |
| CI Class Import | x_ca_cmdb_ci_class_import |
| Cloudaware Import Settings | x_ca_cmdb_ci_class_import_settings |
| Cloudaware Import Fields Mapping | x_ca_cmdb_import_fields_mapping |
Application Tables
| Label | Table name |
|---|---|
| AWS Account | x_ca_cmdb_aws_account |
| AWS DynamoDB Backup | x_ca_cmdb_aws_dynamo_db_backup |
| AWS DynamoDB Table | x_ca_cmdb_aws_dynamo_db_table |
| AWS EBS Snapshot | x_ca_cmdb_aws_snapshot |
| AWS EBS Volume | x_ca_cmdb_aws_volume |
| AWS EC2 Image | x_ca_cmdb_aws_image |
| AWS EC2 Instance | x_ca_cmdb_aws_instance |
| AWS EC2 Security Group | x_ca_cmdb_aws_security_group |
| AWS ELB Load Balancer | x_ca_cmdb_aws_load_balancer |
| AWS ElastiCache Cluster | x_ca_cmdb_aws_cache_cluster |
| AWS ElastiCache Node | x_ca_cmdb_aws_cache_node |
| AWS Lambda Function | x_ca_cmdb_aws_lambda_function |
| AWS RDS Cluster | x_ca_cmdb_aws_db_cluster |
| AWS RDS Instance | x_ca_cmdb_aws_db_instance |
| AWS Redshift Cluster | x_ca_cmdb_aws_redshift_cluster |
| AWS S3 Bucket | x_ca_cmdb_aws_bucket |
To disable imports for a specific application table, open Cloudaware Import Settings (x_ca_cmdb_ci_class_import_settings) and set Active to False for the corresponding class. Data for inactive tables is not imported.
Verify Data Upload Status
After the workflow runs, verify the import status in the Cloudaware Import Settings table.
Open the following URL in the ServiceNow instance:
https://YOURINSTANCE.service-now.com/x_ca_cmdb_ci_class_import_settings.do
Replace YOURINSTANCE with the ServiceNow instance ID.
Troubleshooting
OAuth Token Cannot Be Retrieved
- Confirm that the
.p12certificate from Cloudaware is attached to the JWT certificate record. - Confirm that the JWT key uses the certificate as the signing keystore.
- Confirm that the
issandsubstandard claims use the service account email address provided by Cloudaware. - Confirm that the
audclaim and OAuth token endpoint are set tohttps://oauth2.googleapis.com/token. - Confirm that the custom
scopeclaim is set tohttps://www.googleapis.com/auth/bigquery.readonly.
Workflow Runs but No Data Is Imported
- Confirm that the Import All CI Data from Cloudaware flow is active.
- Confirm that the flow variables use the correct connection alias, Project ID, and Dataset ID.
- Confirm that the Update Import Settings and Fields Mapping flow was tested once after installation.
- Review Cloudaware Import Settings and confirm that the target CI classes are active.
Still stuck? Contact Cloudaware Support at support@cloudaware.com with the ServiceNow instance name, connection alias name, Project ID, Dataset ID, and the latest workflow execution details.