Oracle Fail Safe Manager provides a wizard to help you configure instances of the following Oracle Application Server components for high availability:
Oracle Process Manager and Notification Server (OPMN)
Oracle Enterprise Manager 10g Application Server Control (Application Server Control) service
The metadata repository, if it was installed in the same Oracle home as the other Oracle Application Server components
The following topics are discussed in this chapter:
If a metadata repository is in the same home where you installed Oracle Application Server, then before adding instances of Oracle Application Server components to a group, you must do the following:
Add at least one virtual address to the group.
Ensure that the database files are on cluster disks. If a failover occurs, then any cluster node that is a possible owner of the instance must be able to access the database files.
You need the following information to complete the wizard. Examples are provided in parentheses.
Oracle home where Oracle Application Server is installed (OAS)
If the metadata repository was installed in the Oracle home where Oracle Application Server is installed, then you also need the following information:
Database instance name (OFS5)
Database name (OFS5DB)
Database parameter file (T:\OFSDB\PARA\initofs5.ora)
Database SYS account password if the database has a password file
To configure Oracle Application Server components for high availability, perform the following steps:
Install Oracle Application Server as described in Oracle Application Server Installation Guide (10g Release 2 (10.1.2) for Microsoft Windows).
Open Oracle Fail Safe Manager.
On the tree view, select the standalone Oracle Application Server instance that you want to add to a group.
From the Resources menu, select Add to Group. The Add Resource to Group Wizard opens.
In the Resource Type box, select Oracle Application Server.
In the Group Name box, select the group to which you want to add Oracle Application Server.
Click Next.
Complete the remaining wizard pages. If you need assistance, then click Help on the wizard page.
Note the following:
Unlike a standalone database instance, a standalone Oracle Application Server instance is represented in the tree view on each cluster node. You can select the standalone instance that you want to add to a group from any one of the cluster nodes.
A standalone Oracle Application Server instance is represented in the tree view as the home into which Oracle Application Server was installed. After it is configured into the group, it is represented by the resources that compose it: OPMN and Application Server Control. Oracle Fail Safe brings these resources online after it has configured them on each cluster node.
To make an Oracle Application Server metadata repository that is not installed in the same home as Oracle Application Server highly available, you add it to the group to which you intend to add the other Oracle Application Server components. It is important that you add it to the group before you add the other Oracle Application Server components because Oracle Fail Safe sets up a dependency between OPMN and the metadata repository when it configures OPMN into the group.
If you decide you no longer want to have Oracle Application Server components configured for high availability, then remove them from the group that contains them.
Because the OPMN server has a dependency on the Oracle Application Server Control service, you must remove the Oracle Application Server Control service from the group before you remove the OPMN server. In addition, if the metadata repository was added to the group when you configured the other Oracle Application Server components into the group, then it must be removed after the Oracle Application Server Control service and the OPMN server are removed because of dependencies it has on the other components.
To remove Oracle Application Server components from a group:
Open Oracle Fail Safe Manager.
In the tree view, select the Oracle Application Server Control service that you want to remove and then, on the Resources menu, select Remove from Group.
The Confirm Remove Resource from Group box opens. Click Yes in the Confirm Remove from Group box. A window opens to show you the progress of the operation.
When the operation to remove the Oracle Application Server Control service completes, select the OPMN server that you want to remove and then, on the Resources menu, select Remove from Group.
The Confirm Remove Resource from Group box opens. Click Yes in the Confirm Remove from Group box. A window opens to show you the progress of the operation.
When the operation to remove the OPMN server completes, select the metadata repository (if it was added when you configured the Oracle Application Server Control service into the group) and then, on the Resources menu, select Remove from Group.
The Confirm Remove Resource from Group box opens. Click Yes in the Confirm Remove from Group box. A window opens to show you the progress of the operation.
After you remove the Oracle Application Server components from a fail-safe group, they remain on the cluster as standalone resources. Note the following:
Unlike a standalone database instance, a standalone Oracle Application Server instance is represented in the tree view on each cluster node.
A standalone Oracle Application Server instance is represented in the tree view as the home into which Oracle Application Server was installed.