8 Changing Network Configurations

8.2.1 Understanding the chgiphost Command

The chgiphost command-line utility changes the hostname, domain name, or IP address of a middle-tier instance, Infrastructure, or Identity Management installation.

The utility is located at:

• On UNIX systems:

  ORACLE_HOME/chgip/scripts/chgiphost.sh
  
  

• On Windows systems:

  ORACLE_HOME\chgip\scripts\chgiphost.bat
  
  

Table 8-2 shows the options for the command.

Note that if you use chgiphost to change the hostname or domain name, it does not update the instance name. For example, assume that the original instance name, with the hostname and domain name appended, is:

101202mid.myhost1.mydomain.com

If you change the hostname to myhost2, the instance name remains the same.

8.2.2 Changing the Hostname or Domain Name of a Middle-Tier Installation

This section describes how to change the hostname, domain name, or both, of a host that contains any of the following middle-tier installation types:

• J2EE and Web Cache

• Portal and Wireless

• Business Intelligence and Forms

The following sections describe the procedure:

• Before You Begin

• Task 1: Prepare Your Host

• Task 2: Change the Hostname

• Task 3: Run the chgiphost Command

• Task 4: Restart Your Environment

• Task 5: Update OracleAS Portal, OracleAS Wireless, OracleAS Single Sign-On, and Oracle Ultra Search

• Task 6: Manually Update the Hostname in Files

Before You Begin

Review the following items before you start:

• If any installations contain Oracle Content Management Software Development Kit, you must perform additional steps. Refer to Oracle Content Management SDK Administrator's Guide before starting this procedure.

• If the middle-tier instance is registered with Oracle Internet Directory, you must supply the cn=orcladmin password during the procedure.

• Consider changing the log level before running the chgiphost command so you can view more detailed information. See Section 8.2.6.2, "Setting the Log Level for chgiphost" for more information.

• If your old hostname is a string that is likely to appear in a configuration file, the chgiphost command may encounter problems when trying to update the configuration files. Refer to Section 8.2.6.3, "Customizing the chgiphost Command" for information on how to avoid this problem.

• Write down the old hostname and IP address before you begin. You will be prompted for these values.

• Oracle recommends that you perform a backup of your environment before you start this procedure. Refer to Part V, "Backup and Recovery".

Task 1: Prepare Your Host

Prepare your host for the change by removing instances from OracleAS Clusters and stopping all processes:

1. If the host contains a middle-tier instance that is part of an OracleAS Cluster, remove the instance from the OracleAS Cluster. You can add the instance back into the cluster at the end of the procedure.

   
   

   See Also: Oracle Application Server High Availability Guide for instructions on removing instances from an OracleAS Cluster

   
   

2. If the host contains an instance that stores the file-based repository used by an OracleAS File-Based farm, you must remove all instances from that farm, even if they reside on other hosts. This is because the repository ID will change when you change the hostname. As a result, you must remove all instances from the farm, change the hostname (which will change the repository ID), then add the instances back to the farm at the end of this procedure using the new repository ID.

   To remove an instance from an OracleAS File-Based Farm, run the following command in the instance Oracle home:

   (UNIX) ORACLE_HOME/dcm/bin/dcmctl leavefarm 
   (Windows) ORACLE_HOME\dcm\bin\dcmctl leavefarm
   
   

3. If the host contains a J2EE and Web Cache instance that is part of an OracleAS File-Based Farm that uses a repository on another host or an OracleAS Database-Based Farm, remove the instance from the farm:

   (UNIX) ORACLE_HOME/dcm/bin/dcmctl leavefarm 
   (Windows) ORACLE_HOME\dcm\bin\dcmctl leavefarm
   
   

   You can add the instance back to the farm at the end of the procedure.

4. If the host contains a middle-tier instance that is part of an OracleAS Web Cache cluster, remove the instance from the cache cluster. You can add the instance back into the cluster at the end of the procedure.

   
   

   See Also: Oracle Application Server Web Cache Administrator's Guide for instructions on removing caches from a cache cluster

   
   

5. Shut down each middle-tier instance on the host by running the following commands in each Oracle home:

   • On UNIX systems:

     ORACLE_HOME/bin/emctl stop iasconsole
     ORACLE_HOME/opmn/bin/opmnctl stopall
     
     

   • On Windows systems:

     ORACLE_HOME\bin\emctl stop iasconsole
     ORACLE_HOME\opmn\bin\opmnctl stopall
     
     

6. If the middle-tier instance was part of an OracleAS File-Based Farm, make sure the DCM daemon is running in the file-based repository instance. This applies whether the repository instance is on the same host or a different host.

   To verify if the DCM daemon is running, run the following command in the file-based repository Oracle home:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl status
   (Windows) ORACLE_HOME\opmn\bin\opmnctl status
   
   

   To start the DCM daemon:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=dcm-daemon
   (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=dcm-daemon
   
   

7. To make sure Oracle Application Server processes will not start automatically after a restart of the host, disable any automated startup scripts you may have set up, such as /etc/init.d scripts.

8. Make sure the Oracle Internet Directory that is used by the middle-tier is started.

Task 2: Change the Hostname

Update your operating system with the new hostname, domain name, or both. Consult your operating system documentation for information on how to perform the following steps. You can also change the IP address, if desired.

1. Make the updates to your operating system to properly change the hostname, domain name, or both.

2. Restart the host, if necessary for your operating system.

3. Verify that you can ping the host from another host in your network. Be sure to ping using the new hostname to make sure everything is resolving properly.

Task 3: Run the chgiphost Command

Follow these steps for each middle-tier instance on your host. Be sure to complete the steps entirely for one middle-tier instance before you move on to the next.

1. Log in to the host as the user that installed the middle-tier instance.

2. Make sure your ORACLE_HOME environment variable is set to the middle-tier Oracle home. Do not use a trailing slash (UNIX) or backslash (Windows) when specifying the variable.

3. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you must set depend on the type of your UNIX operating system.

4. Run the following commands in the middle-tier Oracle home:

   • On UNIX systems:

     cd ORACLE_HOME/chgip/scripts
     ./chgiphost.sh -mid
     
     

   • On Windows systems:

     cd ORACLE_HOME\chgip\scripts
     cmd /c chgiphost.bat -mid
     
     

   The chgiphost command prompts for information, as shown in Table 8-3. Note that the prompts may provide values in parentheses. You can enter a different value, or press the return key to accept the suggested value.

   Table 8-3 Prompts and Actions for chgiphost -mid

   Prompt	Action
   Enter fully qualified hostname (hostname.domainname) of destination	Enter the new fully-qualified hostname. This may be a new hostname, domain name, or both.
   Enter valid IP Address of destination	If you changed the IP address of the host, enter the new IP address. Otherwise, enter the current IP address.
   Enter valid IP Address of source	If you changed the IP address of the host, enter the old IP address. Otherwise, enter the current IP address.
   OIDAdmin Password:	Enter the cn=orcladmin password for the Oracle Internet Directory in which this middle-tier instance is registered.

   
   

5. Verify that the tool ran successfully by checking for errors in the files in the following directory:

   • On UNIX systems:

     ORACLE_HOME/chgip/log
     
     

   • On Windows systems:

     ORACLE_HOME\chgip\log
     

Task 4: Restart Your Environment

Restart the middle-tier instances and restore your configuration to the way it was before you started the procedure:

1. Start each middle-tier instance on your host by running the following commands in each Oracle home:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl startall
     ORACLE_HOME/bin/emctl start iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl startall
     ORACLE_HOME\bin\emctl start iasconsole
     
     

2. If you removed any instances from an OracleAS Web Cache cluster at the beginning of this procedure, add them back to the cache cluster.

   
   

   See Also: Oracle Application Server Web Cache Administrator's Guide for instructions on adding caches to a cluster

   
   

3. If the host contained an instance that stored the file-based repository used by an OracleAS File-Based farm:

   1. Obtain the new repository ID for the new farm by running the following command in the Oracle home of that instance:

      (UNIX) ORACLE_HOME/dcm/bin/dcmctl getRepositoryID
      (Windows) ORACLE_HOME\dcm\bin\dcmctl getRepositoryID
      
      

   2. Re-create the OracleAS File-Based Farm by adding that instance to the new farm using the new repository ID obtained in the preceding step. The repository_ID is of the form hostname:port.

      (UNIX) ORACLE_HOME/dcm/bin/dcmctl joinfarm -r repository_ID
      (WINDOWS) ORACLE_HOME\dcm\bin\dcmctl joinfarm -r repository_ID
      
      

   3. Add all instances on other hosts back to the new farm using the command in the preceding step.

4. If you removed any J2EE and Web Cache instances from an OracleAS File-Based Farm (that uses a repository on another host) at the beginning of this procedure, add each one back as follows:

   (UNIX) ORACLE_HOME/dcm/bin/dcmctl joinfarm -r repository_ID
   (Windows) ORACLE_HOME\dcm\bin\dcmctl joinfarm -r repository_ID
   
   

   In the preceding command, repository_ID is the hostname:port value returned by running the following command in the file-based repository Oracle home:

   (UNIX) ORACLE_HOME/dcm/bin/dcmctl getRepositoryID
   (Windows) ORACLE_HOME\dcm\bin\dcmctl getRepositoryID
   
   

5. If you removed any J2EE and Web Cache instances from an OracleAS Database-Based Farm at the beginning of this procedure, add each one back as follows:

   (UNIX) ORACLE_HOME/dcm/bin/dcmctl joinfarm
   (Windows) ORACLE_HOME\dcm\bin\dcmctl joinfarm
   
   

6. If you removed any instances from an OracleAS Cluster at the beginning of this procedure, add them back to the cluster.

   
   

   See Also: Oracle Application Server High Availability Guide for instructions on adding instances to an OracleAS Cluster

   
   

7. If you disabled any processes for automatically starting Oracle Application Server at the beginning of this procedure, enable them.

Task 5: Update OracleAS Portal, OracleAS Wireless, OracleAS Single Sign-On, and Oracle Ultra Search

You must update OracleAS Portal, OracleAS Wireless, OracleAS Single Sign-On, and Oracle Ultra Search when you change the hostname.

1. Update OracleAS Portal with the new OracleAS Wireless service URL.

   If you change the hostname, the OracleAS Wireless server URL will also change to use this new hostname. Therefore, you must update OracleAS Portal with the new OracleAS Wireless service URL. For more information, refer to "Updating the OracleAS Wireless Portal Service URL Reference" in Oracle Application Server Portal Configuration Guide.

2. Update OracleAS Single Sign-On server with the new OracleAS Wireless SSO Partner URL.

   If you change the hostname, the OracleAS Wireless SSO Partner URL uses the new hostname. Therefore, you must update OracleAS Single Sign-On with the new OracleAS Wireless SSO Partner URL.

   Rather than manually changing the OracleAS Single Sign-On settings, Oracle recommends that you re-register the OracleAS Wireless server with OracleAS Single Sign-On using the following command line tool:

   (UNIX) ORACLE_HOME/wireless/bin/reRegisterSSO.sh
   (Windows) ORACLE_HOME\wireless\bin\reRegisterSSO.bat
   
   

   This tool, which prompts you through the registration process, not only updates the OracleAS Wireless URL in the OracleAS Single Sign-On server, but it also updates the SSO URL in the OracleAS Wireless server.

3. Re-register OracleAS Portal as an Oracle Ultra Search Content Source.

   If you change the hostname, the OracleAS Portal URL will also change to use this new hostname. Therefore, you must update Oracle Ultra Search with the new OracleAS Portal URL. In Oracle Ultra Search, the OracleAS Portal URL is used to register OracleAS Portal as a crawlable content source. For more information, refer to "Registering OracleAS Portal as a Content Source" in Oracle Application Server Portal Configuration Guide.

Task 6: Manually Update the Hostname in Files

If you edited a file and entered the hostname as part of a user-defined parameter such as the Oracle home path, the hostname is not automatically updated by running the chgiphost command. To update the hostname in such cases, you must edit the files manually. For example on UNIX, the plsql.conf file may contain an NFS path including the hostname, such as: /net/dsun1/private/....

The chgiphost command also does not edit the hostname references in the documentation files. You must manually edit these files to update the hostname. Examples of such files are the following files in the ORACLE_HOME/Apache/Apache/htdocs directory:

• index.html.de

• index.html.es_ES

• index.html.fr

• index.html.it

• index.html.ja

• index.html.ko

• index.html.pt_BR

• index.html.zh_CN

• index.html.zh_TW

8.2.3 Changing the Hostname, Domain Name, or IP Address of an Identity Management Installation

This section describes how to change the hostname, domain name, or IP address on a host that contains an Identity Management installation. This procedure applies to any Identity Management-only installation, including the following:

• Identity Management with only Oracle Internet Directory configured

• Identity Management with OracleAS Single Sign-On and Oracle Delegated Administration Services configured (Oracle Directory Integration and Provisioning is optional)

• Identity Management with Oracle Internet Directory, OracleAS Single Sign-On, and Oracle Delegated Administration Services configured (Oracle Directory Integration and Provisioning is optional)

The following sections describe the procedure:

• Before You Begin

• Task 1: Shut Down Middle-Tier Instances

• Task 2: Prepare Your Host

• Task 3: Change the Hostname or IP Address

• Task 4: Run the chgiphost Command

• Task 5: Restart Your Environment

• Task 6: Update Your Environment

• Task 7: Update Oracle Internet Directory If LDAP-Based Replication Is Used

Before You Begin

Review the following items before you start the procedure:

• Consider changing the log level before running the chgiphost command so you can view more detailed information. See Section 8.2.6.2, "Setting the Log Level for chgiphost" for more information.

• If your old hostname is a string that is likely to appear in a configuration file, the chgiphost command may encounter problems when trying to update the configuration files. Refer to Section 8.2.6.3, "Customizing the chgiphost Command" for information on how to avoid this problem.

• Write down the old hostname and IP address before you begin. You will be prompted for these values.

• Oracle recommends that you perform a backup of your environment before you start this procedure. Refer to Part V, "Backup and Recovery" for more information.

Task 1: Shut Down Middle-Tier Instances

For each middle-tier instance that uses Identity Management, stop the Application Server Control Console and the middle-tier instance using the following commands:

• On UNIX systems:

  ORACLE_HOME/bin/emctl stop iasconsole
  ORACLE_HOME/opmn/bin/opmnctl stopall
  
  

• On Windows systems:

  ORACLE_HOME\bin\emctl stop iasconsole
  ORACLE_HOME\opmn\bin\opmnctl stopall
  
  

Task 2: Prepare Your Host

Prepare your host for the hostname change by stopping all processes:

1. Set the ORACLE_HOME environment variable.

2. Shut down the Identity Management installation, including the servers, such as Oracle Directory Server, Directory Integration and Provisioning Data server, and Replication Server, and Application Server Control Console. For example, on UNIX, use the following commands:

   ORACLE_HOME/bin/emctl stop iasconsole
   ORACLE_HOME/bin/oidctl server=odisrv instance=instance_number stop
   ORACLE_HOME/bin/oidctl connect=global_db_name server=oidrepld instance=instance_number stop
   ORACLE_HOME/bin/oidctl server=oidldapd instance=instance_number stop
   ORACLE_HOME/opmn/bin/opmnctl stopall
   
   

3. To make sure Oracle Application Server processes will not start automatically after a restart of the host, disable any automated startup scripts you may have set up, such as /etc/init.d scripts.

Task 3: Change the Hostname or IP Address

Update your operating system with the new hostname, domain name, or IP address. Consult your operating system documentation for information on how to perform the following steps:

1. Make the updates to your operating system to properly change hostname, domain name, or both.

2. Restart the host, if necessary for your operating system.

3. Verify that you can ping the host from another host in your network. Be sure to ping using the new hostname to make sure everything is resolving properly.

Task 4: Run the chgiphost Command

Perform these steps using the Identity Management Oracle home:

1. Log in to the host as the user that installed Identity Management.

2. Set the ORACLE_HOME environment variable. Do not use a trailing slash (UNIX) or backslash (Windows) when specifying the ORACLE_HOME variable.

3. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you must set depend on the type of your UNIX operating system.

4. Run the following commands in the Identity Management Oracle home:

   • On UNIX systems:

     cd ORACLE_HOME/chgip/scripts
     ./chgiphost.sh -idm
     
     

   • On Windows systems:

     cd ORACLE_HOME\chgip\scripts
     cmd /c chgiphost.bat -idm
     
     

   The chgiphost command prompts for information, as shown in Table 8-4. Note that the prompts may provide values in parentheses. You can enter a different value, or press the return key to accept the suggested value.

   Table 8-4 Prompts and Actions for chgiphost -idm

   Prompt	Action
   Enter fully qualified hostname (hostname.domainname) of destination	If you changed the hostname or domain name on your system, enter the new fully-qualified hostname. Otherwise, enter the current fully-qualified hostname.
   Enter fully qualified hostname (hostname.domainname) of source	If you changed the hostname or domain name on your system, enter the old fully-qualified hostname. Otherwise, enter the current fully-qualified hostname.
   Enter valid IP Address of destination	If you changed the IP address of the system, enter the new IP address. Otherwise, enter the current IP address
   Enter valid IP Address of source	If you changed the IP address of the system, enter the old IP address. Otherwise, enter the current IP address

   
   

5. Verify that the tool ran successfully by checking for errors in the files in the following directory:

   (UNIX) ORACLE_HOME/chgip/log
   (Windows) ORACLE_HOME\chgip\log
   

Task 5: Restart Your Environment

Restart the Identity Management installation and any other instances that you stopped during this procedure:

1. Restart the Identity Management instance, using the following commands:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall
     ORACLE_HOME/opmn/bin/opmnctl startall
     ORACLE_HOME/bin/emctl start iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall
     ORACLE_HOME\opmn\bin\opmnctl startall
     ORACLE_HOME\bin\emctl start iasconsole
     
     

2. If you disabled any processes for automatically starting Oracle Application Server at the beginning of this procedure, enable them.

Task 6: Update Your Environment

This task contains the steps to update your environment for the new hostname, domain name, or IP address. The steps you need to take depend on how your environment is configured. If you changed the hostname or IP address of the host containing:

• Oracle Internet Directory only: See "Configuration 1: Oracle Internet Directory Only". Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you change the host that contains Oracle Internet Directory. In this case, you must update the other Identity Management components and the middle tiers that use this Identity Management.

• Identity Management components other than Oracle Internet Directory: See "Configuration 2: OracleAS Single Sign-On, Oracle Delegated Administration Services, and (optionally) Oracle Directory Integration and Provisioning". Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you change the host that contains the other Identity Management components. In this case, you must update the middle tiers that use this Identity Management.

• Oracle Internet Directory and other Identity Management components: See "Configuration 3: Oracle Internet Directory, OracleAS Single Sign-On, Oracle Delegated Administration Services, and (optionally) Oracle Directory Integration and Provisioning". Oracle Internet Directory and the other Identity Management components are installed on the same host. In this case, you must update the middle tiers that use this Identity Management.

If your environment uses LDAP-Based replication of Oracle Internet Directory and Oracle Internet Directory is on a different host than OracleAS Metadata Repository, you can change the hostname, domain name or IP address of the host containing the Master (supplier) or Replica (consumer) Oracle Internet Directory. See Task 7: Update Oracle Internet Directory If LDAP-Based Replication Is Used for information.

Configuration 1: Oracle Internet Directory Only In this case, Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you changed the host that contains Oracle Internet Directory. Take the following steps:

1. In the OracleAS Single Sign-On installation, stop the Infrastructure processes and the Application Server Control Console:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall
     ORACLE_HOME/bin/emctl stop iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall
     ORACLE_HOME\bin\emctl stop iasconsole
     
     

2. Update the ias.properties file in every instance that uses Oracle Internet Directory. This includes other Identity Management instances (OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning) and middle-tier instances (J2EE and Web Cache, Portal and Wireless, and Business Intelligence and Forms).

   In each Oracle home, update the following file:

   (UNIX) ORACLE_HOME/config/ias.properties
   (Windows) ORACLE_HOME\config\ias.properties
   
   

   In the file, update the OIDhost parameter in with the new hostname:

   OIDhost=newhost.us.oracle.com
   
   

3. Update the ldap.ora file in every instance that uses Oracle Internet Directory. This includes other Identity Management instances (OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning) and middle-tier instances (J2EE and Web Cache, Portal and Wireless, and Business Intelligence and Forms).

   In each Oracle home, edit the following file:

   (UNIX) ORACLE_HOME/ldap/admin/ldap.ora
   (Windows) ORACLE_HOME\ldap\admin\ldap.ora
   
   

   In the file, update the DIRECTORY_SERVERS parameter with the new fully-qualified hostname.

4. In the Oracle homes for the other Identity Management components and the middle-tier instances, restart OPMN and Application Server Control Console:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl start
     ORACLE_HOME/bin/emctl start iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl start
     ORACLE_HOME\bin\emctl start iasconsole
     
     

5. In the Oracle homes for the other Identity Management components and each middle tier, run the Change Identity Management Services wizard and supply the new Oracle Internet Directory information:

   1. Using the Application Server Control Console, navigate to the Application Server Home page for OracleAS Single Sign-On.

   2. Click the Infrastructure link.

   3. On the Infrastructure page, in the Identity Management section, click Change.

   4. Follow the steps in the wizard for supplying the new Identity Management information (new hostname).

      Note that although you may see the new Internet Directory host and port on the page, you still need to perform this step. The Application Server Control Console displays the virtual hostname only because it read it from the updated ias.properties file.

6. When the wizard completes, it asks you to restart the affected components. Run the following commands in each Oracle home:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall
     ORACLE_HOME/opmn/bin/opmnctl startall
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall
     ORACLE_HOME\opmn\bin\opmnctl startall
     
     

7. If OracleAS Certificate Authority is installed, take the following steps:

   1. Stop OracleAS Certificate Authority, the OC4J oca process, and the Oracle HTTP Server on the host running OracleAS Certificate Authority. For example, on UNIX, execute the following commands:

      ORACLE_HOME/oca/bin/ocactl stop
      ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=oca
      ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
      
      

   2. Edit the following file and change the name of the host listed in the file:

      (UNIX) ORACLE_HOME/oca/conf/oca.conf
      (Windows) ORACLE_HOME\oca\conf\oca.conf
      
      

   3. Reassociate with OracleAS Single Sign-On and Oracle Internet Directory. For example, on UNIX:

      ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port OcaSslPort
      
      

   4. Start Oracle HTTP Server, the OC4J oca process, and OracleAS Certificate Authority. For example, on UNIX:

      ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
      ORACLE_HOME/opmn/bin/opmnctl startproc process-type=oca
      ORACLE_HOME/oca/bin/ocactl start
      
      

Configuration 2: OracleAS Single Sign-On, Oracle Delegated Administration Services, and (optionally) Oracle Directory Integration and Provisioning In this case, Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you changed the host that contains the other Identity Management components.

In each middle-tier installation (J2EE and Web Cache, Portal and Wireless, or Business Intelligence and Forms), take the following steps:

1. Start the OPMN and the Application Server Control Console:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl start
     ORACLE_HOME/bin/emctl start iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl start
     ORACLE_HOME\bin\emctl start iasconsole
     
     

2. In the Oracle home for each middle tier, run the Change Identity Management Services wizard and supply the new Oracle Internet Directory information:

   1. Using the Application Server Control Console, navigate to the Application Server Home page for OracleAS Single Sign-On.

   2. Click the Infrastructure link.

   3. On the Infrastructure page, in the Identity Management section, click Change.

   4. Follow the steps in the wizard for supplying the new Identity Management information (new hostname).

      Note that although you may see the new Internet Directory host and port on the page, you still need to perform this step. The Application Server Control Console displays the virtual hostname only because it read it from the updated ias.properties file.

3. Restart the affected components. Run the following commands in each Oracle home:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall
     ORACLE_HOME/opmn/bin/opmnctl startall
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall
     ORACLE_HOME\opmn\bin\opmnctl startall
     
     

Configuration 3: Oracle Internet Directory, OracleAS Single Sign-On, Oracle Delegated Administration Services, and (optionally) Oracle Directory Integration and Provisioning In this case, Oracle Internet Directory and the other Identity Management components are installed on the same host and this is the host you changed. Take the following steps:

1. Start the OPMN and the Application Server Control Console:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl start
     ORACLE_HOME/bin/emctl start iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl start
     ORACLE_HOME\bin\emctl start iasconsole
     
     

2. Update the ias.properties file in every middle-tier instance.

   In each Oracle home, update the following file:

   (UNIX) ORACLE_HOME/config/ias.properties
   (Windows) ORACLE_HOME\config\ias.propertie
   
   

   In the file, update the OIDhost parameter in with the new hostname:

   OIDhost=newhost.us.oracle.com
   
   

3. Update the ldap.ora file in every middle-tier instance that uses the Identity Management instance.

   In each Oracle home, edit the following file:

   (UNIX) ORACLE_HOME/ldap/admin/ldap.ora
   (Windows) ORACLE_HOME\ldap\admin\ldap.ora
   
   

   In the file, update the DIRECTORY_SERVERS parameter with the new fully-qualified hostname.

4. In each middle-tier installation (J2EE and Web Cache, Portal and Wireless, or Business Intelligence and Forms), run the Change Identity Management Services wizard:

   1. Using the Application Server Control Console, navigate to the Application Server Home page for the middle-tier instance.

   2. Click the Infrastructure link.

   3. On the Infrastructure page, in the Identity Management section, click Change.

      Note that the Infrastructure page may display an error, but the error will be resolved after you complete the steps in the wizard.

   4. Follow the steps in the wizard for supplying the new Identity Management information.

5. Restart the affected components. Run the following commands in each Oracle home:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall
     ORACLE_HOME/opmn/bin/opmnctl startall
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall
     ORACLE_HOME\opmn\bin\opmnctl startall
     
     

Task 7: Update Oracle Internet Directory If LDAP-Based Replication Is Used

If your environment uses LDAP-Based replication of Oracle Internet Directory and Oracle Internet Directory is on a different host than OracleAS Metadata Repository, you can change the hostname, domain name or IP address of the host containing the Master (supplier) or Replica (consumer) Oracle Internet Directory:

• Configuration A: Host with Master Oracle Internet Directory is Changed

• Configuration B: Host with Replica Oracle Internet Directory is Changed

Configuration A: Host with Master Oracle Internet Directory is Changed

If you change the hostname, domain name, or IP address of the host containing the Master Oracle Internet Directory, take the following steps:

1. Obtain the replica ID of the Master Oracle Internet Directory:

   ldapsearch -p master_port -h master_host -b "" -s base "objectclass=*" orclreplicaid
   
   

2. On both the Master and the Replica, update either orclreplicauri or orclreplicasecondaryuri or both, if they exist, in the replica entry of the Master Oracle Internet Directory. Take the following steps:

   1. Create a file named mod.ldif and enter the following lines in the file:

      dn: orclreplicaid=master_replicaID,cn=replication configuration
      changetype:modify
      replace: orclreplicauri
      orclreplicauri: ldap://new_master_host:new_master_port/
      
      

      In the example, master_replicaID is the ID obtained in Step a, new_master_host is the new hostname of the Master Oracle Internet Directory, and new_master_port is the port number for the Master Oracle Internet Directory.

   2. Run the following command on the Master:

      ldapmodify -p master_port -h master_host -f mod.ldif
      
      

   3. Run the following command on the Replica:

      ldapmodify -p replica_port -h replica_host -f mod.ldif
      
      

3. Restart the Replication server at the Replica:

   oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h
    replica_host -p replica_port -m false" stop
   oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h
    replica_host -p replica_port -m false" start
   
   

   In the example, replica_host is the hostname of the Replica Oracle Internet Directory and replica_port is the port of the Replica Oracle Internet Directory.

Configuration B: Host with Replica Oracle Internet Directory is Changed

If you change the hostname, domain name, or IP address of the host containing the Replica Oracle Internet Directory, take the following steps:

1. Obtain the replica ID of the Replica Oracle Internet Directory:

   ldapsearch -p replica_port -h replica_host -b "" -s base "objectclass=*" orclreplicaid
   
   

2. On both the Master and the Replica, update either orclreplicauri or orclreplicasecondaryuri or both, if they exist, in the replica entry of the Replica Oracle Internet Directory. Take the following steps:

   1. Create a file named mod.ldif and enter the following lines in the file:

      dn: orclreplicaid=replica_replicaID,cn=replication configuration
      changetype:modify
      replace: orclreplicauri
      orclreplicauri: ldap://new_replica_host:new_replica_port/
      
      

      In the example, replica_replicaID is the ID obtained in Step a, new_replica_host is the new hostname of the Replica Oracle Internet Directory, and new_replica_port is the port number for the Replica Oracle Internet Directory.

   2. Run the following command on the Master:

      ldapmodify -p master_port -h master_host -f mod.ldif
      
      

   3. Run the following command on the Replica:

      ldapmodify -p replica_port -h replica_host -f mod.ldif
      
      

3. Restart the Replication server at the Replica:

   oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h
    new_replica_host -p new_replica_port -m false" stop
   oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h
    new_replica_host -p new_replica_port -m false" start
   
   

   In the example, new_replica_host is the new hostname of the Replica Oracle Internet Directory and new_replica_port is the port of the Replica Oracle Internet Directory.

8.2.4 Changing the Hostname or Domain Name of an OracleAS Certificate Authority Installation

If you have installed OracleAS Certificate Authority, and you want to change the name of the OracleAS Certificate Authority host, then you must perform these steps:

1. Verify that Oracle Internet Directory and OracleAS Metadata Repository are started.

2. Stop OracleAS Certificate Authority, the OC4J oca process, and the Oracle HTTP Server on the host running OracleAS Certificate Authority. For example, on UNIX, execute the following commands:

   ORACLE_HOME/oca/bin/ocactl stop
   ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=oca
   ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
   
   

3. Change the name of the host where OracleAS Certificate Authority is running.

4. Regenerate the SSL wallet. For example, on UNIX:

   ORACLE_HOME/oca/bin/ocactl generatewallet -type CASSL
   
   

5. Reassociate with OracleAS Single Sign-On and Oracle Internet Directory. For example, on UNIX:

   ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port OcaSslPort
   
   

6. Start Oracle HTTP Server, the OC4J oca process, and OracleAS Certificate Authority. For example, on UNIX:

   ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
   ORACLE_HOME/opmn/bin/opmnctl startproc process-type=oca
   ORACLE_HOME/oca/bin/ocactl start
   
   

8.2.5 Changing the IP Address of an Infrastructure Containing a Metadata Repository

This section describes how to change the IP address of a host that contains either of the following Infrastructure installation types:

• Metadata Repository only

• Identity Management and Metadata Repository

The following sections describe the procedure:

• Before You Begin

• Task 1: Shut Down Middle-Tier Instances

• Task 2: Prepare Your Host

• Task 3: Change the IP Address

• Task 4: Update the Infrastructure

• Task 5: Restart Your Environment

Before You Begin

Review the following items before you start the procedure:

• Write down the old IP address before you begin. You will be prompted for this during the procedure.

• Oracle recommends that you perform a backup of your environment before you start this procedure. Refer to Part V, "Backup and Recovery".

Task 1: Shut Down Middle-Tier Instances

Shut down all middle-tier instances that use the Infrastructure installation, even if they are on other hosts.

Task 2: Prepare Your Host

Prepare your host for the change by stopping all processes:

1. Set the ORACLE_HOME and ORACLE_SID environment variables.

2. Shut down the Infrastructure:

   • On UNIX systems:

     ORACLE_HOME/bin/emctl stop iasconsole
     ORACLE_HOME/opmn/bin/opmnctl stopall
     
     

   • On Windows systems:

     ORACLE_HOME\bin\emctl stop iasconsole
     ORACLE_HOME\opmn\bin\opmnctl stopall
     
     

   Shut down the listener and database:

   lsnrctl stop
   
   sqlplus /nolog
   SQL> connect SYS as SYSDBA
   SQL> shutdown
   SQL> quit
   
   

3. Verify that all Oracle Application Server processes have stopped.

4. To make sure Oracle Application Server processes will not start automatically after a restart of the host, disable any automated startup scripts you may have set up, such as /etc/init.d scripts.

Task 3: Change the IP Address

Update your operating system with the new IP address, restart the host, and verify that the host is functioning properly on your network. Consult your operating system documentation for information on how to perform the following steps:

1. Make the updates to your operating system to properly change the IP address.

2. Restart the host, if required by your operating system.

3. Verify that you can ping the host from another host in your network. Be sure to ping using the new IP address to make sure everything is resolving properly.

Task 4: Update the Infrastructure

Update the Infrastructure on your host with the new IP address:

1. Log in to the host as the user that installed the Infrastructure.

2. Set the ORACLE_HOME and ORACLE_SID environment variables. Do not use a trailing slash (UNIX) or backslash (Windows) when specifying the ORACLE_HOME variable.

3. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you must set depend on the type of your UNIX operating system.

4. Start the database and listener:

   sqlplus /nolog
   SQL> connect SYS as SYSDBA
   SQL> startup
   SQL> quit
   
   lsnrctl start
   
   

5. Start OPMN:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl start
   (Windows) ORACLE_HOME\opmn\bin\opmnctl start
   
   

6. Start Oracle Internet Directory:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID process-type=OID
   (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=OID process-type=OID
   
   

7. Run the following commands in the Infrastructure Oracle home:

   • On UNIX systems:

     cd ORACLE_HOME/chgip/scripts
     ./chgiphost.sh -infra
     
     

   • On Windows systems:

     cd ORACLE_HOME\chgip\scripts
     cmd /c chgiphost.bat -infra
     
     

   The chgiphost command prompts for the old and new IP address.

8. Verify that the tool ran successfully by checking for errors in the files in the following directory:

   (UNIX) ORACLE_HOME/chgip/log
   (Windows) ORACLE_HOME\chgip\log
   

Task 5: Restart Your Environment

Start the remaining components of the Infrastructure and start any middle-tier instances that use it:

1. Start the Infrastructure:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl startall
     ORACLE_HOME/bin/emctl start iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl startall
     ORACLE_HOME\bin\emctl start iasconsole
     
     

2. If a middle-tier instance is on the same host as the Infrastructure, then you need to run the chgiphost command on the middle-tier instance before restarting the middle-tier processes.

3. If you disabled any processes for automatically starting Oracle Application Server at the beginning of this procedure, enable them.

8.2.6 Special Topics for Changing Your Hostname or Domain Name

This section contains the following special topics that apply to changing the hostname or domain name of an Oracle Application Server host:

• Running SSLConfigTool for SSL Environments

• Setting the Log Level for chgiphost

• Customizing the chgiphost Command

• Changing a Hostname after Upgrading from Windows 2000 to Windows 2003

• Recovering from Errors When Changing Your Hostname

OS_path\system32\drivers\etc\hosts

1.2.3.4 myhost.mydomain myhost

8.3.1 Moving from Off-Network to On-Network (Static IP Address)

This procedure assumes you have installed Oracle Application Server on a host that is off the network, using a standard hostname (not localhost), and would like to move on the network and use a static IP address. The IP address may be the default loopback IP, or any standard IP address.

To move onto the network, you can simply plug the host into the network. No updates to Oracle Application Server are required.

8.3.2 Moving from Off-Network to On-Network (DHCP)

This procedure assumes you have installed on a host that is off the network, using a standard hostname (not localhost), and would like to move on the network and use DHCP. The IP address of the host can be any static IP address or loopback IP address, and should be configured to the hostname.

To move onto the network, connect the host to the network using DHCP and configure the hostname to the loopback IP address only.

8.3.3 Moving from On-Network to Off-Network (Static IP Address)

Follow this procedure if your host is on the network, using a static IP address, and you would like to move it off the network:

1. Configure the /etc/hosts file so the IP address and hostname can be resolved locally.

2. Take the host off the network.

3. There is no need to perform any steps to change the hostname or IP address.

8.3.4 Moving from On-Network to Off-Network (DHCP)

Follow this procedure if your host is on the network, using DHCP in loopback mode, and you would like to move it off the network:

1. Configure the /etc/hosts file so the IP address and hostname can be resolved locally.

2. Take the host off the network.

3. There is no need to perform any steps to change the hostname or IP address.

8.4.1 Changing from a Static IP Address to DHCP

To change a host from a static IP address to DHCP:

1. Configure the host to have a hostname associated with the loopback IP address before you convert the host to DHCP.

2. Convert the host to DHCP. There is no need to update Oracle Application Server.

8.4.2 Changing from DHCP to a Static IP Address

To change a host from DHCP to a static IP address:

1. Configure the host to use a static IP address.

2. There is no need to update Oracle Application Server.