R12 Installation Guide

R12 Installation Guide Page No:1

 Table Of Contents

1. Pre-requisites for Installing ………………………………… 3

Operating System Requirement ………………………………………….. 3
Hardware Requirement …………....….……..…………………………….. 3
CPU’s required………………………..…………………………………….. 5
Memory Required…………………………………………………………… 5
2. Creating UNIX users and Groups ……………………………… 6
Creating OS Groups. ……….…………………………………………….... 6
Creating OS Users.………….…………………………………………….… 6
Check the Ownership and Privilege. ….……………………….….... 6
3. Steps for starting the installation …………………….…………. 6
Multi node installation ……..…………………………………….………… 17

4. Post Install Steps ………………………………………………….19

5. References…………………………………………………………. 21

R12 Installation Guide Page No:2

The following Requirements should be met to Install R12 Oracle Applications.

Hardware Requirement:

Linux Windows
Disk Space (min) 150 Gb 150 Gb
Memory 1 Gb 1 Gb
Number of CPU’s 1 1
Clock Speed of CPU 1.6 GHz 1.6 GHz

Operating System Requirement:

Linux:

Operating System Kernel version Update

Oracle Enterprise Linux 4 2.6.9-42.0.0.0.1.EL 4 - Update 4 or higher (32-
bit)
Oracle Enterprise Linux 5 2.6.18-8.el5PAE 5 - Update 1 or higher (32-
bit)
Red Hat Enterprise Linux 2.4.21-27.EL 3 - Update 4 or higher (32-
AS/ES 3 bit)
Red Hat Enterprise Linux
AS/ES 4 2.6.9-42.EL Update 4 or higher (32-bit)
Red Hat Enterprise Linux 5 2.6.18-8.el5PAE 5 - Update 1 or hgiher (32-
bit)

Windows:

Windows server 2003 (all editions)

R12 Installation Guide Page No:3

Software Requirements:

JDK Requirement: (For Both Linux and Windows)

JDK 5.0 required for R12 Oracle Applications and there is no need to install it separately
as it is bundled with Oracle Applications.

For Linux:

Maintenance Tools Required:

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

For Windows:

Microsoft Visual Studio 2005

Install Visual C++ 2005 (also known as Visual C++ 8.0) included in Microsoft Visual
Studio 2005, which needs to be purchased from Microsoft or resellers of Microsoft
products.

Note: Visual C++ 2005 (8.0) must be installed from either the Standard or Professional
editions of Microsoft Visual Studio 2005.

Note: Visual C++ 2008 (9.0) is not currently certified with EBS Release 12.

MKS Toolkit
Versions 9.0 (Patch 3 or higher), 9.1 and 9.2 of the MKS Toolkit are currently certified
for use with EBS Release 12. Use any of the Developer series (for Developers, for
Professional Developers, or for Enterprise Developers).

GNU Make (Shareware)

Version 3.81 is required. Download and unzip patch 5897842. This patch contains the
GNU Make source files and the pre-built executable file, gnumake.exe.
Copy gnumake.exe (located in make-3.81/WinRel/) to the UNIX Toolkit installation
directory, for example, C:\MKS90\mksnt.

R12 Installation Guide Page No:4

Microsoft Visual C++ 2005 Redistributable Package (x86)
If you have a multi-node Oracle Applications system and do not have Microsoft Visual
Studio 2005 on the node hosting the database tier, the Microsoft Visual C++ 2005
Redistributable Package is required.

CPU Requirement:

For testing Installations we can have a single CPU of 1.6 GHz. The CPU requirements
increase with the following aspects.

 The size of database.

 The number of concurrent users.
 The average growth of database.
 The type of concurrent processing jobs that needs to be run.
 The other services the server will host apart from Oracle
Applications.
 The nodes Planned for the architecture.

Memory Requirement:

For testing installation we can have a RAM of 1 GB. The CPU requirements increase
with the following aspects .The memory requirement will also depend upon the
concurrent user and the number of users.

1) The size of the database as depending on it we have to calculate the SGA to be.
2) It also depends on the number of concurrent users and sessions connecting to the
database.
3) The data processing estimated on the database.
4) If it’s a single instance or multi node RAC database.
5) Other software planning to install on the server.

R12 Installation Guide Page No:5

2. Creating UNIX users and Groups:

Creating Os Groups:
Create a group by name ‘dba’
# groupadd -g 5000 dba
To check the group information
# cat /etc/group
Creating Os Users:
Create two Os users one will be the owner for Oracle Database and One will be the
owner for Applications.
# useradd –g dba -d /home/oracle –m oracle
# useradd –g dba -d /home/applmgr –m applmgr
Assign Passwords:
# passwd oracle
# passwd applvis
To Check the Users information:
# Cat /etc/passwd
Check the Ownership and Privileges:
#chown –R oracle:dba /disk1 /disk2 /disk3
# chmod –R 775 /disk1 /disk2 /disk3

3. Steps for starting the installation:

Go to the R12 Oracle Applications Software Stage

/StageR12/StartCD/Disk1/rapidwiz/ and execute the following command:

$./rapidwiz

The following screen appears:

R12 Installation Guide Page No:6

