ORA EBS R12 Blade Center 072208

Oracle E-Business Suite Release 12 on
IBM BladeCenter Hints and Tips

. . . . . . . .
Betty Lee
IBM Oracle International Competency Center
July 2008
© Copyright IBM Corporation, 2008. All Rights Reserved.

All trademarks or registered trademarks mentioned herein are the property of their respective holders
Table of contents
Disclaimer ....................................................................................................................................1
Abstract........................................................................................................................................2
Introduction .................................................................................................................................2
Prerequisites ...............................................................................................................................2
Oracle E-Business Suite Release 12 Overview ........................................................................3
Architectural Components ....................................................................................................................... 3
Desktop Tier ...................................................................................................................... 3
Application Tier.................................................................................................................. 3
Database Tier .................................................................................................................... 5
Managed File System .............................................................................................................................. 6
Single-node versus multi-node Installation..............................................................................6
About System x and BladeCenter .............................................................................................8
Hardware ................................................................................................................................................. 9
Software................................................................................................................................................. 10
Prerequisites .............................................................................................................................12
Disk requirements .................................................................................................................................. 12
Installing the required Red Hat Enterprise Linux 4 Update 4 packages................................................ 12
Java Development Kit 5.0 ...................................................................................................................... 13
Kernel Settings....................................................................................................................................... 13
Setting the shell limits on database tier ................................................................................................. 14
Networking ............................................................................................................................................. 14
Oracle E-Business Release 12 Considerations......................................................................15
Installation / Maintenance ...................................................................................................................... 15
Database Version ............................................................................................................ 15
Domain Name.................................................................................................................. 15
Running Autoconfig on Database Tier ............................................................................ 15
Updating ICX_parameters............................................................................................... 16
Running Autoconfig on Applications Tier ........................................................................ 16
Updating appsweb.cfg..................................................................................................... 18
Starting Application Processes........................................................................................ 18
Logging into the Applications .......................................................................................... 22
Additional Configuration and Deployment Options ......................................................... 23
Initialization Parameters......................................................................................................................... 23
Desktop Clients...................................................................................................................................... 24
Upgrade ................................................................................................................................................. 24
Post Installation Notes ........................................................................................................................... 24
Possible Errors....................................................................................................................................... 25
During Installation............................................................................................................ 25
Post-Installation ............................................................................................................... 26
Maintenance .......................................................................................................................................... 27
Summary................................................................................................................................................ 28
Oracle E-Business Suite Release 12 on IBM System x Hints and Tips

http://www.ibm.com/support/techdocs
© Copyright 2007, IBM Corporation 2
Reference...................................................................................................................................29
About the author .......................................................................................................................30
Appendix A: Oracle E-Business Suite Release 12 Terminology ..........................................31
Appendix B: Oracle E-Business Suite Release 12 Installation Steps ..................................32
Running rapidwiz ................................................................................................................................... 32
Starting Rapid Install Wizard ................................................................................................................. 34
Appendix C: E-Business Suite Release 12 .............................................................................49
Appendix D: Oracle Applications Manager.............................................................................51
Trademarks and special notices..............................................................................................52
Oracle E-Business Suite Release 12 on IBM System x Hints and Tips

© Copyright 2007, IBM Corporation 3
Disclaimer
This document reflects the understanding of the IBM Oracle International Competency Center (ICC)
about Oracle solutions running on IBM servers and storage products. It was produced and reviewed by
the members of IBM Oracle ICC and other IBM team members.
The information in this paper is intended to provide guidance for those implementing Oracle E-Business
Suite Release 12. It discusses the findings based on a solution that was created and tested under
laboratory conditions at the ICC. As a result, these findings may not be realized in all customer
environments and the implementation suggested in this paper may require additional steps,
configurations and performance analysis.
The information herein is provided “AS IS” with no warranties, expressed or implied. This information
does not constitute a specification or is part of the warranty for any IBM or Oracle products.
Implementation and certification of the solution rests on the implementation team at the specific
installation. The users of this guide should always check the latest release information in the product
“Readme” documents and its related web pages for updates.
If you have questions about the contents of this document, please direct them to the IBM Oracle
International Competency Center (ibmoracl@us.ibm.com). Any feedback with suggestions is very
welcome.
Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

© Copyright 2008, IBM Corporation
1
Abstract
The objective of this paper is to assist those who are installing Oracle E-Business Suite Release
12 on the IBM BladeCenter® running the Linux® Operating System. The information in this
paper is written from experience gained by working on the Oracle Application Standard
Benchmark (OASB) kit and generally available documentation from IBM, Oracle, and other
sources.
Introduction
Oracle E-Business Suite Release 12 is sold as a “global release” because it offers a global solution for an
enterprise to manage globally by helping companies to meet global market needs.
All these new functionalities and capabilities offered by Oracle E-Business Suite Release 12 and the
latest System x™ family of servers from IBM can help customers to improve their ability to manage their
business.
This paper will discuss briefly the overall components of Oracle E-Business Suite Release 12, IBM
System x and BladeCenter. Emphasis will be on providing tips and consideration of installation and
implementation of Oracle E-Business Suite Release 12 on the Red Hat Linux distribution.
For Oracle E-Business Suite Release 12 on IBM AIX® 5.3, please refer to the white paper called “Oracle
E-Business Suite Release 12 Installation and Tips for IBM AIX 5.3” at:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101168
Prerequisites
Fair understanding of Oracle databases
Good knowledge of Linux and UNIX® operating systems

2
Oracle E-Business Suite Release 12 Overview
Oracle E-Business Suite Release 12 is a new release for Oracle E-Business Suite 11i. It continues to
offer solutions for different type of businesses across the globe and allows them to access the
applications via the internet. The latest update available for Oracle E-Business Suite Release 12 is
Release 12 RUP4 for all modules, and Release 12 RUP5 for Financials and HRMS modules. Please
check the Certify page on Oracle’s Metalink website for updates on newer patches and releases
periodically.
These terms will be used in this section and their meanings are as follows:
Services: a process or a group of processes running on a single machine and that offer a
particular functionality.
Tier: a server or a group of services, for example, application tier or database tier.
Node: a host running one or more servers. Sometimes a group of servers that work closely
together is named a cluster.
Please refer to Appendix A for Oracle E-Business Suite Release 12 terminology.
Architectural Components
Oracle E-Business Suite Release 12 is composed of primarily three tiers: the desktop tier, the application
tier, and the database tier.
Desktop Tier
The desktop tier is mainly a client interface which can be a Microsoft®-Windows® based PC or thin
client. By running a Java™ applet in a Web browser it will launch HTML-based applications and/or
Forms-based applications.
In Oracle E-Business Suite Release 12 it provides a single sign-on feature which allows a user to sign
on one-time only to access HTML-based applications, Forms-based applications, and Business
Intelligence applications.
The desktop tier contains the forms client applet and desktop Java client. Forms client applet is a
collection of Java Archive (JAR) files which consist of all Java classes needed to run the presentation
layer of Oracle Application forms. The desktop Java client must have a Java Virtual Machine (JVM)
which is called J2SE plug-in installed. One of the main differences between Oracle E-Business Suite
11i and Oracle E-Business Suite Release 12 is the change from Oracle JInitiator to J2SE Plug-in
during the applications launch.
Application Tier
The application tier is sometimes referred as middle tier because it manages the communication
between the desktop tier and database tier. It is comprised of four servers or service groups which
include:

