The client listener provides a log of each transaction it processes. The log is placed in iwoevent.log in the directory specified by the IWOEVENT_HOME environment variable.
Note: The IWOEVENT_HOME environment variable must be created on the J.D. Enterprise Server. For more information, see Configuring EnterpriseOne for Outbound Transaction Processing.
When an event failure occurs, the event payload is saved to the local file system in a subdirectory of the IWOEVENT_HOME directory.
For example, if the IWOEVENT_HOME environment variable is set to d:\IWOEVENT, the iWay Application System Adapter for J.D. Edwards EnterpriseOne is not available, and you have the following alias:
edamcs1
The event information is saved to the following directory:
d:\IWOEVENT\edamcs1
The following is a sample portion of the log file.
...Event call begin... userId : JDE batchNumber : 0 transactionNumber: 102628 lineNumber : 2.000000 transactionType : JDEWO sequenceNumber : 1.000000 Request xml: ======================== <?xml version="1.0" encoding="UTF-8"?><jde><request><connection> <dsn /><user /><password /><sp><proc>JDEWO</proc> <data><ediUserId>JDE</ediUserId><ediBatchNumber>0</ediBatchNumber> <ediTransactionNumber>102628</ediTransactionNumber> </data></sp></connection></request></jde> ======================== Connection failed with Error connect socket failed: IO_DRIVERERROR WSAECONNREFUSED(274D) Payload dumped into file [g:\jdedwardsoneworld\ddp\b7333\outbound\ibiwfk\1055355515.xml] Event call begin... userId : JDE batchNumber : 0 transactionNumber: 102629 lineNumber : 2.000000 transactionType : JDEWO sequenceNumber : 1.000000 Request xml: ======================== <?xml version="1.0" encoding="UTF-8"?> <jde><request><connection><dsn /> <user /><password /> <sp><proc>JDEWO</proc><data><ediUserId>JDE</ediUserId> <ediBatchNumber>0</ediBatchNumber> <ediTransactionNumber>102629</ediTransactionNumber> </data></sp></connection></request></jde> ======================== Connection failed with Error connect socket failed: IO_DRIVERERROR WSAECONNREFUSED(274D) ...
The following is the sample request.
<?xml version="1.0" encoding="UTF?8"?> <jde> <request> <connection> <dsn /> <user /> <password/> <sp> <proc>JDESOOUT</proc> <data> <ediUserId>islywm</ediUserId> <ediBatchNumber>100</ediBatchNumber> <ediTransactionNumber>100100</ediTransactionNumber> </data> </sp> </connection> </request> </jde>
When the integration server receives the XML request from the event listener, it invokes the JDE Adapter to process the request. The adapter creates a J.D. Edwards XML request and executes the request against the EnterpriseOne system.
Note: No user ID or password information passes to the integration server from the EnterpriseOne Event listener. Secured communication from the EnterpriseOne Event listener to the adapter is not implemented.
The following is a sample request sent to J.D. Edwards EnterpriseOne.
<jdeRequest environment="DV7333" user="JDE" type="trans" sessionidle="300" session="" pwd="JDE"> <transaction type="JDESOOUT" action="transactionInfo"> <key> <column name="EdiUserId">islywm</column> <column name="EdiBatchNumber">100</column> <column name="EdiTransactionNumber">100100</column> </key> </transaction> </jdeRequest>
The following is a sample response from J.D. Edwards EnterpriseOne.
<jdeResponse type='trans' user='user' session='session1' environment='env'> <transaction type='JDESOOUT' action='transactionInfo'> <returnCode code='0'>XML Request OK</returnCode> <key> <column name='EdiUserId'></column> <column name='EdiBatchNumber'></column> <column name='EdiTransactNumber'></column> </key> <table name='F4201Z1' type='header'> <column name='EdiUserId'></column> <column name='EdiBatchNumber'></column> </table> <table name='F4211Z1' type='detail'> <column name='EdiUserId'></column> <column name='EdiBatchNumber'></column> </table> <table name='F49211Z1' type='additionalHeader'> <WARNING>No record found</WARNING> </table> </transaction> </jdeResponse>
iWay Software |