Oracle B32100-01 ユーザーズマニュアル
Installing an OracleAS Cluster (Identity Management) Configuration
9-10
Oracle Application Server Installation Guide
If you have a staticports.ini file, you should also use the same file for installations on
subsequent nodes.
subsequent nodes.
9.5.3.2 Disable TCP Monitoring on Load Balancer for First Node
Before installing on the first node, you must make sure that TCP monitoring is not
enabled for the Virtual IP on the first node.
enabled for the Virtual IP on the first node.
9.5.3.3 Configure the Load Balancer to Return Immediately to the Calling Client
It is highly recommended that you configure the load balancer virtual server to return
immediately to the calling client when the backend services to which it forwards traffic
are unavailable. This is preferred over the client disconnecting on its own after a
timeout based on the TCP/IP settings on the client machine.
immediately to the calling client when the backend services to which it forwards traffic
are unavailable. This is preferred over the client disconnecting on its own after a
timeout based on the TCP/IP settings on the client machine.
If your load balancer is not configured this way, the Java Security Configuration
Assistant may report the following:
Assistant may report the following:
WARNING: DCM service may not be available at this time to synchronize $ORACLE_
HOME/j2ee/home/config/jazn-data.xml file.
Refer to
information on how to correct this problem after the installation is finished.
9.5.3.4 Ensure that the OracleAS Metadata Repository Is Not Registered with any
Oracle Internet Directory
Oracle Internet Directory
When you perform the installation on the first node, you need to specify an OracleAS
Metadata Repository that is not registered with any Oracle Internet Directory. The
installer checks for this. If the installer finds that the OracleAS Metadata Repository is
already registered with an Oracle Internet Directory, then it assumes that you are
installing on subsequent nodes, and that you want to join the cluster that was created
when you installed on the first node. It prompts you for the existing cluster name, and
the connect information for the Oracle Internet Directory.
Metadata Repository that is not registered with any Oracle Internet Directory. The
installer checks for this. If the installer finds that the OracleAS Metadata Repository is
already registered with an Oracle Internet Directory, then it assumes that you are
installing on subsequent nodes, and that you want to join the cluster that was created
when you installed on the first node. It prompts you for the existing cluster name, and
the connect information for the Oracle Internet Directory.
9.5.3.5 Select the Same Components for Each Node
You must select the same components in the Select Configuration Options screen when
installing on each node. For example, if you select Oracle Internet Directory, OracleAS
Single Sign-On, and Oracle Delegated Administration Services on the first node, you
must select these same set of components on subsequent nodes.
installing on each node. For example, if you select Oracle Internet Directory, OracleAS
Single Sign-On, and Oracle Delegated Administration Services on the first node, you
must select these same set of components on subsequent nodes.
9.5.3.6 Run the Installer
Follow the steps in
Key Points for Installing on the First Node
■
In the Select Configuration Options screen, select High Availability and
Replication
Replication
, in addition to selecting the components.
■
In the Select High Availability or Replication Option screen, select OracleAS
Cluster (Identity Management)
Cluster (Identity Management)
.
See Also:
The Oracle Application Server High Availability Guide for
more information on load balancer requirements.