3
1. Web Services
2. Forms Services
3. Concurrent Processing Server
4. Administration (Admin) Server
Another difference between Oracle E-Business 11i and Oracle E-Business Suite Release 12 is that
Oracle Application Server (OracleAS) 10g is packaged with Oracle E-Business Suite Release 12 and
provides Web and Forms services whereas Oracle E-Business Suite 11i had Web server and Forms
server as separate processes.
Moreover, Oracle recommends only one type of platform for the application tier for easier
maintenance.
Oracle E-Business Suite Release 12 uses two different OracleAS 10g releases which are installed in
separate ORACLE_HOME.
1. OracleAS 10.1.3 ORACLE_HOME consists of the latest version of Java Servlet Engine
(OC4J), Oracle Process Manager (opmn), Apache and application modules.
2. OracleAS 10.1.2 ORACLE_HOME comprises mainly frmweb executable and formsapp.ear.

In summary, the following table shows the different versions of Oracle Database and OracleAS
ORACLE_HOME in Oracle E-Business Suite 11i and Oracle E-Business Suite Release 12.
Oracle E-Business 11i Release 12

Suite
Database Server Oracle9i Oracle10g Release 2 (10.2)

ORACLE_HOME
OracleAS Tools, Developer Oracle9iAS 1.0.2.2.2 OracleAS 10g (10.1.2)

ORACLE_HOME
OracleAS Java or Web Oracle9iAS 1.0.2.2.2 OracleAS 10g (10.1.3)

ORACLE_HOME
Table 1: Different versions of ORACLE_HOME under Oracle E-Business Suite 11i and Oracle E-Business Suite
Release 12
Another name change for Oracle E-Business Suite Release 12 is that the Self-Service applications
are now referred as HTML-based applications. It uses the Oracle Applications Framework as the
development platform.
In Oracle E-Business Suite Release 12, the Reports Server is obsolete; all reports are run by rwrun
executable in Concurrent Processing server.

4
Daily Business Intelligence (DBI) has replaced Business Intelligence System (BIS); and through DBI
overview pages, managers can read summarized information across multiple organizations with the
ability to drill down details on a daily basis.
Database Tier
The database tier contains the Oracle database server which is comprised of all database files,
Oracle applications database executables, and Oracle applications online help information.
Since the Oracle database server sometimes is available on some platforms that have been certified
whereas Oracle applications have not been certified on those platforms, mixed platform architecture
(formally referred as split configuration architecture) can be utilized. For instance, the database tier
can be deployed on the IBM System z™ running Linux while the application tier can be deployed on
an Intel® x86 machine running Linux and the desktop tier on a platform running Microsoft Windows.
Oracle E-Business Suite Release 12 has utilized the Oracle Applications Tablespace Model (OATM)
which used a small number of tablespaces. All these tablespaces used locally-managed
tablespaces. Depending on the type of data the objects contain and their I/O characteristics, the
objects are stored in these shared tablespaces. For instance, if the table contains transaction data,
then it is allocated to APPS_TS_TX_DATA. If the table contains seed data, it is allocated to
APPS_TS_SEED. Although most indexes stayed together with the base table in the same
tablespaces, transaction indexes are allocated to APPS_TS_TX_IDX.
The following are the main applications tablespaces in Oracle E-Business Suite Release 12:
1. APPS_CALCLIP
2. APPS_OMO
3. APPS_TS_ARCHIVE
4. APPS_TS_DISCO
5. APPS_TS_INTERFACE
6. APPS_TS_MEDIA
7. APPS_TS_NOLOGGING
8. APPS_TS_QUEUES
9. APPS_TS_SEED
10. APPS_TS_SUMMARY
11. APPS_TS_TOOLS
12. APPS_TS_TX_DATA
13. APPS_TS_TX_IDX
14. APPS_UNDOTS1

5
Please refer to the Oracle Applications Concepts Release 12 manual (Part No. B31450-01) for further
details on this subject.
Managed File System

In Oracle E-Business Suite Release 12, there are three ORACLE Homes: One for database and two for
Oracle Applications Servers. The reason of having two ORACLE Homes for Oracle Applications servers
is that the development environment for Forms and Reports is using Oracle Database 10.1.2.
There is a new environment variable besides APPL_TOP and COMMON_TOP in Oracle E-Business
Suite Release 12. It is called INSTANCE_TOP ($INST_TOP). The startup and shutdown scripts for
applications processes, and configuration scripts for the applications are allocated in $INST_TOP.
IAS 10.1.3 I IAS 10.1.2 Database

ORACLE_HOME ORACLE_HOME ORACLE_HOME
10.2
RSF 10.1 RSF 10.1

RSF 10.1 RDBMS Components
Apache 1.3 Forms 10
OC4J Reports 10
APPL_TOP
* APPL_TOP contains Applications’
code staging area
COMMON TOP * COMMON TOP contains runtime location

for Java and HTML
* INSTANCE TOP contains configuration

INSTANCE TOP and run-time generated files
Figure 1: Oracle E-Business Suite Release 12 Managed File System
Single-node versus multi-node Installation

Oracle E-Business Suite Release 12 can be installed on a singe node or multiple nodes (multi-node). All
the services will be installed on a single host for a single-node installation.
For single-node installation, you could use the Express Install and create a user for the database and
applications installation. This method of installation is mostly adopted by organizations which have small
workload. It is also useful for test and development environments.

6
Report
Server
Forms
Server
Web
Web Admin
Browser
Web
Browser Server
Database
Browser
Concurrent Server
Desktop Processing
Clients Server
Discoverer
Server
Web
Server
Application Tier Database Tier
Single Node
Figure 2: Single-node installation
You can also set up more than one service on multiple nodes. You can have different applications nodes
performing different functions. For example, one applications node can be used for concurrent
processing server; and the other applications node can be used for Admin server and Application Server.
In this way, the workload will be well distributed across the applications node.
For multi-node installation, you need to use the Standard Install and create users for both database and
applications installation. You could use oracle to be the user on the database node; and applmgr to be
the user on the applications node. In this case, you will need to use root to install on both nodes so that
Oracle can have permission to install on them. Remember to start the installation on the database node
first. Then, proceed onwards to other applications node. However, you could install on the multiple
applications node at the same time.
For more details on installation, please refer to Oracle Applications Installation Guide: Using Rapid Install
Release 12 (Part No, B31295-04). The detailed installation steps are located in Appendix B: Oracle E-
Business Suite Release 12 Installation Steps.

7
App node 1
Report
Server DB Node
Forms
Server
Admin
Server
Web
Web
Browser
Web
Browser
Browser App node 2 Database
Concurrent Server
Desktop Processing
Clients Server
Web
Server
App node 3
Discoverer
Server
Database Tier
Application Tier
Figure 3: Multi-node installation example
About System x and BladeCenter

Oracle E-Business Suite Release 12 architecture offers great flexibility when it comes to hardware
configuration. Workload, availability and operational requirements will drive the configuration of servers.
The System x platform and the IBM BladeCenter provide a wide variety of servers for the configuration of
Oracle E-Business Suite Release 12. System x servers range from 2-way to 16-way models in tower or
rack-optimized form factors. IBM BladeCenter offers flexible modular technology by integrating Intel
processor-based or AMD processor-based, and IBM POWERTM processor-based blade servers into a
highly integrated package featuring high redundancy, remote management, network, and SAN (Storage
Area Network) integration.
The System x and BladeCenter servers can run either Linux or Microsoft Windows operating systems.
POWER processor-based blade servers can run either AIX or Linux. For more information, please refer
to the following table:

8
IBM Systems Web sites
IBM BladeCenter http://www-03.ibm.com/systems/bladecenter
IBM AMD processor-based Systems http://www-03.ibm.com/servers/eserver/opteron/index.html
IBM System x http://www-03.ibm.com/systems/x
IBM Intel processor-based Systems http://www-03.ibm.com/systems/browse/inpro/index.html
Table 2: IBM Systems and related web sites
Hardware
The hardware configuration used to develop this paper is shown in the following diagram. Two blades in
the IBM BladeCenter were used for the database and applications tiers. A SAN consisting of an IBM
System Storage® DS4800 Storage Server and DS4000™ EXP700 storage expansion units provided disk
storage for each blade. For information on IBM TotalStorage DS4800, please refer to http://www-
03.ibm.com/systems/storage/disk/ds4000/ds4800.
Public Network
Database Tier Applications Tier

