2 Installing and Configuring Oracle9iAS CC Using the Gold Image

This chapter describes how to install and configure an Oracle9i Application Server Certified Configuration (Oracle9iAS CC) from the Gold Image.

Oracle9i Application Server components are pre-installed and pre-configured in the Gold Image. When you install and configure Oracle9iAS CC using the Gold Image, the installation and configuration time is significantly less than the installation and configuration time when using the product CD-ROMs. The installation from the Gold Image saves you time when deploying Oracle9i Application Server.

This chapter contains the following sections:

Prerequisites for Installation and Configuration
Two-Tier Deployment
Single-Tier Deployment
J2EE and Web Cache Deployment without Infrastructure
Postconfiguration
Starting the Infrastructure Database in Archive Log Mode
Handling Configuration Failures

Prerequisites for Installation and Configuration

Ensure that you meet the following prerequisites before you install and configure Oracle9iAS CC.

When you perform the first Gold Image installation, your system must be clean with no previous Oracle homes configured or Oracle processes running.

Access to the Gold Image

Before installing using the Gold Image, you must make the Gold Image stage area accessible on your system. You can mount the Gold Image stage area from a remote machine using NFS, or copy it onto the local machine and extract it in the location described below.

By default, Oracle9iAS CC references the /stage/ias902 directory as the location for the Gold Image stage area. If you want to put the Gold Image in another directory, you must set the CC_STAGE_AREA environment variable to that location, as follows:

# CC_STAGE_AREA=/mystage/gold
# export CC_STAGE_AREA

Single-Tier

Use the following steps to create a single-tier Gold Image from the product CD-ROMs:

Copy the following files from the respective CD-ROMs to $CC_STAGE_AREA or /stage/ias902 (make sure you have enough space):
- CD1: ias902cc_singletier_solaris_image_xaa
- CD2: ias902cc_singletier_solaris_image_xab
- CD3: ias902cc_singletier_solaris_image_xac
- CD4: ias902cc_singletier_solaris_image_xad
- CD5: ias902cc_singletier_solaris_image_xae
- CD6: ias902cc_singletier_solaris_image_xaf
Run one of the following commands:
- $ cd $CC_STAGE_AREA
- $ cd /stage/ias902

Run the following commands to create the Single Tier Gold Image:

$ cat ias902cc_singletier_solaris_image_xa* \ > ias902cc_singletier_solaris_images.tar
$ rm ias902cc_singletier_solaris_image_xa*
$ tar xvf ias902cc_singletier_solaris_images.tar

Two Tier

Use the following steps to create a two-tier Gold Image from the product CD-ROMs:

Copy the following files from the respective CD-ROMs to $CC_STAGE_AREA or /stage/ias902 (make sure you have enough space):
- CD1: ias902cc_twotier_dbt_solaris_image_xaa
- CD2: ias902cc_twotier_dbt_solaris_image_xab
- CD3: ias902cc_twotier_dbt_solaris_image_xac
- CD4: ias902cc_twotier_mt_solaris_image_xaa
- CD5: ias902cc_twotier_mt_solaris_image_xab
- CD6: ias902cc_twotier_mt_solaris_image_xac
- CD7: ias902cc_twotier_mt_solaris_image_xad
- CD8: ias902cc_twotier_mt_solaris_image_xae
Run one of the following commands:
- $ cd $CC_STAGE_AREA
- $ cd /stage/ias902

Run the following commands to create the Two-Tier Gold Image:

$ cat ias902cc_twotier_dbt_solaris_images_xa* \ > ias902cc_twotier_dbt_image.tar
$ cat ias902cc_twotier_mt_solaris_images_xa* \ > ias902cc_twotier_mt_image.tar

$ rm ias902cc_twotier_dbt_solaris_images_xa*
$ rm ias902cc_twotier_mt_solaris_images_xa*

$ tar -xvf ias902cc_twotier_dbt_image.tar
$ tar -xvf ias902cc_twotier_mt_image.tar

J2EE 902

Use the following steps to create a J2EE 902 Gold Image from the product CD-ROMs:

Copy the following files from the respective CD-ROMs to $CC_STAGE_AREA or /stage/ias902 (make sure you have enough space):
```
CD1 : ias902cc_j2eewc_noinfra_solaris_image_xaa
CD2 : ias902cc_j2eewc_noinfra_solaris_image_xab
```
Run one of the following commands:
- $ cd $CC_STAGE_AREA
- $ cd /stage/ias902

Run the following commands to create the J2EE 902 Gold Image:

$ cat ias902cc_j2eewc_noinfra_solaris_image_xa* \ > ias902cc_j2eewc_noinfra_solaris_images.tar
$ rm ias902cc_j2eewc_noinfra_solaris_image_xa*
$ tar xvf ias902cc_j2eewc_noinfra_solaris_images.tar

Required Information for Installation and Configuration

You will need the following information before installing and configuring Oracle9iAS CC:

4-letter customer ID
Install type (singletier, midtier, or dbtier)
Instance type (’t’ for test, ’d’ for development, or ’p’ for production)

Note:

The system will prompt you to log in as the root user to start installation, configuration, or cloning. However, internally, the system performs all the operations as a normal operating system user (not the root user) who owns or will own the Oracle software (except when it is mandatory to perform operations as the root user).

After you complete the installation and configuration of Oracle9iAS CC, you must perform maintenance and management operations using a normal operating system user who owns a particular Oracle home (unless the base product requires a different user).

Two-Tier Deployment

A two-tier deployment involves the deployment of the components in the following table.

Table 2-1 Deployment

Tier	Component
Database-Tier	Infrastructure database
Middle-Tier	Infrastructure mid-tier - Oracle Internet Directory (OiD) and Single Sign-On (SSO) server Complete Oracle9i Application Server mid-tier (Up to Oracle9iAS Business Intelligence and Oracle9iAS Forms Services), Oracle Internet File System (CM_SDK), and Oracle Application Interconnect (OAI).

Caution:

You must first configure the Infrastructure database on the database-tier, then the Infrastructure mid-tier on the middle-tier before configuring other components.

Installing Database-Tier Components

Install database-tier components using the following:

Log in as the root user on the database tier.
Change the directory to the Gold Image stage area using the following command:
```
# cd /<<stage area>/Disk0
```

Run the install.sh script with the following options:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=dbtier

This installs the Infrastructure database.

Example 2-1 Deriving $ORACLE_BASE and User ID of the Installation Owner on the Database-Tier

For example, if the customer ID is ’orcl’ and the instance type is ’p’ for production, then the Infrastructure database will be installed in the /porcls/oracle directory and owned by user orporcls.

Installing Middle-Tier Components

Install the middle-tier components using the following:

Log in as the root user on the middle-tier.
Change directories to the Gold Image stage area using the following command:
```
# cd /<stage area>/Disk0
```

Run the install.sh script with the following options:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=midtier

This installs the Infrastructure mid-tier and Oracle9i Application Server middle-tier in their respective Oracle homes.

Example 2-2 Deriving $ORACLE_BASE and User ID of the Installation Owner on the Middle-Tier

For example, if the customer ID is ‘orcl’ and the instance type is ‘p’, then:

Infrastructure mid-tier (oidsso) will be installed in the /porcls/idm directory and owned by user iaporclo
Oracle9i Application Server mid-tier will be installed in the /porclo/ias directory and owned by user iaporclo

Configuring Infrastructure Database on the Database-Tier

This section details configuring the Infrastructure database Oracle home on the database-tier in the /XYYYYs/oracle/product/infra_902 directory. Configure Infrastructure database on the database-tier using the following instructions:

Log in as the root user on the database-tier.
Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:
```
# . /etc/ora_cc_env
# cd $ORACLE_CC_ROOT/ias/902
```
Set the DISPLAY variable to a valid X server.
Run the config.sh script using one of the following:
- Input file
- Interactive mode

Configuring Infrastructure Database Using Interactive Mode

Use the following command to configure the Infrastructure database in interactive mode:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage

The configuration tool will start configuration by requesting information about the instance that you want to configure.

Configuring Infrastructure Database Using An Input File

Use the following procedure to configure the Infrastructure database with input parameters (except passwords) specified in the parameter file:

Copy the $ORACLE_CC_ROOT/clone/config/clone_src.properties file to another file, such as config_inputfile.
Edit the config_inputfile file and specify the parameters needed for the specific configuration that you need to carry out.

Note:
The system will not accept the passwords in the input file for security reasons. It will prompt you for passwords during interactive mode when you run the config.sh script.

Run the config.sh script as follows:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage -propfile  <propfile name>

If any parameter is missing or incorrect, the config.sh will print out an error message and will not continue with the configuration. You can correct the error in the input file and re-run the configuration.

This will configure the Infrastructure database and bring it up at the end of configuration.

Verifying Configuration

Check the configuration log file located in the $ORACLE_CC_ROOT/logs/config directory for any errors.

To verify that the Infrastructure database is correctly installed and configured, log in to the system as the user who owns the Infrastructure database Oracle home. Source the profile and choose this Oracle home. Log in to the Infrastructure database as the SYS user. The login should be successful.

Configuring Infrastructure Mid-Tier on the Middle-Tier

Note:

You must configure the Infrastructure database on the database-tier before you configure the Infrastructure mid-tier on the middle-tier.

This section details configuring the Infrastructure mid-tier Oracle home on the middle-tier in the /XYYYYs/idm/product/infra_902 directory. Configure Infrastructure mid-tier on the middle-tier using the following:

Log in as the root user on the middle-tier.
Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:
```
# . /etc/ora_cc_env
# cd $ORACLE_CC_ROOT/ias/902
```
Set the DISPLAY variable to the valid X server.
Run the config.sh script using one of the following:
- Input file
- Interactive mode

Configuring Infrastructure Mid-Tier Using Interactive Mode

Use the following command to configure Infrastructure mid-tier in interactive mode:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage

The configuration tool will start configuration by requesting information about the instance that you want to configure.

Configuring Infrastructure Mid-Tier Using An Input File

Use the following procedure to configure the Infrastructure middle-tier with input parameters (except passwords) specified in the parameter file:

Copy the $ORACLE_CC_ROOT/clone/config/clone_src.properties file to another file, such as config_inputfile.
Edit the config_inputfile file and specify the parameters needed for the specific configuration that you need to carry out. The config_inputfile file contains descriptions and default values for each parameter.

Note:
The system will not accept the passwords in the input file for security reasons. It will prompt you for passwords during interactive mode when you run the config.sh script.

Run the config.sh script with the appropriate options to configure Oracle9iAS CC.

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage -propfile  <propfile name>

If any parameter is missing or incorrect, the config.sh will print out an error message and will not continue with the configuration. You can correct the error in the input file and re-run the configuration.

This will configure the Infrastructure mid-tier and bring it up at the end of configuration.

Verifying Configuration

Check the configuration log file located in the $ORACLE_CC_ROOT/logs/config directory for any errors.

To verify that the Infrastructure mid-tier is correctly installed and configured, go to the URL, http://<hostname>.<domainname>:7777/oiddas. Log in as the orcladmin user with the password that you specified during configuration. The login should be successful.

Configuring Oracle9i Application Server Mid-Tier Components on the Middle-Tier

Note:

before you configure Oracle9i Application Server mid-tier components on the middle-tier, you must configure the following:

Infrastructure database on the database-tier
Infrastructure mid-tier on the middle-tier

This section details configuring the Oracle homes for the Oracle9i Application Server mid-tier components in the /XYYYYo/ias/product/iasmt_902 directory.

Configure Oracle9i Application Server mid-tier components on the middle-tier by using the following steps:

Log in as the root user on the middle-tier.
Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:
```
# . /etc/ora_cc_env
# cd $ORACLE_CC_ROOT/ias/902
```
Set the DISPLAY variable to the valid X server.
Run the config.sh script using one of the following:
- Input file
- Interactive mode

Configuring Oracle9i Application Server Mid-Tier Components Using Interactive Mode

To configure the Oracle9i Application Server mid-tier components, use the following commands depending on the components you need to configure:

For all Oracle9i Application Server mid-tier components (J2EE, Web Cache, Wireless, and Portal), run the following command:
```
# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage
```
The configuration tool will start configuration by listing all unconfigured Oracle homes.
Select an Oracle home from the list.
Select one of the following configuration options:
- Business Intelligence and Forms
- J2EE and Web Cache with Infrastructure
- Portal and Wireless

Configuring Oracle9i Application Server Mid-Tier Components Using An Input File

To configure the Oracle9i Application Server mid-tier components, use the following procedure to configure Oracle9iAS CC with input parameters (except passwords) specified in the parameter file:

Copy the $ORACLE_CC_ROOT/clone/config/clone_src.properties file to another file, such as config_inputfile.
Edit the config_inputfile file and specify the parameters needed for the specific configuration you need to carry out.

