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 Developer Reference > Creating Discovery and Integration Adapters > Developing Jython Adapters > Record DFM Code

Record DFM Code

It can be very useful to record an entire execution, including all parameters, for example, when debugging and testing code. This task describes how to record an entire execution with all relevant variables. Furthermore, you can view extra debug information that is usually not printed to log files even at the debug level.

To record DFM code:

Access Administration > RTSM Administration > Data Flow Management > Universal Discovery. Right-click the job whose run must be logged and select Go to Adapter to open the Adapter Management application.
Locate the Execution Options pane in the Adapter Configuration tab, as shown below.
Change the Create communication log box to Always. For details on setting logging options, see Execution Options Pane.

The following example is the XML log file that is created when the Host Connection by Shell job runs and the Create communication logs box is set to Always or On Failure:

The following example shows the message and stacktrace parameters:

Note CDATA mechanism is used to store information retrieved from user environment in the communication logs. When scan files get some characters or XML segments that cannot be parsed by the CDATA mechanism, the information will be saved in binary format for further troubleshooting purpose. HPE Software Support will decode the binary data in the communication logs to perform troubleshooting.

Send Help Center feedback