|
|
Hi,
We have EBS 12.1.3 with 12c database running on PRD, UAT & DEV instances. Currently, iSupplier is configured by having a new network interface with a different IP address and its working fine on PRD. As part of Lift&Shift to Oracle Cloud @ Customer where there is a limitation as such that the configuration requires oracle internal application middle-tier server to have at least two network interfaces “which is not visible in OCC”. One network interface is required for the external entry point and another for the internal entry point. These network interfaces must be configured to resolve to two different hostnames in the DNS.
We did check the MOS reference on Oracle E-Business Suite R12 Configuration in a DMZ ( Doc ID 380490.1 ).
What we would like to know is that, could we proceed with the below approach of having an alias manipulation without the need to have additional host/licenses?
> Add a new alias of isupplier referring to ebs-apps-node1 & ebs-apps-node2. New alias will act as a hostname as part of the configuration.
Ex:-
172.nnn.nnn.1 ebs-vm1-host ebs-vm1-fqdn supplierweb01(with FQDN)
172.nnn.nnn.2 ebs-vm2-host ebs-vm2-fqdn supplierweb02(with FQDN)
> Build/Clone existing context file with the new alias hostname along with a new port (to avoid port conflict)
Ex:- Two different context files
<SID>_ ebsappnode1.xml & ebsappnode02.xml ---- Usual EBS application Context XML files for two different nodes
<SID>_ supplierweb01.xml & <SID>_ supplierweb02.xml ---- For iSupplier context files for two different nodes
> For all external connections at LB level, reverse proxy intercepts the requests and forward it to existing internal web-tier.
Please advise...
Regards,
Ata
|
Locked
