E1: OUTBND: How to Disable Enterprise Server Trigger Message to RTE
(Doc ID 1310963.1)
Last updated on NOVEMBER 01, 2018
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
The RTE system is designed to deliver messages in two ways to the transaction server. When an RTE is generated from a business function(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:
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document