Verify PROPATH and Event Recording
This test ensures that the QAD Enterprise Applications database set was properly configured with the correct PROPATH and database connections. It verifies that an event is recorded when a change occurs in the source application.
It assumes that a suitable QXO-adapted QAD Enterprise Applications is available as a source application.
To perform the test, do the following:
1 Start a browser session on the client and set the URL to:
http://<qxtendhost>:<port>/<QXO webapp>
2 In the QXO Console, click the Configuration tab and then click Event Types under your source application.
3 Edit the source application event types and select the Active check box for the cm_mstr event type.
4 Launch a QAD Enterprise Applications session. Use Customer Maintenance (2.1.1) to create a customer.
If the following error message displays in Customer Maintenance, the PROPATH is incorrect:
** "filename" was not found. (293)
Correct the PROPATH for the QXO database set and create new startup scripts.
5 Go to QXtend Outbound Control (36.16.19) and verify that the Enable QXtend Outbound option is set to Yes. This setting is required to log events to the qxevents database.
6 From your QAD Enterprise Applications session, access the Progress Editor. From Tools|Data Dictionary|Database, choose Select Working Database and select the qxevents database.
7 Choose Admin|Dump Data and Definitions|Table Contents (.d) file.
8 Choose the ert_app_event table, press Go, and specify an output file name.
9 Open the output file in a text editor and verify that it contains a record similar to the following:
1 "0x0057d684" "TMP1497" "mfg" "" "cm_mstr" 2453319.175590277 "mfgprod" 1 3
If no records display in the file, one of the following may have occurred:
• The cm_mstr event type is not active. Restart this test and select the Active check box for cm_mstr in the QXO Console.
• The source application database schema was not updated correctly during installation. Verify that replication write and replication delete triggers exist for the cm_mstr table. If these triggers do not exist, you must reinstall the adapter to QAD Enterprise Applications.
To verify the existence of the triggers:
1 From your QAD Enterprise Applications session, access the Progress Editor.
2 From Tools|Data Dictionary|Database, choose Select Working Database and select the qaddb database.
3 Choose Database|Reports|Trigger.
4 In the Trigger Report, verify that the following information displays:
|
Table/Field Name
|
Event
|
Check CRC
|
Flags
|
Procedure
|
|
cm_mstr
|
RP-DEL
|
no
|
|
cmrd.t
|
|
|
RP-WRI
|
no
|
|
cmrw.t
|