Application Server Change Network Configuration

Oracle® Application Server Administrator's Guide
10g Release 2 (10.1.2)

Part No. B13995-01
8 Changing Network Configurations

This chapter provides procedures for changing the network configuration of an
Oracle Application Server host.
It contains the following topics:
• Overview of Procedures for Changing Network Configurations

• Changing Your Hostname, Domain Name, or IP Address
• Moving Between Off-network and On-network
• Changing Between a Static IP Address and DHCP
8.1 Overview of Procedures for Changing Network

Configurations
The following procedures for changing network configurations are presented
in this chapter:
• Changing Your Hostname, Domain Name, or IP Address
This section describes how to update Oracle Application Server when

changing the hostname, domain name, or IP address of a host.
• 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.
8.2 Changing Your Hostname, Domain Name, or IP

Address
After you have installed Oracle Application Server, there may come a time
when you want to change the hostname, domain name, or IP address of the
host. Depending on your installation type, you may perform some or all of
these operations.
Table 8-1 summarizes the installation types that support hostname, domain
name, and IP address changes, and provides pointers to the appropriate
procedures.
Table 8-1 Supported Procedures for Hostname, Domain Name, and IP

Address Changes
Changing the
Hostname or Domain Changing the IP
Installation Type Name Address
Middle-tier Supported Supported
Refer to Section 8.2.1, Simply change the

"Changing the address in your
Hostname or Domain operating system. No
Name of a Middle-tier updates to Oracle
Installation" Application Server are
required
Infrastructure: Identity Not supported Supported
Management and Metadata
Repository Refer to Section 8.2.4,
"Changing the IP
Address of an
Infrastructure
Containing a Metadata
Repository"
Infrastructure: Metadata Not supported Supported
Repository only
Refer to Section 8.2.4,
"Changing the IP
Address of an
Infrastructure
Containing a Metadata
Repository"
Infrastructure: Identity Supported Supported
Management only
Refer to Section 8.2.2, Refer to Section 8.2.2,
Applies to Identity "Changing the "Changing the
Management installations Hostname, Domain Hostname, Domain
with the following Name, or IP Address of Name, or IP Address of
components configured: an Identity an Identity
Management Management
Changing the
Hostname or Domain Changing the IP
Installation Type Name Address
• Oracle Internet Installation" Installation"

Directory only
• OracleAS Single Sign-
On, Oracle Delegated
Administration
Services, and
(optionally) Oracle
Directory Integration
and Provisioning
• Oracle Internet
Directory, OracleAS
Single Sign-On, Oracle
Delegated
Administration
Services, and
(optionally) Oracle
Directory Integration
and Provisioning
OracleAS Certificate Authority Supported Supported
Refer to Section 8.2.3, Simply change the

"Changingthe address in your
Hostname or Domain operating system. No
Name of an OracleAS updates to Oracle
Certificate Authority Application Server are
Installation" required
8.2.1 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 Discoverer
Note:
This procedure is not supported for OracleAS Developer Kits

10g.
The procedure contains the following:
• Things to Know Before You Start

• 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 and OracleAS Wireless
• Task 6: Manually Update the Hostname in Files
Things to Know Before You Start
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 Also:
Section 8.2.5.1, "Setting the Log Level for chgiphost"
• If your old hostname is a string that is likely to appear in a configuration

file, the chgiphost script may encounter problems when trying to update
the configuration files. Refer to Section 8.2.5.2, "Customizing the
chgiphost Script" 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. So 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:
On UNIX systems:
ORACLE_HOME/dcm/bin/dcmctl leavefarm
On Windows systems:
ORACLE_HOME\dcm\bin\dcmctl leavefarm
2. 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:
On UNIX systems:
ORACLE_HOME/dcm/bin/dcmctl leavefarm
On Windows systems:
ORACLE_HOME\dcm\bin\dcmctl leavefarm
You can add the instance back to the farm at the end of the procedure.
3. 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
4. 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
5. 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:
On UNIX systems:
ORACLE_HOME/opmn/bin/opmnctl status
On Windows systems:
ORACLE_HOME\opmn\bin\opmnctl status
To start the DCM daemon:
On UNIX systems:
ORACLE_HOME/opmn/bin/opmnctl startproc ias
component=dcmdaemon
On Windows systems:
ORACLE_HOME\opmn\bin\opmnctl startproc ias
component=dcmdaemon
6. Make sure Oracle Application Server processes will not start

automatically after restarting the host by disabling any automated
startup scripts you may have set up, such as /etc/init.d scripts.
7. Make sure the Oracle Internet Directory that the middle-tier is using is
running.
Task 2: Change the Hostname
Update your operating system with the new hostname, domain name, or both.
Consult your operating system documentation for more 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.
3. On UNIX systems, set the LD_LIBRARY_PATH,
LD_LIBRARY_PATH_64, or SHLIB_PATH environment variables to the
proper values, as shown in Table 1-1. The actual environment variables
and values that you have to 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
chgiphost.bat mid
The chgiphost command prompts for information, as shown in Table

8-2. 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-2 Prompts and Actions for chgiphost -mid
Prompt Action
Enter fully qualified hostname Enter the new fully-qualified
(hostname.domainname) of hostname. This may be a new
Prompt Action
destination hostname, domain name, or both.
Enter valid IP Address of If you changed the IP address of the
destination host, enter the new IP address.
Otherwise, enter the current IP

address.
Enter valid IP Address of If you changed the IP address of the
source host, enter the old IP address.

address.
OIDAdmin Password: Enter the cn=orcladmin password
for the Oracle Internet Directory in
which this middle-tier instance is
registered.
2. 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 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:
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:
a. Obtain the new repository ID for the new farm by running the
following command in the Oracle home of that instance:
On UNIX systems:
ORACLE_HOME/dcm/bin/dcmctl getRepositoryID
On Windows systems:
ORACLE_HOME\dcm\bin\dcmctl getRepositoryID
b. Recreate 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.
On UNIX systems:
ORACLE_HOME/dcm/bin/dcmctl joinfarm r
repository_ID
On Windows systems:
ORACLE_HOME\dcm\bin\dcmctl joinfarm r
repository_ID
c. Add all instances on other hosts back to the new farm using the
command in the preceding step.
2. 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:
On UNIX systems:
ORACLE_HOME/dcm/bin/dcmctl joinfarm r
repository_ID
On Windows systems:
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-base
repository Oracle home:
On UNIX systems:
ORACLE_HOME/dcm/bin/dcmctl getRepositoryID
On Windows systems:
ORACLE_HOME\dcm\bin\dcmctl getRepositoryID
2. 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:
On UNIX systems:
ORACLE_HOME/dcm/bin/dcmctl joinfarm
On Windows systems:
ORACLE_HOME\dcm\bin\dcmctl joinfarm
3. 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
4. If you disabled any processes for automatically starting Oracle

Application Server at the beginning of this procedure, enable them.
Task 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.
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.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
8.2.2 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)
Note:
If your Identity Management installation consists of only

OracleAS Certificate Authority, you can use the procedure
described in Section 8.2.3, "Changingthe Hostname or Domain
Name of an OracleAS Certificate Authority Installation".

• Task 1: Shut Down Middle-Tier Instances
• Task 3: Change the Hostname or IP Address
• Task 4: Start Oracle Internet Directory
• Task 5: Run the chgiphost Command
• Task 6: Update Your Environment
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 Also:
Section 8.2.5.1, "Setting the Log Level for chgiphost"
• If your old hostname is a string that is likely to appear in a configuration

file, the chgiphost script may encounter problems when trying to update
the configuration files. Refer to Section 8.2.5.2, "Customizing the
chgiphost Script" 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.
Recovery".
Task 1: Shut Down Middle-Tier Instances
For each middle-tier instance that uses Identity Management, stop the middle-
tier instance as follows:
1. On the Application Server home page of the Application Server Control
Console, click Stop All.
2. Leave the Application Server Control Console running.
It is important that you leave the Application Server Control Console running
in each of the middle-tier instances while you perform this procedure.
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:
On UNIX systems:
ORACLE_HOME/bin/emctl stop iasconsole
On Windows systems:
ORACLE_HOME\bin\emctl stop iasconsole

automatically after a restart the host by disabling any automated
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 more 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.
sure to ping using the new hostname to make sure everything is
resolving properly.
Task 4: Start Oracle Internet Directory
If the Identity Management installation contains Oracle Internet Directory, start

the directory:
• On UNIX systems:
• ORACLE_HOME/opmn/bin/opmnctl start
• ORACLE_HOME/opmn/bin/opmnctl startproc ias
component=OID
•
• On Windows systems:
• ORACLE_HOME\opmn\bin\opmnctl start
• ORACLE_HOME\opmn\bin\opmnctl startproc ias
component=OID
Task 5: 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 and ORACLE_SID environment variables.
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
chgiphost.bat idm
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 -idm
Prompt Action
Enter fully qualified hostname If you changed the hostname or
(hostname.domainname) of domain name on your system,
destination enter the new fully-qualified
hostname.
Otherwise, enter the current fully-

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

qualified hostname.
Enter valid IP Address of If you changed the IP address of
destination the system, enter the new IP
address.

address
Enter valid IP Address of source If you changed the IP address of
the system, enter the old IP
address.

address
On UNIX systems:
ORACLE_HOME/chgip/log
On Windows systems:
ORACLE_HOME\chgip\log
Task 6: Update Your Environment
This task contains the steps to update your environment for the new
hostname, domain name, or IP address. It is divided into three sections.
Follow the steps in the section that matches your Identity Management
configuration. The sections are::
• Configuration 1: Oracle Internet Directory only

• Configuration 2: OracleAS Single Sign-On, Oracle Delegated
Administration Services, and (optionally) Oracle Directory Integration
and Provisioning
• Configuration 3: Oracle Internet Directory, OracleAS Single Sign-On,
Oracle Delegated Administration Services, and (optionally) Oracle
Directory Integration and Provisioning
Configuration 1: Oracle Internet Directory only
1. 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,
Oracle Directory Integration and Provisioning) and middle-tier
instances (J2EE and Web Cache, Portal and Wireless, and Oracle
Business Intelligence).
In each Oracle home:
a. Edit the following file::

b. (UNIX) ORACLE_HOME/ldap/admin/ldap.ora
c. (Windows) ORACLE_HOME\ldap\admin\ldap.ora
d.
e.Update the DIRECTORY_SERVERS parameter with the new fully-
qualified hostname.
2. In the OracleAS Single Sign-On installation, run the Change Identity
Management Services wizard and supply the new Oracle Internet
Directory information:
a. Using the Application Server Control Console, navigate to the
Application Server home page for OracleAS Single Sign-On.
b. Click the Infrastructure link.
c. On the Infrastructure page, in the Identity Management section,
click Change.
d. Follow the steps in the wizard for supplying the new Identity
Management information (new hostname).
3. In each middle-tier installation (J2EE and Web Cache, Portal and
Wireless, or Oracle Business Intelligence), run the Change Identity
Management Services wizard and supply the new Oracle Internet
Directory information, as described in the preceding step.
Configuration 2: OracleAS Single Sign-On, Oracle Delegated Administration

Services, and (optionally) Oracle Directory Integration and Provisioning
1. Run the following command (ORACLE_HOME is the OracleAS Single

Sign-On Oracle home):
On UNIX systems:
ORACLE_HOME/jdk/bin/java jar
ORACLE_HOME/sso/lib/ossoca.jar reassoc midtier
ORACLE_HOME old_hostname new_hostname
On Windows systems:
ORACLE_HOME\jdk\bin\java jar
ORACLE_HOME\sso\lib\ossoca.jar reassoc midtier
2. Re-register OracleAS Single Sign-On (ORACLE_HOME is the OracleAS

Single Sign-On Oracle home):
On UNIX systems:
ORACLE_HOME/sso/lib/ossoreg.jar
oracle_home_path middle_tier_oracle_home
site_name
middle_tier_hostname:http_port_number
config_mod_osso TRUE
mod_osso_url mod_osso_url
u user
On Windows systems:
ORACLE_HOME\sso\lib\ossoreg.jar
oracle_home_path middle_tier_oracle_home
site_name
middle_tier_hostname:http_port_number
config_mod_osso TRUE
mod_osso_url mod_osso_url
u user
See Also:
Oracle Application Server Single Sign-On Administrator's

Guide for more information on running the preceding command
3. If Oracle Directory Integration and Provisioning is configured, run the

following command:
On UNIX systems:
ORACLE_HOME/bin/odisrvreg h OID_hostname p
OID_port D "cn=orcladmin" w
orcladmin_password
On Windows systems:
ORACLE_HOME\bin\odisrvreg h OID_hostname p
orcladmin_password
4. If you have Oracle Delegated Administration Services configured,

follow these steps to update the Oracle Delegated Administration
Services URL entry in Oracle Internet Directory.
a. Create a file named mod.ldif with the following contents (you can
create the file in any directory):
b. dn:cn=OperationURLs,cn=DAS,cn=Products,cn=Oracl
eContext
c. changetype:modify
d. replace:orcldasurlbase
e. orcldasurlbase:http://hostname:http_port_number
/
f.
Where hostname is the new hostname and

