How To Manage Manual Failover for Application Server Control 10.1.3 (Doc ID 429344.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Application Server 10g Enterprise Edition - Version: 10.1.3.0.0 to 10.1.3.4.0
Enterprise Manager for iAS - Version: 10.1.3.0.0 to 10.1.3.4.0
Information in this document applies to any platform.
Checked for relevance on 22-May-2009

Goal

This document describes the manual steps for Application Server Control (ASC) failover in Application Server version 10.1.3.

In Application Server 10.1.3, AS Control has been re-architected as a J2EE application called ascontrol. The OC4J instance where the ascontrol application is running is known as the OC4J Administrative Instance. The idea behind this was to make ASControl more of a lightweight architecture that would not require a lot of system resources.

If more than one ascontrol application is running in your cluster topology, the following warning message appears at the top of the Cluster Topology page:

 

====================================================

You have more than one instance of the Application Server Control application
running in this cluster. This is not a recommended configuration and could lead
to unexpected problems. Please stop the additional instances of Application
Server Control or disable routing to these instances.

====================================================


Each Oracle Application Server instance has its own Application Server Control that is used to manage the instance. After joining a cluster, only one Application Server Control is required to manage the entire cluster and the other ones must be stopped.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms