15 Changing Oracle Fusion Middleware Network Configurations

Oracle Fusion Middleware provides procedures for changing the network configuration, such as the host name or IP address, of an Oracle Fusion Middleware host and the Oracle database that Oracle Fusion Middleware uses. It also provides support for the IPv6 protocol with Oracle Fusion Middleware.

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

Using a combination of binary cloning, the chghost utility, and copying files from one host to another, Oracle Fusion Middleware supports the following changes:

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 Management Access Manager

  • Oracle Identity Governance

  • Oracle Internet Directory

The following component requires additional steps after you run the chghost utility:

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:

  • The value set in the command-line argument.

  • The value of the JAVA_HOME set in the environment.

  • The JAVA_HOME found in the DOMAIN_HOME or ORACLE_HOME.

-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 :

  • hostname: Ignore host name validation errors.

  • datasource: Ignore data source validation errors.

  • all: Ignore both host name and data source validation errors.

            

 Note : If ignoreValidationErrors is specified without any value then it defaults to all.

           

-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:

    setenv CHGHOST_JAVA_OPTIONS "-Dchghost.ignore.validation.port=true 
                             -Dchghost.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.

Changing the Host Name or IP Address of Oracle Fusion Middleware

You can change the host name or IP address of the host containing Oracle Fusion Middleware.

In this scenario, you have an Administration Server on Host_A, Managed Servers on Host_B, and the database on Host_C. You have changed the host name of one or more of these hosts. In the following example, you want to change Host_A to Host_A1 and Host_B to Host_B1.
To change the host name for the Administration Server from Host_A to Host_A1:
  1. Change the hostname, domain name, or IP address of your host.
  2. Stop the Administration Server and all Managed Servers if they are running.
  3. Create an input file that contains the following:
    [ARGUMENTS]
    
    [SERVER_HOST_MAPPING]
    #pattern source_host_name=target_host_name
    Host_A.domain.com=Host_A1.domain.com
    Host_B.domain.com=Host_B1.domain.com
    You can pass any of the arguments, except chgHostInputFile, in the input file. In this example, you pass the arguments on the command line.
    If all of the servers are on the same host, you do not need to take any separate action for them.
  4. Create a wallet directory, specifying the file specification, including the name of the directory and passing the administration user name to the command. For example:
    ORACLE_HOME/oracle_common/common/bin/configWallet.sh -walletDir /scratch/myWalletDir admin_username
    The command will prompt you to enter the password and to confirm the password. It creates the wallet directory if it does not exist and populates it with a cwallet.sso file.
  5. Execute the following command on Host A:
    ./chghost.sh -chgHostInputFile input_file
         -javaHome location_of_javahome 
         -domainLoc target_domain_path
         -domainAdminUserName username
         -walletDir location_of_wallet_dir
         -logPriority log_level
         -logDir location_of_log_file
  6. To change the name of Host_B, which holds the Managed Servers, to Host_B1, create an input file that contains the following:
    [ARGUMENTS]
    
    [SERVER_HOST_MAPPING]
    #pattern source_host_name=target_host_name
    Host_A.domain.com=Host_A1.domain.com
    Host_B.domain.com=Host_B1.domain.com
    
  7. Create a wallet file, as described in Step 4.
  8. Execute the chghost command on Host_B1, as described in Step 5.
The references within Oracle Fusion Middleware are changed to the new host names.

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.

  1. On Host_A, execute the copyBinary script:
    cd ORACLE_HOME/oracle_common/bin/
    ./copyBinary.sh -javaHome path_of_jdk
                    -sourceOracleHomeLoc OracleHome_location 
                    -archiveLoc location_of_resulting_jar_file 
    See copyBinary Script for the complete syntax of the copyBinary script.
  2. Copy the resulting jar file to Host_A1.
  3. Unpack the jar file:
    • Use the pasteBinary script on Host_A1. The script is located in:
      (UNIX) ORACLE_HOME/oracle_common/bin/pasteBinary.sh
      (Windows) ORACLE_HOME\oracle_common\bin\pasteBinary.cmd
      

      If Oracle Fusion Middleware is not installed on Host_A1, copy the following files from Host_A:

      (UNIX) ORACLE_HOME/oracle_common/bin/pasteBinary.sh
      (Windows) ORACLE_HOME\oracle_common\bin\pasteBinary.cmd
      

      Execute the following command:

      pasteBinary.sh -javaHome /scratch/oracle/jdk1.8.0_40
                     -archiveLoc  /tmp/oh_copy.jar 
                     -targetOracleHomeLoc /scratch/oracle/Oracle_home_prod 
                     -targetOracleHomeName Oracle_home_prod
      

      See pasteBinary Script for the complete syntax.

    • If an Oracle Home does not exist on Host_A1, use the following command:
      /scratch/jdk1.8.0_131/bin/java -jar /scratch/archive.jar
            -targetOracleHomeLoc /scratch/Oracle_home 
            -invPtrLoc /scratch/oracle/oraInst.loc 
            -javaHome /scratch/jdk1.8.0_131/
  4. Copy the domain home to Host_A1.
    1. Use a utility to create an archive of the domain home on Host_A. For example, use zip to archive the domain home directory structure for the domain soa_domain, on Host_A:
      cd ORACLE_HOME/domains
      zip domain.zip -r soa_domain
      You can also use the tar command.
    2. Copy the archive to Host_A1 and use unzip to unpack the archive. You must unpack it in the same directory structure as on Host A. For example, if the domain was in ORACLE_HOME/domains on Host_A, it must be in ORACLE_HOME/domains on Host_A1.
      cd ORACLE_HOME/domains
      unzip domain.zip 
  5. Create an input file that contains the following:
    [ARGUMENTS]
    
    [SERVER_HOST_MAPPING]
    #pattern source_host_name=target_host_name
    Host_A.domain.com=Host_A1.domain.com
    
  6. Create a wallet directory, specifying the full path, including the name of the directory and passing the administration user name to the command. For example:
    ORACLE_HOME/oracle_common/common/bin/configWallet.sh -walletDir /scratch/myWalletDir admin_username
    The command will prompt you to enter the password and to confirm the password. It creates the wallet directory if it does not exist and populates it with a cwallet.sso file.
  7. Run the chghost command on Host_A1:
    ./chghost.sh -chgHostInputFile input_file
         -javaHome location_of_javahome 
         -domainLoc target_domain_path
         -domainAdminUserName username
         -walletDir location_of_wallet_dir
         -logPriority log_level
         -logDir location_of_log_file
Now, Oracle Fusion Middleware is on Host_A1 and the host name has been changed in the Oracle Fusion Middleware instance.

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.

  1. On Host_A, execute the copyBinary script:
    cd ORACLE_HOME/oracle_common/bin/
    ./copyBinary.sh -javaHome path_of_jdk
                    -sourceOracleHomeLoc OracleHome_location 
                    -archiveLoc location_of_resulting_jar_file 
    See copyBinary Script for the complete syntax of the copyBinary script.
  2. Copy the resulting jar file to Host_A1.
  3. Unpack the jar file:
    • Use the pasteBinary script on Host_A1. The script is located in:
      (UNIX) ORACLE_HOME/oracle_common/bin/pasteBinary.sh
      (Windows) ORACLE_HOME\oracle_common\bin\pasteBinary.cmd
      

      If Oracle Fusion Middleware is not installed on Host_A1, copy the following files from Host_A:

      (UNIX) ORACLE_HOME/oracle_common/bin/pasteBinary.sh
      (Windows) ORACLE_HOME\oracle_common\bin\pasteBinary.cmd
      

      Execute the following command:

      pasteBinary.sh -javaHome /scratch/oracle/jdk1.8.0_40
                     -archiveLoc  /tmp/oh_copy.jar 
                     -targetOracleHomeLoc /scratch/oracle/Oracle_home_prod 
                     -targetOracleHomeName Oracle_home_prod
      

      See pasteBinary Script for the complete syntax.

    • If an Oracle Home does not exist on Host_A1, use the following command:
      /scratch/jdk1.8.0_131/bin/java -jar /scratch/archive.jar
            -targetOracleHomeLoc /scratch/Oracle_home 
            -invPtrLoc /scratch/oracle/oraInst.loc 
            -javaHome /scratch/jdk1.8.0_131/
  4. Copy the domain home to Host_A1.
    1. Use a utility to create an archive of the domain home on Host_A. For example, use zip to archive the domain home directory structure for the domain soa_domain, on Host_A:
      cd ORACLE_HOME/domains
      zip domain.zip -r soa_domain 
    2. Copy the archive to Host_A1 and use unzip to unpack the archive. You must unpack it in the same directory structure as on Host_A. For example, if the domain was in ORACLE_HOME/domains on Host_A, it must be in ORACLE_HOME/domains on Host_A1.
      cd ORACLE_HOME/domains
      unzip domain.zip 
  5. Create an input file that contains the following:
    [ARGUMENTS]
    
    [SERVER_HOST_MAPPING]
    #pattern source_host_name=target_host_name
    Host_A.domain.com=Host_A1.domain.com
    Host_B.domain.com=Host_B1.domain.com
    
  6. Create a wallet directory, specifying the full path, including the name of the directory and passing the administration user name to the command. For example:
    ORACLE_HOME/oracle_common/common/bin/configWallet.sh -walletDir /scratch/myWalletDir admin_username
    The command will prompt you to enter the password and to confirm the password. It creates the wallet directory if it does not exist and populates it with a cwallet.sso file.
  7. Run the chghost command on Host_A1:
    ./chghost.sh -chgHostInputFile input_file
         -javaHome location_of_javahome 
         -domainLoc target_domain_path
         -domainAdminUserName username
         -walletDir location_of_wallet_dir
         -logPriority log_level
         -logDir location_of_log_file
    
  8. On Host_B, execute the copyBinary script:
    cd ORACLE_HOME/oracle_common/bin/
    ./copyBinary.sh -javaHome path_of_jdk
                    -sourceOracleHomeLoc OracleHome_location 
                    -archiveLoc location_of_resulting_jar_file 
    See copyBinary Script for the complete syntax of the copyBinary script.
  9. Copy the resulting jar file to Host_B1.
  10. Unpack the jar file. If an Oracle Home exists on Host_B1, you can use the pasteBinary script, as described in pasteBinary Script. If an Oracle Home does not exist on Host_B1, use the following command:
    /scratch/jdk1.8.0_131/bin/java -jar /scratch/archive.jar 
       -targetOracleHomeLoc /scratch/Oracle_home 
       -invPtrLoc /scratch/oracle/oraInst.loc 
       -javaHome /scratch/jdk1.8.0_131/
  11. Copy the domain home to Host_B1.
    1. Use a utility to create an archive of the domain home on Host_B. For example, use zip to archive the domain home directory structure for the domain soa_domain, on Host_B:
      cd ORACLE_HOME/domains
      zip domain.zip -r soa_domain
    2. Copy the archive to Host_B1 and use unzip to unpack the archive. You must unpack it in the same directory structure as on Host_B. For example, if the domain was in ORACLE_HOME/domains on Host_B, it must be in ORACLE_HOME/domains on Host_B1.
      cd ORACLE_HOME/domains
      unzip domain.zip 
  12. On Host_B1, create an input file that contains the following:
    [ARGUMENTS]
    
    [SERVER_HOST_MAPPING]
    #pattern source_host_name=target_host_name
    Host_A.domain.com=Host_A1.domain.com
    Host_B.domain.com=Host_B1.domain.com
    
  13. Create a wallet directory, as described in Step 6.
  14. Run the chghost command on Host_B1, passing it the adminURL and managed options:
    ./chghost.sh -chgHostInputFile input_file
         -javaHome location_of_javahome 
         -domainLoc target_domain_path
         -domainAdminUserName username
         -walletDir location_of_wallet_dir
         -logPriority log_level
         -logDir location_of_log_file
         -adminURL t3://target_admin_host:target_domain_port 
         -managed
The references within Oracle Fusion Middleware are changed to the new host names.

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.

In this scenario, you have a database on Host_C and you have changed the name of the host to Host_C1. The Adminstration Server is on Host_A and the Managed Servers are on Host_B. You are not changing the names or moving the Adminstration Server or Managed Servers.

To change the host name for the database from Host_C to Host_C1:

  1. Change the hostname, domain name, or IP address of your host.
  2. Create an input file that contains the following:
    [ARGUMENTS]
    
    [DATABASE_MAPPING]
    #  You can only change the database host name.
    Host_C.domain.com=Host_C1.domain.com
    
    You can pass any of the arguments, except chgHostInputFile, in the input file. In this example, you pass the arguments on the command line.
  3. Stop the Administration Server and the Managed Servers.
  4. Execute the following command on the Administration Server host and on the Managed Server host:
    ./chghost.sh -chgHostInputFile input_file
         -javaHome location_of_javahome 
         -domainLoc target_domain_path
         -domainAdminUserName username
         -walletDir location_of_wallet_dir
         -logPriority log_level
         -logDir location_of_log_file
  5. Start the Administration Server and the Managed Servers.
