9 Changing Network Configurations

9.1 Which Networking Features are Supported on Your Platform?

Oracle Application Server supports a variety of options for configuring and changing networking features. Depending on your operating system platform, you can install Oracle Application Server on:

• A host with a static IP address and hostname (all platforms support this option)

• A host that uses DHCP

• A host that is off the network

  
  

  See Also: Oracle Application Server 10g Installation Guide for your platform for more information

  
  

After installation, you may want to change the networking configuration. This chapter provides procedures for changing the networking configuration of an Oracle Application Server host.

9.2 Overview of Procedures for Changing Network Configurations

• Changing the Hostname and IP Address (Middle Tier)

  Follow this procedure if your host uses a static IP address and hostname, and you would like to change to a different static IP address, hostname, or both. This procedure is for hosts that contain one or more middle-tier instances.

  Some examples of when to use this procedure are:

  • Your organization moved to a new geographic location and you must move to a new subnet

  • You must change the hostname on your system

• Changing the IP Address (Infrastructure)

  Follow this procedure if your host uses a static IP address and hostname, an you would like to change to a different static IP address. The hostname must remain the same. This procedure is for hosts that contain an Infrastructure. You can use this procedure if your host moves to a new subnet.

• Moving Between Off-network and On-network

  This section provides procedures for moving an Oracle Application Server host on and off the network. You may use DHCP or a static IP address when on the network. You can use these procedures, for example, if you installed Oracle Application Server on your laptop and would like to plug in to different networks to use it.

• Changing Between a Static IP Address and DHCP

  This section provides procedures for changing from a static IP address to DHCP, and from DHCP to a static IP address. You might use these if you install on a static IP address but then decide you would like to use DHCP so you can be more mobile, or if you are using DHCP and must plug in to a network using a static IP address.

9.3 Changing the Hostname and IP Address (Middle Tier)

This section describes how to change the hostname and IP address of a host that contains one or more Oracle Application Server middle-tier installations. You can use this procedure to change:

• The hostname only

• The IP address only

• Both the hostname and IP address

You can use this procedure on J2EE and Web Cache, Portal and Wireless, and Business Intelligence and Forms installations. You can also use it on a Forms:Reports standalone installation. This procedure is not supported for OracleAS Developer Kits 10g installations.

The procedure includes:

• Changing the hostname and IP address on your operating system

  The details on how to do this are not provided, since this varies according to your operating system type and configuration. Consult your operating system documentation to determine how to do this before beginning the procedure.

• Updating Oracle Application Server for the new hostname and IP address

  The details on how to do this are provided in the procedure. For tips on recovering from errors, see Section 9.7, "Recovering from Errors when Using chgiphost.sh".

Step 1: Prepare Your Host

In this step, you prepare your host for the change by removing instances from 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 cluster. You can add the instance back into the cluster at the end of the procedure.

   
   

   See Also: Oracle Application Server 10g High Availability Guide for instructions on removing instances from a cluster

   
   

2. 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 cluster

   
   

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

   emctl stop iasconsole
   opmnctl stopall
   
   

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

5. Make sure Oracle Application Server processes will not start automatically after a reboot by disabling any automated startup scripts you may have set up, such as /etc/init.d scripts.

6. Make sure the Oracle Internet Directory that the middle-tier is using is running.

Step 2: Change the Hostname and IP Address on Your Operating System

In this step, you update your operating system with the new hostname, IP address, or both, reboot, and verify that the host is functioning properly on your network. Consult your operating system documentation, system administrator, and network administrator for more information on how to do this.

1. Make the updates to your operating system to properly change the hostname, IP address, or both.

2. Reboot the host.

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.

Step 3: Update the Middle-Tier Instances on Your Host

In this step, you update the Oracle Application Server middle-tier instances on your host with the new hostname and IP address. 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.

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

   (UNIX)
   cd ORACLE_HOME/chgip/scripts
   ./chgiphost.sh -mid
   
   (Windows)
   cd ORACLE_HOME\chgip\scripts
   chgiphost.bat -mid
   
   

   The chgiphost.sh command prompts for information, as shown in Table 9-1. You may not receive all of the prompts, depending on your middle-tier installation type.

   Note that the prompts may provide values in parenthesis. These are not default values—they are just reminders. You must enter a value for each prompt.

