E1: COM Using JDE Interoperability COM Connector with a Firewall (Doc ID 627648.1)

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.

Symptoms

Using Interoperability clients via the COM connector or using XML system API with firewall in place.  The JDENet communication between the interoperability client and the JDENet listener, on the Enterprise Server, is not reliable as far as knowing which exact TCP ports will be used for communications back and forth, and does not stay on the same port as the original listening port.  When the Interoperability client connects to Enterprise Server, a new port is sent back, designating the real port which will be used for the actual transaction, and this port can be a random port available on the machine.  This poses a problem for knowing in advance which ports to open up through a firewall if the client is outside of the firewall.

Changes

 

Cause

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