Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Query not Configured in smPushConf.xml
Sample Configuration
The TQL queries used for pushing relationships must be configured in the smPushConf.xml file.
<config>
<mapping>
<!--
Wildcard is supported for TQL names while you configure the mapping now,
you can add the '*' at the end of the TQL name while configuring the mapping.
We use the wildcard for mapping in OOTB, so each time you do save as to a TQL,
you could still push it to SM without manual changing the mapping.
For e.g., if you have saved the <TQL_name> query to <TQL_name>_1, and <TQL_name>_2,
the TQL name is specified as <TQL_name>* in this configuration file, and the
integration will automatically use this mapping entry on all of the three TQLs.
However, using the exact TQL name to configure the mapping is still supported.
-->
<tql name="SM Business Service Relations Push 2.0" resourceCollectionName="Relationships" resourceName="Relationship"/>
<tql name="SM CRG Relations Push 2.0" resourceCollectionName="Relationships" resourceName="Relationship"/>
<tql name="SM Node Relations Push 2.0" resourceCollectionName="Relationships" resourceName="Relationship"/>
<tql name="SM Layer2 Topology Relations Push 2.0" resourceCollectionName="Relationships" resourceName="Relationship"/>
</mapping>
</config>
Error Message
The push job fails with a “Failed” status. From both the log file and the detail error message of the failed job in the Universal CMDB studio (see How to Check the Error Message of a Failed Push Job), you receive an error like the following:
java.lang.RuntimeException: No mapping is found for TQL: "SM Business Service Push 2.0", or Cannot retrieve the mapping from SM side by QueryNodeName [bizservice", please configure in smPushConf.xml or SM configuration at com.mercury.topaz.fcmdb.adapters.serviceDeskAdapter.push.SmGenericPusher.push(SmGenericPusher.java:119) ... 35 more --- End of probe-side exception --- at com.hp.ucmdb.discovery.probe.agents.probemgr.adhoctasks.AdHocProbeRequestOperation.convertThrowableToStringSafeException(AdHocProbeRequestOperation.java:86) at com.hp.ucmdb.discovery.probe.agents.probemgr.adhoctasks.AdHocProbeRequestOperation.performAction(AdHocProbeRequestOperation.java:77) at com.hp.ucmdb.discovery.probe.agents.probemgr.taskdispatcher.AdHocTaskDispatcher.dispatchTask(AdHocTaskDispatcher.java:70) at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) at javax.management.StandardMBean.invoke(StandardMBean.java:405) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305) at org.springframework.jmx.access.MBeanClientInterceptor.doInvoke(MBeanClientInterceptor.java:405) at org.springframework.jmx.access.MBeanClientInterceptor.invoke(MBeanClientInterceptor.java:353) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) at com.sun.proxy.$Proxy57.dispatchTask(Unknown Source) at com.hp.ucmdb.discovery.probe.agents.probegw.managementtasks.adhoctasks.AdhocThread.run(AdhocThread.java:54) ... 3 more
Solution
Search for text string No mapping is found for TQL to find the name of the query that is not yet configured, and then add a mapping entry for the query in the smPushConf.xml file.