http_port_number is the Oracle HTTP Server port for the
Identity Management installation. Note the slash at the end of
the orcldasurlbase URL.
g. Run the following command:

h. ldapmodify D cn=orcladmin w password p
OID_port f mod.ldif
i.
Management Services wizard:
a. Using the Application Server Control Console, navigate to the
Application Server home page for the middle-tier instance..
b. Click the Infrastructure link.
c. On the Infrastructure page, in the Identity Management section,
click Change.
d. Follow the steps in the wizard for supplying the new Identity
Management information.
Configuration 3: Oracle Internet Directory, OracleAS Single Sign-On, Oracle

Delegated Administration Services, and (optionally) Oracle Directory
Integration and Provisioning
1. Update the ldap.ora file in each middle-tier instance (J2EE and Web
Cache, Portal and Wireless, and Oracle Business Intelligence) that
uses Oracle Internet Directory.
In each Oracle home:
a. Edit the following file::

b. (UNIX) ORACLE_HOME/ldap/admin/ldap.ora
c. (Windows) ORACLE_HOME\ldap\admin\ldap.ora
d.
e.Update the DIRECTORY_SERVERS parameter with the new fully-
qualified hostname.
2. Run the following command (ORACLE_HOME is the Identity
Management Oracle home):
On UNIX systems:
ORACLE_HOME/sso/lib/ossoca.jar reassoc repos
ORACLE_HOME
ORACLE_HOME/sso/lib/ossoca.jar reassoc midtier
On Windows systems:
ORACLE_HOME\sso\lib\ossoca.jar reassoc repos
ORACLE_HOME
ORACLE_HOME\sso\lib\ossoca.jar reassoc midtier
2. If Oracle Directory Integration and Provisioning is configured, run the

following command:
On UNIX systems:
ORACLE_HOME/bin/odisrvreg h OID_hostname p
orcladmin_password
On Windows systems:
ORACLE_HOME\bin\odisrvreg h OID_hostname p
orcladmin_password
3. If you have Oracle Delegated Administration Services configured,

follow these steps to update the Oracle Delegated Administration
Services URL entry in Oracle Internet Directory.
a. Create a file named mod.ldif with the following contents (you can
create the file in any directory):
b. dn:cn=OperationURLs,cn=DAS,cn=Products,cn=Oracl
eContext
c. changetype:modify
d. replace:orcldasurlbase
e. orcldasurlbase:http://hostname:http_port_number
/
f.
Where hostname is the new hostname and

http_port_number is the Oracle HTTP Server port for the
Identity Management installation. Note the slash at the end of
the orcldasurlbase URL.
g. Run the following command:

h. ldapmodify D cn=orcladmin w password p
OID_port f mod.ldif
i.
Management Services wizard:
j. Using the Application Server Control Console, navigate to the

Application Server home page for the middle-tier instance..
k. Click the Infrastructure link.
l. On the Infrastructure page, in the Identity Management section,
click Change.
m. Follow the steps in the wizard for supplying the new Identity
Management information.
Restart the Identity Management installation and restore your configuration

back to the way it was before you started the procedure.
1. Restart the Identity Management instance:
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

3. Start all middle-tier instances that use the Identity Management
installation.
8.2.3 Changing the Hostname or Domain Name of an OracleAS

Certificate Authority Installation
If you have installed OracleAS Certificate Authority by itself on a separate host

(it uses an OracleAS Metadata Repository installed on a different host), and
you want to change the name of the OracleAS Certificate Authority host, then
you have to perform these steps:
1. Stop all Oracle Application Server processes on the host running

OracleAS Certificate Authority.
2. ORACLE_HOME/opmn/bin/opmnctl stopall
3.
4. Change the name of the host where OracleAS Certificate Authority is
running.
5. Replace the old hostname with the new hostname in the following files.
ORACLE_HOME refers to the directory where you installed OracleAS
Certificate Authority.
6. ORACLE_HOME/oca/bin/ocactl.pl
7. ORACLE_HOME/oca/bin/cmdeinst.pl
8. ORACLE_HOME/Apache/Apache/conf/ocm_apache.conf
9. ORACLE_HOME/Apache/Apache/conf/httpd.conf
10. ORACLE_HOME/Apache/Apache/conf/ssl.conf
11. ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf
12. ORACLE_HOME/opmn/conf/opmn.xml
13. ORACLE_HOME/opmn/conf/ons.conf
14.
15. Regenerate the SSL wallet.
16. ORACLE_HOME/oca/bin/ocactl generatewallet type
CASSL
17.
18. Reregister with OracleAS Single Sign-On.
19. ORACLE_HOME/oca/bin/ocactl changesecurity
server_auth_port realOcaSslPort
20.
realOcaSslPort is the OracleAS Certificate Authority server

authentication port. The default port for this is 4400.
21. Start OPMN and all the OPMN-managed processes.

22. ORACLE_HOME/opmn/bin/opmnctl startall
23.
24. Start OracleAS Certificate Authority.
25. ORACLE_HOME/oca/bin/ocactl start
8.2.4 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

• Task 1: Shut Down Middle-Tier Instances
• Task 3: Change the IP Address
• Task 4: Update the Infrastructure
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.
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.
Prepare your host for the change by stopping all processes.

2. Shut down the Infrastructure:
3. emctl stop iasconsole
4. opmnctl stopall
5. lsnrctl stop
6.
7. sqlplus /nolog
8. SQL> connect SYS as SYSDBA
9. SQL> shutdown
10.SQL> quit
11.
12. Verify that all Oracle Application Server processes have stopped.
automatically after a restarting the host by disabling any automated
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 more information on how to do this.
1. Make the updates to your operating system to properly change the IP

address.
2. Restart the host, if required by your operating system.
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.

operating system.
4. Start the database:
5. sqlplus /nolog
6. SQL> connect SYS as SYSDBA
7. SQL> startup
8. SQL> quit
9.
10.lsnrctl start
11. Start OPMN:
12.opmnctl start
13.
14. Start Oracle Internet Directory:
15.opmnctl startproc iascomponent=OID processtype=OID
16.
17. Run the following commands in the Infrastructure Oracle home:
18.(UNIX)
19. cd ORACLE_HOME/chgip/scripts
20../chgiphost.sh infra
21.
22.(Windows)
23. cd ORACLE_HOME\chgip\scripts
24.chgiphost.bat infra
25.
The chgiphost command prompts for the old and new IP address.
27. ORACLE_HOME/chgip/log
Finish starting the Infrastructure and start any middle-tier instances that use it.
1. Finish starting the Infrastructure:

2. opmnctl startall
3. emctl start iasconsole
4.
5. If a middle-tier instance is on the same host as the infrastructure, then
you need to run the chgiphost script on the middle-tier instance
before restarting the middle-tier processes.
8.2.5 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:
• Setting the Log Level for chgiphost

• Customizing the chgiphost Script
• Changing your Hostname after Upgrading from Windows 2000 to
Windows 2003
• Recovering from Errors When Changing Your Hostname
8.2.5.1 Setting the Log Level for chgiphost
By default, the console log level for the chgiphost command is SEVERE.
This causes only critical information to be printed while running chgiphost. If
you would like to view additional progress information, set the console log
level to CONFIG as follows:
1. Edit the following file:

2. (UNIX) ORACLE_HOME/chgip/config/chgip.log.properties
3. (Windows)
ORACLE_HOME\chgip\config\chgip.log.properties
4.
5. Change the java.util.logging.ConsoleHandler.level
parameter to CONFIG:
6. java.util.logging.ConsoleHandler.level = CONFIG
8.2.5.2 Customizing the chgiphost Script
By default, the chgiphost script updates key configuration files in the Oracle
home with the new hostname. If either of the following cases apply to your
installation, you may want to consider customizing the behavior of the
chgiphost script:
• You have created additional configuration files that contain the

hostname and would like the chgiphost script to update those files.
In order to update these files, add their full path name to the following
file before running chgiphost:
o On UNIX systems:
o ORACLE_HOME/chgip/config/hostname.lst
o
o On Windows systems:
o ORACLE_HOME\chgip\config\hostname.lst
o
• Your old hostname is very short (one or two letters) or is a string that is
likely to appear in a configuration file
Before running chgiphost, examine each of the files listed in

hostname.lst to determine if the old hostname exists in any settings
in those files. If you find a match, you can correct those settings after
you run chgiphost.
• Your Oracle home contains the hostname in its full path.
In this case, the chgiphost script may not update your configuration
files properly. You can avoid this problem by using a Java utility called
FileFixer, which searches for specific text strings in a file by matching
regular expressions, and updates them to their new values. Note that
FileFixer searches for patterns one line at a time. It cannot match
patterns across lines.
To use FileFixer:
1.Make a copy of the following file:
o On UNIX systems:
o ORACLE_HOME/chgip/config/hostname_short_sa
mple.lst.xml
o
o On Windows systems:
o ORACLE_HOME\chgip\config\hostname_short_sa
mple.lst.xml
o
2.Edit your copy of the file to specify the regular expression
matching required for your old and new hostnames. The file
contains an example of how to do this.
3.Specify the file when running the chgiphost script:
4.chgiphost option hostnameShortXml
full_path_to_your_xml_file
5.
For example, if you named your file

/mydir/my_sample.lst.xml, and you are updating a
middle-tier installation, run chgiphost as follows:
chgiphost mid hostnameShortXml
/mydir/my_sample.lst.xml
8.2.5.3 Changing your 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.mydomain before

the upgrade, and your IP address is 1.2.3.4, add the following line:
1.2.3.4 myhost.mydomain myhost
8.2.5.4 Recovering from Errors When Changing Your Hostname
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

For example, you will get an error message if you enter the wrong password
for Oracle Internet Directory. 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.
If you encounter an error when running chgiphost.sh, you should fix the
error and run chgiphost.sh again.
8.3 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 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 Installation Guide for more
information.
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 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 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.
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.

Application Server Change Network Configuration

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Application Server Change Network Configuration

Enviado por

Direitos autorais:

Formatos disponíveis

Oracle® Application Server Administrator's Guide

10g Release 2 (10.1.2)

8 Changing Network Configurations

It contains the following topics:

• Overview of Procedures for Changing Network Configurations

8.1 Overview of Procedures for Changing Network

• Changing Your Hostname, Domain Name, or IP Address

This section describes how to update Oracle Application Server when

• Moving Between Off-network and On-network

This section provides procedures for moving an Oracle Application

• Changing Between a Static IP Address and DHCP

This section provides procedures for changing from a static IP address

8.2 Changing Your Hostname, Domain Name, or IP

Table 8-1 Supported Procedures for Hostname, Domain Name, and IP

Refer to Section 8.2.1, Simply change the

• Oracle Internet Installation" Installation"

Refer to Section 8.2.3, Simply change the

8.2.1 Changing the Hostname or Domain Name of a Middle-tier

• J2EE and Web Cache

This procedure is not supported for OracleAS Developer Kits

The procedure contains the following:

• Things to Know Before You Start

Things to Know Before You Start

Review the following items before you start:

• If any installations contain Oracle Content Management Software

Section 8.2.5.1, "Setting the Log Level for chgiphost"

• If your old hostname is a string that is likely to appear in a configuration

Task 1: Prepare Your Host

Oracle Application Server High Availability Guide for

2. If the host contains an instance that stores the file-based repository

To remove an instance from an OracleAS File-based Farm, run the

3. If the host contains a middle-tier instance that is part of an OracleAS

Oracle Application Server Web Cache Administrator's Guide

4. Shut down each middle-tier instance on the host by running the

5. If the middle-tier instance was part of an OracleAS File-based Farm,

To verify if the DCM daemon is running, run the following command in

To start the DCM daemon:

6. Make sure Oracle Application Server processes will not start

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

Task 3: Run the chgiphost Command

The chgiphost command prompts for information, as shown in Table

Table 8-2 Prompts and Actions for chgiphost -mid

Otherwise, enter the current IP

Otherwise, enter the current IP

Task 4: Restart Your Environment

1. Start each middle-tier instance on your host by running the following

2. If you removed any instances from an OracleAS Web Cache cluster at

Oracle Application Server Web Cache Administrator's Guide

3. If the host contained an instance that stored the file-based repository

b. Recreate the OracleAS File-based Farm by adding that instance

In the preceding command, repository_ID is the hostname:port

3. If you removed any instances from an OracleAS Cluster at the

Oracle Application Server High Availability Guide for

4. If you disabled any processes for automatically starting Oracle

Task 5: Update OracleAS Portal and OracleAS Wireless

Task 6: Manually Update the Hostname in Files

If you edited a file and entered the hostname as part of a user-defined

8.2.2 Changing the Hostname, Domain Name, or IP Address of an

This section describes how to change the hostname, domain name, or IP

• Identity Management with only Oracle Internet Directory configured

If your Identity Management installation consists of only

The procedure contains the following:

• Things to Know Before You Start