Blade HS21 Blade HS21
DS4800 Storage
Server
FAStT EXP700
Storage Expansion
Units
Figure 4: Hardware configuration

9
Software
In this test configuration Linux operating systems, FAStT software and Oracle E-Business Suite Release
12 have been installed on both database and applications tiers.
Linux operating systems

Red Hat Enterprise Linux 4 (RHEL4) Update 4 32-bit is installed on both tiers. Please refer to Oracle
product certification page in Oracle Metalink for the latest certification information. This is the
certification information for both applications and database tiers as of June, 2008.
Platform/OS RHEL AS/ES 3 RHEL AS/ES Oracle Enterprise SLES-9

4/Oracle VM Linux 4/Oracle VM
Linux x86 Yes Yes Yes Yes
Table 3: Certifications of Oracle E-Business Suite Release 12 on Linux x86 32-bit Operating Systems for Application
and Database Tiers.
Note: The database server needs to be in 10gR2 32-bit version.
Platform/OS RHEL AS/ES 3 Linux x86 Oracle Enterprise SLES-9

Linux 4
Linux x86-64 Yes Yes Yes Yes
Table 4: Certifications of Oracle E-Business Suite Release 12 on Linux x86 64-bit Operating Systems for Application
and Database Tiers.
.
Note: The database server needs to be in 10gR2 64-bit version.

Please refer to Metalink Note: 465915.1. “Using Oracle VM with Oracle E-Business Suite Release 11i
or Release 12” for more details on the steps and requirements for running Oracle E-Business Suite
11i or Release 12 in an Oracle VM Linux x86 environment. Note: Oracle E-Business Suite Release
12 is certified on Microsoft Windows 2000 x86 SP4, Microsoft Windows 2003(x86), and Microsoft
Windows XP Professional for both applications and database tiers.
FAStT software
• IBM DS4000 Storage Manager V.9.23 for x86 Linux
• IBM DS4000 Storage Manager V9.23 Linux 2.6 RDAC
To download IBM DS4000 Storage Manager and RDAC, please go to: http://www-
304.ibm.com/jct01004c/systems/support/storage/disk/ds4800/stormgr1.html.
Oracle E-Business Suite Release 12

You can download this product from http://edelivery.oracle.com/ or you can request the media pack
from Oracle Support.

10
To download from the Oracle web site, please go to http://edelivery.oracle.com and navigate to
“Oracle E-Business Suite Applications Release 12.0 Media Pack” for your platform. In this paper,
“Oracle E-Business Suite Applications Release 12 Media Pack for Linux x86” is the location where
most of the zip files were downloaded from. The following parts have been downloaded and consist
of the core Oracle E-Business Suite Release 12.0.4 with Vision Demo database (These files are
updated on March 02, 2008 with part number B37230-01):
• Oracle Applications Release 12.0.4 Rapid Install Start Here
• Oracle Applications Release 12.0.4 for Linux x86 Rapid Install RDBMS
• Oracle Applications Release 12.0.4 for Linux x86 Rapid Install Databases
• Oracle Applications Release 12.0.4 for Linux x86 Rapid Install Tools
• Oracle Applications Release 12.0.4 for Linux x86 Rapid Install APPL_TOP
After downloading them, they need to be unzipped in the base directory. For instance, you have
created the base directory as /d01/stage12. You will need to copy all the zip files to the base
directory and unzip them there. It will then have the proper directory name under the base directory.
For examples, /d01/stage12 will have all sub-directories after unzip all the files.
[oracle@blade7 VIS_blade7]$ cd /d01/stage12
[oracle@blade7 stage12]$ ls
doc install oraAppDB oraApps oraDB oraiAS runInstaller stage startCD

utils
[oracle@blade7 stage12]$ cd oraApps
[oracle@blade7 oraApps]$ ls
component.label Disk1 Disk2 Disk3 Disk4 Disk5 Disk6 Disk7 dvd.label
Figure 5: Staging directory
Please refer to Oracle Metalink Note: 406138.1, “Oracle E-Business Suite 12.0 Rapid Install with
Electronic Delivery Release 12.0”, which contains details for download and staging instructions. More
details can also be found in Metalink Note: 549389.1, “Oracle Applications Release Notes, Release
12.0.4”.
Please be aware that Release 12.0.4 introduces a new version of the Release 12 Rapid Install. This
release also contains all the fixes and functionalities that are needed to set up a new Release 12
system or upgrade an existing 11i system.
Another way to get the media pack is by requesting it from Oracle Support or through Oracle
Metalink. The software usually is shipped in a set of DVDs.

11
Prerequisites
Installation of Oracle E-Business Suite Release 12 is similar across the platforms for which it is certified.
There are some differences for operating systems prerequisite requirements. This section will be
focusing on preparing Red Hat Enterprise Linux 4 update 4.
For Red Hat Enterprise Linux AS/ES 4, JDK (for E-Business Suite) 1.5.0_08 is certified on Oracle
Release 12.0.
Disk requirements
Depending whether you want to install Vision Demo database, more disk space will be needed. The
following table shows you the disk space needed for applications and database nodes.
Node file system Disk space required
Applications node 28 GB
Database node (fresh install) 45 GB
Database node (Vision Demo database) 133 GB
Figure 6: Disk requirements
You will need at least 33 GB for staging area for both applications and database nodes. In addition, you
will need at least 500 MB of free temporary space for both nodes. The temporary directory can be set by
TMPDIR environment variable in Linux, or TEMP and TMP environment variables in Microsoft Windows.
Please refer to Oracle Applications Installation Guide: Using Rapid Install Release 12 (Part No. B31295-
04) for more details.
Installing the required Red Hat Enterprise Linux 4 Update 4 packages

During a fresh installation of RHEL4U4, select the following from the Package Group Selection screen:
Development tools
Kernel development
Legacy software development
The following package groups are not installed by default but are useful for system administration:
FTP server
Legacy network server
After installation, please make sure that you have the following packages with the minimum versions by
running ldconfig –v.
(If you are installing in a 32-bit operating systems, you need the packages with 32-bit; otherwise, the 64-
bit operating systems will need x86_64 packages.)
binutils-2.15.92.0.2-21.x86_64.rpm
compat-db-4.1.25-9.i386.rpm (32-bit)

12
compat-db-4.1.25-9.x86_64.rpm
control-center-2.8.0-12.rhel4.5.x86_64.rpm
gcc-3.4.6-3.x86_64.rpm
gcc-c++-3.4.6-3.x86_64.rpm
glibc-2.3.4-2.25.i386.rpm (32-bit)
glibc-2.3.4-2.25.x86_64.rpm
glibc-devel-2.3.4-2.25.i386.rpm (32-bit)
glibc-devel-2.3.4-2.25.x86_64.rpm
glibc-common-2.3.4-2.25.x86_64.rpm
gnome-libs-1.4.1.2.90-44.1.x86_64.rpm
libstdc++-3.4.6-3.i386.rpm (32-bit)
libstdc++-3.4.6-3.x86_64.rpm
libstdc++-devel-3.4.6-3.i386.rpm (32-bit)
libstdc++-devel-3.4.6-3.x86_64.rpm
libgcc-3.4.6-3.i386.rpm (32-bit)
libgcc-3.4.6-3.x86_64.rpm
make-3.80-6.EL4.x86_64.rpm
pdksh-5.2.14-30.3.x86_64.rpm
setarch-1.6-1.x86_64.rpm
sysstat-5.0.5-11.rhel4.x86_64.rpm
xscreensaver-4.18-5.rhel4.11.x86_64.rpm
openmotif21-2.1.30-11.RHEL4.6.x86_64.rpm**
libaio-0.3.105-2.x86_64.rpm
libaio-0.3.105-2.i386.rpm (32-bit)
libaio-devel-0.3.105-2.x86_64.rpm
libaio-devel-0.3.105-2.i386.rpm (32-bit)
** According to Oracle Metalink Note: 416305.1, for Red Hat 4.0, the openmotif version must be 2.1.30,
and the package name must be in the following format: openmotif21-2.1.30.xxx. For example, openmotif-
2.2.3.10.RHEL4.5 is not supported.
There are additional kernel and software requirements for Linux 64-bit operating systems. For instance,
you will need additional maintenance tools like ar, gcc, g++, ksh, ld, linux32, make and X Display Server.
Please refer to Oracle Metalink Note: 416305.1 Oracle Applications Installation and Upgrade Notes
Release 12 (12.0) for Linux (64-bit) for more details.
Java Development Kit 5.0

