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

Operations Manager i10.62

Administer > RTSM > RTSM Data Flow Management > Integrations > Integration Studio > Live Data Push Jobs

Live Data Push Jobs

A live data push job no longer relies on the schedule setting. Instead, a live data push job runs in following manner:

When the result of its active TQL queries changes, it automatically runs a delta synchronization and sends the change to the consumer (external system).
A live data push job can contain multiple TQL queries, and the job runs a delta synchronization when any of its TQL query result changes.
If a TQL query result changes during the running of the job, the latest changes wait until the job finishes, and then trigger another run of the job.
When a live data push job and a scheduled data push job use the same TQL query, the two jobs cannot run concurrently. If a job already runs, the other waits until the running job finishes.
If you manually stop a live data push job, then the changes occurred during the running of the job do not trigger another run of the job.

Note

HPE recommends to use only one TQL query in a live data push job.
Live data push jobs only perform delta synchronizations. In order to perform full synchronizations, you need a scheduled data push job that contains the same TQL query.
If the priority level of a TQL query is Not Active, it automatically changes to Low when you add the TQL query to a live data push job.
When you remove a live job or deactivate the Enable live job option of the job, if the contained TQL query is not part of any other live jobs, the priority level of the TQL query is then set to Not Active.
After you create a TQL query and use it in a live data push job, do not modify the layout attributes of any link in the TQL query. Otherwise, the live data push job fails.