Oracle® Application Server 10g

1 Restrictions and Supported Configurations

The following sections describe the restrictions and supported configurations for performing the procedure described in this document:

• General Restrictions

• Supported Installation Types

• Support for Separately Installed Components

2 Creating a New targets.xml for the Active Application Server Control

By default, each Oracle Application Server instance has its own Application Server Control Console URL and its own list of targets to manage. The targets managed by each Application Server Control are defined in the following configuration file in the home directory of the Oracle Application Server instance:

$ORACLE_HOME/sysman/emd/targets.xml (UNIX)
%ORACLE_HOME%\sysman\emd\targets.xml (Windows)

The first step in managing multiple application server instances from a single Application Server Control is to combine the targets.xml files for each instance into one.

To create a new targets.xml that includes the application server targets for multiple application server instances, use the following procedure:

1. Stop the Application Server Control for each of the application server instances on the host.

   On UNIX systems, enter the following command in each Oracle Application Server Oracle home to stop the Application Server Control:

   prompt> ORACLE_HOME/bin/emctl stop iasconsole
   
   

   On Windows systems, use the Services control panel to stop the Application Server Control service for each Oracle home.

2. If it's not set already, set the ORACLE_HOME environment variable so it represents the complete path to the home directory of the active Application Server Control, which you will use to manage multiple application server instances on the host.

   For example:

   prompt> setenv ORACLE_HOME /dev01/oracle/oas1/ (UNIX)
   prompt> set ORACLE_HOME=D:\oracle\oas1\ (Windows)
   
   

3. Set the JAVA_HOME environment variable so it represents the location of your Java executable.

   For example:

   prompt> setenv JAVA_HOME $ORACLE_HOME/jdk (UNIX)
   prompt> set JAVA_HOME=%ORACLE_HOME%\jdk (Windows)
   
   

4. Change directory to the following location in the home directory of the active Application Server Control:

   $ORACLE_HOME/sysman/emd/ (UNIX)
   %ORACLE_HOME%\sysman\emd\ (Windows)
   
   

5. Copy the targets.xml file so you have a backup copy that will not be overwritten:

   prompt> cp targets.xml old_targets.xml (UNIX)
   prompt> copy targets.xml old_targets.xml (Windows)
   
   

6. Enter the following command at the command prompt:

   prompt> $JAVA_HOME/bin/java -jar $ORACLE_HOME/jlib/emConfigInstall.jar listtargetsfully <source_home> <active_home> > targets_temp.xml (UNIX)
   
   prompt> %JAVA_HOME%\bin\java -jar %ORACLE_HOME%\jlib\emConfigInstall.jar listtargetsfully <source_home> <active_home> targets_temp.xml (Windows)
   
   

   Replace <source_home> with the full path to the Oracle home of the application server instance that will be managed by the active Application Server Control.

   Replace <active_home> with the full path to the Oracle home for the active Application Server Control.

   For example:

   prompt> $JAVA_HOME/bin/java -jar $ORACLE_HOME/jlib/emConfigInstall.jar listtargetsfully /dev0/oracle/oas2/ $ORACLE_HOME > targets_temp.xml (UNIX)
   
   prompt> %JAVA_HOME%\bin\java -jar %ORACLE_HOME%\jlib\emConfigInstall.jar listtargetsfully C:\oracle\oas2 %ORACLE_HOME% > targets_temp.xml (Windows)
   
   

   This command lists the contents of the targets.xml file in the source Oracle home and redirects the output to a temporary version of the targets.xml file. This temporary version of the file (targets_temp.xml) contains the contents of the targets.xml files in the source Oracle Home. The temporary file also includes any encrypted information (such as target monitoring credentials) in a format that can be read successfully by the active Application Server Control.

   
   

   Note: It is important that you use the emConfigInstall.jar administrative tool to create the targets_temp.xml temporary file. Do not attempt to copy and paste the contents of the inactive targets.xml into the targets.xml of the active Oracle home; otherwise, encrypted information in the targets.xml file will be lost.

   
   

7. Using a text editor, open the targets_temp.xml file and copy all of the content, except the following:

   • The <Targets> and </Targets> tags at the beginning and at the end of the file

   • The target definition for the host target. For example:

     <Target TYPE="host" NAME="sys1.acme.com" DISPLAY_NAME="sys1.acme.com" VERSION="1.0">
     </Target>
     
     

8. Paste the content you copied from the targets_temp.xml file into the targets.xml file in the Oracle home of the active Application Server Control.

   Be sure to paste the content at the end of the file, but before the </Targets> tag. In other words, be sure that all the target definitions are within the <Targets> and </Targets> tags.

9. Locate the following entry for each oracle_ias target type in the new targets.xml file:

   <Property NAME="StandaloneConsoleURL" VALUE="http://node_name:port/emd/console"/>
   
   

   This entry identifies the URL and port number of the Application Server Control Console used to manage the application server instance.

10. Make sure the port number for each of these entries matches the port number of the active Application Server Control Console, which you will be using to manage multiple application server targets on this host.

11. Save and close the updated targets.xml file.

3 Updating the StandaloneConsoleURL Property in the Inactive targets.xml File

By default, when you install multiple instances of Oracle Application Server on a host, each instance is assigned a unique port number from which you can view the Application Server Control Console for that instance. However, when you configure your system to use only one Application Server Control for multiple instances, all the instances on the host must reference the same URL and port number.

As a result, you must make sure that other software components on the system also use only the port for the active Application Server Control.

Specifically, you must make sure that the Distributed Configuration Management (DCM) software associated with the inactive Application Server Control is updated to recognize the port number of the active Application Server Control.

You accomplish this task by updating the original targets.xml in the Oracle home directory of the inactive Application Server Control so that the StandaloneConsoleURL property refers to the active Application Server Control URL and port number.

Perform the following task in the Oracle home of the inactive Application Server Control:

1. If you have not done so already, stop the inactive Application Server Control.

   On UNIX systems, enter the following command:

   prompt> INACTIVE_ORACLE_HOME/bin/emctl stop iasconsole
   
   

   On Windows systems, use the Services control panel to stop the Application Server Control service for the inactive Oracle home.

2. Use a text editor to open the targets.xml file, which is located in the following directory of the inactive Oracle home:

   INACTIVE_ORACLE_HOME/sysman/emd/ (UNIX)
   INACTIVE_ORACLE_HOME\sysman\emd\ (Windows)
   
   

3. Locate the StandaloneConsoleURL property for the oracle_ias target:

   <Property NAME="StandaloneConsoleURL" VALUE="http://<node_name>:<port>/emd/console"/>
   
   

   This entry identifies the URL and port number of the Application Server Control Console used to manage this application server instance.

4. Make sure the port number for this entry matches the port number of the active Application Server Control Console, which you will be using to manage this application server target.

5. Save and close the updated targets.xml file.

6. Start and then stop the inactive Application Server Control Console.

   On UNIX systems, use the following commands to start and then stop the Application Server Control:

   prompt> INACTIVE_ORACLE_HOME/bin/emctl start iasconsole
   prompt> INACTIVE_ORACLE_HOME/bin/emctl stop iasconsole
   
   

   On Windows systems, use the Services control panel to start and then stop the inactive Application Server Control service.

   When you restart the Application Server Control Console, DCM is initialized and registers the new port value.

   Now that you have configured the active Application Server Control, you no longer need to run this instance of the Application Server Control.

4 Updating the opmn.xml File to Refer to the Active Application Server Control

The Oracle Process Management and Notification (OPMN) software within each Oracle Application Server Oracle home is configured to work with the local Application Server Control for that instance.

When you configure your system to use only one Application Server Control, you must edit the OPMN configuration file in the Oracle home of the inactive Application Server Control. Specifically, you must configure OPMN so that it references the active Application Server Control and not the local, inactive Application Server Control.

Perform this procedure in the Oracle home of the inactive Application Server Control:

1. Stop OPMN.

   On UNIX systems, enter the following command in the Oracle home of the inactive Application Server Control:

   prompt> INACTIVE_ORACLE_HOME/opmn/bin/opmnctl stopall
   
   

   On Windows systems, use the Services control panel to stop the process manager service for the inactive Oracle home.

2. Use a text editor to open the opmn.xml file for the instance:

   INACTIVE_ORACLE_HOME/opmn/conf/opmn.xml (UNIX)
   INACTIVE_ORACLE_HOME\opmn\conf\opmn.xml (Windows)
   
   

3. Locate the following entry in the file:

   <ias-component id="dcm-daemon" status="enabled" id-matching="true">
             .
             .
             .
           <data id="java-parameters" value="-Xmx256m -Xrs
               -Doracle.ias.sysmgmt.logging.loglevel=ERROR
               -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=$TMP"/>
             .
             .
             .
   </ias-component>
   
   

4. Add the following to the existing java-parameters data tag:

   -DemLocOverride=<oracle_home_of_the_active_application_server_control>
   
   

   For example:

   <data id="java-parameters" value="-Xmx256m -Xrs
         -Doracle.ias.sysmgmt.logging.loglevel=ERROR
         -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=$TMP
         -DemLocOverride=/dev0/oracle/oas1"/>
   
   

   Note that the additional Java parameter must be inserted before the closing quotation mark.

5. Save and close the opmn.xml file.

6. Start OPMN.

   On UNIX systems, enter the following command:

   prompt> INACTIVE_ORACLE_HOME/opmn/bin/opmnctl startall
   
   

   On Windows systems, use the Services control panel to start the process manager service for the inactive Oracle home.

5 Restarting the Active Application Server Control and Verifying the Results

The procedure you use to verify the results of this procedure varies depending upon your configuration. See the following topics for more information:

• Verifying the Procedure for Infrastructure Installations

• Verifying the Procedure for Middle-Tier Installations

6 Deinstallation Procedures

After you have performed the procedures in this document, you may want to deinstall one of the application server instances on the host.

The following sections provide instructions you should follow before you remove either the active or the inactive application server instance:

• Deinstalling the Oracle Home with the Active Application Server Control

• Deinstalling the Oracle Home with the Inactive Application Server Control

7 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.