Java Development Kit (JDK) 5.0 is required for Oracle E-Business Suite Release 12 and is bundled with
Oracle E-Business Suite Release 12. Rapid Install will install it automatically. JDK 1.5.0_08 is certified
with Oracle E-Business Suite Release 12.
Kernel Settings
You will also need to configure your kernel settings in /etc/sysctl.conf. After making the changes,
remember to apply the changes by doing sysctl –p or reboot your systems.

13
net.core.rmem_max = 262144
net.core.rmem_default =262144
net.core.wmem_max = 262144
net.core.wmem_default = 262144
net.ipv4.ip_local_port_range = 1024 65000
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 142
kernel.msgmax = 8192
kernel.msgmnb = 65535
kernel.msgmni = 2878
fs.file-max = 65536
Figure 7: Kernel settings
Setting the shell limits on database tier

As root user, add the following lines to /etc/security/limits.conf:
* soft nproc 16384
* hard nproc 16384
* soft nofile 65536
* hard nofile 65536
Figure 8: Shell limits
Networking
As root user, add the following line to /etc/hosts:
9.38.158.177 blade7.sanmateo.ibm.com blade7
Figure 9: /etc/hosts
The format of /etc/hosts is <ip_address> <node_name>.<domain_name> <node_name>.

Please make sure to include domain name in /etc/sysconfig/network file.
The format of /etc/sysconfig/network is HOSTNAME=<node_name>.<domain_name>.
For our testing the following line is added in /etc/sysconfig/network:

14
NETWORKING=yes
HOSTNAME=blade7.sanmateo.ibm.com
Figure 10: /etc/sysconfig/network
Oracle E-Business Release 12 Considerations

This section discusses hints and consideration during the installation, upgrade, and maintenance of
Oracle E-Business Release 12.
Installation / Maintenance
Database Version
The minimum release level and edition to support Oracle E-Business Suite Release 12 is Oracle
Database 10g Release 2 (10.2.0.2) Enterprise Edition.
Domain Name
First of all, you need to make sure that your domain name is set in the servers in your database and
application tiers.
For instance, you need to get the domain name returned when you typed domainname.
[oracle@blade7 ]$ domainname
blade7.sanmateo.ibm.com
Figure 11: domainname
Running Autoconfig on Database Tier

After Oracle database 10g has been installed on the database server, you need to run autoconfig on
database server first before running autoconfig on the application tier. The autoconfig.sh is located
under $ORACLE_HOME/appsutil directory.
[oracle@blade7 ]$ ./adautocfg.sh
Enter the APPS user password:
AutoConfig is configuring the Database environment...
AutoConfig will consider the custom templates if present.
Using ORACLE_HOME location : /u01/app/oracle/10.2.0.3
Classpath :
/u01/app/oracle/10.2.0.3/jdk/jre/lib/rt.jar:/u01/app/o
racle/10.2.0.3/jdk/lib/dt.jar:/u01/app/oracle/10.2.0.3/jdk/lib/tools.jar:/u01/app
/oracle/10.
2.0.3/jdbc/lib/ojdbc14.jar:/u01/app/oracle/10.2.0.3/appsutil/java/xmlparserv2.zip
:/u01/app/o

15
racle/10.2.0.3/appsutil/java:/u01/app/oracle/10.2.0.3/jlib/netcfg.jar:/u01/app/or
acle/10.2.0 .3/jlib/ldapjclnt10.jar
Using Context file :

/u01/app/oracle/10.2.0.3/appsutil/trndtest_oracle.xml
Context Value Management will now update the Context file
Updating Context file...COMPLETED
Attempting upload of Context file and templates to database...COMPLETED
Updating rdbms version in Context file to db102
Updating rdbms type in Context file to 32 bits
Configuring templates from ORACLE_HOME ...
AutoConfig completed successfully.
The log file for this session is located at:

/u01/app/oracle/10.2.0.3/appsutil/log/trndtest/ 06121354/adconfig.log
Figure 12: Running autoconfig.sh on database tier
Updating ICX_parameters
It is important to update icx_parameters table when you change the server’s domain.
SQL> update apps.icx_parameters
2 set session_cookie_domain = '.oracle.com';
1 row updated.
SQL> commit;
Commit complete.
Figure 13: Updating ICX_parameters table
Running Autoconfig on Applications Tier

After the Oracle E-business Release 12 installation, autoconfig.sh needs to be run on the application
tier. The autoconfig.sh is located in $INST_TOP/admin/scripts directory.
[oracle@blade8 ]$ pwd
/ds2/ora/inst/apps/trndtest/admin/scripts
[oracle@blade8 scripts]$ ./adautocfg.sh
Enter the APPS user password:

16
AutoConfig is configuring the Applications environment...
AutoConfig will consider the custom templates if present.
Using CONFIG_HOME location : /ds2/ora/inst/apps/trndtest
Classpath :
/ds2/ora/apps/apps_st/comn/java/lib/appsborg2.zip:
/ds2/ora/apps/apps_st/comn/java/classes
Using Context file :

/ds2/ora/apps/apps_st/appl/admin/trndtest.xml
Context Value Management will now update the Context file
Updating Context file...COMPLETED
Attempting upload of Context file and templates to database...COMPLETED
Configuring templates from all of the product tops...
Configuring AD_TOP........COMPLETED
Configuring FND_TOP.......COMPLETED
Configuring ICX_TOP.......COMPLETED
Configuring IEO_TOP.......COMPLETED
Configuring BIS_TOP.......COMPLETED
Configuring AMS_TOP.......COMPLETED
Configuring CCT_TOP.......COMPLETED
Configuring WSH_TOP.......COMPLETED
Configuring CLN_TOP.......COMPLETED
Configuring OKE_TOP.......COMPLETED
Configuring OKL_TOP.......COMPLETED
Configuring OKS_TOP.......COMPLETED
Configuring CSF_TOP.......COMPLETED
Configuring IGS_TOP.......COMPLETED
Configuring IBY_TOP.......COMPLETED
Configuring JTF_TOP.......COMPLETED
Configuring MWA_TOP.......COMPLETED
Configuring CN_TOP........COMPLETED

17
Configuring CSI_TOP.......COMPLETED
Configuring WIP_TOP.......COMPLETED
Configuring CSE_TOP.......COMPLETED
Configuring EAM_TOP.......COMPLETED
Configuring FTE_TOP.......COMPLETED
Configuring ONT_TOP.......COMPLETED
Configuring AR_TOP........COMPLETED
Configuring AHL_TOP.......COMPLETED
Configuring OZF_TOP.......COMPLETED
Configuring IES_TOP.......COMPLETED
Configuring CSD_TOP.......COMPLETED
AutoConfig completed successfully.
The log file for this session is located at:

/ds2/ora/inst/apps/trndtest/admin/log/06121406/adconfig.log
Figure 14: Running autoconfig.sh on applications tier
Updating appsweb.cfg
After that, $FORMS_WEB_CONFIG_FILE needs to be updated by commenting out domainName.
; If you are not using the above Forms Servlet, you are using the
; Forms Server, which is running on machine serverName, on port serverPort:
serverPort=9091
serverName=blade8
domainName=.sanmateo.ibm.com
Figure 15: Conmenting out domainName in appsweb.cfg
Starting Application Processes

The next step is to run $INST_TOP/admin/scripts/adstrtal.sh which will run a list of scripts:
1. adopmnctl.sh (starting Oracle Process Manager)
2. adapcctl.sh (starting Oracle HTTP Server)
3. adoacorectl.sh (starting OACORE OC4J)
4. adformsctl.sh (starting Forms OC4J as Forms connect mode)
5. adoafmctl.sh (starting OAFM OC4J)
6. adalnctl.sh (starting listener process APPS_SID)

18
7. adcmctl.sh (starting Internal Concurrent Manager)
Please note that if there are any errors in running these scripts (the status is not zero), you need to
make sure that all the errors are fixed before continuing.
[oracle@blade8 scripts]$ ./adstrtal.sh apps/appspassword
You are running adstrtal.sh version 120.13
Executing service control script:
/ds2/ora/inst/apps/trndtest/admin/scripts/adopmnctl.sh start
script returned:
****************************************************
You are running adopmnctl.sh version 120.4
Starting Oracle Process Manager (OPMN) ...
adopmnctl.sh: exiting with status 0
adopmnctl.sh: check the logfile

/ds2/ora/inst/apps/trndtest/logs/appl/admin/log/adopmnctl.txt for more
information ...
.end std out.
.end err out.
****************************************************
/ds2/ora/inst/apps/trndtest/admin/scripts/adapcctl.sh start
script returned:
****************************************************
You are running adapcctl.sh version 120.6
Starting OPMN managed Oracle HTTP Server (OHS) instance ...
adapcctl.sh: exiting with status 0
adapcctl.sh: check the logfile

/ds2/ora/inst/apps/trndtest/logs/appl/admin/log/adapcctl.txt for more information
...
.end std out.
.end err out.
****************************************************

19
/ds2/ora/inst/apps/trndtest/admin/scripts/adoacorectl.sh start
script returned:
****************************************************
You are running adoacorectl.sh version 120.11
Starting OPMN managed OACORE OC4J instance ...
adoacorectl.sh: exiting with status 0
adoacorectl.sh: check the logfile

/ds2/ora/inst/apps/trndtest/logs/appl/admin/log/adoacorectl.txt for more
information ...
.end std out.
.end err out.
****************************************************
/ds2/ora/inst/apps/trndtest/admin/scripts/adformsctl.sh start
script returned:
****************************************************
You are running adformsctl.sh version 120.12
Not starting the Forms OC4J instance as Forms connect mode is set to socket.
adformsctl.sh: exiting with status 1
.end std out.
.end err out.
****************************************************
/ds2/ora/inst/apps/trndtest/admin/scripts/adoafmctl.sh start
script returned:
****************************************************
You are running adoafmctl.sh version 120.6
Starting OPMN managed OAFM OC4J instance ...
adoafmctl.sh: exiting with status 0

20
adoafmctl.sh: check the logfile
/ds2/ora/inst/apps/trndtest/logs/appl/admin/log/adoafmctl.txt for more
information ...
.end std out.
.end err out.
****************************************************
/ds2/ora/inst/apps/trndtest/admin/scripts/adalnctl.sh start
script returned:
****************************************************
adalnctl.sh version 120.3
Checking for FNDFS executable.
Starting listener process APPS_trndtest.
adalnctl.sh: exiting with status 0
adalnctl.sh: check the logfile

/ds2/ora/inst/apps/trndtest/logs/appl/admin/log/adalnctl.txt for more information
...
.end std out.
.end err out.
****************************************************
/ds2/ora/inst/apps/trndtest/admin/scripts/adcmctl.sh start
script returned:
****************************************************
You are running adcmctl.sh version 120.14
Starting concurrent manager for trndtest ...
Starting trndtest_0612@trndtest Internal Concurrent Manager
Default printer is noprint
adcmctl.sh: exiting with status 0
adcmctl.sh: check the logfile

/ds2/ora/inst/apps/trndtest/logs/appl/admin/log/adcmctl.txt for more information
...

21
.end std out.
.end err out.
****************************************************
adstrtal.sh: Exiting with status 1
adstrtal.sh: check the logfile

/ds2/ora/inst/apps/trndtest/logs/appl/admin/log/adstrtal.log for more information
...
Figure 16: Starting applications processes
There is an error in running adformsctl.sh because it was trying to bring up the form server in socket
mode. The default mode is Servlet mode. In this case, the following command is run to bring up the
applications in socket mode. The format of the command is:
frmsrv host=<hostname with domain name> port=<port_number> mode=socket log=<log_directory>
frmsrv host=blade8.sanmateo.ibm.com port=9091 mode=socket

log=/tmp/forms_socket.log
Figure 17: Commands to bring up forms in socket mode
This will bring up two frm background processes. Please make sure you kill any old frm processes if
there is any; and have the second process frmweb running with the current date and time.
oracle 19975 19974 0 14:28 pts/2 00:00:00 frmsrv host

i780x005.us.oracle.com port 9091 mode socket log /tmp/forms_socket.log
oracle 19976 19975 0 14:28 pts/2 00:00:00 frmweb

webfile=5,0,PID19975,/tmp/forms_socket.log
Figure 18: frm background processes
Logging into the Applications

There is a change in the user passwords setting in Oracle E-Business Suite Release 12. You can
optionally set Oracle applications user passwords as case-sensitive or case-insensitive by changing
the profile option Password Case Option in the applications.
By typing http://<server:port>/OA_HTML/AppsLogin in your web browser, you will get the Applications
login page.

22
Figure 19: Applications Login page
If you have not installed J2SE Plug-in in your desktop client, the web browser will prompt you to
download the required installation executable when you start to run a form, for example the
Administer Concurrent Managers form. Please refer to Appendix C: Oracle E-Business Suite
Release 12 for more details.
Additional Configuration and Deployment Options

The AutoConfig utility coming with Oracle E-Business Suite Release 12 offers more than application
configurations. It has other deployment options:
Hardware-based load-balancing routers
Secure Socket Layer (SSL)
Demilitarized Zones (DMZ) and reverse proxies
Multiple domain names for the same e-Business suite environment
Integration with OracleAS 10g
Real Application Clusters (RAC) and Automatic Storage Management (ASM)
Please refer to Metalink Note: 380483.1 , “Oracle E-Business Suite Release 12 Additional
Configuration and Deployment Options” for more information.
Initialization Parameters
There are a few changes in the recommended initialization parameters for Oracle E-Business Suite
Release 12 versus Oracle E-Business Suite 11i. Please refer to Metalink Note: 396009.1 Database

23
Initialization Parameters for Oracle Applications Release 12 for Release 12 database initialization
parameters.
Desktop Clients
Just like Oracle E-Business Suite 11i, Oracle E-Business Suite Release 12 also supports Microsoft
Windows 2000, Microsoft XP and Macintosh OS X v10.4 as their desktop client platforms. However, CPU
speed is a very important factor to the performance of Oracle E-Business Suite Release 12. In addition,
this product is very sensitive to the amount of memory that desktop client has. Oracle recommends at
least 350 MHz processors and 256 MB of RAM for both Microsoft Windows and Apple Mac OS X V10.4
clients.
Please refer to Metalink Note: 389422.1 , “Recommended Browsers for Oracle E-Business Suite Release
12” for the recommended browsers and requirements for using them with Oracle E-Business Suite
Release 12.
Upgrade
You could use two primary utilities: Rapid Install and AutoPatch, to upgrade from Oracle E-Business Suite
11i to Oracle E-Business Suite Release 12. The upgrade process has been changed from a two-step
approach to a one-step approach. You need to run Rapid Install to install the new Oracle E-Business
Suite Release 12 technology stack, and run AutoPatch to upgrade the Oracle E-Business Suite database
to Release 12. However, the minimum version for this upgrade is 11.5.7. As a result, if your version is
11.5.1 to 11.5.6, you will have to upgrade your applications to 11.5.7 first before upgrading to Release 12.
On the other hand, you will need to upgrade your Oracle E-Business Suite database to 10.2.0.2 prior to
the upgrade process and running AutoPatch.
Please refer to Metalink Note: 403339.1 “Oracle 10gR2 Database Preparation Guidelines for an E-
Business Suite Release 12” for more details on upgrade preparation guidelines for Oracle E-Business
Suite Release 12.
If you are using Oracle Projects, please refer to Metalink Note: 409206.1 , “Required Pre-Upgrade Tasks
for Oracle Projects, Release 12” for some pre-upgrade tasks. Before you upgrade your applications,
please verify your guest password and update it within the applications.
There is a Maintenance Wizard (which contains the Oracle E-Business 12 Upgrade Assistant) for the
customers with a valid product support contract. Please refer to Metalink Note : 215527.1, ”Maintenance
Wizard Overview” for more information on this tool.
Please refer to Oracle Applications Upgrade Guide: Release 11i to Release 12 (Part No. B31566-01) for
more details on upgrading to Oracle E-Business Suite Release 12.
Post Installation Notes

It is important to gather statistics on both applications and database objects before starting to use them.
You can use the following script to gather statistics on all application statistics:

24
SQL> exec fnd_stats.gather_schema_statistics(‘ALL’);
Figure 20: Gathering applications statistics
If you want to gather specific schema, you could replace the schema name with “ALL” in Figure 20.
For database statistics, you could use this script:
SQL> exec dbms_stats.gather_database_stats;
Figure 21: Gathering database statistics
Another post-installation step is to compile and validate all applications and database objects. You could
use AD Administration (adadmin) utility to compile and validate applications objects, and utlrp.sql located
under $ORACLE_HOME/rdbms/admin directory for database objects.
You also need to run adadmin to maintain snapshot information. From the Main Menu, choose Maintain
Applications Files, then Maintain Snapshot Information, and then Update Current View Snapshot, then
finally Update Complete APPL_TOP.
Please refer to Metalink Note: 394692.1, “Oracle Applications Documentation Resources, Release 12” for
details about snapshots.
Metalink Note:380482.1, “Oracle E-Business Suite Release 12 Technology Stack Documentation
Roadmap” contains all the important documents about the usage of various components of the
Technology Stack in Oracle E-Business Suite Release 12.
Possible Errors
You may get different kinds of errors during installation and when you tried to bring up the applications.
This section posted some possible errors that you may encounter. If you have encountered some other
errors, always check with Oracle Metalink for the latest patches and solution.
During Installation
You may get this error after you provide the database and applications nodes configuration.
Figure 22: Error message after providing database and applications node configuration

25
Figure 23: Error message after accepting OK from the previous error message box
After checking that Apps OS User exists and it does belong to the Apps OS Group, it may be a rapid
install wizard bug. You will need to make sure that you have applied the latest patch for rapidwiz. In
this case, after applying patch 5885627 and changing some parameter values according to the
Installation and Update Notes provided in Metalink, you are able to proceed to the next stage.
Post-Installation
You may get an error when you try to open an output file or log file from the Forms session. Please
note that in order to view the output files on the Forms, you need to make sure that the exact
directory path of utl_file_dir exist on both database and application tiers.
Another common error may occur after you have brought up the applications and are about to open a
Form session:

26
Figure 24: Error messages when bringing up Oracle E-Business Suite Release 12
The solution is to comment out domainName in appsweb.cfg file ($FORMS_WEB_CONFIG_FILE).
vi $FORMS_WEB_CONFIG_FILE
comment out domainname
which means from
;domainName=.us.oracle.com
to
domainName=.us.oracle.com
Figure 25: Commenting out domainName in $FORMS_WEB_CONFIG_FILE
If you get the following errors when you are bringing up the Forms, the solution is also to comment
out domainName in appsweb.cfg.
Unable to generate forwarding URL. Exception:

oracle.apps.fnd.security.DataVerificationException: Invalid CRC length. -55
Figure 26: Possible errors
In conclusion, if you encounter any difficulties in bringing up the applications, shutdown the
applications cleanly, run autoconfig on the database tier first and then run autoconfig on the
applications tiers. Please make sure that there are no errors in the autoconfig output in both tiers.
Maintenance
After you have brought up the applications successfully and are running the applications smoothly, you
still need to check Oracle Metalink Notes regularly to see if there are any new patches for Oracle E-
Business Suite Release 12. For instance, there is a new critical patch update for Oracle E-Business

27
Suite Release 12 on July 2007. Please refer to Metalink Note: 432882.1 , “Oracle E-Business Suite
Critical Patch Update Note” , July 2007 for more details.
As mentioned in Appendix B, Oracle Configuration Manager (OCM) keeps you updated regarding any
new patches for your applications should you choose to install it.
Another tool that comes with Oracle E-Business Suite Release 12 is Oracle Applications Manager (OAM).
It serves as an administrative tool to manage your applications. A sample page can be found in Appendix
D: Oracle Applications Manager.
Summary
Prior to the Oracle E-Business Suite Release 12 installation, detailed configuration of software and
hardware are very important to the successful installation of Oracle Applications. Following the steps
carefully detailed in the Oracle documentation and in Metalink Notes will definitely help to smooth the
installation procedures. Always try to install Oracle Applications on testing servers, practicing the steps
several times, before moving to production servers.
There are definitely some difference between Oracle E-Business Suite 11i and Oracle E-Business Suite
Release 12; however, they are not significant changes and in fact, the software installation is simpler with
the new Release.

28
Reference
Oracle Documentation
Oracle Metalink Note: 405293.1 Oracle Applications Release Notes Release 12
Oracle Metalink Note: 403339.1 Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite
Release 12 Upgrade
Oracle Metalink Note: 409206.1 Required Pre-Upgrade Tasks for Oracle Projects, Release 12
Oracle Metalink Note: 387859.1 Using AutoConfig to Manage System Configurations in Oracle
Applications Release 12
Oracle Metalink Note: 396009.1 for Database Initialization Parameters for Oracle Applications Release 12
Oracle Metalink Note: 416305.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for
Linux (64-bit)
Oracle Metalink Note: 406138.1 Oracle E-Business Suite 12.0 Rapid Install with Electronic Delivery
Release 12.0
Oracle Metalink Note: Oracle E-Business Suite Critical Patch Update Note July 2007
Oracle Metalink Note: 380483.1 Oracle E-Business Suite Release 12 Additional Configuration and
Deployment Options
Oracle Metalink Note : 215527.1 Maintenance Wizard Overview
Oracle Metalink Note: 389422.1 Recommended Browsers for Oracle E-Business Suite Release 12
Oracle Metalink Note: 394692.1 Oracle Applications Documentation Resources, Release 12
Oracle Metalink Note: 432882.1 Oracle E-Business Suite Critical Patch Update Note July 2007
Oracle Applications Maintenance Utilities Release 12 (Part No. B31568-01)
Oracle Applications Concepts Release 12 (Part No. B31450-03)
Oracle Applications Installation Guide: Using Rapid Install Release 12 (Part No. B31295-04)
IBM Documentation
Experiences with Oracle E-Business Suite 11i on IBM x-Series, IBM BladeCenter, IBM TotalStorage, and
Red Hat Linux Version 1.0 by Stephen Poon, Sanjay Ruprell
Oracle E-Business Suite Release 12 Installation and Tips for IBM AIX 5.3
These Web sites provide useful references to supplement the information contained in this document:

