2 System Configuration and Verification

This chapter describes the tasks needed to configure and verify the Oracle E-Business Suite Certified Configuration. Make sure that you complete these tasks before users access the system.

This chapter includes the following topics:

Account Information
System Configuration
System Verification
Integrating Oracle Internet Directory with Oracle Applications 11i

Account Information

Before setting up the Oracle E-Business Suite Certified Configuration, provide the following information to Oracle Support Services:

Contact information
Hardware configuration
Software configuration
System serial number
Software and OS version

This information is essential for establishing an account with Oracle, and accessing Oracle Support Services. Provide the information by submitting the Service Initialization Form that you received with the Welcome e-mail message. If unable to locate the form, then contact Oracle Support at 1.800.376.9079.

System Configuration

This section provides instructions on how to use the Oracle E-Business Suite Certified Configuration cloning utility to configure the system. You can run the cloning utility from the command line or from a Web-based wizard.

The cloning utility enables you to manipulate environments on an Oracle E-Business Suite Certified Configuration. This includes cloning from environment A to environment B, restoring a fresh environment from the original zip archives, changing the identity of an existing environment, and deleting environments. It supports both VERITAS Volume Manager 3.2 and NetApps storage options.

Oracle E-Business Suite Certified Configuration Wizard

The Oracle E-Business Suite Certified Configuration wizard is a web-based tool used for cloning or updating Oracle Applications or OLAP, where cloning refers to making a copy of an environment with a different name, and updating refers to renaming an existing environment. When you update an existing environment to another environment, for example Development to Production, the wizard changes the system identifier, user names, and directory names to reflect the standards for the Production environment.

Before you use the wizard, verify that the Oracle HTTP Server is running. The Oracle HTTP Server automatically starts up when you initially run the setup_oap.sh script and subsequently each time you reboot the machine. To verify that the Oracle HTTP Server is already running, execute the following command:

$ ps -ef | grep oemadm | grep -v grep

You should see output similar to the following:

oemadm   10901 10899  0 Sep12 pts/4    00:00:00 /oem/oracle/product/oemagent/bin
oemadm   10903 10901  0 Sep12 pts/4    00:00:00 /oem/oracle/product/oemagent/bin
oemadm   10904 10903  0 Sep12 pts/4    00:00:00 /oem/oracle/product/oemagent/bin
oemadm   10915 10903  0 Sep12 pts/4    00:00:00 /oem/oracle/product/oemagent/bin
oemadm   10916 10903  0 Sep12 pts/4    00:00:00 /oem/oracle/product/oemagent/bin
oemadm   10917 10903  0 Sep12 pts/4    00:00:00 /oem/oracle/product/oemagent/bin

If the Oracle HTTP Server is not running, log in as the oemadm user and start it, using the following commands:

$ cd /oem/oracle/product/oemagent/Apache/Apache/bin
$ ./apachectl startssl

Note:

The Wizard shares the Oracle HTTP Server with the Unified Serviceability Interface.

To use the wizard, access the following URL using either Microsoft Internet Explorer version 4.0 or higher, or Netscape Navigator version 6.0 or higher:

https://hostname.domainname:7788/cwz/config.jsp

The wizard consists of three main tabs: Apps, OLAP, and Log. The Apps and OLAP tabs have two subtabs: Clone and Update.

The following sections describe how to configure the environments using the Oracle E-Business Suite Certified Configuration wizard.

CAUTION:

When configuring a multi-node environment, configure the node containing the database component before configuring the other nodes.

Cloning or Updating the Environment

To clone or update an Oracle E-Business Suite Certified Configuration environment, perform the following steps:

In the wizard, click the Apps tab.
Click Clone or Update from the subtab.
Choose the Source environment to clone or update from the menu.
Type in a unique Customer Short Code (maximum of four characters).
Choose the Environment type for the clone, or for the updated environment from the menu. The choices are Test, Stage, Development, and Production.

Select one of the following:

Local - Clone or update the environment on the local disk.

NFS - Clone or update the environment using NFS-mount. In the dialog box that appears, enter the file system to mount.

Note:

The Production environment is the only environment that uses a backup file system. When you clone or update a Production environment the wizard copies the backup file system or creates the missing backup file system, respectively.

