In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




QXO Event Service Process
Event services are the QXO processes that initially connect to the qxevents database to identify what changes have occurred in the source application and then to the production database to extract the data and write it to the qxodb.
The actual process an event service follows is:
1
Poll for and identify an eligible event in qxevents.
2
Identify affected business objects in QXO.
3
Build a data object to hold the data.
4
Extract the data from qaddb into the data object.
5
Store the data object in qxodb.
Note: These steps are not applicable to business objects that employ DDP since these business objects are passed directly to the qxodb database in QXO.
An event service can extract data from source applications using either the table rowid or an OID on the database table. The event service does not extract data from a source application if the source application type is suspended. For details see QXO Source Applications.
Note: In QAD QXtend version 1.4, the XML format of event messages changed. Messages in the old format that were previously extracted and stored are converted to the new format when they are required.
Creating an Event Service
Event services are defined to operate with a specified set of source applications.
1
In the Configuration tab, click Event Service in the navigation tree. The Event Services overview screen displays.
2
Click New to create a new event service.

Event Services Configuration Parameters
Session Code
Enter a code (maximum 10 characters) for this service. Using a naming convention such as EVS<serviceName> makes it easier to identify the service as an event service later on.
Session Description
Specify a description (maximum 15 characters).
Polling Frequency
Enter the number of seconds for the service to wait between polls to the qxevents database.
Max Retry Limit
Enter the maximum number of times during a single session that the service will attempt to reprocess a failed application event (maximum 9999).
Alert Monitor Frequency
Specify the number of minutes between alert messages when the Alert Message Type is set to MSG and thresholds have been set. See Alert Message Types.
Number of Agents
Specify the number of agents to start for the service when the AppServer is started.
Events to Process
Enter the maximum number of events to be processed by a source application before switching to a different one. This is used only when an event service is defined with more than one source application, and is used to ensure throughput across all registered source applications.
Alert Message Types
Check the message types that you want to be raised as alert conditions for this profile. Choose one or all of the following: MSG (used for metric-related alert messages), ERR (errors), WRN (warnings).
Note: For details on configuring e-mail alerts for metric-related alert messages see QXO E-mail Alerts.
When you select MSG, additional options display.

Setting MSG Alert Metrics
The MSG alert metrics let you specify alert thresholds for Processed, Pending, or Error conditions. In Figure 2.19, a threshold on processed messages is set. If the defined threshold is reached, an alert is raised. Another alert will not be raised—although processing will continue—until the value specified in the Alert Monitor Frequency has elapsed. For example, if the Pending value is set to greater than 20 and the Alert Monitor Frequency is set to 10, if there are 100 messages pending an alert would be raised. If 10 minutes later there were still more than 20 messages pending, another alert would be raised.
Note: The type of conditions reflect the type of service being configured. For an event service, for example, the conditions relate to event processing. For the message publisher and message sender, the conditions relate to QDoc creation and QDoc delivery, respectively.
Operator
Choose the numeric operator for each processing condition.
Threshold
Enter the number of events to occur before an alert is issued.
3
Click Lookup to register source applications with this service. A lookup displays available and currently assigned source applications. Use the Add and Remove buttons to update the lists.

Source Application Lookup
4
Click OK to save and exit the Register Source Applications screen.
5
Click Save to save the event service configuration.
Note: Two Oracle source applications with the same logical name (specified in the connection parameters of the source application database) cannot be registered to one event service.
Registering Event Types with an Event Service
After you create a new event service, it appears under Event Service in the navigation tree. By default, all active event types in the event service’s registered source applications are automatically registered with it as well. However, you can configure an event service to only process specific event types so as to create dedicated event service instances for high-priority events, allowing them to be processed as soon as they arise. This is achieved through registering specific event types of a source application with an event service for processing.
1
Under Event Service in the navigation tree, click the event service you want to configure to display all its registered source applications under it.
2
Click a source application.
3
The Event Registration screen on the right shows that all active event types in the source application are automatically registered with the event service. Clear the Auto Register All Events option.

Event Registration (Default)
4
Click Register Events to register event types with this service.

Event Registration
5
A lookup window displays available and currently registered event types. Use the Add and Remove buttons to update the lists.

Event Registration Lookup
6
Click OK to save and exit the Register Events screen.
7
Click Save to save the event service configuration.