E1: OUTBND: How to Disable Enterprise Server Trigger Message to RTE
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
Currency Review - 1/21/2014
The RTE system is designed to deliver messages in two ways to the transaction server. When an RTE is generated from a BSFN, a server level trigger is invoked notifying the transaction server that an RTE event is ready to be delivered. The second method is from the transaction server side where it continues to poll the F90710 table to see whether events exist which need to be delivered. These methods together guarantee the quickest delivery of RTE messages to another system.
In the first method (server trigger) an OCM record to added to System and Server Map which identifies the RTE server and the listening port on that server. The trigger message is sent via that listening port connection.
In some cases we have found that the security server kernel might crash if the jdenet listen port on the RTE server does not match the port number listed for RTE in the System and Server Map. There also might be some other network reason the trigger is unable to be delivered to the transaction server. In these cases, you will find error messages within the jde logs.
The error message found in the Enterprise Server jde.log:
1297186 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=146, msgHost=<RTE IP Address>, msgPort=7015, sendingHost=127.0.0.1, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=1297193, resKrnl=0, msgFlags=0.
The error message in the Call Object Kernel log:
Unable to find location of Transaction server host and port
Warning: could not send trigger to app server for event 1, due to error 8. Is server up?
Under these circumstances it is possible to disable the Enterprise Server trigger from sending a message to the RTE server. The events will still be processed since the RTE server will continue polling and retrieving records directly from the F90710 table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms