Monday, May 13, 2013

Sharing The Application Tier File System in Oracle E-Business Suite Release 12: 384248.1


Sharing The Application Tier File System in Oracle E-Business Suite Release 12

Section 1: Overview

1.1 Shared Application Tier File System Concepts and Terminology

You can configure multiple application node machines working with a single Oracle E-Business Suite database node. This creation of a "multi-node" Oracle E-Business Suite instance is frequently done to lower cost of ownership (many small machines are cheaper than one big one), increase fault tolerance (one machine fails, others do not), or scale the instance (support more users and a greater load).
When configuring Oracle E-Business Suite to use a shared application tier file system, the application tier node can be configured to perform any of the standard application tier services, such as Forms, Web, and Concurrent Processing (Batch).
Note the following definitions:

Node

A node is a logical set of processes running on one hardware machine. Sometimes a node is also referred to as a "server" or an "instance". In a single-node installation of Oracle E-Business Suite, all the Applications processes (including the database processes) run on one node, whereas in a multi-node installation, the processes are distributed across multiple nodes.
A multi-node installation of Release 12 supports both shared and non-shared application tier file systems. An application tier file system consists of:
  • APPL_TOP file system (APPL_TOP and COMMON_TOP directories).
  • Application tier technology stack file system (OracleAS 10.1.2 and 10.1.3 Oracle Homes).
  • Instance Home (INST_TOP) file system. Each application tier has a unique Instance Home file system associated with it.
  • OraInventory directory which stores information about all the components installed in various Oracle Homes

Service

A service is a functional set of Oracle E-Business Suite application processes running on one or more nodes. Where applicable, the term 'service' is replacing the more traditional term of 'server'.

Application Tier Services

The following are the major application tier services:
  • Root services
  • Web Entry Point services
  • Web Application services
  • Batch Processing services
  • Other services

Primary Application Tier Node

A primary application tier node is the first application tier node where the APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home and OracleAS 10.1.3 Oracle Home are installed and configured.

Secondary Application Tier Node

A secondary application tier node is an application tier node where APPL_TOP, COMMON_TOP, 10.1.2 Oracle Home and 10.1.3 Oracle Home are visible and configured. The APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home and OracleAS 10.1.3 Oracle Home file system is mounted to this node from the primary application tier node, or from an NFS server.

Instance Home

Instance Home is the top-level directory that contains all the instance specific files associated with an Application Tier node (APPL_TOP, OracleAS 10.1.2 Oracle Home and OracleAS 10.1.3 Oracle Home, log files, pid files and certificates files). In a shared file system, each application tier will have a unique Instance Home, which should be located on the local file system.

1.2 Shared Application Tier File System Architecture

The Oracle E-Business Suite Release 12 architecture is a framework for multi-tiered, distributed computing. In this model, various services are distributed among multiple levels, or tiers, as shown in the figure below. Refer to Oracle Applications Concepts in the Oracle Applications Documentation Library to learn more about Oracle E-Business Suite architecture.
In a shared file system, all application tier files (with the specific exception of the Instance Home file system) are installed on a shared disk resource, which is mounted on each application tier node.Any application tier node can be configured to perform any of the standard application tier services, such as Forms, Web and Concurrent Processing (Batch) services. All changes made to the shared file system are immediately accessible to all application tier nodes.
Note:
  • For optimum performance, it is advisable to use a local file system for the Instance Home.
  • To implement a shared file system, all application tier nodes must be running the same operating system.


1.3 Shared Application Tier File System Layout

When configuring Oracle E-Business Suite to use a shared application tier file system, an application tier node can be configured to perform any of the standard application tier services, such as Forms, Web, or Concurrent Processing (Batch) services. An application tier will have a unique Instance Home associated with it that cannot be shared with other application tiers. You can configure the services running on an application tier node to match the node's intended role.
Note: In a shared file system, User ID and group ID should be consistent across all nodes to avoid file access permission issues. You must retain the same absolute path for the mount points of the shared file system on each node. The value for the context variable "s_atName" must be same across all the application tier nodes context files.

