Installing Oracle Application 12.1.1 using Rapid Install

Operating System: Red Hat Enterprise Linux          5 - Update 1 or higher (32-bit)

System Software and Networking Requirements:

This section describes the system software needed on different platforms, and essential

Networking requirements.

System Software:

The following maintenance tools must be installed on all machines, and their locations

specified both in the PATH of the account that runs the wizard, and in the PATH of the

accounts that will own the database tier and Applications tier file systems.

Networking

The key networking requirement is for the hosts file to include an entry for the

installation machine, formatted as follows:

<IP address> <hostname>.<domainname> <hostname>

Important: The domain name must not be a single word.

CPU Requirements

Because there are different product combinations, different user profiles, and different

configurations, there is no one sizing answer for all hardware platforms. Some

hardware vendors have sizing worksheets that model the CPU and memory

requirements of Oracle Applications on their hardware.

The most reliable strategy to ensure that the hardware is sized appropriately is to install

a test environment, and then set a benchmark with a configuration, product mix, and

user load that simulates your own current and expected workloads. These "actual"

conditions can help verify performance before you install your production-ready

environment. If such a benchmark is not feasible, Oracle Consulting Services and your

hardware vendor can help you find another Oracle Applications system running a

product mix and user profile similar to yours.

As installing Oracle Applications moves towards a Grid-type model, there will be more

scope for easily scaling hardware to meet additional needs, with the relevant software

components being deployed automatically on new machines according to the machines'

designated functions.

CPU requirements for running Oracle Applications depend on:

• Number of concurrent users and their usage profiles

• Number of concurrent manager processes and the types of jobs that they are

    running

• Load for activities other than Oracle Applications

• Size of the database

• Desired response time

Memory Requirements

The Oracle Database requires adequate memory to be available in order to support the

specific needs of a given installation. To calculate the total memory requirements on the

machine where the database is installed, the following demands must be taken into

account:

• Oracle Database overhead

• Size of System Global Area (SGA)

• Number of concurrent users

• Any non-Oracle software that has to run on the machine (this is not recommended)

In carrying out the above calculations, you should aim to allow for any expected growth

in usage over the planned lifetime of the Applications system, although the increasing

usage of Oracle Real Application clusters (Oracle RAC) and related technologies means

that it is now easier to scale a system to meet additional requirements, typically by

adding another machine.

Disk Space Requirements

Rapid Install installs the file system and database files for all products, regardless of

their licensed status. The approximate file system disk space requirements for a

standard installation are:

File System Space Requirements for Standard Installation

Node: Space Required:

Applications node file system (includes

OracleAS 10.1.2 Oracle Home, OracleAS 10.1.3

Oracle Home, COMMON_TOP, APPL_TOP,

and INST_TOP)

35 GB (50 GB on HP-UX Itanium)

Database node file system (Fresh install) 55 GB

Database node file system (Vision Demo

database)

208 GB (210 GB on HP-UX Itanium)

The total space required for a standard system (not including the stage area) is 85 GB

for a fresh install with a production database, and 233 GB for a fresh install with a

Vision Demo database. As indicated in the table, the corresponding figures will be

higher for the HP-UX Itanium platform.

Note: The database node disk space requirements for both the

production database and the Vision Demo database include database

files (.dbf) and the 11gR1 database Oracle Home.

Stage area

For a production database install, running Rapid Install from a stage area requires at

least 47 GB to accommodate the file system and database files in the stage area.

Applications log and output files

Many Oracle Applications products generate log and output files during runtime. The

disk space needed varies with the number of users and transactions, and depends on

how frequently you purge these files. Consult the product-specific documentation for

more information.

Tip: Log and output files are not automatically purged. Determine a

strategy for archiving and purging these files after the installation, and

monitor the disk space they consume to determine how much space

you may need in the future.

Temporary directories and files

For install time temporary disk space, Rapid Install uses the directory defined by the

TMPDIR variable (on UNIX) or TEMP and TMP variables (on Windows). You should

ensure there is at least 1 GB of free temporary space before starting an installation.

At runtime, Oracle Applications requires temporary disk space. For example, each

concurrent manager writes temporary parameter files, Oracle Reports writes temporary

format files, and Oracle Forms writes temporary buffer records. Rapid Install sets the

temporary directory based on the value you supply on node-specific settings screens.

Updates and patches

You will need disk space for applying updates, patches, maintenance packs, family

packs, and minipacks, and for any backup files that may be created.

Note: See AutoPatch in Oracle Applications Maintenance Utilities. See also

Patching Your System in Oracle Applications Maintenance Procedures, and

Oracle Applications Patching Procedures (new for Release 12).

Other files