Click the Start button. A summary of your choices appears.
If the summary is correct, click OK; otherwise click Cancel.

Cloning or Updating OLAP

To clone or update an OLAP environment, perform the following steps:

In the wizard, click the OLAP tab, and then click on the Clone or Update subtab.
Choose the Source environment to clone or update from the menu.
Type in a unique Customer Short Code (maximum of four characters).
Choose the Environment type from the menu. The choices are Test, Stage, Development, and Production.
Select one of the following:
- Local - Clone or update the environment on the local disk.
- NFS - Clone or update the environment using NFS-mount. In the dialog box that appears, enter the file system to mount.
Click Start. A summary of your choices appears.
If the summary is correct, click OK; otherwise click Cancel.

Viewing the Wizard Logs

To view the wizard log, click the Log tab. Only the latest log, /tmp/cwz.log, is viewable from the wizard. You can also view this and other logs in the $EBSO_HOME/log directory.

Command Line Configuration Wizard

The Oracle E-Business Suite Certified Configuration wizard provides a GUI front-end to the cloning utility. Alternatively, you can run this configuration wizard through the command line interface. This section describes the details of the underlying building blocks of the cloning utility.

There are basically three main phases in a cloning process. Each phase is handled by a script. The following table describes each phase and its corresponding script.

Table 2-1 Cloning Phases

Phases	Script
Phase 1: Create and mount a set of partitions for the new environment, and create the corresponding owners.	$EBSO_HOME/admin/cfgmntpt.sh
Phase 2: Copy files from environment A to environment B.	$EBSO_HOME/admin/crenv.sh
Phase 3: Update the new environment with a new identity.	$EBSO_HOME/admin/upd11i.sh $EBSO_HOME/admin/updoes.sh $EBSO_HOME/admin/updoid.sh

Normally, it is not necessary to run these scripts individually. The wrapper script, $EBSO_HOME/admin/wizard.sh, enables you to execute all three phases at once. Make sure that you run the wizard.sh script as the root user.You should only run the scripts in Table 2-1, "Cloning Phases" if there is a need for manual intervention (For example, database recovery).

For example, if you copy the file system manually to a different host, instead of using the crenv.sh script, you must run the $EBSO_HOME/dba/gencrctrl.sh script as the oracle user to refresh the control file SQL script, create_ctrl.sql, in your source environment before you start the copy. This ensures that you will not lose any newly added data files. This step is mandatory unless you are certain that no one added new data files to the environment.

The task to update Oracle Applications 11i environments is based on AutoConfig technology. In addition, it also ensures that the resultant environment is compliant with the Oracle E-Business Suite Outsourcing conventions. For more information on AutoConfig, refer to the OracleMetalink document 165195.1.

The following table contains some examples of how you can use the cloning utility. The examples use customer short code, abcd, and they assume that the environments are on locally attached hard disks. If you use network attached storage, substitute -i nfs for -i local in each example. Before you run these commands, make sure that you shutdown the environment completely.

Table 2-2 Examples of Using the wizard.sh Script

Example	Syntax
Cloning a single node Oracle Applications 11i environment.	# ./wizard.sh -c pabcdi dabcdi -i local
Updating a single node Oracle Applications 11i environment.	# ./wizard.sh -u dabcdi tabcdi
Cloning a multi-node Oracle Applications 11i environment.	First run the following command on the database tier: # ./wizard.sh -c dabcdi tabcdi -i local -o oracle Then run the following command on the applications tier: # ./wizard.sh -c dabcdi tabcdi -i local -o apps -m\ dbhost,cphost,admhost,webhost,frmhost
Updating a multi-node Oracle Applications 11i environment.	First run the following command on the database tier: # ./wizard.sh -u dabcdi pabcdi -o oracle Then run the following command on the applications tier: # ./wizard.sh -u dabcdi pabcdi -o apps -m\ dbhost,cphost,admhost,webhost,frmhost
Cloning an Oracle Database Certified Configuration environment.	# ./wizard.sh -c pabcdd dabcdd -i local
Updating an Oracle Database Certified Configuration environment.	# ./wizard.sh -u dabcdd tabcdd
Cloning an Oracle Internet Directory environment.	# ./wizard.sh -c pabcds dabcds -i local
Updating an Oracle Internet Directory environment.	# ./wizard.sh -u dabcds tabcds
Cloning an OLAP environment.	# ./wizard.sh -c pabcdx dabcdx -i local
Updating an OLAP environment.	# ./wizard.sh -u dabcdx tabcdx

