Changing the Network Configuration of a Managed Server

Changing Network Configurations 15-7 ■ 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. Refer to the Oracle Fusion Middleware Installation Planning Guide for more information.

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

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

15.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 etchosts 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.

15.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 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 Oracle Fusion Middleware Installation Planning Guide for more information. ■ 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. 15-8 Oracle Fusion Middleware Administrators Guide

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

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

15.5 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 Table 15–1 describes support for IPv6 by Oracle Fusion Middleware components. In the table: ■ The column IPv6 Only shows whether a component supports using IPv6 only for all communication. ■ The column Dual Stack shows whether a component supports using both IPv6 and IPv4 for communication. For example, some components do not support using IPv6 only, because some of the communication is with the Oracle Database, which supports IPv4, not IPv6. Those components support dual stack, allowing for IPv6 communication with other components. Table 15–1 Support for IPv6 Component IPv6 Only Dual Stack Notes Oracle Access Manager Yes Yes To configure for IPv6, see Section 15.5.5 . Oracle Application Development Framework Yes Yes Oracle Business Intelligence Discoverer No No Uses reverse proxy to communicate with Oracle Web Cache or Oracle HTTP Server, which can be configured for IPv6. Oracle Data Integrator No Yes Requires a dual stack because Oracle Database requires IPv4 addresses. The Agent requires IPv4 addresses. The Oracle Data Integrator server can be on a dual-stack host. The browser client can be on either IPv4 or IPv6 hosts.