The references within Oracle Fusion Middleware are changed to the new host name.

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.

In this scenario, you have a database on Host_C and you want to move it to Host_C1. The Adminstration Server is on Host_A and the Managed Servers are on Host_B. You are not changing the names or moving the Adminstration Server or Managed Servers.
  1. Move the database to a new host, using Oracle Database methods, such as RMAN or the Oracle Database export and import utilities. For more information, see Fusion Middleware Creating Schemas with the Repository Creation Utility.
    Note the following:
    • The service name and SID of the database on the new host must be the same as on the source host.
    • The port on the new host must be the same as on the source host.
    • The database on the new host must contain the same schemas as on the source host and the schemas must have the same prefix as on the source host.
  2. Create an input file that contains the following:
    [ARGUMENTS]
    
    [DATABASE_MAPPING]
    #  You can only change the database host name.
    Host_C.domain.com=Host_C1.domain.com
    
    You can pass any of the arguments, except chgHostInputFile, in the input file. In this example, you pass the arguments on the command line.
  3. Stop the Administration Server and the Managed Servers.
  4. Execute the following command on the Administration Server host (HOST_A) and on the Managed Server host (HOST_B):
    ./chghost.sh -chgHostInputFile input_file
         -javaHome location_of_javahome 
         -domainLoc target_domain_path
         -domainAdminUserName username
         -walletDir location_of_wallet_dir
         -logPriority log_level
         -logDir location_of_log_file
  5. Start the Administration Server and the Managed Servers.

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.

  1. Create an input file that contains the following:
    [ARGUMENTS]
    
    [SERVER_HOST_MAPPING]
    #pattern source_host_name=target_host_name
    Host_A.domain.com=Host_A1.domain.com
    Host_B.domain.com=Host_B1.domain.com
    
    
    [DATABASE_MAPPING]
    Host_C.domain.com=Host_C1.domain.com
    
    You will use this file when you run the chghost command.
  2. Run the copyBinary script on Host_A, copy the jar file to Host_A1, run the pasteBinary command on Host_A1 and copy the domain from Host_A to Host_A1, as described in Steps 1 through 4 in Moving a Multinode Oracle Fusion Middleware to New Hosts.
  3. Create a wallet directory, as described in Step 6 in Moving a Multinode Oracle Fusion Middleware to New Hosts.
  4. Run the chghost command on Host_A1, as described in Step 7 in Moving a Multinode Oracle Fusion Middleware to New Hosts. Use the input file shown in the first step.
  5. Run the copyBinary script on Host_B, copy the jar file to Host_B1, run the pasteBinary command on Host_B1 and copy the domain from Host_B to Host_B1, as described in Steps 8 through 11 in Moving a Multinode Oracle Fusion Middleware to New Hosts.
  6. Create a wallet directory, as described in Step 6 in Moving a Multinode Oracle Fusion Middleware to New Hosts.
  7. Run the chghost command on Host_B1, passing it the adminURL and managed options, as described in Step 14 in Moving a Multinode Oracle Fusion Middleware to New Hosts.
  8. Move the database to a new host, using Oracle Database methods. See Step 1 in Moving an Oracle Fusion Middleware Database to a New Host.
  9. Create an input file that contains the following:
    [ARGUMENTS]
    
    [DATABASE_MAPPING]
    #  You can only change the database host name.
    Host_C.domain.com=Host_C1.domain.com
    
  10. Stop the Administration Server and the Managed Servers.
  11. Execute the chghost command on Administration Server host (HOST_A1) and on the Managed Server host (HOST_B1), as described in Step 4 in Moving an Oracle Fusion Middleware Database to a New Host.
  12. Start the Administration Server and the Managed Servers.

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.

To update the host name and port information, you run the following script:
ORACLE_HOME/forms/fads/fads_config.py

The script takes the following mandatory arguments:

  • The Host Port Number

  • The Administration Server host name

  • The Administration port

  • The applications directory

For example:

wlst.sh ORACLE_HOME/forms/fads/fads_config.py updateHostPort myserverhost myserverport Oracle_Home/applications/forms_domain

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)

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.

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:

  1. Connect the host to the network using DHCP.
  2. Configure the host name to the loopback IP address only.

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 host name can be resolved locally.
  2. Take the host off the network.

    There is no need to perform any steps to change the host name or IP address.

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.

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 host name 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 Fusion Middleware.

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 Fusion Middleware.

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

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.

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"