Chapter 4 Activating event-driven data exchanges 81
Creating a request using the eiexfer utility
To specify an immediate event-driven request for an employee whose record is
identified by the AR System server ID number 23456 from the employees’ data
exchange using a wait interval of 10 seconds and a retry count of 20:
eiexfer -x myserver -l jdoe -p password -s employees -r 23456
-i -w 10 -c 20 -n <instance name>
To specify an immediate event-driven request for a bulk exchange of all
employee records using the default wait time of 5 seconds and a retry count of
20:
eiexfer -x myserver -l jdoe -p password -b employees -i -c 20
-n <instance name>
To specify an event-driven request to transfer a record for an employee named
Tom Smith from the employees’ data exchange:
eiexfer -x myserver -l jdoe -p password -s employees -k “Smith Tom” -n
<instance name>
Completion codes returned by eiexfer
Data exchange requests that are submitted through the eiexfer utility return
completion codes that indicate the status of a request. These codes fall into several
categories, which are listed in Table 4-6.
The completion codes are listed in Table 4-7. A brief definition follows each
message in the table.
Table 4-6: eiexfer completion code categories
Category Description
0 Request completed successfully.
100-199 Request was not submitted to event-driven request queue.
200-299 Request was submitted, but the Integration Engine service could not be
notified to handle the request.
300-399 Request was submitted and the Integration Engine service was notified to
handle the request, but the completion status could not be obtained.
400-499 Request was handled by the Integration Engine service, but the data
failed to transfer. The request in the Application Pending form contains
the error message indicating the cause of the failure.
Table 4-7: eiexfer completion code messages
ID Number Message
0
Request completed successfully.
The event-driven request is complete and no errors were encountered
during the data transfer.
-101
Required parameters are missing.
One or more required parameters are missing from the event-driven
request. The request was not submitted for processing.
