QXO Source Applications
Source applications are the specific databases from which the QXO event service extracts data. Each source application database that shares a unique schema—for example, all QAD Enterprise Applications eB2, SP3 databases—can be managed under a single source application type. For version eB2.1 or above databases, this also extends to multiple domains that share a schema definition.
A source application type also lets you identify the specific event types—database triggers and/or business events—you want to extract from the databases within that type. Event types are essentially the tables within the source databases.
Source applications that employ DDP post business objects directly to QXO via the service interface API, and consequently do not require an event service. For DDP source application types there is no need to define databases, domains, or business object groups.
You can also define business object groups for any source application. Business object groups enforce the correct chronological sequencing of data messages from dependent business objects. It is required, however, that all active event types of these business objects are all registered with the same event service. Each business object can belong to only one group.
Note: Business object groups cannot be defined for business objects that employ DDP.
In this first step, you define all the source applications from which you require data. You must also define a source application before you can update business objects or profiles.
In the QXO Console, click the Configuration tab to gain access to all the processing implementation services. Click the Source Applications node in the left-hand tree view. If it was not already displayed, the Source Application Types screen displays.
Click New in the Source Application Types screen. An entry line is added to the screen.
Creating a New Source Application Type
Specify the name of the new source application type.
Enter a description as required.
Select this option to indicate the source application type is active. The source application type must be active to be available on the Business Object and Profile tabs. In addition, the event service will not extract data from a source application unless the source application is active.
This setting indicates whether the source application type uses a rowid or object identifier (OID) to identify the data object that has changed. A rowid is an internal system-generated identifier used by the database, whereas an OID is an actual field on the table.
Source application types eB and eB2 use rowids only. Types eB2.1 and above can use either a rowid or OID.
Note: In order to use the OID index in eB2.1 or QAD SE you must first load the optional Enhanced Controls schema. For the QAD EE source application loading this schema is not required since by default the OID index is on.
The Use Rowids option is preset and cannot be changed for predefined source application types. Source applications that do not use rowids require the unique identifier in the data object to be specified. For details see Modifying Business Object Data Objects
Indicates if this source application posts event data directly to QXO. This setting cannot be changed for predefined source application types.
If this setting is selected, the source application node on the tree menu does not display further information—databases, domains, business object groups, and event types, for example.
Important: In order to load the QAD standard business objects and profiles, the business objects use the following predefined source application types provided with QAD QXtend:
If you choose to change the naming convention, the folders containing the QAD-standard business object XML to be loaded must be renamed to the defined source application type. See Importing Business Objects and Profiles
. The XML resides in QXOsrvInstallDir
Click Source Applications in the navigation tree to open the node. The active source application types display. Click it to open the Source Applications screen.
Click New to display the Source Application Details screen.
Source Application Details
Enter a code identifying a source application from which QXO messages originate. You use this code to identify the source application in the event services definition.
Enter a brief description as needed.
Calculated Field AppServer Parameters
In general, enter the AppServer name (–AppService) and the AppServer host (–H); for example:
-AppService qxoappservice -H co9906
In the example, the application service is qxoappservice and the host is co9906.
The AppServer Parameters field supports the use of calculated field programs documented in Implementing Calculated Fields
Note: If calculated field programs are not required to be executed on the AppServer, then this field can be left blank.
Additional values can be entered in this field. For details on AppServer parameters, see the Progress documentation.
Specify whether to suspend the source application on one or both of the following errors: database connection error and calculation error.
If you select Database Connection Error, the source application will be automatically suspended on database connection error; if you select Calculation Error, the source application will be automatically suspended on calculated field program error.
All QXO services only process events and messages of active source applications and ignore events and messages of suspended source applications. In addition, suspended source applications cannot be connected for any UI operations, such as source application configuration.
You can manually resume or suspend source applications through QXO Dashboard or batch process scripts. Batch process query shows the Suspended status.
When a source application is resumed, QXO services automatically reprocesses the extracted data and raw messages with the ERR status.
You can configure e-mail alerts to be sent on calculation and database errors to registered recipients. See QXO E-mail Alerts
Select this field to turn on WAN options. When it is selected, the following three options are displayed.
Enabling WAN Options can help to achieve better system performance and reliability when QXtend connects to a source application through a Wide Area Network.
Database Connection Max Retry Limit
Specify the maximum times for QXO to reconnect to the source application database after connection failed.
Note: If Suspend on Database Connection Error is selected, the system will not suspend the source application until it has failed to connect after multiple retries.
QXtend Adapter AppServer Parameters
Enter an AppServer (for example, qadsi_AS) that connects to source application databases and has the QXtend Adapter directory in the Propath. When this parameter is set, QXtend can run event consolidation on the AppServer instead of in event service, which can significantly reduce the time for event consolidation over a WAN connection. In general, the parameters include the AppServer name (-AppService) and the AppServer host (-H); for example:
-AppService qadsi_AS -H co9906
Monitor Events on Dashboard
Determines whether to monitor event counts on QXO Dashboard.
If the source application is connected through a WAN connection, it takes a long time to refresh the Dashboard. Before the refresh is completed, some information—such as the number of events processed—is not displayed; but you can use the buttons on the Dashboard.
Click Save to save the new source application.
Repeat these steps for each source application in the source application type.