Note:
The system will not accept the passwords in the input file for security reasons. It will prompt you for passwords during interactive mode when you run the config.sh script.
Run the config.sh script with the appropriate options to configure Oracle9iAS CC. For example, to configure E-mail, use the following command:
```
# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage -propfile  <propfile name>
```
If any parameter is missing or incorrect, the config.sh will print out an error message and will not continue with the configuration. You can correct the error in the input file and re-run the configuration.

This will configure Oracle9i Application Server mid-tier components and bring up the mid-tier at the end of configuration.

Verifying Configuration

Check the configuration log file located in the $ORACLE_CC_ROOT/logs/config directory for any errors.

To verify that the Oracle9i Application Server middle-tier Portal component is correctly installed and configured, go to the URL, http://<hostname>.<domainname>:7778/pls/portal. Click on the Login link and log in as portal with the password specified during configuration. The login should be successful.

Note:

You must perform the steps in "Postconfiguration" to complete the deployment.

Single-Tier Deployment

A single-tier deployment involves installing and configuring all the components on a single node. A single-tier deployment configures the following components:

Complete Infrastructure (includes the Infrastructure database), Oracle Internet Directory Server (OiD), and Oracle9iAS Single Sign-On (SSO) Server.
Complete Oracle9i Application Server mid-tier components (Up to Business Intelligence and Forms install types), Oracle Internet File System (Oracle9iFS), and Oracle Application InterConnect (OAI).

Installing Components on the Single-Tier

Install components on the single-tier using the following:

Log in as the root user on the single-tier.
Change directories to the Gold Image stage area, using the following command:
```
# cd /<stage area>/Disk0
```

Run the install.sh script with the following options:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=singletier

This installs Infrastructure and Oracle9i Application Server components in their respective Oracle homes.

Example 2-3 Deriving $ORACLE_BASE and User ID of the Installation Owner on the Single-Tier

For example, if the customer ID is ‘orcl’ and the instance type is ‘d’, then:

Infrastructure will be installed in the /dorcls/oracle directory and owned by user, iadorclo.
Oracle9i Application Server mid-tier components will be installed in the /dorclo/ias directory and owned by user, iadorclo.

Configuring Infrastructure on the Single-Tier

Configure Infrastructure on the single-tier using the following:

Log in as the root user on the single-tier.
Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:
```
# . /etc/ora_cc_env
# cd $ORACLE_CC_ROOT/ias/902
```
Set the DISPLAY variable to the valid X server.
Run the config.sh script using one of the following:
- Input file
- Interactive mode

Configuring Infrastructure on the Single-Tier Using Interactive Mode

Use the following command to configure the Infrastructure in interactive mode:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage

The configuration tool will start configuration by requesting information about the instance that you want to configure.

Configuring Infrastructure on the Single-Tier Using An Input File

Use the following procedure to configure Infrastructure with input parameters (except passwords) specified in the parameter file:

Copy the $ORACLE_CC_ROOT/clone/config/clone_src.properties file to another file, such as config_inputfile.
Edit the config_inputfile file and specify the parameters needed for the specific configuration you need to carry out.

Note:
The system will not accept the passwords in the input file for security reasons. It will prompt you for passwords during interactive mode when you run the config.sh script.

Run the config.sh script with the appropriate options to configure Oracle9iAS CC.

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage -propfile  <propfile name>

If any parameter is missing or incorrect, the config.sh will print out an error message and will not continue with the configuration. You can correct the error in the input file and re-run the configuration.

This will configure Infrastructure and bring it up at the end of configuration.

Verifying Configuration

Check the configuration log file located in the $ORACLE_CC_ROOT/logs/config directory for any errors.

To verify that the Infrastructure is correctly installed and configured, go to the URL, http://<hostname>.<domainname>:7777/oiddas. Log in as the orcladmin user with the password that you specified during configuration. The login should be successful.

Configuring Oracle9i Application Server Mid-Tier Components on the Single-Tier

Configure Oracle9i Application Server mid-tier components on the single-tier using the following procedure:

Log in as the root user on the single-tier.
Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:
```
# . /etc/ora_cc_env
# cd $ORACLE_CC_ROOT/ias/902
```
Set the DISPLAY variable to the valid X server.
Run the config.sh script using one of the following:
- Input file
- Interactive mode

Configuring Oracle9i Application Server Mid-Tier Components on the Single-Tier in Interactive Mode

To configure the Oracle9i Application Server mid-tier components, use the following commands depending on the components you need to configure:

For all Oracle9i Application Server mid-tier components (J2EE, Web Cache, Wireless, and Portal), run the following command:
```
# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage
```
The configuration tool will start configuration by listing all unconfigured Oracle homes.
Select an Oracle home from the list.
Select one of the following configuration options:
- Business Intelligence and Forms
- J2EE and Web Cache with Infrastructure
- Portal and Wireless

Configuring Oracle9i Application Server Mid-Tier Components on the Single-Tier Using An Input File

Use the following procedure to configure Oracle9i Application Server mid-tier components with input parameters (except passwords) specified in parameter file:

Copy the $ORACLE_CC_ROOT/clone/config/clone_src.properties file to another file, such as config_inputfile.
Edit the config_inputfile file and specify the parameters needed for the specific configuration you need to carry out.

Note:
The system will not accept the passwords in the input file for security reasons. It will prompt you for passwords during interactive mode when you run the config.sh script.
Run the config.sh script with the appropriate options to configure Oracle9iAS CC. For example, to configure all the mid-tier components, use the following command:
```
# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage -propfile  <propfile name>
```
If any parameter is missing or incorrect, the config.sh will print out an error message and will not continue with the configuration. You can correct the error in the input file and re-run the configuration.

This will configure Oracle9i Application Server mid-tier components and bring up the mid-tier at the end of configuration.

Verifying Configuration

Check the configuration log file located in the $ORACLE_CC_ROOT/logs/config directory for any errors.

Note:

You must perform the steps in "Postconfiguration" to complete the deployment.

J2EE and Web Cache Deployment without Infrastructure

This type of deployment involves installing and configuring only J2EE and Web Cache in a single Oracle home.

Installing Components for J2EE and Web Cache Deployment

Install components on the single-tier using the following:

Log in as the root user on the single-tier.
Change directories to the Gold Image stage area using the following command:
```
# cd /<stage area>/Disk0
```

Run the install.sh script with the following options:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=j2eewc_no_infra

This installs Oracle9i Application Server mid-tier components.

Configuring J2EE and Web Cache

Configure Infrastructure on the single-tier using the following procedure:

Log in as the root user.
Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:
```
# . /etc/ora_cc_env
# cd $ORACLE_CC_ROOT/ias/902
```
Set the DISPLAY variable to the valid X server.
Run the config.sh script using one of the following:
- Input file
- Interactive mode

Configuring J2EE and Web Cache in Interactive Mode

Use the following command to configure Infrastructure in interactive mode:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage

Configuring J2EE and Web Cache Using An Input File

Use the following procedure to configure Infrastructure with input parameters (except passwords) specified in parameter file:

Copy the $ORACLE_CC_ROOT/clone/config/clone_src.properties file to another file, such as config_inputfile.
Edit the config_inputfile file and specify the parameters needed for the specific configuration you need to carry out.
Note that the passwords in the input file will not be honored because of security reasons. You will be prompted for passwords during interactive mode when you run the config.sh script.

Run the config.sh script with the appropriate options to configure Oracle9iAS CC.

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage -propfile  <propfile name>

If any parameter is missing or incorrect, the config.sh will print out an error message and will not continue with the configuration. You can correct the error in the input file and re-run the configuration.

This will configure the Infrastructure and bring it up at the end of configuration.

Verifying Configuration

Check the configuration log file located in the $ORACLE_CC_ROOT/logs/config directory for any errors.

Configuring Oracle9i Application Server Mid-Tier Components on the Single-Tier

Configure Oracle9i Application Server mid-tier components on the single-tier using the following:

Log in as the root user on the single-tier.
Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:
```
# . /etc/ora_cc_env
# cd $ORACLE_CC_ROOT/ias/902
```
Set the DISPLAY variable to the valid X server.
Run the config.sh script using one of the following:
- Input file
- Interactive mode

Configuring Oracle9i Application Server Mid-Tier Components on the Single-Tier in Interactive Mode

For all mid-tier components, run the following command:

# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage

The configuration tool will start configuration by requesting information about the instance that you want to configure.

Configuring Oracle9i Application Server Mid-Tier Components on the Single-Tier Using An Input File

Use the following procedure to configure Oracle9i Application Server mid-tier components with input parameters (except passwords) specified in the parameter file:

Copy the $ORACLE_CC_ROOT/clone/config/clone_src.properties file to another file, such as config_inputfile.
Edit the config_inputfile file and specify the parameters needed for the specific configuration you need to carry out.