The total disk space estimate must account for the requirements of files other than those

directly related to Oracle Applications. For example:

• Operating system software

• Online backups

• Custom Applications development files

• Files for any other software that you use.

Kernel Requirements: 2.6.18-8.el5PAE

Note : To determine Version, Enter: $uname -r

Required Packages:

Red Hat Enterprise Linux 5* (base and Advanced Platform)

Update 1 (5.1) or higher of Red Hat Enterprise Linux (RHEL) 5 is required

The following i386 packages are not part of the OS distribution media and must be downloaded separately (from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux for RHEL 5) and installed manually:

• openmotif21-2.1.30-11.EL5.i386¹
• xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386
• For Update 1 or 2:
• binutils-2.17.50.0.6-6.0.1.i386²
• For Update 3:
• binutils-2.17.50.0.6-9.0.1.i386²
• For Update 4 (5.4) or higher, see workaround listed below in the 'After Installing or Upgrading' section.

The following i386 packages must be installed from the RHEL 5 distribution media:

• compat-glibc-2.3.4-2.26
• compat-glibc-headers-2.3.4-2.26
• gcc-4.1.2-14.el5
• gcc-c++-4.1.2-14.el5
• glibc-2.5-12³
• glibc-common-2.5-12³
• glibc-devel-2.5-12
• glibc-headers-2.5-12
• kernel-headers-2.6.18-128.el5
• libgcc-4.1.2-14.el5³
• libstdc++-devel-4.1.2-14.el5
• libstdc++-4.1.2-14.el5³
• make-3.81-1.1³
• gdbm-1.8.0-26.2.1³
• libXp-1.0.0-8.1.el5
• libaio-0.3.106-3.2³
• libgomp-4.1.2-14.el5
• sysstat-7.0.0-3.el5
• compat-libstdc++-296-2.96-138
• compat-libstdc++-33-3.2.3-61

Additionally, the following RPMs are required for an 11gR1 Database (which is bundled with the 12.1.1 release) on the database tier:

• elfutils-libelf-devel-0.125
• elfutils-libelf-devel-static-0.125
• libaio-devel-0.3.106
• unixODBC-2.2.11
• unixODBC-devel-2.2.11
• kernel-headers-2.6

Note:

1.      The openmotif package version must be 2.1.30. For example, openmotif-2.2.3-10. RHEL4.5 is not supported.

2.       This GNU linker (ld) version 2.17 provided by Oracle is required for relinking the modules in Advanced Planning & Scheduling (MSC, MSO, MSR) and Profitability Manager (FEMCCE)

3.      This rpm is distributed as part of the 'default' installation of Enterprise Linux.

4.      After installing these patches, run ldconfig -v.

 Software Requirements:

The following maintenance tools must be installed on all machines, and their locations specified both in the PATH of the account that runs Rapid Install and in the PATH of the accounts that will own the database tier and application tier file systems.

• ar
• gcc
• g++
• ld
• ksh
• make
• X Display Server

Kernel Settings:

Edit the /etc/sysctl.conf file to configure our kernel settings. After editing the file, use the "sysctl -p" command or restart the system to invoke the new settings.

The following table lists the kernel settings for Red Hat Enterprise Linux AS/ES 3, 4, and 5:

Parameter	Value
kernel.semmsl	2561
kernel.semmns	320001
kernel.semopm	1001
kernel.semmni	1421
kernel.shmall	2097152
kernel.shmmax	Half the size of the physical memory (in bytes), and at least 21474836482
kernel.shmmni	4096
kernel.msgmax	8192
kernel.msgmnb	65535
kernel.msgmni	2878
fs.file-max	131072
net.ipv4.ip_local_port_range	10000 650003
net.core.rmem_default	262144
net.core.rmem_max	4194304
net.core.wmem_default	262144
net.core.wmem_max	262144

Note:

1.      If the current value for any parameter is higher than the value listed in the following table, then do not change the value of that parameter

2.      Set using the following entry in the /etc/sysctl.conf file: kernel.sem = 256 32000 100 142

3.      On the server running the EBS Database, this kernel parameter must be the lesser of half the size of the physical memory (in bytes) and 4294967295

4.      Values recommended for the local port range may need to be adjusted according to the specific needs of the user's environment in order to avoid port conflicts.

Domain Name System (DNS) Resolver Parameters:

Two Domain Name System (DNS) resolver parameters (timeout and attempts) are set by default to low values when the operating system is installed. These low values may cause attempted network connections to an Oracle database to fail. If this happens, add or update the following entries to these minimum settings in the /etc/resolv.conf file on each server node:

options attempts:5

options timeout:15

Verifying Host Names:

Use the following to verify host name settings:

For Red Hat Enterprise Linux AS/ES 3, 4 and 5:

1. Verify that the /etc/hosts file is formatted as follows:

2.      127.0.0.1 localhost.localdomain localhost

[ip_address] [node_name].[domain_name] [node_name]

3. Verify that the /etc/sysconfig/network file is formatted as follows:

HOSTNAME=[node_name].[domain_name]

4. If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.
5. If wechanged any files in the previous steps, restart the system.

Modifying the Number of Open File Descriptors:

Open the /etc/security/limits.conf file and change the existing values for "hard" and "soft" parameters as follows. Restart the system after making changes.

Note: If the current value for any parameter is higher than the value listed in this document, then do not change the value of that parameter.

  * hard nofile 65535

  * soft nofile 4096

  * hard nproc 16384

  * soft nproc 2047

OS Library Patch for Oracle HTTP Server (RHEL 5 only) :

Download and apply the patch 6078836 from My Oracle Support to fix an issue with the Oracle HTTP Server (missing libdb.so.2) bundled with the E-Business Suite technology stack.

Note:  This patch (which includes a required operating system library) must be applied before installing Oracle E-Business Suite.

Patch Pre-Requirements:

             1)Your system configuration (Oracle Server version and patch

 level, OS Version) must exactly match those in the bug  database entry - You must have NO OTHER PATCHES installed on  your Oracle Server since the latest patch set (or base release  x.y.z if you have no patch sets installed).

2)You must have Perl 5.00503 (or later) installed under the ORACLE_HOME, or elsewhere within the host environment.

Patch Installation Instructions:

 Stop all OHS instances in the iAS instance under repair;

 Note that, each iAS instance may be repaired separately, but the OHS instances cannot be.

 To apply the patch, unzip the PSE container file:

% unzip p6078836_101330_Linuxx86.zip

 Set your current directory to the directory where the patch

 is located:

 % cd 6078836 

Note:  This file is for RedHat 5 (or later) ONLY.

 As the super-user, copy libdb.so.2 to /usr/lib

 % mv /usr/lib/libdb.so.2 /usr/lib/libdb.so.2.6078836 (if libdb.so.2 exist already in /usr/lib)

 % cp libdb.so.2 /usr/lib

 Restart the OHS instances of the iAS instance under repair.

 Patch Special Instructions:

 If the Oracle inventory is not setup correctly this utility will

 fail. To check accessibility to the inventory you can use the

 command

 % opatch lsinventory

 If you have any problems installing this PSE or are not sure

 about inventory setup please call Oracle support.

 Patch Deinstallation Instructions:

 Use the following command:

 As the Super-user

 %  mv /usr/lib/libdb.so.2.6078836 /usr/lib/libdb.so.2

Link to Motif library for Oracle Application Server 10.1.2 (RHEL 5 only) :

Perform the following command (as root on our system) to update a required link to a Motif library prior to relinking or patching the 10.1.2 Application Server Oracle Home:

# unlink /usr/lib/libXtst.so.6
# ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

Without this updated link, we may see the following errors during a relink of the 10.1.2 Oracle Home:

