IBM Tivoli Netcool OMNIbus Activities
Applies To: System Center 2016 - Orchestrator
This integration pack adds the IBM Tivoli Netcool/OMNIbus category to the Activity pane in the Runbook Designer. This category contains the following activities:
Common Configuration Instructions for All Activities
The following configuration instructions apply to all activities in this integration pack. Links to this section are included in the configuration instructions for each activity.
Each activity can have a set of properties that define the configuration of that activity. These properties can includes how the activity connects to other activities or how the activity performs its actions. You can view or modify an activity's properties when the activity is in the runbook window.
To configure the properties for an activity
Double-click the activity name.
Optionally, you can right-click the activity name, and then click Properties.
Click Finish to save your configuration entries.
In the activity properties dialog box, tabs along the left side provide access to settings for the activity. The number of available tabs for activity properties can differ from one activity to another; all activities have a General, a Details, and a Run Behavior tab. Some activities have additional tabs.
This tab contains the Name and Description properties for the activity. By default, the Name of the activity is the same as its activity type, and the Description is blank. You can modify these properties to create descriptive names or provide detailed descriptions of the activity.
This tab contains the properties that are specific to the activity.
Connection Name Property
All activities in this integration pack have a Connection Name property at the top of the Details tab. This property specifies the connection to the IBM Tivoli Netcool/OMNIbus server.
To configure the Connection Name property
- Click the ellipsis (...) button next to the Name field, and then select the applicable connection name.
Filter Behavior Property
The Monitor and Get activities use filters to determine the values that invoke a runbook or retrieve activity. Property values of potential matches are compared to the filter values to determine if they meet the criteria. When configuring filter values, you select one of the available methods of comparison. There is an option to either match or not match the filter for each method.
- Equals: the property of the alert exactly matches the text or number specified in the filter.
- Does not equal: the property of the alert does not match the text or number specified in the filter.
- Is less than or equal to: the property of the alert is less than or equal to the value specified in the filter.
- Is less than: the property of the alert is less than the value specified in the filter.
- Is greater than or equal to: the property of the alert is greater than or equal to the value specified in the filter.
- Is greater than: the property of the alert is greater than the value specified in the filter.
- Matches pattern: this condition uses the Netcool Regular Expressions Library syntax, described in the Netcool User Guide.
- Does not match pattern: this condition uses the Netcool Regular Expressions Library syntax, described in the Netcool User Guide.
Run Behavior Tab
This tab contains the properties that determine how the activity handles multi-value published data and what notifications to send if the activity fails or runs longer than the timeout period.
Multi-Value Published Data Behavior
Get activities retrieve information from another activity or an outside source. They can return one or more values in available from published data. For example, the Get Collection Member activity, the data might be a list of computers that belong to a specified collection.
By default, the data from the Get activity published as multiple individual outputs. This can trigger another activity in a workflow, as many times as there are items published. You can also provide a single output for the activity by enabling the Flatten option. When you enable the Flatten option, you must choose a formatting option:
- Separate with line breaks. Each output is on a new line. This format is useful for creating human-readable text files as output.
- Separate with _ . One or more characters of your choice separate each output.
- Use CSV format. All output is in CSV (comma-separated value) format. This format is useful for importing data into spreadsheets.
Activities produce a new set of data every time it runs. The Flatten feature does not flatten data across multiple instances of the same activity.
Some activities take a limited amount of time to complete. If the activity does not complete within a specified time, they can appear to stop responding. You can configure the number of seconds to wait for completion of an activity. After this wait period, a platform event is sent and the issue is reported. Additionally, you can choose whether to generate a platform event if the activity returns a failure.
To send a notification when an activity fails
In the Event Notifications box, enter the number of seconds of time before generating a notification.
Select Report if activity fails to run to generate a failure notification.
Published data is the method that one activity shares information with other activities in a runbook. It is the data produced by the actions of an activity. This data is published to an internal data bus unique for each runbook. Activities in a workflow can subscribe to the published data of another activity and use it in their configuration. Link conditions also use published data to add decision-making capabilities to a runbook.
An activity can only subscribe to published data from activities that run before it in the runbook. You can use published data to populate the property values needed by an activity.
To use published data
Right-click the Property Value box, click Subscribe, and then click Published Data.
Click the Activity drop-down list box and select the activity from which you want to obtain the data.
To view data elements common to all policies, select Show Common Published Data.
Click the published data element that you want to use, and then click OK.
For a list of the data elements published by each activity, see the Published Data tables in the activity topic. For information about the Common Published Data items, see the Common Published Data topic in Using Runbooks in System Center 2016 - Orchestrator.