Example Shared File System
The following is an example of mount points shared on each application tier node:
  • COMMON_TOP: /d01/shared_mount/apps/apps_st/viscomn
  • APPL_TOP: /d01/shared_mount/apps/apps_st/visappl
  • OracleAS 10.1.2 ORACLE_HOME: /d01/shared_mount/apps/tech_st/10.1.2
  • OracleAS 10.1.3 ORACLE_HOME: /d01/shared_mount/apps/tech_st/10.1.3
  • OraInventory /d01/shared_mount/OraInventory
In the figure shown below, entitled "Shared Application Tier File System", Server-ap6012rt is the primary application tier node, and uses the file systems "/d01/shared_mount" and "/d01/local". The file system "/d01/local" contains the Instance Home, and "/d01/shared_mount" contains the APPL_TOP, COMMON_TOP, OracleAS 10.1.2 and 10.1.3 Oracle Home.
Server-ap6011rt is the secondary application tier node, and the shared file system "/d01/shared_mount" is also mounted on this node. The file systems "/d01/local/apps/<CONTEXT NAME for Server-ap6012rt>" and "/d01/local/apps/<CONTEXT NAME for Server-ap6011rt>"are only visible on the respective nodes.

1.4 Using a Shared Application Tier File System in an Oracle Cluster File System Environment

Note: OCFS2 patches are limited to customers with an Oracle Linux Support Subscription. For OCFS2 support and operating system details, refer to the Project: OCFS2 website.
  • Oracle Cluster File System (OCFS2) for Linux OCFS2 1.4 and higher is supported for Oracle E-Business Suite Release 12 application tier file systems.
    • System administrators may deploy both the APPL_TOP and INST_TOP on Linux-based OCFS2 shared-disk cluster file systems.
  • Oracle E-Business Suite Release 12 certification tests with OCFS2-based application tier shared file systems used the following configuration:
    • Oracle Enterprise Linux Version 5 Update 4 (OEL5U4 64-bit) running OCFS2 1.4.4
    • Separate volumes for APPL_TOP and INST_TOP storage (INST_TOP was also tested and is certified with local storage)
    • Oracle E-Business Suite application tier mount options used: rw, _netdev, nointr
    • Mount option datavolume was not used in the application tier mounts
  • For detailed instructions on configuring OCFS2, see OCFS2: A Cluster File System for Linux: User's Guide for Release 1.4 on the Project: OCFS2 website.

Section 2: Planning Deployment Options

2.1 Enabling Admin Capability for the Application Tier Node(s)

In a multi-node Oracle E-Business Suite instance, you can have more than one application node used for administration (to patch the instance). Verify and update the context file using the Oracle Applications Manager (OAM) Context Editor on all the application tier node(s)
Variable Name
Variable Value
s_appl_config_home
Same as s_at
s_isAdAdmin
YES

2.2 Enabling Concurrent Processing (Batch) Service on Application Tier Node(s)

In a multi-node Oracle E-Business Suite instance, you can have more than one application node where the Concurrent Processing (Batch) service is enabled. All the application node(s) where the Concurrent Processing (Batch) service is enabled should have the $APPLCSF and $FNDREVIVERPID environment variables set to the same value.  A shared file system should be allocated for the concurrent manager logs and reviver pids. Verify and update the context file using the Oracle Applications Manager (OAM) Context Editor  for all the Application Node(s):
Variable Name
Variable Value
s_applcsf
Same on all nodes
s_fndreviverpiddir
Same on all nodes
s_isAdConc
YES
s_isAdConcDev
YES
s_batch_status
enabled
s_tnsstatus
enabled

2.3 Enabling Web Service on Application Tier Node(s)

In a multi-node Oracle E-Business Suite instance, you can have more than one Application node where Web entry point services are enabled.
For information on implementing load balancing in Oracle E-Business Suite Release 12, see My Oracle Support Knowledge document <="" a="">380489.1 , Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite Release 12.

2.4 Enabling Forms Service on Application Tier Node(s)

