Oracle E-Business Suite R12 Configuration in a DMZ - Linux

Oracle E-Business Suite R12 Configuration in a DMZ

Index :

   1. OS verification.
   2. Backup the source system.
   3. Copy the source application tier to the DMZ machine.
   4. Create user and group for the DMZ machine.
   5. Create directories for the target DMZ and give them the required grant and ownership.
   6. Configure the DMZ.
   7. Run autoconfig on both application tiers and the database tier.
   8. Start and check the services.
 
OS verification

 i)  Create OS user

 ii)  Host file format

     The  “/etc/hosts”  file  should use the  following  format  and Hostname          

        IP Address   Full Qualified Hostname    alias

 Example:
       10.10.19.39   irecruit.oracle.com     irecruit

        10.10.11.31   internal.oracle.com    internal


iii) Mount Point / Storage Details

     All disks in a disk group should have the same I/O density (Megabytes per       second of transfer   rate per Gigabyte of capacity)
     Metalink note id: Oracle E-Business Suite R12 Configuration in a  DMZ (380490.1)

iv)  Software Requirement

       Ar,ld,make ,X Display Server.

 v)  Login into the Source and shut the application services.

 vi) Take a backup of the application directories and transfer it to the target server.

Configuring DMZ

 
1.    Prepare the source system, copy it to the new node (external) and configure it.

2.    Execute adcfgclone.pl on new node
       perl adcfgclone.pl appsTier

3.    Shutdown Source Application.

4.    Optional: Adding a New Node to an Existing System
      After adcfgclone.pl completes, source the Applications environment and run the following   commands on the target system :

        $ cd [COMMON_TOP]/clone/bin
        $ perl adaddnode.pl

5.    On External Tier, further navigate to $COMMON_TOP/clone/bin directory and run the               adcfgclone.pl with appsTier.

       perl adcfgclone.pl appsTier

6.    Once this process completes successfully shut down the services change the following parameters in the .xml file

On Secondary Node (External node) :
Load application envoronemnt and change as below.
vi $CONTEXT_FILE

<oa_system_config>
         <TIER_DB oa_var="s_isDB">NO</TIER_DB>
         <TIER_ADMIN oa_var="s_isAdmin">NO</TIER_ADMIN>
         <TIER_WEB oa_var="s_isWeb">YES</TIER_WEB>
         <TIER_FORMS oa_var="s_isForms">NO</TIER_FORMS>
         <TIER_NODE oa_var="s_isConc">NO</TIER_NODE>
         <TIER_FORMSDEV oa_var="s_isFormsDev">NO</TIER_FORMSDEV>
         <TIER_NODEDEV oa_var="s_isConcDev">NO</TIER_NODEDEV>
         <TIER_WEBDEV oa_var="s_isWebDev">YES</TIER_WEBDEV>
         <config_option type="techstack" oa_var="s_techstack">as1013</config_option>
         <config_option type="techstack" oa_var="s_tnsmode">generateTNS</config_option>
         <config_option type="adx" oa_var="s_apps_version">12.1.3</config_option>
         <config_option type="techstack" oa_var="s_apache_mode">NORMAL</config_option>
         <ias_version oa_var="s_ias_version">10.1.3.5.0</ias_version>
      </oa_system_config>

7.    Run the node clean package as apps user

Load environemnt on DMZ (external node) and
 sqlplus /nolog
SQL> conn apps
Enter password:
Connected.
SQL> exec fnd_conc_clone.setup_clean;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.

8.    Run autoconfig in the series as stated below
A.    Database tier
B.    Primary apps tier
C.    DMZ (External tier)

9.    After the completion of the autoconfig run the following script as apps from the primary node :

sqlplus apps/welcome @$FND_TOP/patch/115/sql/txkChangeProfH.sql SERVRESP

This would change the profile options hierarchy type values to SERVRESP.

10.    Run autoconfig again on the primary node.

11.    After the completion of the script start the primary instance.

12.    login as sysadmin and change the following profiles at server level

This Completes the DMZ Configurations !!!!

13. Expose the responsibility to the external tier as per the requirement as seen in the following
screen shot.