| Info |
|---|
Due to limited discovery cloud asset discovery capabilities in ServiceNow, many customers choose to use Cloudaware CMDB to populate or enrich cloud resources in ServiceNow via Cloudaware. For a complete gap analysis of discoverable objects in ServiceNow vs. Cloudaware click The list of objects discoverable by Cloudaware is available here. |
| Table of Contents |
|---|
Decide On The Integration Approach
...
Using a push approach, responsibility for most of the integration work is in the Cloudaware corner. Cloudaware is responsible for pushing assets and configuration into ServiceNow in a timely manner. A customer’s main responsibility is to provide Cloudaware with access and define a custom class to contain Cloudaware data. Sample class definitions can be found here. The disadvantage of the push approach is the customer is now continually dependent on Cloudaware for any schema modifications in the custom Class. Should the customer want to change the frequency or the types of attributes that Cloudaware sends to ServiceNow, it will have to request such changes from Cloudaware. Cloudaware handles these requests with the same priority as all other customer-related service requests.
...
Create a custom class in ServiceNow
Create a user for Cloudaware in ServiceNow
Grant API access to Cloudaware
Grant access to the custom class and table to Cloudaware user
Configure credentials in Cloudaware admin panel (guide)
Submit a service request to Cloudaware to activate push integration
Validate date
...
Determine which types of CIs will be pulled from Cloudaware
Decide where in ServiceNow schema the data from Cloudaware will be stored
Download Cloudaware Enterprise WSDL and upload to ServiceNow (guide)
Develop Cloudaware SOQL queries for each type of CI resource
Create ServiceNow scripts to pull and paginate data from Cloudaware using SOAP messages
Insert the extracted data into desired location
Ensure change detection and data deletion is working