IBM SG24-6526-00 User Manual
Chapter 4. Installing and setting up vendor.connect
89
4.2.7 Work Management Trigger Handler for the iSeries
The OSLVCD3/TRGRHNDLR CL program is provided to start the Work Management Trigger
Handler. The program runs a shell script, which is found in the vendorconnect folder on the
iSeries (trigger.sh). To run the CL program, enter:
Handler. The program runs a shell script, which is found in the vendorconnect folder on the
iSeries (trigger.sh). To run the CL program, enter:
CALL OSLVCD3/TRGRHNDLR
After the program runs, the following three jobs should be running within QEJBSBS:
QP0ZSPWP
QZSHSH
VCTRIGGERS
These files may be identified because they will run under the user profile of whoever started
them. You should submit this program to run automatically as part of any day start routines or
after an IPL.
them. You should submit this program to run automatically as part of any day start routines or
after an IPL.
4.2.8 Active Architecture framework
The Active Architecture framework handles the processing of the triggers in two steps. The
publisher and the controller between them convert the triggers so that they are sent to the
correct Java processor.
publisher and the controller between them convert the triggers so that they are sent to the
correct Java processor.
Publisher
The publisher process picks up the raw database trigger messages placed on MQSeries.
TRIGGER.OUT queue by the OSLWFF3 and WF500A programs. Then it converts them to
XML messages and puts them on the AIF.TRIGGER.OUT queue.
TRIGGER.OUT queue by the OSLWFF3 and WF500A programs. Then it converts them to
XML messages and puts them on the AIF.TRIGGER.OUT queue.
Verifying whether folders have write authority
You should load the AEF, com, and com.geac.erp.system21.aef folders on the iSeries so that
they are directly off the root directory in the file structure. Use the WRKLNK command to
ensure that these folders are all writable:
they are directly off the root directory in the file structure. Use the WRKLNK command to
ensure that these folders are all writable:
WRKLNK '/<directory>'
Select option
9
to view authority. Assign
*PUBLIC *RWX
authority.
Checking the properties file
Check AEF/TriggerHandler.properties file to ensure that the MQSeries names correspond to
those that are set up in the MQSeries setup in 4.2.6, “MQSeries” on page 88.
those that are set up in the MQSeries setup in 4.2.6, “MQSeries” on page 88.
Updating the event documents
There are events (XML documents under the com.geac.erp.system21.aef/xml folder) that
filter out any unwanted messages. To reduce the amount of data initially held in the
vendor.connect database, these events filter based on the suppliers that currently use
vendor.connect. This enables a vendor.connect user to gradually roll out the system to more
suppliers, until the majority are using it, at which time the Supplier Filter Rule (but not the
other rules, which are an integral part of the operation of the system) can be removed
completely.
filter out any unwanted messages. To reduce the amount of data initially held in the
vendor.connect database, these events filter based on the suppliers that currently use
vendor.connect. This enables a vendor.connect user to gradually roll out the system to more
suppliers, until the majority are using it, at which time the Supplier Filter Rule (but not the
other rules, which are an integral part of the operation of the system) can be removed
completely.
These events are machine specific. Therefore, you must change the folder names to match
the same name as your iSeries server.
the same name as your iSeries server.
Changing the folder names
There are two folder names that you must change. One is under
com.geac.erp.system21.aef/xml/rules, and one is under
com.geac.erp.system21.aef/xml/rules, and one is under