We often encounter queries on JDE Adapter inbound operation. Some troubleshooting steps for Inbound for JD Edwards Adapter are listed below:
1. Make sure the ping command is successful to the JD Edwards Enterprise One Server viz ..EnterpriseServer (ES) and TransactionServer.
2. If you are using host names in jdeinterop.ini / jdbj.ini / tnsnames.ora etc.. configuration files, make sure the host name to IP address mapping is
done in etc/hosts file or the host name has a DNS entry.
3. Verify that the JDE Transaction Server is running.
4. Verify that there are event types defined in JDE server.
5. Verify that the subscriber and subscription to the events are defined in JDE server.
6. Verify that the event and subscription status are active in JDE server
7. Verify that the configuration is correct for the JDE server address, port, Username, Password, Environment, Role and that the configuration files are
in the class path.
JDE inbound mechanism is different from other Adapters such as JDBC. JDE Adapter does not poll events from the Event Table, but polls the Real-time events
in the JDE Transaction Server. The event type may not be defined or subscription to the events may be not defined in the JDE Server. Generate an event through
Companies Application. See "Applications" section below.
Working with Companies Application - P0010. This application is used for generating RTCOOUT event.
Event Subscription Application - P90702A. This application is used to configure event subscription for users.
Hope this information was useful .Meet you all soon in my next blog !