15 Changing Oracle Fusion Middleware Network Configurations
- About Changing the Network Configuration
You can change the host name and IP address of an Oracle Fusion Middleware domain and the database that is used by Oracle Fusion Middleware. - Moving Between On-Network and Off-Network
You can move an Oracle Fusion Middleware host on and off the network. - Changing Between a Static IP Address and DHCP
You can change between a static IP address and DHCP. - Using IPv6
Oracle Fusion Middleware supports Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6.)
Parent topic: Advanced Administration
About Changing the Network Configuration
You can change the host name and IP address of an Oracle Fusion Middleware domain and the database that is used by Oracle Fusion Middleware.
- Overview of Changing the Network Configuration
- About the chghost Utility
With the chghost utility, you can change the host name, network domain name, or IP address of a machine that contains Oracle Fusion Middleware installations or the database that contains the Oracle Fusion Middleware schemas. - Changing the Host Name of Oracle Fusion Middleware
You can change the host name of the host containing Oracle Fusion Middleware. - Moving Oracle Fusion Middleware to a New Host
- Moving a Multinode Oracle Fusion Middleware to New Hosts
If you have Oracle Fusion Middleware installed on more than one host, you can move it to new hosts. - Changing the Host Name or IP Address of a Database
You can change the host name or IP address of the host that contains the database that holds Oracle Fusion Middleware schema. - Moving an Oracle Fusion Middleware Database to a New Host
You can move the database that holds Oracle Fusion Middleware schema to a new host. - Moving a Multinode Oracle Fusion Middleware and Its Database to New Hosts
If you have Oracle Fusion Middleware and its database installed on more than one host, you can move it to new hosts. - Additional Tasks for Changing the Network Configuration
Some components require additional steps after you have run the chghost utility to change the network configuration.
Parent topic: Changing Oracle Fusion Middleware Network Configurations
Overview of Changing the Network Configuration
Using a combination of binary cloning, the chghost utility, and copying files from one host to another, Oracle Fusion Middleware supports the following changes:
-
Changing the host name or IP address of the Administration Server or one or more of the Managed Servers. See Changing the Host Name of Oracle Fusion Middleware.
-
Moving Oracle Fusion Middleware to a different host. See Moving Oracle Fusion Middleware to a New Host or Moving a Multinode Oracle Fusion Middleware to New Hosts.
-
Changing the host name or IP address of the host that contains the database that contains the Oracle Fusion Middleware schemas. See Changing the Host Name or IP Address of a Database.
-
Moving the database that contains the Oracle Fusion Middleware schemas to a different host. See Moving an Oracle Fusion Middleware Database to a New Host.
-
Moving Oracle Fusion Middleware and its database to a different host. See Moving a Multinode Oracle Fusion Middleware and Its Database to New Hosts.
Note the following:
-
You cannot change the topology. For example, you cannot add or remove a Managed Server and you cannot change the WebLogic Server domain name. You cannot change the port number.
-
The paths of both the source and target instances must be the same. You cannot change them.
-
You cannot move Oracle Fusion Middleware from one type of operating system to another. You can only move it to the same type of operating system.
-
If you are moving the database from one host to another, the database type cannot be changed. For example, you cannot change the database type from an Oracle Database to a SQL Server database.
-
In a multinode environment, you can move or change the network configuration of each node separately. For example, if the Administration Server is on Host A and the Managed Servers are on Host B, you can move or change the network configuration of the Administration Servers, the Managed Servers, or both.
-
The chghost utility does not move binary data or data in a database.
-
The chghost utility does not support environments where SSL only is configured. SSL-only means that either the administration port is enabled or only the SSL port is enabled.
The following components do not support the chghost script:
-
Oracle WebCenter Sites
-
Oracle BI EE
-
Oracle Data Integrator
- Oracle Access Manager
-
Oracle Internet Directory
-
Oracle Forms Services: See Additional Tasks for Changing the Network Configuration of Oracle Forms Services.
Parent topic: About Changing the Network Configuration
About the chghost Utility
With the chghost utility, you can change the host name, network domain name, or IP address of a machine that contains Oracle Fusion Middleware installations or the database that contains the Oracle Fusion Middleware schemas.
The chghost utility changes any references to the host name, network domain name, or IP address within Oracle Fusion Middleware, using the information you provide in the command line or an input file.
The location of the chghost command is:
(UNIX) ORACLE_HOME/oracle_common/bin/chghost.sh (Windows) ORACLE_HOME\oracle_common\bin\chghost.bat
If you are changing the host name, network domain name, or IP address of the Administration Server, the format of the command is:
./chghost.sh -chgHostInputFile ini_file -javaHome location_of_javahome -domainLoc target_domain_path -domainAdminUserName username -walletDir location_of_wallet_dir [-logPriority log_level] [-logDir location_of_log_file] [-ignoreValidationErrors option[, option]]
In a multinode environment, if you are changing the host name, network domain name, or IP address of a Managed Server, the format of the command is:
./chghost.sh -chgHostInputFile ini_file -javaHome location_of_javahome -domainLoc target_domain_path -domainAdminUserName username -walletDir location_of_wallet_dir [-logPriority log_level] [-logDir location_of_log_file] [-ignoreValidationErrors option[, option]] -adminURL URL_of_admin_server -managed
Table 15-1 describes the options for the chghost command.
Table 15-1 Options for the chghost Command
| Option | Description |
|---|---|
|
-javaHome |
The Java home. The utility invokes the Java instance using the following precedence:
|
|
-chgHostInputFile |
The absolute path, including the file name, to the input file which contains information about the server host mapping and the database host mapping. It can also contain the command line options, except for chgHostInput file. |
|
-domainLoc |
The absolute path to the domain for which you want to change the network configuration. |
|
-domainAdminUserName |
The administration user. |
|
-walletDir |
The absolute path to a directory where the chghost utility will create a file containing the administrative user password. |
|
-logPriority |
Optional. The level of the information written to the log files. Valid values are (from highest to lowest value): SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST. |
|
-logDir |
Optional. The absolute path to the directory in which the chghost utility writes log information. |
|
-ignoreValidationErrors |
Optional. The following comma-separated values are allowed :
Note : If
|
|
-adminURL |
The URL of the administration server. Use this only when you are changing the host name of a host that contains Managed Servers, not the Administration Server. |
|
-managed |
The URL of the administration server. Use this only when you are changing the host name of a host that contains Managed Servers, not the Administration Server. |
You must create an input file to be passed to the chgHostInput parameter. The input file has the following format:
# Headers are within the brackets[]. Don't change the header name.
[ARGUMENTS]
-domainLoc domain_location
-domainAdminUserName admin_username
-walletDir wallet_location
-logPriority log_priority
-logDir log_directory
-ignoreValidationErrors option[, option]
# The following two arguments are used only when changing
# the host name of a host that contains Managed Servers,
# not the Administration Server.
-adminURL URL_of_admin_server
-managed
[SERVER_HOST_MAPPING]
#pattern source_host_name=target_host_name
source_admin_server_host.example.com=target_admin_server_host.example.com
source_admin_server_IPAddress=target_admin_server_IPAddress
source_managed_server_host.example.com=target_managed_server_host.example.com
[DATABASE_MAPPING]
# You can only change the database host name.
db1_host.example.com=db2_host.example.com
[LDAP_MAPPING]
# You can only change the LDAP host name.
ldap1_host.example.com=ldap2_host.example.com
Note the following:
-
Do not change the Header names (the names within the brackets, such as [DATABASE_MAPPING] ).
-
For both the SERVER_HOST_MAPPING and the DATABASE_MAPPING, if you specify the full canonical name for the source system, you must specify the full canonical name for the target system. If you specify the short name for the source system, you must specify the short name for the target system. For example, the following mappings are not valid:
host_a.example.com=host_a1.com host_a.com=host_a1.example.com -
The Administration Server and all Managed Servers must be stopped when you run the chghost script.
-
If a different database is used for the source and target, the database port number and SID must be same on the target as on the source.
-
If the chghost utility failed during execution because of a port validation error (that is, more than one server has the same port), set the following properties, then run the chghost utility again:
-Dchghost.ignore.validation.port=true -chghost.temporary.port.range=lowerPort-higherport
During execution of the chghost utility, it assigns a temporary port. Then, at the end of the execution, it will restore the original port.
For example:Linux:
CHGHOST_JAVA_OPTIONS="$CHGHOST_JAVA_OPTIONS -Dchghost.ignore.validation.port=true -Dchghost.temporary.port.range=443-10000" export CHGHOST_JAVA_OPTIONSWindows:
set CHGHOST_JAVA_OPTIONS]=%CHGHOST_JAVA_OPTIONS% -Dchghost.ignore.validation.port=true -Dchghost.temporary.port.range=443-10000
Parent topic: About Changing the Network Configuration
Changing the Host Name of Oracle Fusion Middleware
You can change the host name of the host containing Oracle Fusion Middleware.
Parent topic: About Changing the Network Configuration
Moving Oracle Fusion Middleware to a New Host
In this scenario, you want to move Oracle Fusion Middleware to a new host. It is currently on Host_A and you want to move it to Host_A1.
You use the copyBinary and pasteBinary commands to move the binary files and you use the chghost command to change the host name or IP address of Oracle Fusion Middleware.
Parent topic: About Changing the Network Configuration
Moving a Multinode Oracle Fusion Middleware to New Hosts
If you have Oracle Fusion Middleware installed on more than one host, you can move it to new hosts.
In this scenario, you have Oracle Fusion Middleware installed on more than one host and you want to move to new hosts. The Administration Server is in Host_A and the Managed Servers are on Host_B You want to move the Admnistration Server to Host_A1 and the Managed Servers to Host_B1.
You use the copyBinary and pasteBinary commands to move the binary files and you use the chghost command to change the host name or IP address of Oracle Fusion Middleware.
Parent topic: About Changing the Network Configuration
Changing the Host Name or IP Address of a Database
You can change the host name or IP address of the host that contains the database that holds Oracle Fusion Middleware schema.
To change the host name for the database from Host_C to Host_C1:
Parent topic: About Changing the Network Configuration
Moving an Oracle Fusion Middleware Database to a New Host
You can move the database that holds Oracle Fusion Middleware schema to a new host.
Parent topic: About Changing the Network Configuration
Moving a Multinode Oracle Fusion Middleware and Its Database to New Hosts
If you have Oracle Fusion Middleware and its database installed on more than one host, you can move it to new hosts.
In this scenario, you have Oracle Fusion Middleware installed on more than one host and you want to move to new hosts. The Administration Server is in Host_A and the Managed Servers are on Host_B You want to move the Admnistration Server to Host_A1 and the Managed Servers to Host_B1. In addition, you have the database installed on Host_C and you want to move it to Host_C1.
You use the copyBinary and pasteBinary commands to move the binary files and you use the chghost command to change the host name or IP address of Oracle Fusion Middleware.
Parent topic: About Changing the Network Configuration
Additional Tasks for Changing the Network Configuration
Some components require additional steps after you have run the chghost utility to change the network configuration.
- Additional Tasks for Changing the Network Configuration of Oracle Forms Services
After you run the chghost utility, you need to take additional steps to update the host and port information for Forms Application Deployment Services.
Parent topic: About Changing the Network Configuration
Additional Tasks for Changing the Network Configuration of Oracle Forms Services
After you run the chghost utility, you need to take additional steps to update the host and port information for Forms Application Deployment Services.
ORACLE_HOME/forms/fads/fads_config.pyThe script takes the following mandatory arguments:
-
The Administration Server host name
-
The Administration Server port
-
The applications directory
For example:
wlst.sh ORACLE_HOME/forms/fads/fads_config.py updateHostPort myserverhost myserverport Oracle_Home/applications/forms_domain
Parent topic: Additional Tasks for Changing the Network Configuration
Moving Between On-Network and Off-Network
You can move an Oracle Fusion Middleware host on and off the network.
The following assumptions and restrictions apply:
-
The host must contain an instance that does not use an Infrastructure, or both the middle-tier instance and Infrastructure must be on the same host.
-
DHCP must be used in loopback mode. Refer to the Oracle Fusion Middleware System Requirements and Specifications.
-
Only IP address change is supported; the host name must remain unchanged.
-
Hosts in DHCP mode should not use the default host name (
localhost.localdomain). The hosts should be configured to use a standard host name and the loopback IP should resolve to that host name. -
A loopback adapter is required for all off-network installations (DHCP or static IP).
This section contains the following topics:
- Moving from Off-Network to On-Network (Static IP Address)
- Moving from Off-Network to On-Network (DHCP)
- Moving from On-Network to Off-Network (Static IP Address)
Parent topic: Changing Oracle Fusion Middleware Network Configurations
Moving from Off-Network to On-Network (Static IP Address)
This procedure assumes you have installed Oracle Fusion Middleware on a host that is off the network, using a standard host name (not localhost), and would like to move on to the network and use a static IP address. The IP address may be the default loopback IP, or any standard IP address.
To move on to the network, you can simply connect the host to the network. No updates to Oracle Fusion Middleware are required.
Parent topic: Moving Between On-Network and Off-Network
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 host name (not localhost), and would like to move on to 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 host name.
To move on to the network:
- Connect the host to the network using DHCP.
- Configure the host name to the loopback IP address only.
Parent topic: Moving Between On-Network and Off-Network
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:
Parent topic: Moving Between On-Network and Off-Network
Changing Between a Static IP Address and DHCP
You can change between a static IP address and DHCP.
The following assumptions and restrictions apply:
-
The host must contain all Oracle Fusion Middleware components, including Identity Management components, and any database associated with those components. That is, the entire Oracle Fusion Middleware environment must be on the host.
-
DHCP must be used in loopback mode. Refer to the Oracle Fusion Middleware System Requirements and Specifications.
-
Only IP address change is supported; the host name must remain unchanged.
-
Hosts in DHCP mode should not use the default host name (
localhost.localdomain). The hosts should be configured to use a standard host name and the loopback IP should resolve to that host name.
Parent topic: Changing Oracle Fusion Middleware Network Configurations
Changing from a Static IP Address to DHCP
To change a host from a static IP address to DHCP:
- Configure the host to have a host name associated with the loopback IP address before you convert the host to DHCP.
- Convert the host to DHCP. There is no need to update Oracle Fusion Middleware.
Parent topic: Changing Between a Static IP Address and DHCP
Changing from DHCP to a Static IP Address
To change a host from DHCP to a static IP address:
- Configure the host to use a static IP address.
- There is no need to update Oracle Fusion Middleware.
Parent topic: Changing Between a Static IP Address and DHCP
Using IPv6
Oracle Fusion Middleware supports Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6.)
Among other features, IPv6 supports a larger address space (128 bits) than IPv4 (32 bits), providing an exponential increase in the number of computers that can be addressable on the Web.
An IPv6 address is expressed as 8 groups of 4 hexadecimal digits. For example:
2001:0db8:85a3:08d3:1319:8a2e:0370:7334
For information about the support for IPv6 by Oracle Fusion Middleware components, see Oracle Fusion Middleware System Requirements and Specifications.
Most components support IPv6. The following topics provide more information about configuring Oracle Fusion Middleware certain components for IPv6:
- Configuring Oracle HTTP Server for IPv6
- Using Dual Stack with Oracle SOA Suite, Oracle Identity Governance, and Fusion Middleware Control
Parent topic: Changing Oracle Fusion Middleware Network Configurations
Configuring Oracle HTTP Server for IPv6
To configure Oracle HTTP Server to communicate using IPv6, you modify configuration files in the following directory:
(UNIX) DOMAIN_HOME/config/fmwconfig/components/OHS/ohs_name (Windows) DOMAIN_HOME\config\fmwconfig\components\OHS\ohs_name
For example, to configure Oracle HTTP Server to communicate with Oracle WebLogic Server on hosts that are running IPv6, you configure mod_wl_ohs. You edit the configuration files in the following directory:
DOMAIN_HOME/config/fmwconfig/components/OHS/instances/ohs1
In the files, specify either the resolvable host name or the IPv6 address in one of the following parameters:
WebLogicHost hostname | [IPaddress] WebCluster [IPaddress_1]:portnum1, [IPaddress_2]:portnum2, [IPaddress_3]:portnum3, ...
You must enclose the IPv6 address in brackets.
Any errors are logged in the Oracle HTTP Server logs. To generate more information, set the mod_weblogic directives Debug All and WLLogFile path. Oracle HTTP Server logs module-specific messages.
Note:
In previous versions, Oracle HTTP Server contained restrictions about using dynamic clusters with IPv6 nodes. For example, the Oracle HTTP Server plug-in for Oracle WebLogic Server had limited IPv6 support in that the DSL (dynamic server list) feature of the plug-in was not supported; only the static configuration of server lists was supported (DynamicServerList=OFF). Those restrictions have been lifted.
The OHS installation/configuration comes with a default SSL wallet containing a certificate with subject line having localhost mentioned in it.
If you put the localhost in admin.conf in
Listen, VirtualHost, and
ServerName directives then everything works fine.
If you don't want to use the localhost in admin.conf then, you
can use the fqdn name of that host.
For example:
abc.xyz.com in Listen,
VirtualHost, and ServerName directives.
Here you have to create a new wallet with a new certificate containing
abc.xyz.com in the certificate subject line and should
specify this new wallet in the admin.conf.
The nodemanager OHS plugin reads the OHS admin.conf and uses
these settings to connect to OHS.
Parent topic: Using IPv6
Using Dual Stack with Oracle SOA Suite, Oracle Identity Governance, and Fusion Middleware Control
Oracle SOA Suite and Oracle Identity Governance supports a dual-stack configuration. However, when you use Fusion Middleware Control with Oracle SOA Suite or Oracle Identity Governance, you must specify the protocol in the following file. Otherwise, Fusion Middleware Control may not work correctly.
DSOMAIN_HOME/bin/startWebLogic.sh
In the file, add the following line, specifying the IP protocol after the line
${DOMAIN_HOME}/bin/setDomainEnv.sh:
$DOMAIN_HOME/bin JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.net.preferIPv4Stack=true"Parent topic: Using IPv6