To delete environments, make sure that you shut down the environment. Then run the cfgmntpt.sh script for each environment, using the following command:

# ./cfgmntpt.sh -d <mount_point> -i local

System Verification

After updating the environment information, verify that the environment and system are functioning correctly using Oracle Applications Release 11i (11.5.8). The first time that you access the application, it will prompt you to download JInitiator. After you install the software, restart the browser, and proceed with the login procedure. The following tasks describe how to log in, and verify the system:

Start the Web browser.
Enter the URL for the environment. The Oracle Applications Rapid Install portal window will appear.

The URL depends on the environment, refer to "URLs for Oracle Applications 11i" in for more information.
Click the Apps Logon Links option. The Logon Information for the instance window will appear.
Click Personal Home Page. The Oracle Applications Logon window will appear.
Enter sysadmin for the user name and password.
Click Connect. The Self-Service System Administrator window will appear.
Click System Administrator.
Select Manager from the Concurrent menu.
Select Administer from the Manager list.
Verify that the values in the Actual column match the values in the Target column. If the values match, then the Concurrent Manager processes are running correctly.
Select Run from the Requests menu.
Select Single Request from the Run list.
Enter Active Users in the name field of the request form. This field is case-sensitive.
Click Submit. The Requests form will appear.
Click Refresh Data to update the Phase column for the request.
Click View Log... when the Phase column lists the request as complete.
Verify the log file appears in the Report Review Agent.
Click the question mark icon in the top navigation bar. If the environment and system are functioning correctly, then the Applications Help window will appear.
Select Exit from the File menu to exit Oracle Applications Release 11i (11.5.8).

Integrating Oracle Internet Directory with Oracle Applications 11i

After you successfully install the OID component, perform the following steps to configure the Login Server in your Oracle Applications 11i environment to use Oracle Internet Directory (OID) for user authentication. The example below configures the OID environment, TABCDS, against Oracle Applications 11i environment, TABCDI.

Go to the Oracle Applications 11i environment.
As the oracle user, ortabcdi, install the LDAP packages using the following commands:
```
$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus ‘/ as sysdba’ @catldap.sql
```

As the apps user, aptabcdi, enable OID authentication using the following commands:

$ cd $IAS_TOP/portal30/admin/plsql/sso
$ sqlplus portal30_sso/portal30_sso @ssooid.sql

Enter the following information when prompted:
- Host: oid_host.domain
- Port: oid_server_port
- Search Base: cn=Login Server (portal30_sso)
- Unique Attribute: cn
- Bind DN: cn=orcladmin
- Bind Password: welcome
As the apps user, aptabcdi, use the following commands to generate an Oracle Applications 11i user list, users.ldif, to be loaded into the LDAP directory:
```
$ cd $IAS_TOP/portal30/admin/plsql/sso
$ sqlplus portal30_sso/portal30_sso @ssoldif.sql
```
Enter a file location that is in the utl_file_dir directory path (For example, /usr/tmp).
Go to the OID environment.
As the oracle user, ortabcds, startup the OID server if it is not already running.
Load the Oracle Applications 11i users list, that you created in step 5, using the following commands:
```
$ ldapadd -h <oid_host> -p <oid_server_port> -D cn=orcladmin -w welcome -f\
 users.ldif
```
Go to the Oracle Applications 11i environment.
As the apps user, aptabcdi, follow the directions in step 1 of the Implementing Single Sign-On for Oracle Applications 11i with Login Server Authentication Using Oracle Internet Directory note (OracleMetaLink Note:150832.1) to apply OID synchronization patches 2503242, 2499306, and 2635379.
As the apps user, aptabcdi, perform the remaining configuration steps 2 through 6, as required, in Note:150832.1 to synchronize the OID user data and FND_USER on an ongoing basis.