In a multi-node Oracle E-Business Suite instance, you can have more than one Application node where the Web application service (Forms) is enabled. Verify and update the context file using the Oracle Applications Manager (OAM) Context Editor for all the application node(s):
Variable Name
Variable Value
s_isForms
YES
s_isFormsDev
YES
s_formsstatus
enabled

Section 3: Installing a Shared Application Tier File System with Release 12 Rapid Install

Rapid Install configures multi-node systems to use a shared application tier file system as the default. Before you run Rapid Install, you must do the following:
  1. Pre-Install tasks
    • Allocate the shared file system for the installation
    • Create the user id and group id for the Applications user (such as APPLMGR) on all the application nodes. The user and group id must be the same on all the nodes
    • The shared file system must be mounted on all the application nodes, so that the file system layout is same across all the nodes.
  2. Run Rapid Install on each node, and specify the appropriate mount points
    When running Rapid Install for the first time you need to provide details for all the nodes you choose to configure. To specify the details for additional Application nodes, click on the 'Add Server' button in the'Node Information' screen for each additional node to be configured. You must define the path to the applications file system to be the same on each node. The following paths must be the same:
    • APPL_TOP
    • COMMON_TOP
    • Tools ORACLE_HOME
    • Web ORACLE_HOME
For example:
    1. Shared COMMON_TOP: /d01/shared_mount/apps/apps_st/viscomn
    2. Shared APPL_TOP: /d01/shared_mount/apps/apps_st/visappl
    3. Shared Tools ORACLE_HOME: /d01/shared_mount/apps/tech_st/visora/10.1.2
    4. Shared Web ORACLE_HOME: /d01/shared_mount/apps/tech_st/visora/10.1.3

Note:To enable the node being added to share the application tier file system you must select the Shared Filesystem checkbox and select the primary node from the drop-down list. Refer to Oracle Applications Installation Guide: Using Rapid Install in the Oracle Applications Documentation Library for more details.

If the primary application node is not the same as the database node, run Rapid Install on each added application node as well as on the primary application node. In the Rapid Install 'Configuration Choice' screen, choose 'Load the following saved configuration' and enter the appropriate database connect string. For more details, refer to 'Standard Installations' in Chapter 2, 'Performing an Installation', of Oracle Applications Installation Guide: Using Rapid Install, available in the Oracle Applications Documentation Library.

Section 4: Adding a Node to a Shared Application Tier File System

This section describes how to add a node to a shared application tier file system.
  1. Prepare existing node
    Execute Rapid Clone on the existing node
    As the APPLMGR user, log in to the node that is sharing the file system and execute the following commands:
$ cd <INST_TOP>/admin/scripts/
$ perl adpreclone.pl appsTier
  1. Make the Applications files accessible
    Mount the shared file system disk to the Application node that you want to add. For example, after mounting the shared file system disk, the following file system is visible from both the application nodes:
    • Shared COMMON_TOP: /d01/shared_mount/apps/apps_st/viscomn
    • Shared APPL_TOP: /d01/shared_mount/apps/apps_st/visappl
    • Shared OracleAS 10.1.2 ORACLE_HOME: /d01/shared_mount/apps/tech_st/visora/10.1.2
    • Shared OracleAS 10.1.3 ORACLE_HOME: /d01/shared_mount/apps/tech_st/visora/10.1.3

Note: User ID and group ID should be consistent across nodes in a shared file system to avoid file access permission issues. You must retain the same absolute path for the mount points of the shared file system on each node. The value for the context variable "s_atName" must be same in the context file for all the application tier nodes.

  1. Configure the node to be added
You will have to copy the Applications context file for the existing node to the current node if the Applications context file for the existing node is not accessible from the current node. Execute the commands listed below in the table. Refer to Appendix A for an example on prompts while running adclonectx.pl.

As the APPLMGR user, log in to the node that you want to add.

cd $COMMON_TOP/clone/bin 

$ perl adclonectx.pl addnode \
contextfile=/SLOTS/slot03/appmgr/inst/apps/txkr12d1/appl/admin/txkr12d1.xml
The above command will create a new context file for the node you were adding to the multi-node system. The next step is to run the AutoConfig utility which will generate the new Instance Home for this node and update the required tables in the database.
$ perl $AD_TOP/bin/adconfig.pl \
contextfile=<specify the path to the new context file, including the file name>
The next step is to run the AutoConfig utility on all the other nodes so that the required configuration files on those are updated with the new node information.

Section 5: Read-Only Node Implementation for Shared Application Tier Node File System

This section describes how to implement read-only file system for shared application tier nodes. The read-only file system node can be configured to perform any of the standard application tier services, such as Forms, Web and Concurrent Processing (Batch). Admin capability should not be configured on this node. The file system associated with APPL_TOP, COMMON_TOP, Tools Oracle Home and Web Oracle Home must be mounted as read-only. This will ensure that any process running on this node will not be able to create or update or delete any file in the file system. The file system associated with Instance Home must have read and write permissions.
For example, the file system permissions should be as follows on this node:
Name
File System Permissions
APPL_TOP: /d01/shared_mount/apps/apps_st/visappl
Read-Only
APPL_TOP: /d01/shared_mount/apps/apps_st/visappl/ad/12.0.0/admin/template/custom
Read-Write
COMMON_TOP: /d01/shared_mount/apps/apps_st/viscomn
Read-Only
COMMON_TOP: /d01/shared_mount/apps/apps_st/viscomn/html/_pages
Read-Write
COMMON_TOP: /d01/shared_mount/apps/apps_st/viscomn/html/fwk/t
Read-Write
COMMON_TOP: /d01/shared_mount/apps/apps_st/viscomn/html/cabo
Read-Write
OracleAS 10.1.2 Tools Oracle Home: /d01/shared_mount/apps/tech_st/visora/10.1.2
Read-Only
OracleAS 10.1.3 Web Oracle Home: /d01/shared_mount/apps/tech_st/visora/10.1.3
Read-Only
INST_TOP: /d01/local/apps/<CONTEXT_NAME>
Read-Write
OraInventory Directory
Read-Only
  1. Run Steps1 through to 3 as described in Section 4
  2. Update the following variable in the context file and run AutoConfig on all the Application Tier nodes
  • The context file for this node should reside in the Instance Home. Verify and update the context file using the Oracle Applications Manager (OAM) Context Editor on all the application node(s):
Variable Name
Variable Value
s_appl_config_home
<Instance Home>/appl
  •  
  • Restart application tier processes.

Section 6: Finishing Tasks

This section lists the tasks that may be necessary, depending on your implementation and the intended use of the multi-node Oracle E-Business Suite instance.
  • If you have more than one application node where 'Web Entry Point services' are enabled, you need to implement load-balancing
For information on implementing load balancing in Oracle E-Business Suite Release 12, see My Oracle Support Knowledge 380490.1 Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite Release 12.
  • If you have more than one application node where 'Batch Processing services' are enabled, you need to implement Parallel Concurrent Processing
For information on configuring Parallel Concurrent Processing (PCP), refer to chapter 'Defining Concurrent Managers' section 'Overview of Parallel Concurrent Processing' in Oracle Applications System Administrator's Guide - Configuration in the Oracle Applications Documentation Library.

Section 7: Migrate Non-Shared Application Tier to Shared Application Tier File System

This section describes how to migrate non-shared application tier file system to shared Application Tier file system.
  1. Migrate any configuration customization to the primary application tier node. For more details, refer to section 'Configuration Customizations' in My Oracle Support Knowledge , Using AutoConfig to Manage System Configurations in Oracle Applications Release 12.
  2. Follow the instructions described in Section 4.
  3. Follow the instructions described in Finishing Tasks.

Section 8: Maintaining a Shared Application Tier file System

This section describes how a shared application tier file system affects system administration
  • Applying Technology Stack Patches  (OracleAS 10.1.2 and OracleAS 10.1.3 Oracle Homes)
Application  services running on the primary and all secondary nodes must be shut down before applying any technology stack patches. Technology stack patches are to be applied on the primary application node only.
  • Applying Applications Patches
Applications patches only need to be applied once, on any one of the application tier nodes. The patched files are immediately accessible to all the other application tier nodes.
In addition, Distributed AD can be used to enhance the patch application process for Applications patches by taking advantage of the shared application tier file system.
  • Applying Applications Patches When Sharing Application Tier File System Among Multiple Database Instances
Applications patches must be applied first to the primary application tier node. When applying patch to the primary node, all the adpatch actions must be executed. You can turn off some of the actions as shown below when applying patches to the secondary database instance.
$ adpatch options=nocopyportion,nogenerateportion,nocompilejsp
  • Oracle HTTP Server Lock Files
    Oracle HTTP Server processes create temporary lock files for its internal operation. The location of these lock files is specified in httpd.conf by the LockFile. You must ensure that value of the AutoConfig variable s_lock_pid_dir is set to a location on the local file system to avoid file locking issues on a network file system.

Section 9: References

  • Rapid Clone
    Rapid Clone automates and simplifies the process of cloning an Oracle Applications Release 12 system. For details, refer to My Oracle Support Knowledge 406982.1 , Cloning Oracle Applications Release 12 with Rapid Clone. 
  • AutoConfig
    AutoConfig is a tool to configure an Oracle Applications Release 12 instance. For details, refer to My Oracle Support Knowledge 387859.1 Using AutoConfig to Manage System Configurations in Oracle Applications Release 12.
  • Distributed AD
    AutoPatch or AD Administration can be directed to distribute workers across the nodes of a shared application tier file system. This type of parallel processing offers improved scalability, performance, and resource utilization. Refer to Oracle Applications Maintenance Utilities in the Oracle Applications Documentation Library for more details. 

    Recommendations for Network Attached Storage or NFS File Systems 

·                     Note: NFS Parameter Recommendations

For Application Tier File System

rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,nfsvers=3,tcp,nolock,acregmin=0,acregmax=0

·                         

  • For Database Tier File System

    DB Oracle Home
    rw,bg,intr,hard,timeo=600,acregmin=0,acregmax=0,wsize=32768,rsize=32768,nfsvers=3,tcp

  •    
  • Data Files
    rw,bg,nointr,hard,proto=tcp,vers=3,rsize=32768,wsize=32768 ( For RAW Devices)

    Additional References
    Mount Options for Oracle files when used with NAS devices 359515.1 
    Oracle Storage Compatibility Program

  •    

  •    

  • The above are recommendations based on Oracle Internal Testing. As the storage is vendor dependent, you may also need to contact your storage vendor and machine administrator to fine tune the options for your environment.
  •  
  •    


Appendix A: Prompts While Running adclonectx.pl

Adclonectx.pl is a perl script that clones the context file. This utility should not be used standalone. This section provides an example of the typical answers to the prompts displayed while running adclonectx.pl.
$ perl adclonectx.pl addnode \
contextfile=/SLOTS/slot03/appmgr/inst/apps/txkr12d1/appl/admin/txkr12d1.xml
Prompts
Response Example
Description
Enter the APPS password:
APPS
Enter the ORACLE password for Application Object Library.
Target hostname (virtual or normal) [ap6802rt]:
ap6802rt
Enter the current hostname. Most of the time it will be the same as default value.
Do you want the inputs to be validated (y/n) [n] ?:
y
Checks for resource conflicts when response is 'y'.
Target system service groups - enable Root Services [enabled] [enabled]:
enabled
Must be enabled if configuring 'Web Entry Point Services' or 'Web Application Services'.
Target system service groups - enable Web Entry Point Services [enabled] [enabled]:
enabled
Must be enabled if configuring 'Web Entry Point Services'.
Target system service groups - enable Web Application Services [enabled] [enabled]:
enabled
Must be enabled if configuring 'Web Entry Point Services'.
Target system service groups - enable Batch Processing Services [enabled] [enabled]:
enabled
Must be enabled if configuring 'Batch Processing Services'.
Target system service groups - enable Other Service Group [enabled] [enabled]:
enabled
Must be enabled if configuring 'Other Service Group'.
Do you want to preserve the Display set to localhost:5.0 (y/n) [y] ?:
n
If you want to continue using your previous display value, respond 'y'. Otherwise, respond 'n' to enter a new value.
Target system Display [ap6802rt:0.0]:
ap6802rt:0.0
Enter a valid display value.
Do you want the the target system to have the same port values as the source system (y/n) [y] ?:
n
If you want to continue using your previous port values , respond 'y'. Otherwise, respond 'n' to enter a new value.
Enter the port pool to be used for the target system node [0-99]:
1
The port pool provides a way to use a set of predefined server ports.
Target system proxy hostname:
www-proxy
Enter a valid proxy hostname.
Target system proxy port:
80
Enter a valid proxy port.
UTL_FILE_DIR on database tier consists of the following directories:
1. /usr/tmp
2. /slot03/oracle/db/tech_st/10.2.0/temp
3. /slot03/oracle/db/tech_st/10.2.0/appsutil/outbound/txkr12d1
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1]:
2
Select a value from the list provided. The selected value will be assigned to APPLPTMP by the utility in the newly cloned context file.

Appendix B: Sharing Oracle E-Business Suite Release 12 File System Among Multiple Database Instances

This section describe the steps you need to follow to share an existing E-Business Release 12 File system with another database instance. In this configuration an application tier file system installed and configured on a single machine is used to access two or more database instances installed on the same or different machines. The diagram shown below illustrates this configuration.
The above diagram illustrates a single-node install of an Oracle E-Business Suite Release 12 on node test.us.oracle.com. This node contains both the application tier and the database tier file system as well as the INST_TOPs related to the database instances TEST and DEV. Also shown is the the node dev.us.oracle.com; this contains a database tier file system for the second database instance DEV, which is sharing the existing application tier in node test.us.oracle.com. The table shown below display the type of file system present on each of the nodes.
Server Name File System
test.us.oracle.com
  • DB Oracle Home for the instance TEST
  • DB Files for the instance TEST
  • Oracle AS 10.1.2 Oracle Home for the instance TEST and DEV
  • Oracle AS 10.1.3 Oracle Home for the instance TEST and DEV
  • Application File System (APPL_TOP) for the instance TEST and DEV
  • Common Top (COMMON_TOP) File System for the instance TEST and DEV
  • Instance TOP (INST_TOP) File System for the instance TEST and DEV
dev.us.oracle.com
  • DB Oracle Home for the instance DEV
  • DB Files for the instance DEV
In the above described configuration, you can choose to run the application tier processes for instance DEV on either on test or dev.us.oracle.com. If you choose to run the processes for instance DEV ondev.us.oracle.com, INST_TOP for this instance must be accessible from dev.us.oracle.com .
The steps described below must be followed by the administrator to create an Oracle E-Business Suite Release 12 File System shareable among multiple database instances. Note that for this configuration to work, all database instances must be patched to the same application level.This configuration option is useful in scenarios where a customer already has a test and development environments set up with separate application tier file system but must now decommission one of the application file system (in the example, dev.us.oracle.com application file system must be decommissioned, and test.us.oracle.com application file system will be shared). 
Note: This configuration option only allows for sharing the application tier file system, and not the database tier file system.

Step 1: Clone the Database Tier

If you already have a database instance that is patched up to the same patch level as the source instance, you do not have to perform this step. Proceed with instructions in Step 2, otherwise use Rapid Clone to create the new database instance. For example, If you already have a development instance you may want to create a test instance.
Note: For details of the latest Rapid Clone patches and general usage of the tool, see My Oracle Support Knowledge document 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone.
There are three phases to this process:

1. Prepare the Source System
  • Execute the following commands on the source system to prepare the source system for cloning. 
$ cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
$ perl adpreclone.pl dbTier
2. Copy the Source System to the Target System
Copy the database tier file system from the source system to the target node by executing the following steps in the order listed.   Ensure the database tier files copied to the target system are owned by the ORACLE user.
  • Copy the database tier file system
    • Log on to the source system database node as the ORACLE user.
    • Perform a normal shutdown of the source system database
    • Copy the database (DBF) files from the source to the target system
    • Copy the source database ORACLE_HOME to the target system