Enter the fully qualified host name (hostname.domainname) of the new system

Enter the IP Address of the new system

Enter the fully qualified host name (hostname.domainname) of the old system

Enter the IP Address of the old system

Enter the password for the Mid Tier IAS instance (ias_admin)

Confirm the password for the Mid Tier IAS instance (ias_admin)

Enter the password for the OID Administrator

Confirm the password for the OID Administrator

Enter the password for the SYS user, of the infra database

ORACLE_HOME/config/ias.properties

Confirm the password for the SYS user, of the infra database

Enter the password for the dsGateway user, of the infra database

Confirm the password for the dsGateway user, of the infra database

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

   ORACLE_HOME/chgip/log
   

Step 4: Restart Oracle Application Server

In this step, you restart the middle-tier instances and restore your configuration back 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:

   opmnctl startall
   emctl start iasconsole
   
   

2. 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 10g High Availability Guide for instructions on adding instances to a cluster

   
   

3. 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

   
   

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

Step 5: Update OracleAS Portal and OracleAS Wireless

This is a special step required for updating OracleAS Portal and OracleAS Wireless when you change the hostname.

When you change the hostname, the OracleAS Wireless server URL changes to use the new hostname. You must update OracleAS Portal with the new OracleAS Wireless service URL.

Refer to the section on "Updating the OracleAS Wireless Portal Service URL Reference" in Oracle Application Server Portal Configuration Guide for instructions.

Step 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.sh script. To update the hostname in such cases, you need to edit the files manually. For example, the plsql.conf file may contain an NFS path including the hostname, such as: /net/dsun1/private/....

The chgiphost.sh script also does not edit the hostname references in the documentation files. You will need to 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

ldapsearch -h oid_host -p oid_port -D cn=orcladmin -w orcladmin_password -b "orclresourcename=dsgateway, orclreferencename=metadata_repository, cn=ias infrastructure databases, cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=*" orclpasswordattribute

ldapsearch -h myhost -p 3060 -D cn=orcladmin -w welcome1 -b "orclresourcename=dsgateway, orclreferencename=asdb.myhost.mydomain.com cn=ias infrastructure databases, cn=ias, cn=products, cn=oraclecontext" -s base
"objectclass=*" orclpasswordattribute

orclpasswordattribute=B7149q3s

9.4 Changing the IP Address (Infrastructure)

This section describes how to change the IP address of a host that contains an Oracle Application Server Infrastructure.

The procedure includes:

• Changing the IP address on your operating system

  The details on how to do this are not provided since this varies according to your operating system type and configuration. Consult your operating system documentation to determine how to do this before beginning the procedure.

• Updating Oracle Application Server for the new IP address

  The details on how to do this are provided in the procedure. For tips on recovering from errors, see Section 9.7, "Recovering from Errors when Using chgiphost.sh".

Step 1: Prepare Your Host

In this step, you prepare your host for the change by stopping all processes.

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

2. Set the ORACLE_HOME and ORACLE_SID environment variables.

3. Shut down the Infrastructure:

   emctl stop iasconsole
   opmnctl stopall
   lsnrctl stop
   
   sqlplus /nolog
   SQL> connect SYS as SYSDBA
   SQL> shutdown
   SQL> quit
   
   

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

5. Make sure Oracle Application Server processes will not start automatically after a reboot by disabling any automated startup scripts you may have set up, such as /etc/init.d scripts.

Step 2: Change the IP Address on Your Operating System

In this step, you update your operating system with the new IP address, reboot, and verify that the host is functioning properly on your network. Consult your operating system documentation, system administrator, and network administrator for more information on how to do this.

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

2. Reboot the host.

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.

Step 3: Update the Infrastructure

In this step, you 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.

3. Start the database:

   sqlplus /nolog
   SQL> connect / as SYSDBA
   SQL> startup
   SQL> quit
   
   

4. Start OPMN:

   opmnctl start
   
   