Click Next

Select the radio button “Install Oracle Applications Release 12” and Click Next.

R12 Installation Guide Page No:7

Select the radio button “Accept Oracle Connection Tools Agreement” if you have
metalink details or else select the other and Click Next.

Select the Radio button “Create a new configuration” if you want to use new
configurations and Click Next.

R12 Installation Guide Page No:8

Select the port pool or even you can edit the port to be used for different services and
Click Next.

Enter the database node information like its SID, Hostname of the server Domain Name,
UNIX user who owns the database node and the base directory of the Database node and
Click Next.

R12 Installation Guide Page No:9

Give the Application node information where you want to install the applications in case
of multimode installations.

If you are doing a single node installation give the same details of the Database node.
And Click Next.

R12 Installation Guide Page No:10

Verify the node information and Click Next.

Verify that the pre-install checks are passed and Click Next.

You will be navigated to a Pop up message to verify to continue with installation, if

you want to go ahead then click YES.

R12 Installation Guide Page No:11

The installation would be started.

Verify the post install check and click Next.

The Installation wizard shows the components Installed. Click Finish.

R12 Installation Guide Page No:12

Multi Node Installation:

If it’s a multi node installation you have start the installation at the next application
nodes.

Copy or mount the R12 Oracle Applications Software stage to Application node.

Go to the /StageR12/StartCD/Disk1/rapidwiz/ directory and execute the following:

$./rapidwiz

Click Next.

R12 Installation Guide Page No:13

Select Radio button “Install Oracle Applications Release R12” and click Next.

Select the radio button “Accept Oracle Connection Tools Agreement” if you have
metalink details or else select the other and Click Next.

R12 Installation Guide Page No:14

Copy the configuration file created on the database node to application node and load that
file during the installation or point the file on the database node.

Click Next.

R12 Installation Guide Page No:15

Verify the check list and click Next.

Click Next.

R12 Installation Guide Page No:16

Installation would progress.

Check the post install tests are passed and click Next.

R12 Installation Guide Page No:17

Click Finish.

Here you will be done with installing R12 Oracle Applications.

R12 Installation Guide Page No:18

4. Post Install Steps:

Log On to Oracle Applications

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

Once the connection has been made, the Applications Login page appears. Enter your
username and password.

After your credentials have been validated, the E-Business Suite Home Page appears.
You can use this page to access responsibilities for any of the individual Oracle
Applications products that your organization has licensed.

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.
You should also change the default passwords for the Applications product accounts of
the production and test databases.

Update PL/SQL Log and Out Directory

The temporary directory on your database server for log and output files from PL/SQL
concurrent programs is set to /usr/tmp (UNIX) or C:\TEMP (Windows) by default. This
value is specified in the utl_file_dir parameter of the database initialization file, and
assigned to the APPLPTMP environment variable. As the temporary files placed in this
directory may contain sensitive information, it should have suitably restricted access,
such as read and write access for the account that owns the database.
Enter your choice of directory as the new value for utl_file_dir in the database
initialization parameter file. Then use the edit AutoConfig parameters feature of Oracle
Applications Manager to update the APPLPTMP variable in the Applications context file
with the new utl_file_dir directory location. Finally, run AutoConfig to recreate the
environment files.

Implement Product and Country-Specific Functionality

Depending on which products or country-specific functionality you plan to use in your
installation, you may need to perform additional tasks or apply additional patches.
Refer to the individual product or country-specific implementation manuals, user's
guides, or OracleMetaLink for details.

Check Client Software For Use With Forms Applet

The connection between the client and the E-Business Suite forms is provided through an
applet in the client Web browser.

R12 Installation Guide Page No:19

Instead of using the browser's own JVM, Oracle Applications Release 12 uses the Sun
J2SE Native Plug-in, which is invoked when a user chooses to access functions that
require it, such as running a form. J2SE replaces Oracle JInitiator, which was used in
Release 11i. If the J2SE Plug-in has not been installed, the browser prompts the user to
download the required installation executable.

Resize the Database

You will need to increase the size of your database to meet the specific requirements of
your system. The increase will in part depend on the products you have licensed and the
additional features (such as multiple languages or multiple organizations) you
Configure in your installation.

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 Applications to locate the
required dynamic libraries at runtime. Rapid Install sets LD_LIBRARY_PATH as
follows:

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

To change the value in any of the application tier locations, use the Edit Parameters
function of the OAM AutoConfig tool to update the following fields (as required). Then,
run AutoConfig (adautocfg.sh) to implement the changes.

Location Parameter
adovars LD_LIBRARY_PATH
10.1.3 Oracle Home LD_LIBRARY_PATH
Tools Oracle Home LD_LIBRARY_PATH

R12 Installation Guide Page No:20

Net Service Listeners in Multi-user Installations

Net Service Listeners use the /var/tmp.oracle directory to store temporary files. To give
all users in a multi-user installation write privileges, update /var/tmp/.oracle with 777
permissions:

$ chmod 777 /var/tmp/.oracle

5. References:

Metalink documents:

Doc ID: Note: 402310.1

Doc ID: Note: 402311.1

R12 Installation Guide Page No:21