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)`

Universal DiscoveryContent Pack 28.00 (CP28)

Integrate > Micro Focus Integrations > Micro Focus SMA-X Push Integration > Tailor the Integration > Integration Architecture

Integration Architecture

This section includes:

Data Flow Architecture

The Push Engine executes the TQL query.
For a differential flow, the data is compared to the last synchronized data, and only the changes are forwarded.
Data is then pushed to the Push Adapter.
The Push Adapter loads the correct mapping for the specific TQL query.
Data is mapped from the UCMDB data Model into the SMA-X Data model according to the mapping XML.
Data is sent to the Push Connector.
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.
The Push Connector starts reconciling and pushing any record without any dependencies, or a record whose dependencies have already been reconciled/pushed to SMA-X.
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.

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.

For details of SMA-X rules and flows, refer to the SMA-X documentation.

For details, see Developing Push Adapters in the Developer Reference section of the UCMDB Help.

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

Variable	Description
externalId	The external ID of the CI in UCMDB.
serviceName	The Web service name used in the SOAP request.
attributesHierarchy	The location of the CI attributes in the SOAP request.
keysHierarchy	The location of the CI keys in the SOAP request.
keyTag	The key in the SOAP request that passes the value of the ID.
keyVal	The ID value from UCMDB.
retrieveRequestName	The name of the SOAP request for a retrieval operation.
createRequestName	The name of the SOAP request for a creation operation.
deleteRequestName	The name of the SOAP request for a delete operation.
updateRequestName	The name of the SOAP request for an update operation.