5. Start Oracle Internet Directory:

   opmnctl startproc ias-component=OID process-type=OID
   
   

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

   (UNIX)
   cd ORACLE_HOME/chgip/scripts
   ./chgiphost.sh -infra
   
   (Windows)
   cd ORACLE_HOME\chgip\scripts
   chgiphost.bat -mid
   
   

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

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

   ORACLE_HOME/bin/chgip/log
   

Step 4: Restart the Infrastructure

In this step, you restart the Infrastructure and any middle-tier instances that use it.

1. Set the ORACLE_HOME and ORACLE_SID environment variables.

2. Start the Infrastructure:

   sqlplus /nolog
   SQL> connect SYS as SYSDBA
   SQL> startup
   SQL> quit
   
   lsnrctl start
   opmnctl startall
   emctl start iasconsole
   
   

3. If a middle-tier instance is on the same host as the infrastructure, then you need to run the chgiphost.sh script on the middle-tier instance before restarting the middle-tier processes.

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

9.5 Moving Between Off-network and On-network

This section describes how to move an Oracle Application Server host on and off the network. The following assumptions and restrictions apply:

• The host must contain an Infrastructure and middle-tier instance, or a J2EE and Web Cache instance that does not use an Infrastructure, that is, the entire Oracle Application Server environment must be on the host.

• DHCP must be used in loopback mode. Refer to Oracle Application Server 10g Installation Guide for more information.

• Only IP address change is supported; the hostname must remain unchanged.

• Hosts in DHCP mode should not use the default hostname (localhost.localdomain). The hosts should be configured to use a standard hostname and the loopback IP should resolve to that hostname.

• A loopback adapter is required for all off-network installations (DHCP or static IP). Refer to Oracle Application Server 10g Installation Guide for more information.

9.6 Changing Between a Static IP Address and DHCP

This section describes how to change between a static IP address and DHCP. The following assumptions and restrictions apply:

• The host must contain an Infrastructure and middle-tier instance, or a J2EE and Web Cache instance that does not use an Infrastructure, that is, the entire Oracle Application Server environment must be on the host.

• DHCP must be used in loopback mode. Refer to Oracle Application Server 10g Installation Guide for more information.

• Only IP address change is supported; the hostname must remain unchanged.

• Hosts in DHCP mode should not use the default hostname (localhost.localdomain). The hosts should be configured to use a standard hostname and the loopback IP should resolve to that hostname.

9.7 Recovering from Errors when Using chgiphost.sh

This section describes how to recover from typical errors you might encounter when using the chgiphost.sh script. It contains the following scenarios:

• Scenario 1: You Specified the Wrong Destination Name

• Scenario 2: You Encountered an Error when Running chgiphost.sh

Scenario 1: You Specified the Wrong Destination Name

Suppose you ran the chgiphost.sh script but specified the wrong destination name. In this case, you can remedy the error by running chgiphost.sh again. Here are the details.

Suppose the current source hostname is loire985, the incorrect destination hostname you specified is mqa985, and the correct destination hostname is sqb985. Initially, you ran chgiphost.sh with source = loire985 and destination = mqa985.

To recover from this error:

1. Run chgiphost.sh with source = mqa985 and destination = sqb985.

2. Run chgiphost.sh again with source = loire985 and destination = sqb985.

Scenario 2: You Encountered an Error when Running chgiphost.sh

If you encounter an error when running chgiphost.sh, you should fix the error and run chgiphost.sh again.

For example, you will get an error message if you enter the wrong password for Oracle Internet Directory or OracleAS Syndication Services. In this case, you should run chgiphost.sh again, with the same source and destination hostnames as before, and make sure to supply the correct password when prompted.

9.8 Changing the Hostname After Upgrading from Windows 2000 to Windows 2003

When you upgrade from Windows 2000 to Windows 2003, lower-case letters in your hostname may be changed to upper-case letters. For example, if your hostname is "myhost" before the upgrade, it may be changed to "MYHOST". If this occurs, some Oracle Application Server processes may not function properly.

To resolve this problem, you do not need to run the chgiphost command to update Oracle Application Server. You can simply add an entry with the lower-case hostname to the hosts file:

OS_path\system32\drivers\etc\hosts

For example, if your fully-qualified hostname was myhost.mydoman before the upgrade, and your IP address is 1.2.3.4, add the following line:

1.2.3.4 myhost.mydomain myhost