E-IB: Configuring Integration Broker Gateways to Combine Protected Internal Network and Inbound Messaging from External Parties
Last updated on APRIL 22, 2015
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.48 and later
Information in this document applies to any platform.
On PeopleTools 8.48 - 8.5x, having Integration Broker (IB) messaging working fine inside an internal local network with no access to or from wider networks.
A need arose to also receive inbound IB messages from an external sender, but at the same time keep the internal network as closed and protected as possible.
For that purpose extra web server and app server were installed in an external network, with the only port open to the internal one being for database connection.
Since there are no open ports for http traffic in or out (per the preferred configuration), the local IB gateway cannot receive data directly from the external sender.
And if a gateway configuration is attempted on the "external" PIA web server, it presents a challenge because it is unreachable to the internal app and web severs:
Being unreachable to internal app servers, it cannot be set up as local gateway; being unreachable to internal web servers, it cannot be set up as remote gateway.
What IB gateway configuration(s) would work in this architecture to both keep the internal IB traffic as before, and also receive inbound IB traffic from outside?
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