 |
| |
| By Shahid Parwez Parwez |
|
|
|
 |
| |
- Basically Shared APPL_TOP's means sharing APPL_TOP and COMMON_TOP across the Application Servers.
- ORACLE_HOME and 8.0.6 ORACLE_HOME can only be shared if operating system on all application severs are same.
|
|
|
|
| Benefits |
| |
- Administration tasks only need to be performed on any one
node in the system
- Application patches only need to be applied to any one node in
the system
- Allows the use of "Distributed AD" to reduce downtime (see
MetaLink 236469.1)
- Reduces overall disk space requirements
- Makes it easier to add additional nodes to your Applications system
- Create single node clones from a shared APPL_TOP multi node
system
- Merge APPL_TOP’’s from different application tiers into a single
TOP APPL_TOP
|
|
|
|
| Disadvantages |
| |
- Single point of failure
- Performance might be an issue, if shared APPL_TOP's filesystem will be a nfs mount APPL_TOP's filesystem will be a nfs mount point.
|
|
|
|
| Implementation |
| |
| Requirement |
- The system must be configured for AutoConfig
- AD mini AD mini--pack H (2673262) must be applied (if on 11.5.8 or lower).
- The environment must be on ADX mini--pack D (3130740) or later.
- The Oracle Universal Installer must be patched to the version 2.2.0.19. Apply patch 3567364 to the iAS and database ORACLE_HOME.
|
|
|
|
| Implementation Contd. |
| |
- If the tech stack for the applications environment was created
with Rapid Install 11.5.8 or earlier, you need to regenerate the
Applications Context File:
- $ cd cd /bin
- $ perl perl adclonectx.pl sharedappltop \
contextfile=<existing Applications Context File>
- This will create a new Applications Context File that
convention < to the standard naming convention <sid>_<host>.xml.
- Run AutoConfig:
- $ cd cd /bin
- $ adconfig.sh adconfig.sh contextfile=<Applications Context File>
|
|
|
|
| Implementation Contd. |
| |
- If the tech stack for the applications environment was created
with Rapid Install 11.5.8 or earlier, you need to regenerate the
Applications Context File:
- $ cd cd
/bin
- $ perl perl adclonectx.pl sharedappltop \
contextfile=<existing Applications Context File>
- This will create a new Applications Context File that
convention < to the standard naming convention <sid>_<host>.xml.
- Run AutoConfig:
- $ cd cd
/bin
- $ adconfig.sh adconfig.sh contextfile=<Applications Context File>
- Adding node.
- Make the APPL_TOP and COMMON_TOP directories accessible to Make
the target node. A NFS file system solution is usually implement the to
meet this requirement. You must retain the same absolute path for the
mount points of the shared APPL_TOP and COMMON_TOP directories.
- Software Minimum Version Verify Command
- Perl 5.005 perl –version
- JDK 1.3.1 java –version
- Zip 2.3 zip –v
- Prepare the source node. Login to the node whose APPL_TOP you are sharing and execute the following commands:
- $ cd cd <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>
- $ perl perl adpreclone.pl adpreclone.pl appsTier
- Clone the technology stack from the source system to the target. Use the following steps as a guide:
- Use the tar utility to create a backup the source <806 ORACLE_HOME> and < iAS ORACLE_HOME>. Copy or ftp to the target node and untar into a directory containing the same absolute path as the source system
- Copy the $HOME/identitydb.obj identitydb.obj file from the source node to $HOME/ identitydb.obj on the target node
- Login to the target node you are adding and execute the followin commands:
$ cd cd <AD_TOP>/bin
$ perl perl adclonectx.pl sharedappltop \ contextfile=<Applications Context file of the sourcenode>
$ cd cd <COMMON_TOP>/clone/bin
$ perl perl adcfgclone.pl adcfgclone.pl appsTier appsTier <Applications Context file of the new node>
- When running adcfgclone.pl , you will be prompted for the “node types node types”. Enter
- the types that the node you are adding is supporting. For example , if the node is
- a forms/web server, answer “Yes Yes” to the questions “Do you want to add forms
- server node?” and “Do you want to add web server node? ” as shown in the
- sample output from adcfgclone.pl below:
Enter the APPS password [APPS]: apps
Do you want to use a virtual hostname for the target node (y/n) [n] ?:n
Target system database SID [ppscde1]:ppscde2
Target system domain name [corp.pbgc.gov]: corp.pbgc.gov
Target system database server node [solcde04]: solcde04
Does the target system have more than one application tier server node (y/n) [y] ?:y
Target system concurrent processing node [solcde04]:solcde04
Target system administration node [solcde04]:solcde04
Target system forms server node [solcde41]:solcde41
Is the target system APPL_TOP divided into multiple mount points ((y/n) [n] ?: n
Target system APPL_TOP mount point [/apps/ppsapps1/ppscde1appl]: /apps/ppsapps2/ppscde2appl
Target system COMMON_TOP directory [/apps/ppsapps1/ppscde1comn]: /apps/ppsapps2/ppscde2comn
- At this point, you should have a new functioning application tier server configured for the services you defined. If you converted from a single node to a multi node shared APPL_TOP as described above, then the URL for the applications login page will change to reflect the hostname of the forms/web node.
- After converting to a shared APPL_TOP, check the 9iAS apache error log for entries similar to:
[Sun Jul 11 22:53:21 2005] [error] [client solcde41] Symbolic link not allowed:
/d01/tst11i/tst11icomn/
- If this error is being logged, then change the “--FollowSymLinks” parameter in the apache httpd.conf file to “+FollowSymLinks” to resolve.
- Also, we have found that when running AutoConfig on the original single tier node, you should also run AutoConfig AutoConfig on the new forms/web tier afterwards.
|
|
|
|
| Conclusion |
| |
- Sharing the APPL_TOP file system is not suited for every environment but if you have multiple application tiers or want to convert a single node into a multi node, it can significantly reduce patching and maintenance. However, carefully consider the trade-offs you may need to make.
- At a minimum, ensure the shared NFS file system is a configuration high availability storage device in a RAID configuration with large network communication bandwidth.
|
|
|
|
