But, that itself wont make the Applications safe enough to make it Externally Deployable.
Oracle E-Business Suite within DMZ must be carried out after a careful planning, and it is advisable to have an external application server for the external purposes.
DMZ can be done in a better way if a reverse proxy server is configured to talk to the external application server.
Steps to configure Oracle Applications to make it externally Deployable within DMZ.
Step 1 - Only Internal application Server and Database.
1) Run pre - clone steps for the internal application server.
step 2 - Copy the internal application server to the external box.
1) run post clone on the external application server.
2) run addnode to add this node within the E-business Suite.
step 3- Prepare for DMZ (with Standalone Apache Server that acts as the Reverse proxy server)
1) Setup the Apache Server to act as the standalone Reverse Proxy server (Note 287176.1)
step 4 -
1) Run sqlplus
2) Update Node Trust Level
3) Upgrade list of responsibilities
4) Update Home Page Mode to Framework
5) Update Oracle E-Business Suite Applications Context File
6) Run AutoConfig and Restart Oracle HTTP Server
7) After a few changes in the Reverse proxy server, the oracle applications will be available for external access.
P.s.- I shall explain more in detail in the future posts...
Can we have a Single Application Server connected to Reverse Proxy server
ReplyDelete