Data flow

The following outlines the synchronization data flow:

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Automatic synchronization data flow

The web service uses the On-Premise Bridge agent to communicate with the UCMDB machine.
The agent checks that the version of UCMDB is supported.
The agent checks if there is an up-to-date UMS adapter installed. If not, it installs the adapter.
The agent checks if an integration point and push job exist. If the integration point does not exist, the agent creates it.

The push job runs in UCMDB immediately after it is created, and twice every day according to a preset schedule.
The integration point pushes data from UCMDB to a staging area, in chunks.
The agent retrieves the chunks of data from the staging area, in the order they were pushed.

Note For details on how to view in UCMDB the TQL queries which push the data to the staging area, see the UCMDB documentation.

Service Management uses the identification web service to identify the configuration items (CIs) retrieved from UCMDB, and where necessary merge them with existing CIs in Service Management. Only CIs which contain enough information to be identified are included in the retrieved data.

Note Each chunk has its own timestamp. The agent retrieves the chunk of data with the next timestamp: the one closest to and after the timestamp of the last chunk retrieved.
The job takes the identified data and sends it to the Service Management server.

The original data is kept in the staging area for 30 days and is then deleted.

Custom synchronization data flow

The web service uses the On-Premise Bridge agent to communicate with the UCMDB machine.
The agent checks that the version of UCMDB is supported.
The user checks if there is an up-to-date UCMDB push adapter installed. If not, the user dowloads the push adapter installs it in UCMDB.
The user checks if an integration point and push job exist. If the integration point does not exist, the user creates the integration point and sets up the push job.

Note The user can customize the push job schedule after the job is created.
The user munually triggers the push job.
Data is pushed to the Push Adapter.
The Push Adapter loads the correct mapping for the specific TQL query.
The integration point pushes data from UCMDB to a staging area, in chunks, according to the mapping XML.
The agent retrieves the chunks of data from the staging area, in the order they were pushed.

Note For details on how to view in UCMDB the TQL queries which push the data to the staging area, see the UCMDB documentation.

Service Management uses the identification web service to identify the configuration items (CIs) retrieved from UCMDB, and where necessary merge them with existing CIs in Service Management. Only CIs which contain enough information to be identified are included in the retrieved data.

Note Each chunk has its own timestamp. The agent retrieves the chunk of data with the next timestamp: the one closest to and after the timestamp of the last chunk retrieved.
The job takes the identified data and sends it to the Service Management server.

The original data is kept in the staging area for 30 days and is then deleted.