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 CMDB11.0

Use > Data Flow Management > Integrations > Integration Studio > Integration Studio Overview > Data Push

Data Push

An integration of Data Push type copies data from the CMDB to an external data repository, so that the CMDB no longer retains control over this data.

You use data push integrations to feed important data from your CMDB into an external system to facilitate your necessary business processes. An example of this is pushing data discovered by DFM into Service Manager, where tickets may be opened that are connected to the actual CIs in your IT infrastructure.

If an authorized state has been defined, you can perform data push from the authorized or actual state.

Data push architecture enhancement

In version 10.30, data push architecture is enhanced to separate the internal resources used by different integrations, localizing at integration point level, resources otherwise shared between the integration points, which, when run in parallel with large amount of data may prove slow. By reducing such shared resources, big improvements can be observed in a concurrent running scenario. Now the engine parallelism can be better exploited through the number of threads allocated. A new JMX setting com.hp.ucmdb.synchronizer.manager.SynchronizerManagerFactory is introduced, which allows you to increase the number of threads for data push jobs from the out-of-the-box value 3 to any desired value. For more information, see How to Increase the Number of Threads for Data Push Jobs.

In version 10.30, the number of CIs from a data push TQL query is increased from 5 million to 20 million on Oracle.

Note Due to previous engine limitation, the number of CIs to push was limited at 5 million CIs to ensure a healthy delivery. With the new data push architecture, the fuse has been increased to 20 million CIs, so push integrations may handle larger number of CIs.

To achieve this, you need use the native Oracle drivers, instead of the Data Direct drivers, due to errors received when using Data Direct drivers.

The values of the following infrastructure settings were also increased on UCMDB server side to support 20 million CIs:

dal.object.condition.max.result.size=99999999
dal.link.condition.max.result.size=99999999
dal.use.memory.instead.temp.table.high.threshold.oracle=60000000
model.change.percent.statistics.threshold=30
replication.timeout=180000000
tql.dfs.max.temp.results=200000000
tql.max.objects.visit.model.calc.task=200000000
push.remote.action.timeout=12000000

To view these settings, you can invoke the UCMDB:service=Settings Services > showSettingsByCategoryJMX method.

For limitations on Data Push jobs, see Limitations – Integration Studio.

Related Information

Send Help Center feedback