3. Configure the Target System
Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, Paths, Ports, and so on.)
  1. Configure the target system database server 

    Log on to the target system as the ORACLE user and type the following commands to configure and start the database:
$ cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
$ perl adcfgclone.pl dbTier
  1. Start the database server and the Net listener 
    Log on to the target system as the ORACLE user and type the following commands to configure and start the database:
$ cd <RDBMS ORACLE_HOME>/appsutil/<context-name>
$ addlnctl.sh start <ORACLE_SID>
$ addbctl.sh start

Step 2: Create Applications Context File and Instance Home

The steps describe below should be use to create a new context file and a new Instance Home to associate the application middle tier node (in the example, test.us.oracle.com) with the new database instance.
For example:
Oracle E-Business Suite Test Server: test.us.oracle.com
This server has a single-node installation of the Release 12 Vision database, and the Applications file system is installed in the following directories:
INSTANCE NAME: TEST 
10.2 RDBMS ORACLE_HOME: /d1/R12/db/tech_st/10.2.0
APPS DBF files: /d1/R12/db/apps_st/10.2.0
COMMON_TOP: /d1/R12/apps/apps_st/testcomn
APPL_TOP: /d1/R12/apps/apps_st/testappl
OracleAS 10.1.2 ORACLE_HOME: /d1/R12/apps/tech_st/10.1.2
OracleAS 10.1.3 ORACLE_HOME: /d1/R12/apps/tech_st/10.1.3
INSTANCE HOME: /d1/R12/inst/apps/<context_name>
Oracle E-Business Suite Development Server: dev.us.oracle.com
INSTANCE NAME: DEV 
10.2 RDBMS ORACLE_HOME: /d1/R12/db/tech_st/10.2.0
APPS DBF files: /d1/R12/db/apps_st/data
To create a context file for the database instance running on dev.us.oracle.com, execute the following command on the test server test.us.oracle.com.
$ perl $COMMON_TOP/clone/bin/adclonectx.pl \
contextfile=/d1/R12/inst/apps/<context_name>/appl/admin/TEST_test.xml
The table below provides an example of the typical answers to the prompts displayed while running adclonectx.pl.
Prompts
Response Example
Description
Enter the APPS password:
APPS
Enter the ORACLE password for Application Object Library.
Target hostname (virtual or normal) [test]:
test
Enter the hostname of the application tier where you will be running the application tier processes for the new database instance. For the example shown above, you will enter "test" as the hostname for this prompt.
Do you want the inputs to be validated (y/n) [n] ?:y
y
Respond with 'y' to validate the user inputs, otherwise enter 'n'.
Target system database SID
DEV
Enter the target database SID.
Target system database server node [test]
dev
Enter the hostname where the new database instance is running.
Target system base directory for source homes
/d1/R12
Enter the base directory where the source homes are installed.
Target system base directory for Instance Homes [/d1/R12/inst]
/d1/R12/inst
Enter the base directory where the Instance Home should be located for the new instance.
Username for the applications file system owner [user1]
user1
Enter the UID of the applications file system owner.
Group for the applications file system owner [dba]
dba
Enter the GID of the applications file system owner.
Do you want to preserve the Display set to test:0.0 (y/n) [y] ?:
y
Respond with 'y', to set the display to the same server.
Do you want the the target system to have the same port values as the source system (y/n) [y] ?:
n
Respond with 'n'.
Enter the port pool to be used for the target system node [0-99]:
20
The port pool provides a way to use a set of predefined server ports. You must choose a port pool that is different from all the other instance that are current running on this machine to avoid port conflicts. It is possible that adclonectx.pl may not be able to connect to the new database instance at this point and give a warning message "RC-40201: Unable to connect to Database TEST". You can safely ignore this message.
New context path and file name [TEST_dev.xml]
/d1/R12/inst/apps/DEV_dev/ appl/admin/DEV_dev.xml
Enter the path to the new context file, including the file name.

Step 3: Review Oracle E-Business Suite Applications Context File for the New Instance

1.    Verify the Context File Created for the New Instance

