Identified the event type you want to subscribe to.Identified the event type you want to subscribe to.Identified the service or services that generate an event you want to subscribe to (if you want to subscribe to an audit event, exception event, or JMS delivery failure event).Written the event handler that will execute when the identified event occurs.
to add a new subscriber.In this field... | Specify... |
Service | The fully qualified name of the event handler that will subscribe to the event (that is, the service that will execute when the event occurs). You can either type the name in the Service field or browse to locate and select the service from a list. Example: sgxorders.Authorization:LogAuthTrans |
Filter | A pattern string to further limit the events this event handler subscribes to. Filters vary depending on the event type you are subscribing to. For example, if you are subscribing to an audit or exception event, create a filter to specify the names of services whose events this event handler subscribes to (that is, the services that, when executed, will invoke the event handler specified in Service). You can use the * character as a wildcard (this is the only wildcard character recognized by this pattern string). The pattern string is case sensitive. For more information about creating event filters, see Creating Event Filters. |
Comment | An optional descriptive comment about this subscription. |
Enabled | Whether the subscription is active or inactive. Set to true to activate the subscription. Set to false to deactivate the subscription. (This allows you to temporarily suspend a subscription without deleting it.) |
Note: | Integration Server saves information for event types and event subscriptions in the eventcfg.bin file. This file is generated the first time you start the Integration Server and is located in the Integration Server_directory \config directory. Copy this file from one Integration Server to another to duplicate event subscriptions across servers. |
