|
Oracle® E-Business Suite Certified Configuration Installation Guide
Release 11i (11.5.10) for AIX Based Systems, hp-ux PA-RISC (64-bit), Linux x86, and Solaris Operating System (SPARC 32-bit) Part No. B15721-03 |
|
![]() Previous |
![]() Next |
This chapter describes installation of existing Oracle Applications systems, and includes all the underlying scripts that are involved. It consists of the following topics:
This section introduces the features supported by Oracle E-Business Suite On Demand utilities. The Oracle E-Business Suite Certified Configuration On Demand utilities enable the following features on an Oracle E-Business Suite Certified Configuration:
Administration Features
Installing an environment from a shiphome
Cloning from a source environment to a target environment
Applications Support Features
Supporting BigIP
Customizing applications
The Oracle E-Business Suite Certified Configuration Utility Pack contains the wizard.sh script which is the user interface for performing all administrative tasks.
The following is the complete command summary for the wizard.sh script:
wizard.sh mode=install/config/validdest_mntpt=Destination mntpt {src_host=Source host src_mntpt=Source mntpt} - For mode install, config, or valid {apps_serv_host=Apps db hostname apps_mntpt=Apps mount point} [ dbype=prod/vision/bfal] - For mode=install, with either Oracle or Application Tier [ bigd=true|false,Url ] [ porttype=mntpt for new port range] [ dbtype=vision/prod/bfa]
In the preceding syntax, text in brackets [ ] is optional, and text in braces { } is mandatory. Note the following syntax terminology:
bigd: BigIP details. By default, the value is false. If you specify true, then you need to provide the BigIP URL. The URL should include the protocol. For example, bigd=true, http://machine.
mnode: Multinode. For multinode support, specify all hostnames.
porttype: Allows users to specify a different port range from the one associated with the destination mount point. Only the port range is affected. Directory structures remain unchanged. Typically the first letter of the value of porttype is used to determine the new port range. An exception is when the second to the last character in the value is a number. In this case, the number will replace the second digit of the new port range. For example, if porttype=igoldi, the first letter (i) will determine the new port range, as the second to last character (d) is not a number. In this example, the new port range is 106. On the other hand, if porttype=igold5i, the second to last character (5) will replace the second digit (0) of the new port range (106). Therefore the new port range is 156. A number in any other position of the porttype value has no effect.
dbtype: This argument is only for mode=install. Specify the type of database to install. Valid values are bfa (Business Flow Accelerator), prod (production), and vision (Vision Demonstration).
In addition, the syntax contains the following variables:
Admin host: Administration-tier host
Apps db hostname: Applications database host name
Apps mount point: Applications mount point
CM host: Concurrent Manager host
DB host: Database host
Forms host: Forms-tier host
Destination mntpt: Destination mount point
Source mntpt: Source mount point
Source host: Source host
Url: URL of tier
Web host: Web-tier host
To prevent accidental termination because running the wizard.sh script might take a long time, Oracle recommends running the wizard.sh script in the background with the UNIX nohup command as follows:
$ nohup wizard.sh arguments &
This section describes the steps required to install Oracle Applications Release 11i (11.5.10) from a stage directory. Installation is the action of creating a new instance from the stage directory. The installation process has four phases. Each phase is controlled by a separate script. The following list describes each phase:
Phase 1: Creation of partitions, mount points, and associated users.
Phase 2: Creation of file copies from the stage area using an unzip utility.
Phase 3: Configuration of the new environment to a new identity.
Phase 4: Validation of the new environment to a new identity.
The wizard.sh script enables the following tasks for installation of the components:
Installation of the Oracle applications-tier and database-tier
Installation of the Oracle database-tier
Installation of the Oracle applications-tier
The prerequisites for the installation is as follows:
Valid display
Unzip 5.42 or higher
ld, make, cc, and ar
All preceding utilities should be present in the PATH statement.
Use the following procedure to install the database-tier and the applications-tier on the same node:
Change directory to the admin directory, using the following command:
$ cd $EBSO_HOME/admin
Run the wizard.sh script using the appropriate command.
When prompted, enter the NetApps partition.
Typically, if you are performing a two-node installation, the database-tier is installed on one node, and the applications-tier is installed on another node. You must install the database-tier before you install the applications-tier.
Use the following procedure to install the database-tier on one node.
Change directory to the admin directory using the following command:
$ cd $EBSO_HOME/admin
Run the wizard.sh script using the appropriate command.
For local file systems:
$ ./wizard.sh mode=install dest_mntpt=pabcdi tier=oracle \
mnode=ple-bol0,ple-bol1,ple-bol1,ple-bol1,ple-bol1
In the preceding command:
ple-bol0 is the database node
ple-bol1 is the applications node
For systems using the Business Flow Accelerator shiphome:
$ ./wizard.sh mode=install dest_mntpt=pabcdi tier=all dbtype=bfa \ mnode=ple-bol0,ple-bol1,ple-bol1,ple-bol1,ple-bol1
In the preceding command:
ple-bol0 is the database node
ple-bol1 is the applications node
Typically, if you are performing a two-node installation, the database-tier is installed on one node, and applications-tier is installed on another node. Install the applications-tier after you have installed the database-tier.
Use the following procedure to install the applications-tier on one node:
Change directory to the admin directory using the following command:
$ cd $EBSO_HOME/admin
Run the wizard.sh script using the following:
$ ./wizard.sh mode=install dest_mntpt=pabcdi tier=apps \ mnode=ple-bol0,ple-bol1,ple-bol1,ple-bol1,ple-bol1
In the preceding command:
ple-bol0 is the database node
ple-bol1 is the applications node
This section describes the steps to configure the Oracle Applications Server 11i. Configuration is the process of making all of the services available for a given environment.
The configuration process has two phases:
Phase 1: Configuration of the new environment to a new identity.
Phase 2: Validation of the new environment to a new identity.
The wizard.sh script enables the following tasks for cloning the components:
Configuration of applications-tier and database-tier
Configuration of database-tier
Configuration of applications-tier
If the database-tier and the applications-tier are not on the same node, then you need to specify the value of the mnode parameter.
The following is a list of system requirements for target systems:
Perl version 5.6.1
Unzip 5.42 or higher
ld, make, cc, and ar
All preceding utilities should be present in the PATH statement.
Use the following procedure to configure the applications-tier and the database-tier on a given node:
Change directory to the admin directory using the following command:
$ cd $EBSO_HOME/admin
Run the wizard.sh script using the following command:
$ ./wizard.sh mode=config src_mntpt=pabcdi dest_mntpt=tabcdi src_ \ host=ple-bol0 tier=all
Use the following procedure to configure the database-tier on a given node as the oracle user:
Change directory to the admin directory, using the following command:
$ cd $EBSO_HOME/admin
Run the wizard.sh script using the following command:
$ ./wizard.sh mode=config src_mntpt=pabcdi dest_mntpt=tabcdi src_ \ host=ple-bol0 tier=oracle
Use the following procedure to configure the applications-tier on a given node as the apps user.
Change directory to the admin directory, using the following command:
$ cd $EBSO_HOME/admin
Run the wizard.sh script using the following command:
$ ./wizard.sh mode=config src_mntpt=pabcdi dest_mntpt=tabcdi src_ \ host=ple-bol0 tier=apps