Check the new context file created by the adclonectx utility. Ensure that values for the AutoConfig variables shown in the table below are set correctly:
Variable Name
Remarks
s_dbhost
Ensure value of this variable is set to the hostname of the new database server.
s_dbport
Ensure value of this variable is set to the TNS listener port on the new database server.
s_appl_config_home
Ensure value of this variable is set to <instance_top>/appl, where <instance_top> is the top level directory created for the new instance.
s_adconfig_file
Ensure value of this variable is set to <instance_top>/appl/admin/adconfig.txt, where <instance_top> is the top level directory created for the new instance.
s_adovars_file
Ensure value of this variable is set to <instance_top>/appl/admin/admin/adovars.env, where <instance_top> is the top level directory created for the new instance.
s_appsora_file
Ensure value of this variable is set to <instance_top>/appl/APPS<s_contextname>.env, where <instance_top> is the top level directory created for the new instance.
s_applsys_file
Ensure value of this variable is set to <instance_top>/appl/<s_contextname>.env, where <instance_top> is the top level directory created for the new instance.

  1. Run AutoConfig to Configure the New Instance

    As the apps user, log in to the node where the application tier is installed (test.us.oracle.com in the example), and execute the following command:
$ $AD_TOP/bin/adconfig.pl \
contextfile=/d1/R12/inst/apps/<context-name-for-dev>/appl/admin/<context-file-created for DEV instance>.xml
You must replace the context file value in the above command to reflect the actual location of the new context file created in Step 2. When AutoConfig completes, it will create an Instance Home and a set of configuration files for the new instance. Review the AutoConfig log file for any errors. 

Step 4: Start Oracle E-Business Suite Application Tier Services

Execute the following commands to start the services:
$ cd <appl_top_location>
$ . .<APPS*.env file for the new instance> /* Source the APPS*.env file for the new instance */ 
$ tnsping <SID> /* To make sure that you are connecting to the new instance */
$ $INST_TOP/admin/scripts/adstrtal.sh <apps username>/<apps passwd> /* To start application tier processes */ 
Access the Oracle E-Business suite login page using the new URL and be sure to perform sanity tests before releasing the environment for test, development or production use.
Refer to Section 8: Maintaining a Shared Application Tier File System for additional instructions when applying application patches in this configuration.

Change Log

Date
Description
Dec 28, 2011
  • Added OCFS2 Support note
Nov 22, 2011
  • Added NFS recommendations
Feb 14, 2011
  • Moved OCFS certification details to new Section 1.4.
  • Replaced references to OracleMetaLink with references to My Oracle Support.
  • Made various updates to formatting.
Mar 04, 2010
  • Updated first yellow note box with OCFS certification details.Metalink-SOH-R12.html.save
Aug 17, 2009
  • Minor edits.
Feb 11. 2009
  • Fixed doc bugs.
May 01. 2008
  • Fixed remarks and doc bugs.
Nov 07, 2007
  • Added Rapid Clone note (406982.1) reference to Appendix B, Step 1.
Oct 31, 2007
  • Restructured note to emphasize that Windows is not supported.
Sep 27, 2007
  • Restructured note for increased readability.
Sep 17, 2007
  • Reviewed note and reworded some parts.
Sep 11, 2007
  • Added note for sharing application tier file system with multiple database instances.
Mar 23, 2007
  • Added note for Windows.
Jan 24, 2007
  • Initial document creation.

References
NOTE:387859.1 - Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12
NOTE:406982.1 - Cloning Oracle Applications Release 12 with Rapid Clone
NOTE:380489.1 - Using Load-Balancers with Oracle E-Business Suite Release 12
NOTE:384248.1 - Sharing The Application Tier File System in Oracle E-Business Suite Release 12




Posted by at

1 comment:

  1. abaan sheikhDecember 17, 2021 at 8:23 AM

    This particular is usually apparently essential and moreover outstanding truth along with for sure fair-minded and moreover admittedly useful My business is looking to find in advance designed for this specific useful stuffs… Wetransfer

    ReplyDelete

Subscribe to: Post Comments (Atom)