/usr/lib/libXtst.so.6: undefined reference to `__stack_chk_fail@GLIBC_2.4'
/usr/lib/libXtst.so.6: undefined reference to `__fprintf_chk@GLIBC_2.3.4'
/usr/lib/libXtst.so.6: undefined reference to `__sprintf_chk@GLIBC_2.3.4'

Since the ldconfig command overrides this link, the above link command (ln) will have to be re-issued after running the ldconfig command.

Before Installing or Upgrading:

If the Release 12.1.1 upgrade is performed with the Rapid Install wizard (Upgrade from 11i to R12), ensure we have the latest Rapid Install patch as described in Oracle Applications Release Notes, Release 12.1.1 (My Oracle Support Doc 798258.1) before we begin our installation or upgrade.

Current Version of Rapid Install

The most current version of the Rapid Install wizard is 12.1.1.11. You can obtain this version by applying <Patch 8639046>, available at My Oracle Support.

To verify the Rapid Install version, use the RapidWizVersion executable

located in the rapidwiz directory on the Start Here DVD.

Here is an example. Your system syntax may vary.

UNIX:

$ cd /Stage12.1.1/startCD/Disk1/rapidwiz

$ ./RapidWizVersion

Complete all operating system requirements, software requirements, and other requirements before installing or upgrading Oracle E-Business Suite.

OPMN port conflict:

By default, the OPMN service of the Application Server technology stack listens on port 6000 when started up during Rapid Install. This can conflict with the X11 port used for the graphics console on Linux servers and prevent Rapid Install from completing.

To address this issue, perform the following steps before installing or upgrading:

• Check if the port 6000 is being used ("netstat -a | grep 6000")
• If so, we should disable the graphics console login process on the Linux server. This can be accomplished by logging in as root and issuing the following commands:
• Find the process that uses port 6000 by the command "lsof -i TCP:6000".
• Use "kill -9" to abort the process found in the previous step
• Confirm that nothing is listening at port 6000 ("netstat -a | grep 6000")
• Modify /etc/inittab by changing "id:5:initdefault:" to "id:3:initdefault:"
• Run "/sbin/init 3" to restart dtlogin

Create Operating System Accounts

Before running Rapid Install, you must create the operating system accounts that will

be used in the installation of the database node and Applications node file systems.

Details of this process depend on whether you are using a UNIX system or Windows

system. Consult the appropriate operating system documentation as required.

For UNIX users

The operating system user that owns the database node file system and starts the

database node services is called the oracle user. The operating system user that owns the

Applications node file system and starts the Applications node services is called the

applmgr user. The names of these accounts must be the same on all nodes in an

Applications system.

Single-user UNIX installations

In order to prepare for a single-user installation, you must first create an oracle user

account and log in as the oracle user to run Rapid Install. The account should be created

with a default shell that is compatible with the Bourne shell.

Note: If using the Korn Shell (ksh), ensure that the $ENV environment

variable is not set before starting the installation, as it can alter variables

that are set by the Oracle installation scripts. The command unset

ENV can be used to unset the variable if necessary.

Multi-user UNIX installations

In order to prepare for a multi-user installation, you must first create an oracle user

account and an applmgr user account. Both should be created with a default shell that is

compatible with the Bourne shell. Log in as root to run Rapid Install. Then specify the

oracle user as the Oracle OS user, and the applmgr user as the Apps OS user.

The oracle user is the account that owns the database node technology stack (11gR1

Oracle Home) and the database files. The default name for the oracle user is ora<SID>.

For example, for a production (PROD) environment, the default Oracle OS username

might be oraprod.

The applmgr user is the account that owns the Applications node technology stack

(APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, and OracleAS 10.1.3

Oracle Home). The default name is appl<SID>. For example, for a Vision Demo (VIS)

environment, the default Apps OS username might be applvis.

On machines containing multiple nodes, you can assign one user account to be the

owner of the database node file system, and another to be the owner of the Applications

node file system. For this type of install, Rapid Install can install both nodes in one run

if the install is started by the root user. If you are installing on a machine with only one

node to install, or with all nodes sharing the same user, you can run the install as either

the root user or the specific user for those nodes.

Setting Up the Stage Area

As preparation for running Rapid Install, you must run a Perl script that creates the

install directory and copies the contents of the Release 12.1.1 software bundle to the

appropriate location in the file system, known as the stage area (or staging area).

Note: While it is possible to perform an installation direct from the

DVDs, creation of a stage area is strongly recommended for optimal

installation performance.

Installation Software Delivery Format

Your installation software comes in DVD format. The individual disks included in the

Release 12.1.1 software bundle are labeled as follows:

• Start Here - Disk 1

• APPL_TOP - Disk n

• RDBMS - Disk n

• Tools - Disk n

• Databases - Disk n

The contents of each of these DVDs will be copied to the specified stage area.

Creating the Stage Area Directory

To create the stage area directory, run the adautostg.pl script. If the script cannot

create the directories, or if there are other system parameters that require modification,

it prompts you to amend the parameters. You must fix any problems before you

continue with the setup process.

Follow these steps to set up a stage area installation:

1. Log in as the operating system user with sufficient privileges to mount, unmount,

and eject the DVD. This user must also have write privileges to the stage area that

you set up.

2. Insert the Start Here disk in the DVD-ROM drive.

3. Mount the DVD (conditional).

If your system runs on a UNIX platform, and if you do not use AutoMount, you

must mount the Start Here disk now.

4. Verify software version (perl).

You must have perl 5.0053 or higher installed, and it must be in your PATH. Use

the following commands to identify the perl version and its location. The command

is the same for both UNIX and Windows platforms:

perl -v

If perl is not installed, you may download it from http://www.perl.com.

5. On UNIX, set the environment variable DISPLAY to an active and authorized

display.

6. Run the adautostg.pl script.

UNIX:

$ cd

$ perl /mnt/cdrom/Disk1/rapidwiz/adautostg.pl

The stage script message informs you that you may either stage all the Rapid Install

components, or selected components only.

7. Set up the stage area directory.

At the prompt for the stage directory, enter the name of the system top-level

directory. The Rapid wizard StageR12 directory will be created in this path. For

example, if you enter /u01 as the top-level directory, the resulting directory path

will be /u01/StageR12.

8. Indicate the components to be staged.

The script prompts you to choose the components that you want to stage:

1.      Oracle Applications

2.       Oracle Database technology stack (RDBMS)

3.      Oracle Applications database (Databases)

4.      Oracle Applications technology stack (Tools)

5.      APPL_TOP

Enter one or more components, separating each one with a space. You can indicate

that you want to stage only the database technology stack, only the APPL_TOP, and

so on.

If you choose 1 (the default), all the main components will be staged.

9. Insert the Rapid Install DVD.

Insert the relevant DVD, as required in the prompt. The system message lists the

files it has copied and their location in the stage area directory.

Stage Area Directory Structure

The stage area created by adautostg.pl looks like this: a top-level directory StageR12,

with principal subdirectories startCD, oraApps, oraDB, oraAS, and oraAppDB.

Stage Area Structure

The number of DVDs (and hence further subdirectories) varies from component to

component.

Starting Rapid Install

Once the stage directory is created, start Rapid Install as shown in the examples below.

The exact path will depend on the disk location you specified for your staging area.

UNIX:

Example

$ cd /u01/StageR12/startCD/Disk1/rapidwiz

$ ./rapidwiz

Top-level Directories and Mount Points

Rapid Install needs to be told the locations of the top-level directories and mount points

on the database node, and the Applications node(s). It derives subdirectories from these

top-level directories.

NLS Settings

Oracle Applications Release 12.1.1 provides multilingual support for text parts of Oracle

Applications, and for product data. Because it offers support for the Unicode AL32UTF8

character set, you can, if required, run a number of languages in a single instance. You

choose the character set for both the database and the Applications products when you

run Rapid Install

1. Start the Rapid Install wizard

Start the wizard from the command line by entering rapidwiz at the prompt. The

Welcome screen lists the database and the technology stack components that are

installed with Oracle Applications

This screen lists the components that are included in, or supported by, this release

of Oracle Applications. You can expand the component lists, using the scroll bar to

bring all the components into view.

A new installation includes a fresh Oracle 11g Release 1 (11gR1) database. In an

upgrade, Rapid Install creates an Oracle 11gR1 database Oracle Home without a

database. You can use this Oracle Home to upgrade or migrate your existing

database to Oracle 11gR1.

2. Select a wizard operation

Use the Select Wizard Operation screen to indicate the action you want Rapid

Install to perform. You begin both new installations and upgrades from this screen.

Based on the action you choose, the Rapid Install wizard continues with the

appropriate screen flow.

The available actions are as follows:

• Install Oracle Applications Release 12.1.1

This action sets up a new, fully configured system, with either a fresh database

or a Vision Demo database. The configuration is derived from the

system-specific configuration parameters you will enter in the Rapid Install

wizard and save in the Applications database (conf_<SID>.txt file initially, until

the database has been created).

• Express Configuration

This install option sets up a fully configured, single-user system with either a

fresh database or Vision Demo database. You supply a few basic parameters,

such as database type and name, top-level install directory, and choice of port

pool. The remaining directories and mount points are supplied by Rapid Install

using default values.

Note: The steps in Setting Up an Express Installation, page 2-

36 in this chapter describe this option.

• Upgrade to Oracle Applications Release 12.1.1

Choose this option to indicate that you are upgrading your E-Business Suite

products to the current version of Oracle Applications. The wizard screen flow presents two paths: one that lays down the file system and installs the new

technology stack, and one that configures servers and starts services.

Note: See Performing an Upgrade, page 3-1 to learn how

Rapid Install works during a system upgrade.

Using the following steps, you will set up a new installation. Choose Install Oracle

Applications Release 12.1.1 and then click Next to continue.

3. Supply Oracle Configuration Manager details

Oracle Configuration Manager (OCM) is a component that is designed to facilitate

support for your Oracle products. Use of Oracle Configuration Manager is optional,

but recommended.

A lightweight agent that consumes minimal CPU resources, OCM supports

automatic discovery of installed components and configuration information, and

provides continuous tracking of key Oracle and system statistics of the machine it is

running on.

Data collected is sent via HTTPS (secure HTTP) to Oracle Support, who can thereby

maintain an up-to-date view of your Oracle installation, facilitating pro-active

problem avoidance and helping to reduce the time needed for resolution of support

issues.

Note: For further details of OCM, click the View details link on the

OCM screen.

4. Identify configuration file

On the Configuration Choice screen, you indicate whether you will be using

previously saved configuration details.

If you choose Create a new configuration , Rapid Install saves the configuration

parameters you enter on the wizard screens in the Applications database, and in a

configuration file (conf_<SID>.txt), which is stored in your system temporary

directory until the installation is completed.

If you choose Load the following saved configuration, the database connect string field

becomes active. For a configuration stored in the database, this field is made up of

<hostname>:<SID>:<database port>, for example

appserv2.company.com:VIS:1521.

Important: The host name must include the domain.

Enter the appropriate database connect string (or conf_<SID>.txt file location, if

applicable) to point Rapid Install to a stored configuration whose parameters you

wish to use. Typically, you would choose this option when performing a

multi-node install, or when restarting Rapid Install after an interruption to the

installation process.

Because this is a new installation, choose Create a new configuration, then click Next

to continue.

5. Specify Global System Settings

On the Global System Settings screen, you indicate whether you want to accept the

default port values. You can specify a Port Pool setting to enable multiple

Applications environments to co-exist on the same machine.

For example, if you select an increment of 3 from the Port Pool list, the values in the

Derived Port Settings will reflect this choice. Use the scroll bar or click Advanced

Edit to see the Port Values screen.

The default value of the Port Pool set is zero, but you can customize it by selecting

another value from the drop-down list in the Port Pool field. There are 100 port pool

selections: if you select an increment of 3, the default values are increased by that

value. The Database Port (1521) becomes 1524, the RPC Port (1626) becomes 1629,

and so on.

At this point, you can simply accept the values for the chosen Port Pool (and

therefore individual ports) by clicking Next. This will suffice for many installations.

Otherwise, you can add an extra level of sophistication by specifying individual port

values to meet particular site-specific requirements, over and above the basic use of

the Port Pool mechanism described above. For example, you might wish to avoid

using a particular port for some reason, perhaps because it will be needed by some

other software. Clicking on the Edit Ports button will open a screen that allows you

to specify the values of any ports you wish.

When finished on this screen, click OK to return to the Global System Settings

screen, and click Next on that screen

6. Define Database Node Configuration

On the Database Node Configuration screen, indicate the kind of database you

want to install in the new system, the name you will use to identify it, the machine

on which it will run, and that machine's domain name. You then need to confirm

the operating system shown on the drop-down list is correct, specify the Oracle

user's operating system account name and group, and finally specify the base

directory under which the installation is to take place.

You can install either a fresh database or a Vision Demo database.

• A fresh database is fully configured and ready to be used for a new

implementation. This type of database is suitable for any type of system that

requires a fresh database, such as a production system or test system. The

default name for a production database is PROD. If you are installing a

database for another use, for example as a test system or a backup system,

choose the Fresh Database option and enter a database name that reflects its

purpose, for example TEST.

• A Vision Demo database is used for demonstration or training purposes. It

contains a fully configured Oracle Applications system that has been

implemented and populated with a set of transactions for a fictitious company.

The Vision Demo database is set up for multiple-organization use. It is installed

with the AL32UTF8 character set to maximize the support for character sets in

this release. The default database name is VIS.

Accept the default database name or type in another name (alphanumeric, not to

exceed 8 characters in length, with no spaces) for the local instance. This name is

often referred to as the database SID.

The Database Install Information screen prompts you for information Rapid Install

needs to set up and install the database.

The Base directory field defaults to a sample directory name, using the operating system syntax for the machine where you started the Rapid Install wizard. This

directory is the top-level directory that Rapid Install uses to derive the mount

points associated with the RDBMS.

The Database OS User is the account that will own the database technology stack

and file system. Enter the name of the Database OS Group. The Database OS User

may belong to other groups, but it must belong to this group.

If you wish to search the file system for a suitable base directory, click Browse to

open a navigation window.

On this screen, click on a suitable folder, or type a path in the Directory field. Click

OK to confirm your choice and return to the Database Node Configuration screen,

or click Cancel to return without making a selection.

After returning to the parent screen, then click Next to continue with the install.

7. Select product license type (Fresh Database installation only)

When installing a fresh database (not a Vision demo database), the wizard prompts you to indicate the type of licensing agreement you have purchased from Oracle. It

then presents the appropriate licensing screen.

Completing a licensing screen does not constitute a license agreement. It simply registers

your products as active. The only way to set up a license agreement is to purchase

Applications products through the Oracle Store or an Oracle sales representative.

You should have complete information about your product license before you

complete the licensing screens.

Rapid Install installs all products regardless of their licensed status. However, you

must register products you have licensed so that they are flagged in the system as

active. An active flag marks products for inclusion in patching and other tasks that

you will perform to update and maintain your system after the initial installation.

Note: Rapid Install automatically installs and registers shared and

dependent products for you.

You can register products using either the Suite license model or the Component license

model. Complete only one of these licensing screens, to match your licensing

agreement.

If you clicked the Suite licensing option on the Suite Selection screen, the Licensing

Page for that option appears.

This licensing model allows wide access to Applications functionality. By choosing

it, you tell Rapid Install to automatically register all products included in the

Applications price bundle. The products that are checked and grayed are licensed

automatically as a part of the suite. The ones that are not must be registered

separately as additional products — they are not part of the E-Business Suite price

bundle. Place a check mark next to any additional products you have licensed and

want to register.

If you clicked the Component licensing option on the Suite Selection screen, the

Licensing Page for that option appears.

Choose this option if your licensing agreement is for individual Applications

component products. These products are licensed based on the number of

authorized users or on the number of business transactions processed. All

individual products are listed on this screen. Products that are grayed out cannot be

selected unless the "parent" component is selected.

Note: To register additional products after the initial installation,

use the License Manager component of Oracle Applications

Manager. For more details, see License Manager in Oracle

Applications System Administrator's Guide - Maintenance.

Complete the appropriate licensing screen and click Next to continue.

8. Select Country-Specific Functionality (Fresh Database installation only)

Some systems require the country-specific functionality of a localized Applications

product. For example, if your company operates in Canada, products such as

Human Resources require additional features to accommodate the Canadian labor

laws and codes that differ from those in the United States. You register the name of

the region associated with the localized product on the Select Country-specific

Functionalities screen.

If your company operates only in the United States, you can bypass this screen. If

you begin doing business in another country at a later date, you can use License

Manager to register the associated region at any time after the original installation

All the country-specific functionalities that Oracle supports are listed on this screen,

arranged alphabetically. Double-click a region in the Available Regions box to move

it into the Selected Regions box or highlight it and click the right arrow (>). To

deselect a region, highlight it and double-click or click the left arrow (<) to remove it

from the Selected Regions box.

To select or deselect all the regions and move them between boxes in a single action,

use the relevant double arrows, >> or <<.

After making your selection, click Next to continue.

9. Select Internationalization Settings (Fresh Database installation only)

American English is the only language installed in your system by default.

However, Oracle Applications supports numerous other languages. These can be

activated using License Manager (part of Oracle Applications Manager), and

installed after the initial Release 12.1.1 installation is complete.

The languages you select help determine to the available options for the other

NLS-related configuration parameters (such as territory and character set) that your

system requires and can support.

Double-click a language in the Available Languages box to move it into the Selected

Languages box or highlight it and click the right arrow (>). Highlight a language in

the Selected Languages box and click the left arrow (<) to remove it. The example

shows Canadian French selected as an additional language. To select or deselect all

10. Enter Primary Applications Node Information

You have already specified the top-level directory for the RDBMS. Now you must

specify top-level directory and subdirectories associated with the Applications

nodes.

The default sample directories use the syntax of the operating system where you

started Rapid Install. In addition, some of the fields are operating system-specific.

The above example shows this screen for a Linux system, where you need to

complete the information for Apps OS User (the account that owns the Applications

tier file system and technology stack) and Apps OS Group (the group to which the

Apps OS User belongs). Accept the defaults, or enter new values.

On all these equivalent Primary Applications Node Configuration screens, the Base

directory is the top-level directory that Rapid Install will use to derive the mount

points for the Applications nodes. You can accept the default or enter a new value.

Clicking the Edit Services button enables you to choose which services are enabled

on this Applications node. Categories are: Root Services, Web Entry Point Services,

Web Application Services, Batch Processing Services, and Other Services.

The services define the set of processes that will be started on each Applications

node, and can be activated or deactivated according to the function the node is to

perform. There is no concept of a "Forms node", "Web node", and so on, as there is

no association between installed files and the services that can be run on that

machine. This model enforces the three-tier architecture and simplifies tasks such as

patching and upgrading.

Note: All the APPL_TOPs on a multi-node system contain the same

files, regardless of a particular node's role (as defined by the

currently activated services).

11. Review Database and Applications Node Information

At this stage, you have specified details for the database node and the primary

Applications node. For simple environments, you may only want a single

Applications node, in which case you simply click Next to bypass the next step.

13. Review Pre-Install Checks

Rapid Install performs a series of system tests to validate the configuration

specified. The System Check Status screen checks port availability.

The Validate System Configuration screen now appears, to indicate whether

various pre-install requirements for the installation have been met.

Begin the Installation

On the Component Installation Review screen, Rapid Install lists the components it

will install, based on the system parameters you entered in the wizard.

Click Next. Rapid Install now displays another alert screen asking you to verify that

you are ready to begin the installation. Click Yes.

Monitor Installation Progress:

1. Check progress bars

During an installation, Rapid Install displays a main progress bar and an individual

progress bar. The main progress bar reports on the completion percentage of the

installation as a whole. The individual progress bar reports on the progress of each

individual step. The installation is not complete until all the progress bars disappear from your screen.

Post-Install Review:

After the installation is complete, Rapid Install automatically validates the installed

Applications environment. Tests include database availability, correctly-configured

environment files, and functioning listeners.

If you wish to review the Post-install Checks screen, click Back. If you want to log on

to Oracle Applications now, click Connect to Oracle Applications Release 12.1.1 to

access the Oracle Applications Login page. Otherwise, click Finish to complete the

Rapid Install session.

Required Tasks for All New Installations

The tasks in this section are required to complete the installation process that was

started by running Rapid Install. You must complete every task in this section.

Log On to Oracle Applications

You log in to Oracle Applications using a web browser from the Applications Login

page URL.

Important: The Rapid Install Portal is obsolete. Its features are all still

available via other routes; for example, you can access Oracle

Applications Manager (OAM) functions by selecting the System

Administrator responsibility.

Oracle Applications Login page

From the Oracle Applications Login page, you can access the E-Business Suite Home

Page, which provides a single point of access to HTML-based applications, forms-based

applications, and Business Intelligence applications. You access the Oracle Applications Login page from the following URL:

Example

http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin

Once the connection has been made, the Oracle E-Business Suite Login page appears.

Enter your username and password.

The system administrator should log in the first time using the sysadmin login account

that is pre-configured in the Applications installation. Use the System Administrator

responsibility to launch an Applications Forms session where the system administrator

can complete the implementation steps.

Change Default Passwords

The default passwords for the SYSTEM and SYS Oracle Applications database accounts

are manager and change_on_install, respectively. To maintain database security and

restrict access to these accounts, you should change these passwords without delay,

ensuring that your choices meet your organization's security requirements. The

password for both SYS and SYSTEM in the Vision Demo is manager.

You should also change the default passwords for the Applications product accounts of

the production and test databases

After your credentials have been validated, the Oracle E-Business Suite Home Page

Oracle appears. From this page you can access responsibilities for any of the individual

Oracle Applications products that are licensed.

After Installing or Upgrading:

Perform the following steps after installing or upgrading to Release 12.1.1 and before allowing users to access the system.

Relink Advanced Supply Chain Planning executables (for SLES 10 and Oracle Linux/RHEL 5.4 or higher only)

During the relink phase of the installation of EBS Release 12 (12.1.1) on RHEL 5.4 (Update 4 or higher), failures will result while relinking the Advanced Supply Chain Planning (ASCP) executables. To fix this problem, users are required to replace the following line under the Linux section of the $AD_TOP/bin/adrelinknew.sh:

CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'

with

CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'

After making this change, users are then required to run the adadmin utility and relink application executables.

Additional Information: The application of an EBS Release Update Pack (RUP) or AD family pack could over-write the adrelinknew.sh file - users must then re-edit and make changes to the above file in order to avoid relinking failures.

LD_LIBRARY_PATH Environment Variable

Dynamic libraries are used as part of the relinking and execution processes. The LD_LIBRARY_PATH environment variable is used by Oracle E-Business Suite to locate the required dynamic libraries at runtime - this variable is set by the Rapid Install wizard during the installation of EBS as well as by the Rapid Clone script (adcfgclone) when configuring the target system.

If we need to change these values, use the Edit Parameters function of the OAM AutoConfig tool (by logging in as 'System Administrator' responsibility, clicking on 'System Administrator', selecting 'AutoConfig' under 'Oracle Applications Manager', and clicking on the 'Environments' tab):

On each application tier server node:

LD_LIBRARY_PATH is set in three places:

·         $APPL_TOP/admin/adovars.env

·         $ORA_CONFIG_HOME/10.1.2/[CONTEXT_NAME].env, in the 10.1.2 Oracle home directory

·         $ORA_CONFIG_HOME/10.1.3/[CONTEXT_NAME].env, in the 10.1.3 Oracle home directory

In the AutoConfig interface, this corresponds to:

Location	Parameter
adovars	LD_LIBRARY_PATH
tools_home (10.1.2)	LD_LIBRARY_PATH
youb_home (10.1.3)	LD_LIBRARY_PATH

On the database server node:

LD_LIBRARY_PATH is set in $ORACLE_HOME/[CONTEXT_NAME].env which corresponds in the AutoConfig interface to:

Location	Parameter
db_home	LD_LIBRARY_PATH

After making these changes, run AutoConfig (adautocfg.sh) to implement the changes on the application and database tiers.

.