29
IBM Publications Center
www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi?CTY=US
IBM Redbooks
www.redbooks.ibm.com
About the author

Betty Lee is an I/T Specialist with the IBM Advanced Technical Support Oracle International Competency
Center based in San Mateo, CA. She provides System x and BladeCenter support for projects at the IBM
Oracle International Competency Center in San Mateo, CA and for enablement activities at Oracle
Corporation in Redwood Shores, CA.

30
Appendix A: Oracle E-Business Suite Release 12
Terminology
Services/Server A process or a group of processes provide(s) certain functionality that runs on the same machine
e.g. Web Services, Forms Services and Concurrent Processing Services
Node Logical grouping of servers
e.g. database node, applications node
Tier Logical grouping of services
e.g. database tier, application tier and desktop tier
These are the new Oracle E-Business Suite Release 12 Services Terminology.
Root Service Group Oracle Process Manager (OPMN)
Web Entry Point Services HTTP Server
Web Application Services OACORE OC4J
Forms OC4J
OAFM OC4J
Batch Processing Services Applications TNS Listener
Concurrent Managers
Fulfillment Server
Other Service Group Oracle Forms Server
Oracle MWA Service

31
Appendix B: Oracle E-Business Suite Release 12
Installation Steps
Running rapidwiz
After you start the Rapid Install wizard, the following menu will be shown. Next provide your base
directory for installation. After that, choose 1 to install Oracle Applications which is the default.
Start Here (Red) DVD
Oracle Applications Release 12.0
January, 2007
This DVD represents the starting point for the Oracle Applications
Release 12 DVD Pack.
The information on this DVD is best obtained by using an HTML browser
to view the file 'welcome.html' in the root directory. From
welcome.html you can navigate the information on this DVD and on the
Oracle support site, Oracle MetaLink.
Organization of the DVD
The following subdirectories exist on this DVD:
Disk1/doc contains Adobe Acrobat versions of Applications
installation documentation. Also contains the Upgrade
Assistant Spreadsheet in Microsoft Excel format.
Disk1/html contains static html pages linked to by welcome.html
Disk1/images contains images used by welcome.html
Disk1/rapidwiz contains the java application for the Rapid Install
Wizard.
Figure 27: Start Here menu

32
Starting AutoStaging at Tue Jun 19 14:27:05 2007
Using adautostg.pl version 120.7
This script allows you to stage Oracle Applications which contains:
- Database technology stack (RDBMS)
- Databases (Vision and Fresh)
- Applications technology stack (AS)
- Applications APPL_TOP
Enter a directory path where the media is to be staged (For example: To create
the stage area at /u01/StageR12 enter /u01 ) :/u01
The stage area will be created at /u01/StageR12
Do you use AutoMount to mount/umount the media y/n [y]?n
Enter the entire mount command [mount -t iso9660 /dev/cdrom /mnt/cdrom]:
Enter the unmount command [umount /mnt/cdrom]:
Choose the components you want to stage
1 - to choose Oracle Applications
2 - to choose Database technology stack (RDBMS)
3 - to choose Databases (Vision and Fresh)
4 - to choose Applications technology stack (AS)
5 - to choose Applications APPL_TOP
Enter number codes separated by spaces [1]:
Figure 28: Autostaging and Installation menu

33
Starting Rapid Install Wizard
After choosing 1 to install Oracle Applications the welcome screen will appear showing the principal
components it will be installing. You can expand the directory and see what is included in each
component.
Figure 29: Oracle E-Business Suite Release 12 Installation Welcome screen
After that it will ask you if you want to proceed with Express Install or Standard Install.
Express Installation is used when you want to set up a fully-configured single-user/single-machine
system. This option can be installed with fresh database or Vision Demo database. You only need to
specify some basic configuration parameters. Other values will be derived by Rapid Install using default
values.
Standard Installation is used when you want to set up a fully-configured system with single-user/single-
machine, or single-user/multi-machine, or multi-user/multi-machine system. This option can be installed
with fresh database or Vision Demo database. The configuration parameters can be entered via the
Rapid Install wizard or from the configuration file (conf_<SID>.txt) that has been saved in a previous
installation or in other node.

34
Figure 30: Express or Standard Installation
Figure 31: Oracle Configuration Manager
In the screen shown in Figure 31, you have an option to install Oracle Configuration Manager (OCM). If
you want to install it you will need to accept Oracle Connection Tools Agreement. Once accepted the
next screen will be shown.

35
Figure 32: Oracle Configuration Manager details
After accepting the agreements, you will be asked to provide a Customer Support Identifier (CSI),
Metalink Account Number, and Country. Please note that all three fields need to be filled out, otherwise it
will not let you proceed. You may also get errors if you omit the Country field. However, the proxy server
configuration is optional.
Next you will be asked to define the configuration for this installation. If you have previously saved a
configuration file during database tier installation or one of the applications tier installations, you can
retrieve it now by providing hostname, SID and database port. Please note that the host name must
include domain name.
This option is used primarily when you are doing a multi-node installation or when restarting Rapid Install
after an interruption during the installation process. This will save you time and avoid errors.
If this is a new configuration, please choose a new configuration as shown in Figure 33.

36
Figure 33: Configuration Choice
You will need to specify the global system settings as shown in Figure 34. Port Pool 0 is the default port
pool. Different port pools can contain different port values. This is particularly useful if you want to set up
multiple applications environments in the same machine.
Figure 34: Global System Settings

37
Figure 35: Database Node Configuration
You can choose to install a fresh database or Vision Demo Database in the database node configuration
screen (Figure 35). For a new implementation normally you will install a fresh database; otherwise for a
training environment you will normally install the Vision Demo database. Please note that Vision Demo
database needs at least 90 GB space more than a fresh database installation.
Please note that the Database OS User, Database OS Group and Base directory must exist on your
machine before installation. The Database OS User must belong to the Database OS Group. The base
directory is the top-level directory of the mount point of the database.
Remember to always start the database node installation first.

38
Figure 36: Primary Applications Node
In the screen shown in Figure 36 you provide the application node configuration information. The Apps
OS User can be the same as the Database OS User. In this case, applmgr user has been chosen to
separate the database and application nodes. As with the database node configuration, the Apps OS
User must belong to Apps OS Group.
Figure 37 shows the summary information for the database and application nodes.

39
Figure 37: Node Information
If you want to add an additional server for application nodes you do so by clicking on Add Server button
on this screen (Figure 37). This will give you another screen as follows (Figure 38):
Figure 38: Additional Applications Node Configuration

40
Figure 39: Pre-Install Check
Figure 39 shows the pre-install tests results for your system. If there is any mark other than the green
check please go back and make sure that they are all validated correctly. Otherwise, you will get errors
at the end of the installation. Then, click Next to continue.
Next you will be asked for the directory path of RDBMS Disk 1 (which means oraDB for your staging
directory) for step 1. Step 2 will ask for the directory path of database Disk 1 (which means oraAppDB for
the staging directory). There are three steps to go through but they only asked for the RDBMS and
database directory paths.
Figure 40: Installation steps windows

41
Figure 41: Post-Install Checks
Please make sure that only green checks are shown for the post-install checks (Figure 41). Otherwise
you will get errors at the end of the installation. Then click Next to continue.
Figure 42: Final screen
This completes the database node installation, next you continue to applications node installation. Before
doing that you need to copy all the rapidwiz files from database node to the applications node(s). In this
case all the rapidwiz files are copied from blade7 to blade8 in the base directory of /d02/stage12.

