Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Fusion Middleware HA - FMW HA - Version: 10.1.3.0.0 to 10.1.3.2.0 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
This note addresses a topology consisting of two or more AS instances installed over two or more separate nodes. (The High Availability term 'node' is used in this article to denote a physical server.)
The AS instances have been configured as a Cluster using the Static Discovery Method as outlined in
Oracle� Application Server Administrator's Guide
10g Release 3 (10.1.3.1.0)
Part Number B28940-01
6 Reconfiguring Application Server Instances
6.2 Configuring Cluster Topologies
Each AS instance has an entry in opmn.xml similar to this example:
<port local="6101" remote="6201" request="6004"/>
<ssl enabled="true" wallet-file="$ORACLE_HOME/opmn/conf/ssl.wlt/default"/>
The output from executing '$ORACLE_HOME/opmn/bin/opmnctl @cluster status' from each AS instance only shows details of the AS instances installed on the local node.
It is possible to ping all of the remote servers.
The goal is for the cluster configuration to communicate with all AS instances in the cluster, including those AS instances on remote nodes.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms