...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="utf-8"?>
<SystemMonitorNotification xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="SystemMonitorNotification_v1.0.xsd">
<Notification>
<NotificationMonitor service_name_on_error="OMS Mass Processing Problem Tracking">
<NotificationInterface service_host="OMS Interfacing Server" monitor_port="5667" monitor_host="dipsy.sos" monitor_encryption="XOR">order history id=%ORDER_HISTORY_ID%, job chain=%JOB_CHAIN_NAME%, order id=%ORDER_ID%, step =%ORDER_STEP_STATE%, error=%ERROR_TEXT%, check = %CHECK_TEXT%</NotificationInterface>
</NotificationMonitor>
<NotificationObject>
<JobChains>
<JobChain scheduler_id="scheduler" notifications="20" name="PDir/CreateGenerateOrder"/>
</JobChains>
<Timers>
<Timer>
<JobChains>
<JobChain notifications="20" name="PDir/CreateGenerateOrder"/>
</JobChains>
</Timer>
</Timers>
</NotificationObject>
</Notification>
<Notification>
<NotificationMonitor service_name_on_success="OMS Mass Processing History">
<NotificationInterface service_host="OMS Interfacing Server" monitor_port="5667" monitor_host="dipsy.sos" monitor_encryption="XOR">order history id=%ORDER_HISTORY_ID%, job chain=%JOB_CHAIN_NAME%, order id=%ORDER_ID%</NotificationInterface>
</NotificationMonitor>
<NotificationObject>
<JobChains>
<JobChain scheduler_id="scheduler" notifications="20" name="PDir/CreateGenerateOrder"/>
</JobChains>
</NotificationObject>
</Notification>
</SystemMonitorNotification>
|
Following the description from above (about the schema):
1.Configuration for Notifications to a System Monitor: in that case it is op5 Monitor.
2.Specifies a System Monitor notification that includes a command line invocation and the JobScheduler objects:
Job Chains
Job Chains for these solutions have to be placed under \live\notification. Four Job Chains were implemented for this solution and they have the following functions:
...