|
Oracle9i Application Server Certified Configuration Deployment and Cloning Guide
Release 2.0.6 for Linux x86 Part No. B10953-02 |
|
|
|
|
Oracle9i Application Server Certified Configuration Deployment and Cloning Guide
Release 2.0.6 for Linux x86 Part No. B10953-02 |
|
|
|
|
This chapter provides instructions on how to fulfill preinstallation requirements before installing Oracle9i Application Server Certified Configuration (Oracle9iAS CC).
This chapter contains the following sections:
Oracle9iAS CCs are predictable system environments. They run on industry-leading operating systems that are patched and updated to specified levels. They are standardized Oracle environments that are rapidly configured and easily deployed.
Oracle9iAS CC contains several additions on top of the base product. These additions ensure standardizations within a hosting environment.
Oracle9iAS CC includes the following deployment features:
Environment Validation Routine: During installation, configuration, cloning, or at other times in the system life cycle, the environment validation routine ensures that the system meets specified minimum requirements. If the system does not meet minimum requirements, installation, configuration, and cloning, it will not proceed.
Adherence to Oracle Outsourcing Standards: Oracle9iAS CC adheres to and enforces the standards defined for Outsourcing during deployment. This includes disk partitions, file system naming standards, operating system users and groups for Oracle software, and so on.
Rapid Deployment Using the Gold Image: Oracle9iAS CC provides an already installed and configured image called the gold image. The Oracle9iAS CC provides easy-to-use command line tools to rapidly install and reconfigure this gold image for Oracle9iAS CC Outsourcing customers. Using the gold image significantly reduces the deployment time.
Rapid Installation and Configuration Using Oracle9i Application Server Certified Configuration Utility Pack: Oracle9iAS CC provides pre-packaged response files and installation driver scripts to install Oracle9iAS CC using the Oracle Universal Installer silent installation. It also provides command line configuration tools to easily configure different components in Oracle9i Application Server.
Cloning: Oracle9iAS CC provides a cloning tool to clone Oracle9i Application Server deployments to rapidly provision identical environments when needed.
You can configure each Oracle9iAS CC as one of the following deployment types:
Oracle9iAS CC Infrastructure: The Oracle9iAS Infrastructure installation creates a combination of a metadata repository database (based on Oracle9i release 9.2.0.2), an Oracle9iAS Single Sign-On server, a Lightweight Directory Access Protocol (LDAP) version 3 (v3) directory server, and a management server that supports Oracle9iAS deployment. The database contains a collection of schemas and metadata that enable Oracle9iAS components. Oracle9iAS Infrastructure is a prerequisite for many Oracle9iAS middle-tier components.
Oracle9iAS CC Middle Tier: The Oracle9iAS installation enables you to deliver Web content, host Web applications, connect to back-office applications, and access your data on wireless devices. All Oracle9iAS applications run on the middle-tier.
An Oracle9iAS CC middle-tier installation can include the following:
J2EE and Oracle9iAS Web Cache: Includes Oracle HTTP Server, OC4J, Oracle9iAS Web Cache. Oracle9iAS Infrastructure optional (for clustering).
Oracle9iAS Portal and Oracle9iAS Wireless: Includes J2EE and Oracle9iAS Web Cache, Oracle9iAS Portal, Oracle9iAS Wireless. Oracle9iAS Infrastructure required.
Oracle9iAS Business Intelligence and Oracle9iAS Forms Services: Includes J2EE and Oracle9iAS Web Cache, Oracle9iAS Portal, Oracle9iAS Wireless, Oracle9iAS Clickstream, Oracle9iAS Personalization, Oracle9iAS Reports Services, Oracle9iAS Forms Services, and Oracle9iAS Discoverer. Oracle9iAS Infrastructure required.
Oracle9iAS CC middle-tier also installs Oracle Internet File System (Oracle9iFS) and Oracle Application Interconnect (OAI) as part of the middle-tier installation.
|
See Also: Refer to Oracle9i Application Server Installation Guide for further information about Oracle9iFS installation. It is available at the Oracle Technical Network Web site:http://otn.oracle.com/docs/content.html |
Since release 2.0.5.1, Oracle added several new features to Oracle9iAS CC. The following provides information on these features in Oracle9iAS CC release 2.0.6:
Using this release, you can install Oracle9i Application Server release 9.0.2 and 9.0.3.
The Oracle9iAS CC install complies with the Oracle Outsourcing standards. The Oracle Outsourcing Standards document is available at:
For this release, the standards cover the following general areas:
Directory structure for ORACLE_BASE, ORACLE_HOME.
Directory structure for data files and archive log partition.
ORACLE_SID, Oracle Net Service names, and Listener names.
Operating system user and groups for Oracle software
The infrastructure database is configured in archive mode.
OAI is integrated into this version of Oracle9iAS CC. OAI installs in the Oracle9i Application Server mid-tier Oracle home.
This release supports single-tier and two-tier deployments for Oracle9i Application Server release 9.0.2.
This release provides a gold image for Oracle9iAS CC release 9.0.3.
|
Note: This release does not support Oracle9iAS CC release 9.0.3 installs from the product CD-ROM. |
This release enables you to install Oracle9iAS CC release 9.0.2 from the Oracle9i Application Server product CD-ROM or from a gold image.
For a product CD-ROM installation, the Oracle9i Application Server product version is 9.0.2.0.1
For gold image installation, the Oracle9i Application Server product is patched up to the following versions:
Oracle9i Application Server 9.0.2.2 Core Patch Set
Oracle9i Application Server 9.0.2.1 Mid-tier Patch Set
Oracle9i Application Server 9.0.2.3 Portal Patch Set
Wireless Patch Set 9.0.2.8.0
Forms and Reports Patch Set 9.0.2.2
Tool to reconfigure Oracle9i Application Server Infrastructure mid-tier and Oracle9i Application Server mid-tier Oracle homes for Virtual Server.
Gold image installation supports the following deployment models (Separate images are available for each deployment model):
Oracle9iAS CC single-tier deployment model
Oracle9iAS CC two-tier deployment model
Oracle9iAS CC J2EE and Web Cache without infrastructure deployment model
This release provides a cloning tool to clone Oracle9iAS CC deployments.
To avoid confusion and improve manageability, this release does not include Oracle9i Certified Configuration release 2.
|
See Also: Refer to the Oracle9i Certified Configuration Release 2 documentation for installation, configuration, and cloning of the customer database. The documentation are available at: |
Oracle9iAS CC supports the following deployment models:
In a two-tier deployment the infrastructure databases reside on the database-tier node. The Oracle Internet Directory (OID) and Oracle9iAS Single Sign-On (SSO) servers, and all Oracle9i Application Server middle-tier components reside on the middle-tier node. This is the preferred model for Oracle Technology Outsourcing deployment because it is secure and scalable.
For Portal, Oracle Internet File System (Oracle9iFS), and other custom applications, the customer database (Oracle9i Release 2 (9.2.0.2)) resides in the database-tier and the application is deployed on the top of Oracle9i Application Server middle-tier in the middle-tier node.
Figure 1-1 depicts the two-tier deployment model.
|
Note: *The Oracle9i Certified Configuration Release 9.2.0.x database is not part of the Oracle9iAS CC Release 9.0.2 image. You should install and configure this ORACLE_HOME using Oracle9i Certified Configuration Release 9.2.0.x. |
In Figure 1-1, the database-tier contains the following Oracle homes:
O_H1: This Oracle home contains the Oracle9iAS Infrastructure database release 9.0.1.3. Only the OID instance of SSO server processes do not run in this Oracle home.
O_H4: This Oracle home contains the Oracle9i Certified Configuration (Oracle9i CC) customer database for Oracle Portal, Oracle9iFS, and other custom applications.
In Figure 1-1, the middle-tier contains the following Oracle homes:
O_H2: This Oracle home contains Oracle9iAS Infrastructure (mid-tier) running OID and SSO servers only.
O_H3: This Oracle home contains the Oracle9iAS CC mid-tier components.
This Oracle home is also used to configure Portal and Oracle9iFS against the customer database.
In a single-tier deployment, you deploy all the components of Oracle9iAS CC on a single node. This is not a preferred method of deployment. However, this deployment can be used for either small-scale intranet deployments or for test purposes.
Figure 1-2 depicts the single-tier deployment model.
|
Note: *The Oracle9i Certified Configuration Release 9.2.0.x database is not part of the Oracle9iAS CC Release 9.0.2 image. You should install and configure this ORACLE_HOME using Oracle9i Certified Configuration Release 9.2.0.x. |
In Figure 1-2, the single-tier contains the following Oracle homes:
OH_1: This Oracle home contains Infrastructure database release 9.0.1.3, and OID and SSO servers.
O_H2: This Oracle home contains the Oracle9i Application Server middle-tier.
O_H3: This Oracle home contains the Oracle9i Certified Configuration customer database for Portal, Oracle9iFS, and other custom applications.
Proceed with the rest of the document to install and configure Oracle9iAS CC.
Ensure that your system meets the requirements in the following sections.
Table 1-1, "Hardware Requirements for Oracle9iAS CC" lists hardware requirements for Oracle9iAS CC.
Table 1-1 Hardware Requirements for Oracle9iAS CC
| Hardware Component | Requirement |
|---|---|
| Minimum number of CPUs | 2 |
| Minimum CPU clock speed | 450 MHz |
| Minimum CPU power factor | 1400 |
| Minimum physical memory | 2 GB |
| Minimum number of NICs | 2 |
| Disk space | See "Partitioning Requirements". |
|
Note: If you have a CPU with a lower frequency, then you will need more CPUs to meet the total system power factor. |
Table 1-2, "Software Requirements for Linux Intel (32-bit)" lists operating system software requirements for Linux that must be met to perform a typical Oracle9iAS CC software installation, and to create a simple prototype database.
Table 1-2 Software Requirements for Linux Intel (32-bit)
Table 1-3, " Linux Kernel Configuration Settings" provides minimum required configuration requirements for the Linux kernel.
Table 1-3 Linux Kernel Configuration Settings
| Kernel Parameter | Minimum Setting | Purpose |
|---|---|---|
| SEMMNI | 100 | Defines the maximum number of semaphore sets (or identifiers) on the system. |
| SEMMNS | 256 |
Defines the maximum number of semaphores in all sets on the system. Use this setting for installation, and raise it to meet the requirements for your system.
The SEMMNS parameter should be set to the sum of the PROCESSES parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database. |
| SEMOPM | 100 |
Defines the maximum number of operations for each semop call.
|
| SEMMSL | 100 | Defines the maximum number of semaphores for each semaphore set (or identifier). Use this setting for installation, and raise it to meet the requirements for your system. |
| SHMMAX | 2147483648 |
Defines the maximum allowable size of one shared memory segment.
To compile an SMP kernel, Oracle Corporation recommends that you set the value to 2 GB or to half the size of RAM, whichever is greater. |
| SHMMNI | 100 | Defines the maximum number of associations between a shared memory segment (or identifier) and the actual shared memory on the system. |
Use the ipcs command to obtain a list of the current settings for the system shared memory and semaphore segments, and their identification numbers and owner.
You can modify kernel parameters at runtime by using the following command syntax:
echo value > parameter
where the variable parameter is the kernel parameter you want to change, and the variable value is the value that you want to assign to the parameter. Using this command syntax modifies the value for the parameter in the /proc file system (and thus the kernel), but you must then reset it at system start.
For example, to change the SHMMNI parameter to 100, enter the following command:
# echo 100 > SHMMNI
To ensure that the system settings are in effect after every restart, log in as root, and insert the following lines in the configuration file /etc/sysctl.conf:
kernel.sem = 100 256 100 100 kernel.shmmax = 2147483648 kernel.shmmni = 100
|
Note: The above kernel settings are recommended values for installation only. Modify them to meet the demands on your system. |
Use the following procedure to modify kernel parameters by changing the /proc file system settings:
Log in as the root user.
Using the following command, change directory to /proc/sys/kernel:
# cd /proc/sys/kernel
Use the cat command to review the current semaphore parameter values of the kernel:
# cat sem
The output of this command lists in order the values for the parameters SEMMSL, SEMMNS, SEMOPM, and SEMMNI. The following is an example of how the output appears:
250 3200 32 128
In this example, 250 is the SEMMSL value, 3200 is the SEMMNS value, 32 is the SEMOPM value, and 128 is the SEMMNI value.
Using the following command syntax, modify the semaphore parameter values:
echo SEMMSL SEMMNS SEMOPM SEMMNI > sem
In the line above:
SEMMSL is the value you want to set for SEMMSL.
SEMMNS is the value you want to set for SEMMNS.
SEMOPM is the value you want to set for SEMOPM.
SEMMNI is the value you want to set for SEMMNI.
For example, to change the parameter settings to the recommended minimum values for installation, enter the following command:
# echo 100 256 100 100 > sem
Using the following command syntax, use the cat command to review the current parameter settings for SHMMAX or SHMMNI:
cat parameter
where the variable parameter is the parameter you want to review. For example, to review the SHMMAX parameter setting, enter the following command:
# cat SHMMAX
If necessary, use the following command syntax to modify shared memory parameters:
echo value > parameter
where the variable parameter is the kernel parameter you want to change, and the variable value is the value that you want to assign to the parameter. Using this command syntax modifies the value for the parameter in the /proc filesystem (and thus the kernel), but you must then reset it at system boot up.
For example, to change the SHMMAX parameter to 2147483648, enter the following command:
# echo 2147483648 > SHMMAX
Oracle9iAS CC requires that you create certain partitions during operating system installation. The following sections provide information on creating partitions for the local disk and for Oracle software.
The following table lists the partitions that you must create on the local disk for a successful installation of Oracle9iAS CC.
Table 1-4 Local Disk Partition Requirements
| Mount Point | Minimum Size (GB) | Description |
|---|---|---|
/
|
9 GB | Besides root, this partition also contains the /usr, /opt, /var and /tmp directories.
|
/boot
|
128 MB | Operating system kernel |
/oem
|
1 GB | Oracle Enterprise Manager installation |
Swap
|
4 GB | The recommended swap space size is 2 times the size of RAM. |
/admin
|
4 GB (minimum or rest of the disk) | Top-level directory for certified configuration scripts, tooling, and so on. |
This section describes the file system layout for two-tier (preferred model) and single-tier deployments of Oracle9iAS CC. Although you can create these partitions on a local disk, Oracle Corporation recommends that you create these partitions on an off-host storage.
The XYYYY naming convention that is used in the following tables is described as follows:
X is a one-letter instance ID (‘t’ for test, ‘p’ for production, and ’d’ for development)
YYYY is the four-letter customer ID
For example, a test instance deployment with a customer ID of ‘orcl’ would replace XYYYY with ‘torcl’.
The following table lists the partitions on a database-tier system.
Table 1-5 Partitions for a Two-Tier Deployment: Partitions on a Database-Tier System
| Product | Mount Point | Size | Description |
|---|---|---|---|
| Oracle9i Release 2 database
(Not part of Oracle9iAS CC release. Obtain from Oracle9i Certified Configuration)
|
/XYYYYo/oracle
|
8GB | Install this using the Oracle9i Certified Configuration. |
/XYYYYo/oradata
|
8 GB | All database-related files will be distributed in the following directories as per Outsourcing standards:
|
|
/XYYYYo/arch
|
4 GB | Archive logs for the Oracle Portal and Oracle9iFS database. | |
| Oracle9iAS Infrastructure database (Infrastructure database)
|
/XYYYYs/oracle
|
4 GB | This will be the ORACLE_BASE. The Oracle home for the Oracle9iAS Infrastructure database will be $ORACLE_BASE/product/infra_902.
|
/XYYYYs/oradata
|
8 GB | All Oracle9iAS Infrastructure database related files will be distributed in the following directories as per Oracle Outsourcing standards:
|
|
/XYYYYs/arch
|
4 GB | Archive logs for Infrastructure database. |
The ORACLE_BASE partition will also contain following few important directories besides ORACLE_HOME:
$ORACLE_BASE/oraInventory - A top-level inventory
$ORACLE_BASE/jre - A top-level directory containing JRE required for OUI
$ORACLE_BASE/oui - A top-level directory containing Oracle Universal Installer
$ORACLE_BASE/admin - A top-level directory containing administrative file for ORACLE_HOME like udump, bdump, and so on.
The following table lists the partitions for a middle-tier deployment.
Table 1-6 Partitions for a Two-Tier Deployment: Partitions on a Middle-Tier System
| Product | Mount Point | Size | Description |
|---|---|---|---|
| Oracle9iAS Infrastructure (OID and SSO servers) (Infrastructure mid-tier) | /XYYYYs/idm
|
8 GB | This will be the ORACLE_BASE. The Oracle home for Oracle9iAS Infrastructure mid-tier running OID and SSO servers is $ORACLE_BASE/product/infra_902.
|
| Oracle9iAS CC middle-tier | /XYYYYo/ias
|
8 GB | This will be the ORACLE_BASE. The Oracle home for Oracle9i Application Server middle-tier components will be $ORACLE_BASE/product/iasmt_902.
|
The following table lists the partitions for a single-tier deployment.
Table 1-7 Partitions for a Single-Tier Deployment
| Product | Mount Point | Size | Description |
|---|---|---|---|
| Oracle9iAS Infrastructure database, and OID and SSO servers
|
/XYYYYs/oracle
|
8 GB | This will be the ORACLE_BASE. The Oracle home for Oracle9iAS Infrastructure database, and OID and SSO servers will be $ORACLE_BASE/product/infra_902.
|
/XYYYYs/oradata
|
8 GB | All Infrastructure database-related files will be distributed in following directories as per standards:
|
|
/XYYYYs/arch
|
4 GB | Archive logs for Infrastructure database. | |
| Oracle9i Release 2 database
(This is only required if you are deploying Oracle Portal or Oracle9iFS against the customer database.)
|
/XYYYYo/oracle
|
8 GB | Install this using the Oracle9i Certified Configuration. |
/XYYYYo/oradata
|
8 GB | All database-related files will be distributed in the following directories as per Outsourcing standards:
|
|
/XYYYYo/arch
|
4 GB | Archive logs for the Oracle Portal and Oracle9iFS database. | |
| Oracle9iAS CC middle-tier | /XYYYYo/ias
|
8 GB | This will be the ORACLE_BASE. The Oracle home for Oracle9i Application Server middle-tier components will be $ORACLE_BASE/product/iasmt_902.
|
|
Note: You only need the Oracle9iAS CC mid-tier partition for a stand alone J2EE and Web Cache Deployment. |
The Oracle9iAS CC does not require you to create specific users. The Oracle9iAS CC installations will create operating system users and groups based on the instance type (X) and customer ID (YYYY).
The following tables describes the list of users and groups that will be created during the installation of Oracle9iAS CC. All the users and groups are created with lowercase letters.
|
Note: During installation, these passwords are set to unknown strings, therefore, you must set the password for these users after installation. |
Table 1-8 Two-Tier Deployment: Users and Groups on Database-Tier
| ORACLE_HOME | OS User | OS Group |
|---|---|---|
| Oracle9iAS Infrastructure database | orXYYYYs
|
dbXYYYYs
|
Table 1-9 Two-Tier Deployment: Users and Groups on Middle-Tier System
| Product | OS User | OS Group |
|---|---|---|
| Oracle9iAS Infrastructure for OID and SSO servers | iaXYYYYo
|
iaXYYYYo
|
| Oracle9i Application Server middle-tier | iaXYYYYo
|
iaXYYYYo
|
Table 1-10 Single-Tier Deployment: Users and Group
| Product | OS User | OS Group |
|---|---|---|
| Oracle9iAS Infrastructure database, and OID and SSO servers | iaXYYYYo
|
iaXYYYYo
|
| Oracle9i Application Server middle-tier | iaXYYYYo
|
iaXYYYYo
|
The /etc/hosts file must contain the fully qualified hostname information for your computer. A fully qualified hostname includes both the name of the host system and its domain. Verify that the /etc/hosts file has the following format:
ip_address fully_qual_hostname short_hostname_aliases
where:
the variable ip_address represents the numeric value IP address for the host
the variable fully_qual_hostname represents the fully qualified host name
the variable short_hostname_aliases represents the alias by which the host can be accessed.
The following example shows a properly configured /etc/hosts file for iascc01 host:
127.0.0.1 localhost 148.87.9.44 iascc01.us.oracle.com iascc01
Complete the following additional operating system setup tasks.
The following setup tasks are required for Linux.
By default, Red Hat Advanced Server version 2.1 installs the IBM JDK and JRE. However, the IBM JDK and JRE are not compatible with Oracle software. Oracle Corporation recommends that you remove the IBM JDK and JRE from your operating system. Oracle Corporation ships the required JDK and JRE with the Oracle9iAS software.
As root, use the following commands to remove the IBM JRE and JDK from your system:
# rpm -e IBMJava2-SDK IBMJava2-JRE
To ensure that your system meets minimum specified requirements, Oracle9iAS CC checks that your system meets all the requirements listed in the preceding sections. Validated requirements include system requirements, partitioning requirements, and administrative account and group requirements. Validation takes place both before Oracle9iAS CC installation and before Oracle9iAS CC configuration.
If your system does not meet the minimum specified requirements, then the installation or configuration process will not proceed further.
As an option, you can use the following procedure to confirm that you meet the minimum specified requirements before installing or configuring Oracle9iAS CC:
Log in as the root user.
You must set variables in the following table before running the validation tool. The variables depend on the type of install. The examples of users and groups in the table are for Oracle9iAS Infrastructure ORACLE_HOME in a two tier deployment with Customer ID, orcl.
Table 1-11 OS User and Group Variables
| Variable | Direction | Example |
|---|---|---|
CC_ORACLE_USER
|
Set to the OS user for the specific type of install. | ortocls
|
CC_ORACLE_INV_GRP
|
Set to the OS group for the specific type of install. | dbtorcls
|
CC_ORACLE_DBA_GRP
|
Set to the OS group for the specific type of install. | dbtorcls
|
|
See Also: See section Operating Users and Groups for details on how to derive the operating system users and groups. |
Use FTP to obtain the Oracle9iAS CC Utility Pack tar file (ias902cc_cdzero.tar.gz) and extract it into a temporary directory.
Perform system checks to ensure that your system meets certified configuration requirements using the following command:
# <directory where cdzero is extracted>/ias/install/ocheck -product\ ias -preconfig -relaxed
If you have a system where you installed the Oracle9iAS CC Utility Pack, use the following command to verify your system setup:
# $ORACLE_CC_ROOT/install/bin/ocheck -product ias -preconfig -relaxed
The Validation Report appears. If the report Status column lists "fail" for any item, then installation or configuration cannot proceed until the cause of the failure is fixed. If the report Status column lists "warn" for any item, then the item deviates from the specified minimum requirements. However, installation or configuration may still run to completion. Oracle Corporation recommends that you meet the minimum specified requirements.
If you receive a fail or warn message during validation, then compare the Expected column with the Value column, which lists your system hardware, software, and accounts and groups status. Make the necessary changes on your system to bring it up to the minimum required specifications for Oracle9iAS CC.
|
 Copyright © 1999, 2003 Oracle Corporation All rights reserved |
|
