<value_format>1</value_format>
<value_format_string>STATIC</value_format_string> <value_scope>1</value_scope> <value_scope_string>AFTER</value_scope_string>
</test>
<test>
<format>1</format>
<format_string>COMPARISON</format_string> <field_id>VNDR02</field_id> <field_scope>1</field_scope> <field_scope_string>AFTER</field_scope_string> <diff_field_id /> <diff_field_scope>1</diff_field_scope>
<diff_field_scope_string>AFTER</diff_field_scope_string> <condition>9</condition> <condition_string>IN</condition_string> <value>abc,def,ghi</value> <value_format>1</value_format> <value_format_string>STATIC</value_format_string> <value_scope>1</value_scope> <value_scope_string>AFTER</value_scope_string>
</test>
</tests>
Controller
This process reads the XML triggers from the AIF.TRIGGER.OUT queue and sends them to the relevant Java processor, based on the header information contained in each XML document.
1.Edit the /AEF/controller.properties file to reflect the iSeries name and the MQSeries Manager that was setup earlier on the iSeries.
2.A shell script is provided to start the AIF controller (/vendorConnect/aifcntrlr.sh). On the last line, insert your iSeries name and the port for the instance of WebSphere that you are using:
java
com.geac.erp.system21.aif.toolkit.Controller
3.Call the OSLVCD3/AIFCNTRLR CL program. The program runs the script. To run the CL program, enter:
CALL OSLVCD3/AIFCNTRLR
When this has run, the following three jobs should be running within QEJBSBS:
QP0ZSPWP
QZSHSH
AIFCNTRLR
They may be identified because the will be running under the user profile of whomever started them.
You may want to schedule this job to stop and start daily or after power downs. However, note that there should be a delay prior to starting this process to allow WebSphere to start the various application servers first. You may achieve this by creating a CL program to start WebSphere and then call AIFCNTRLR with a DLYJOB command in between. The delay may need to be several minutes. You may have to experiment to see what is necessary.
Chapter 4. Installing and setting up vendor.connect 91
