Integration Architecture

This section includes:

• Data Flow Architecture

• Integration TQL Queries

• Service Anywhere Rules and Flows

• Data Mapping

• Push Mapping

Data Flow Architecture

1. The Push Engine executes the TQL query.

2. For a differential flow, the data is compared to the last synchronized data, and only the changes are forwarded.

3. Data is then pushed to the Push Adapter.

4. The Push Adapter loads the correct mapping for the specific TQL query.

5. Data is mapped from the UCMDB data Model into the Service Anywhere Data model according to the mapping XML.

6. Data is sent to the Push Connector.

7. The Push Connector orders all the data in a set of dependency trees, starting with the records that do not depend on any other record.

8. The Push Connector starts reconciling and pushing any record without any dependencies, or a record whose dependencies have already been reconciled/pushed to Service Anywhere.

   1. The Push Connector first tries to reconcile with existing records

   2. If it finds a match, it attempts to update that record,

   3. If it does not find a match, it attempts to create a new record.

Integration TQL Queries

Any attribute using in the mapping flow of the Push Adapter should be marked in the selected layout of the query node.

For more information, see Data Flow Management > Integration Studio > Integration Jobs Pane.

Service Anywhere Rules and Flows

For details of Service Anywhere rules and flows, refer to the Service Anywhere documentation.

Data Mapping

For details, see Developing Push Adapters in the HPE Universal CMDB Developer Reference Guide.

Push Mapping

The following table describes variables in the Generic Push Adapter XML mapping file that are specifically required for integration with Service Anywhere.