Optimize 10.7 | webMethods Optimize Documentation | Configuring BAM | Managing webMethods Optimize Environments | Configuring Logical Servers | Defining Logical Server Subcomponents for the Analytic Engine | Defining JMSEventAction Settings
 
Defining JMSEventAction Settings
You can configure JMSEventActions to facilitate Optimize-based temporal analysis on rule violations. In essence, this functionality enables you to monitor rule violations over time so that you can perform mores sophisticated analysis of events and processes than standard Optimize rule-related functionality supports. Using this functionality, you can send JMS messages to a Broker (local or non-local) in response to rule violations. These JMS messages can be monitored by a KPI that monitors rule violations over a specified time frame and sends the appropriate notifications regarding the rule violations to a designated user.
To configure a JMSEventAction, you must edit the provided XML snippet with the appropriate parameters.
*To configure JMSEventActions
1. In My webMethods: Navigate > Applications > Administration > System-Wide > Environments > Define Environments.
2. On the Define Environments page, click the name of the environment you want to work with.
3. On the Edit Environment page, click the Configure Servers tab.
4. Under the appropriate Analytic Engine logical server node in the configuration tree, click JMSEventAction Settings.
A new area appears beside the configuration tree, labeled JMSEventAction Settings for Analytic Engine.
5. Identify the JMSEventAction to be published, along with the attributes that the event will contain, by editing the XML snippet in the text editor in the settings area. As installed, the XML is configured as a comment (<!-- xml -->). Remove the comment formatting and modify the XML according to the instructions in the XML, commenting out the instructions and notes.
Optimize displays the JMSEventAction you identified in place of Test Action on the Add/Edit/Copy Rule page and the Rule Details page.
6. To identify more than one JMSEventAction, copy and edit the XML shown in the example box above (step 5) for each action.
7. Click Save to save changes or click Cancel to discard any changes you have made in this settings area.
8. Apply the changes by restarting the Analytic Engine.
For more information about restarting the Analytic Engine, see Administering webMethods Optimize.