Practical Guide for Implementing Shared Application File System

By Venkat Perumal

Objectives
 

 

Overview of Shared File System Difference between Shared File System and Shared APPL_TOP Steps to Implement Shared File System Shared Disk resource system management solutions Conclusion

Oracle Application Architecture 3-Tier Architecture

Three Tier Architecture

  

Desktop Tier Application Tier Database Tier

Oracle Application File System

Shared Application File System



Oracle in an attempt to improve scalability and administrative options in E-Business 11i application, Eintroduced the Shared Application File System. The Shared File Application System helps to consolidate an 11i application code tree in a multi-node environment. multiIn a shared application tier file system installation, the APPL_TOP, COMMON_TOP, and Applications technology stack are installed on a shared disk resource mounted to each node in the system. These nodes can be used to provide standard application tier services, such as forms, web, and concurrent processing.

Shared File System

Shared Application File System

Database Files Application Tier Files

Data

DB

APPL

COMN

ORA

Oracle Application database files

Oracle Home for RDBMS Oracle Apps Product files Common Files (Log,Output,Java and HTML) Apps Tech Stack 8.0.6 and iAS

Common for all nodes for Shared File structure

Shared APPL_TOP
Database Files Application Tier Files

Data

DB

APPL

COMN

ORA

Oracle Application database files

Oracle Home for RDBMS Oracle Apps Product files Common Files (Log,Output,Java and HTML) Apps Tech Stack 8.0.6 and iAS

Common for all nodes for Shared APPL_TOP

Advantages of Shared Application File System



 

Improved scalability: It s easier to add a new node. Shared Application File System offers simplified scripts to add a new node with a reduced down time window. Since the changes are visible across all nodes, patches needed to be applied only once. Also, upgrade process time is significantly reduced. Overall disk requirement is greatly reduced. Daily Application Administrative duties such as custom code migration have been simplified. Any changes made in the shared application tier file system are immediately visible on all nodes

Practical ways to implement Shared Application File System

Shared Application File System in new deployments:

Implementing Shared File System in a Multi-Node Multienvironment

Prerequisites: Prerequisites:  Oracle Universal Installer (Minimum Version 2.2)  TXK Autoconfig Templates (RUP O or Higher)  TXK Technology Stack (Min Pack D)  AD Mini Pack (Mini Pack I or Higher)  iAS Patch (Oracle HTTP Server Rollup 5 or higher)  Global Snapshot

Implementing Shared File System in a Multi-Node Multienvironment

Node 1 (Primary Server) Node 2 (Secondary Server)

Concurrent Manager, Reports, Admin

DB

Web, Forms, Discoverer

Implementing Shared File System in a Multi-Node Multienvironment

    

Execute merge Script Copy clone directories Execute rapid clone script Implement shared file scripts Add nodes

Implementing Shared File System in a Multi-Node Multienvironment



Node 1 and Node 2 will be merged as part of the shared file system implementation exercise. Assume that Node 1 is the primary server where concurrent managers/reports/admin services are installed and on Node 2 Web, Forms and Discoverer services are installed. On the primary server (node 1), the first step is to execute the preclone script to generate the manifest for merge. Execute the following script located on COMMON_TOP/admin/<CONTEXT_NAME>/

Implementing Shared File System in a Multi-Node Multienvironment

perl adpreclone.pl appsTier merge Running adgenhfver.pl with command... Perl /u02/ppconctest/testappl/ad/11.5.0/bin/adgenhf ver.pl isPrimary=y applsysusr=APPLSYS tempdir=/u02/ppconctest/testcomn/temp Please enter the APPS User [APPS]: APPS Please enter the APPS password: <appspassword> This is the merge Primary node:

Implementing Shared File System in a Multi-Node Multienvironment

APPL_TOPs belonging to PPTEST, that can be merged with AT_pak365devdb01: AT_pak365devap02(FORMS, WEB) (secondary Server) AT_pak365devdb01(ADMIN, CONCURRENT_PROCESSING) (primary server) Do you want to include AT_pak365devap02 in the merge ? [y]: Do you want to include AT_pak365devdb01 in the merge ? [y]: Generating the high version files manifest. This will take some time, please wait....................... You can now go ahead and run the preparation on the subsequent node(s) while this process completes. (execute the merge script on secondary server) Running Rapid Clone with command...