42
You then go through the same steps as the database node installation. In this case, you could use the
saved configuration file you created during database node installation to save time and avoid errors.
After providing rapidwiz the configuration file the installation will go directly to the following screen (Figure
43).
Figure 43: Pre-Install Checks for applications node
If you see any errors in these pre-install checks please fix them now otherwise you will see this error
message later (Figure 45).
Figure 44: Rapid Install error message
Once all the check marks are green click Next to continue.
The next screen (Figure 45) will list the components that are going to be installed on your systems.

43
Figure 45: Starting to install
Figure 46: Confirmation to continue installation
The process will go through the three steps in installing from rapidwiz files. It will ask for Tools Disk 1 in
the first step which is oraAS in the staging directory. Then, it will ask for APPL_TOP Disk 1 which is
oraApps in the staging directory. There are three steps but it only asks for the Tools and APPL_TOP
directory paths.

44
Figure 47: Installing Oracle Applications screen
After the installation, you will get the following screen (Figure 48).
Figure 48: Post-Install Checks
In this case the exclamation mark is considered as warning whereas a cross must be fixed before
proceeding. If you ignore the “cross” errors and click Next to continue, you will get the following warning
message (Figure 49).

45
Figure 49: Warning message
If you clicked on the “cross icon” beside the Login Page category you will be shown the details of the
errors for that category. The following screen shows the error messages on the Login category (Figure
50).
Figure 50: Login Page error messages
The following screen shows the error message for the Database Availability category (Figure 51).

46
Figure 51: Database Availability error messages
After correcting the errors for Database Availability category and clicking on the Retry button, the Warning
sign (!) becomes a checkmark as shown in Figure 52.
Figure 52: Post-Install checks with corrections

47
At this point we exit from this installation by clicking Cancel button since this is a post-install check and it
will be easier to fix the errors by accessing the Login page directly from the browser.
In this case after shutting down the applications cleanly and running autoconfig on the database tier and
the applications tiers, Oracle E-Business Suite Release 12 is brought up without any remaining problems.

48
Appendix C: Oracle E-Business Suite Release 12
Figure 53: E-business Suite Release 12 Login Page
After you login as Operations, you will get the following screen where you will set your responsibility
(Figure 54).

49
Figure 54: Setting your responsibility
If this is the first time you have accessed the applications on your machine, and after setting up the
responsibility and choosing one of the menus, the system will check to see if you have installed J2SE 5.0
on your machine. If not, it will install J2SE 5.0 for you automatically. The installation takes one or two
minutes to complete.

50
Appendix D: Oracle Applications Manager
This is the Oracle Applications Manager front page (Figure 55).
Figure 55: Oracle Applications Manager
Oracle Applications Manager (OAM) is a standalone tool and it is a powerful toolbox for Oracle
Applications Administrator. It would be used as a plug-in to integrate with Oracle Enterprise Manager 10g
Grid Control (OEM) so that you could monitor your Oracle E-Business Suite system using the OEM utility
optionally.

51
Trademarks and special notices
© Copyright. IBM Corporation 1994-2008. All rights reserved.
References in this document to IBM products or services do not imply that IBM intends to make them
available in every country.
IBM, the IBM logo, AIX, BladeCenter, DS4000, POWER, System Storage, System x, and System z are
trademarks or registered trademarks of International Business Machines Corporation in the United States,
other countries, or both:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States,
other countries, or both.
Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks
or registered trademarks of Red Hat, Inc., in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
Information is provided "AS IS" without warranty of any kind.
All customer examples described are presented as illustrations of how those customers have used IBM
products and the results they may have achieved. Actual environmental costs and performance
characteristics may vary by customer.
Information concerning non-IBM products was obtained from a supplier of these products, published
announcement material, or other publicly available sources and does not constitute an endorsement of
such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly
available information, including vendor announcements and vendor worldwide homepages. IBM has not
tested these products and cannot confirm the accuracy of performance, capability, or any other claims
related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the
supplier of those products.
All statements regarding IBM future direction and intent are subject to change or withdrawal without
notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller
for the full text of the specific Statement of Direction.
Some information addresses anticipated future capabilities. Such information is not intended as a
definitive statement of a commitment to specific levels of performance, function or delivery schedules with
respect to any future products. Such commitments are only made in IBM product announcements. The
information is presented here to communicate IBM's current investment and development activities as a
good faith effort to help with our customers' future planning.

52
Performance is based on measurements and projections using standard IBM benchmarks in a controlled
environment. The actual throughput or performance that any user will experience will vary depending
upon considerations such as the amount of multiprogramming in the user's job stream, the I/O
configuration, the storage configuration, and the workload processed. Therefore, no assurance can be
given that an individual user will achieve throughput or performance improvements equivalent to the
ratios stated here.
Photographs shown are of engineering prototypes. Changes may be incorporated in production models.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part
of the materials for this IBM product and use of those Web sites is at your own risk.

53

ORA EBS R12 Blade Center 072208

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ORA EBS R12 Blade Center 072208

Caricato da

Copyright:

Formati disponibili

Oracle E-Business Suite Release 12 on

IBM BladeCenter Hints and Tips

© Copyright IBM Corporation, 2008. All Rights Reserved.

Oracle E-Business Suite Release 12 on IBM System x Hints and Tips

Oracle E-Business Suite Release 12 on IBM System x Hints and Tips

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Please refer to Appendix A for Oracle E-Business Suite Release 12 terminology.

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

2. OracleAS 10.1.2 ORACLE_HOME comprises mainly frmweb executable and formsapp.ear.

Oracle E-Business 11i Release 12

Database Server Oracle9i Oracle10g Release 2 (10.2)

OracleAS Tools, Developer Oracle9iAS 1.0.2.2.2 OracleAS 10g (10.1.2)

OracleAS Java or Web Oracle9iAS 1.0.2.2.2 OracleAS 10g (10.1.3)

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Managed File System

IAS 10.1.3 I IAS 10.1.2 Database

RSF 10.1 RSF 10.1

COMMON TOP * COMMON TOP contains runtime location

* INSTANCE TOP contains configuration

Figure 1: Oracle E-Business Suite Release 12 Managed File System

Single-node versus multi-node Installation

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Application Tier Database Tier

Figure 2: Single-node installation

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Figure 3: Multi-node installation example

About System x and BladeCenter

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

IBM BladeCenter http://www-03.ibm.com/systems/bladecenter

IBM AMD processor-based Systems http://www-03.ibm.com/servers/eserver/opteron/index.html

IBM System x http://www-03.ibm.com/systems/x

IBM Intel processor-based Systems http://www-03.ibm.com/systems/browse/inpro/index.html

Table 2: IBM Systems and related web sites

Database Tier Applications Tier

Figure 4: Hardware configuration

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Linux operating systems

Platform/OS RHEL AS/ES 3 RHEL AS/ES Oracle Enterprise SLES-9

Linux x86 Yes Yes Yes Yes

Note: The database server needs to be in 10gR2 32-bit version.

Platform/OS RHEL AS/ES 3 Linux x86 Oracle Enterprise SLES-9

Linux x86-64 Yes Yes Yes Yes

Note: The database server needs to be in 10gR2 64-bit version.

Oracle E-Business Suite Release 12

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

[oracle@blade7 VIS_blade7]$ cd /d01/stage12

doc install oraAppDB oraApps oraDB oraiAS runInstaller stage startCD

[oracle@blade7 stage12]$ cd oraApps

component.label Disk1 Disk2 Disk3 Disk4 Disk5 Disk6 Disk7 dvd.label

Figure 5: Staging directory

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Node file system Disk space required

Database node (fresh install) 45 GB

Database node (Vision Demo database) 133 GB

Figure 6: Disk requirements

Installing the required Red Hat Enterprise Linux 4 Update 4 packages

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

Java Development Kit 5.0

Oracle E-Business Suite Release 12 on IBM BladeCenter Hints and Tips

net.ipv4.ip_local_port_range = 1024 65000

kernel.sem = 250 32000 100 142

Figure 7: Kernel settings