Note:
The system will not accept the passwords in the input file for security reasons. It will prompt you for passwords during interactive mode when you run the config.sh script.
Run the config.sh script with the appropriate options to configure Oracle9iAS CC. For example, to configure all the mid-tier components, use the following command:
```
# PATH=$PATH:/usr/ccs/bin; export PATH
# ./config.sh -goldimage -propfile  <propfile name>
```
If any parameter is missing or incorrect, the config.sh will print out an error message and will not continue with the configuration. You can correct the error in the input file and re-run the configuration.

This will configure Oracle9i Application Server mid-tier components and bring up the mid-tier at the end of configuration.

Verifying Configuration

Check the configuration log file located in the $ORACLE_CC_ROOT/logs/config directory for any errors.

Note:

You must perform the steps in "Postconfiguration" to complete the deployment.

Postconfiguration

You must complete the following postconfiguration tasks.

Removing Old Partner Applications

If you used the Gold Image to deploy your Oracle9iAS CC, then use the following to remove old partner applications on the system. This fix is not required for the deployments installed and configured from the Product CD-ROMs.

Log into the Oracle9iAS Single Sign-On (SSO) Server at:
```
http://<hostname:<port/pls/orasso
```
Click SSO Server Administration.
Click Administer Partner Applications.
In the Edit/Delete Partner Application section, delete the following old partner applications:
```
Oracle Portal (portal)
ogolds_infraoidsso.<hostname.<domainname
ogoldo_iasmt.<hostname.<domainname
wireless_deviceportal
```
If there are two application entries with the same name (for example, wireless_deviceportal), then use the following procedure to identify the old application:
1. Click on the Edit icon against the partner application.
2. Note the ID of the application in the Edit Partner Application page.
  
  The application ID with the lesser value is the old partner application

Refreshing ONS Configuration

You must perform these steps in the following sequence.

For Two-Tier Deployment

Use the following procedure to refresh the ONS configuration for a two-tier deployment:

In the Infrastructure database Oracle home on the database-tier, update the ias.properties file in the $ORACLE_HOME/config directory with the proper hostname values for the following entries:
- OIDhost
- SSOhost
Run the following command in the Infrastructure mid-tier Oracle home on the middle-tier system:
```
$ $ORACLE_HOME/dcm/bin/dcmctl listinstances
```
This command updates the $ORACLE_HOME/opmn/conf/ons.conf file with the IP addresses of the database-tier and middle-tier systems.

Verify that the ons.conf file contains the IP addresses of the database-tier and middle-tier systems only.
Run the following command in the Infrastructure database Oracle home on the database-tier system. This command updates the $ORACLE_HOME/opmn/conf/ons.conf file with the IP addresses of the database-tier and middle-tier systems.
```
$ $ORACLE_HOME/dcm/bin/dcmctl listinstances
```
Verify that the ons.conf file contains the IP addresses of the database-tier and middle-tier systems only.

You must now stop and start services in all Oracle homes. See " Administering Oracle9i Application Server CC" in Appendix B for details.

For Single-Tier Deployment

Use the following to refresh the ONS configuration for a single-tier deployment:

Run the following command in the Infrastructure Oracle home. This command updates the $ORACLE_HOME/opmn/conf/ons.conf file with the IP addresses of the current system.
```
$ $ORACLE_HOME/dcm/bin/dcmctl listinstances
```
Verify that the ons.conf file contains the IP addresses of the current system.

You must now stop and start services in all Oracle homes. See " Administering Oracle9i Application Server CC" in Appendix B for details.

Starting the Infrastructure Database in Archive Log Mode

Perform the following procedure to start the Infrastructure database in archive log mode:

Stop all the instances.
Log in as the user who owns the Oracle home that has the Infrastructure database.
Use the following command to set the environment:
```
$ . $ORACLE_HOME/profile.iascc_env
```
Select the $ORACLE_HOME that has the Infrastructure database.

Run the following commands:

$ . sqlplus ’/as sysdba’
SQL> startup mount;
SQL> alter database archivelog;
SQL> alter database opent;
SQL> shutdown immediate;
SQL> exit

Start all the instances.

Handling Configuration Failures

Refer to Appendix C, " Troubleshooting" for handling failures during configuration. If the failure requires you to reinstall the software, follow instructions in Appendix D, " Oracle9i Application Server Certified Configuration Deinstallation" to remove your existing installation.