Implementing Shared File System in a Multi-Node Multienvironment

perl adpreclone.pl appltop merge Running adgenhfver.pl with command... perl /u02/ppformstest/testappl/ad/11.5.0/bin/adgenhfver.pl isPrimary=n applsysusr=APPLSYS tempdir=/u02/ppformstest/testcomn/temp Please enter the APPS User [APPS]: apps Please enter the APPS password: <appspassword) Current APPL_TOP: pak365devap02 This is a subsequent node to be merged into the primary node. Downloading the high version files manifest from the database... Found the manifest for merging pak365devap02 and pak365devdb01 using pak365devdb01 as the Primary node. sqlplus -s apps/pwd4pd @/$AD_TOP/patch/11.5.0/sql/admsnlst.sql DEV pak365devap02, pak365devdb01 APPLSYS $APPL_TOP/admin/out/hfilever_appl_top.txt Nhfilever_appl_top.txt N Manifest located in: $APPL_TOP/admin/dev/out/hfilever_appl_top.txt Running Rapid Clone with command... $APPL_TOP/admin/out/hfilever_appl_top.txt N

Implementing Shared File System in a Multi-Node Multienvironment



As the manifest is generated, copy the contents of clone directory under $COMMON_TOP/clone/appl/<NODE2> from secondary server onto the primary server directory $COMMON_TOP/clone/appl/ on node 1.

Implementing Shared File System in a Multi-Node Multienvironment

Implementing Shared File System in a Multi-Node Multienvironment

In order to generate a new autoconfig.xml for the merged APPL_TOP, execute the following the rapid clone script on Node 1. The clone script merges the APPL_TOP s; by comparing the template files on the Forms tier with concurrent manager clone directory. perl adcfgclone.pl appsTier This script is widely used during rapid clone process where it asks serious of questions related to the new environment and based on the new location, server etc, the script recreates the environment. During the merge process, following information will be displayed in the log file. Log file would reflect changes that occurred during the merge and file names and versions copied from the two APPL_TOPs. Executing merge appl top for JRI merge merge jri files with command: JRI log file located at, $APPL_TOP/admin/<NODE1>/out/jri_logfile.txt JRI report file located at, $APPL_TOP/admin/<NODE1>/out/jri_report.txt


Implementing Shared File System in a Multi-Node Multienvironment

  

Generate JAR files Generate message files Relink executables

Enable shared file system on the Primary Server

cd $FND_TOP/patch/115/bin perl -I $AU_TOP/perl txkSOHM.pl Absolute path of Application's Context XML file: $APPL_TOP/admin/DEV_NODE1.xml Type of Instance [primary/secondary] : primary Absolute path of 8.0.6 Shared Oracle Home : /u02/devora/806 Absolute path of iAS Shared Oracle Home : /u02/devora/iAS Absolute path of config top : /u02/devcomn/conf/node1

Adding new nodes to Application file system

Using a single disk resource, shared Application file system should be mounted onto secondary server or Node 2, to configure additional nodes. Source the current environment file, and execute the following command to add new nodes. $ cd $AD_TOP/bin $ perl adclonectx.pl sharedappltop contextfile=$APPL_TOP/admin/DEV_NODE1.xml Followed by $ cd $AD_TOP/patch/115/bin $ perl -I <AU_TOP>/perl txkSOHM.pl Before executing this script, a separate directory to store instance specific tech stack file should be created. If you have more than 2 nodes in your setup, above script can be used to additional nodes.


Major Operating System requirements



All Application nodes should be running on the same operating system with similar kernel and OS patches. Shared File System is supported only in UNIX. Windows operating system is not supported.

Shared Disk resource system management solutions



Disk must be shared among multiple servers to support the architecture. Adequate protection against single point of failure. Robust Solution - NAS/SAN configurations which includes Sun StorageTek, Red Hat Linux Global File System, VERITAS File System, Network File System (NFS) mounted disk or a disk array, NetApps custom solution for Oracle shared file system and Dell's equal logic SAN

Example

DNS Mapping http://apps.itc.com ..192.168.100.10 http://apps.itc.com .. 192.168.100.10 http://apps.itc.com .. 192.168.100.10

Questions