Tuesday, November 5, 2019

Configuring Oracle E-Business Suite Release 12.x Using Logical Host Names (Doc ID 1968231.1)

This document describes how to deploy Oracle E-Business Suite with machines (nodes) configured using logical host names.
Note: Although examples showing Oracle E-Business Suite Release 12.2 are used throughout this document, the concepts and technical setup also apply to Oracle E-Business Suite Releases 12.0 and 12.1.
The most current version of this document can be obtained in My Oracle Support Knowledge Document 1968231.1.
There is a change log at the end of this document.

In This Document

This document contains the following sections:

Section 1: Overview

This document describes the design considerations and steps required to configure the Oracle E-Business Suite application and database tiers on machines configured to use logical host names. Also it describes supported network topologies and architectures for using logical names with Oracle E-Business Suite.
Note: The design considations discussed in this document may require adjustments for use in Oracle RAC installations, depending on how your machines and network are set up. Specific restrictions are noted in the applicable sections.
This document is intended for Oracle E-Business Suite Release 12 system administrators. It assumes knowledge of networking technologies. The procedures described in this document have security implications. Prior to the implementation of any configuration options described in this document, Oracle strongly recommends that you review deployment architectures with enterprise networking and security groups.
This section includes the following topics:

Section 1.1: Oracle E-Business Suite Release 12 Architecture with Logical Host Names

We recommend that you use the logical host names, not the physical host names, to install the Oracle E-Business Suite database tier and application tier. The advantages of using logical host names are:
  • Hide the actual servers that host the application and business software from end users for better security.
  • Provide the capability of moving the database and application tiers to any other machines without running a clone.
  • Reduce the amount of reconfiguration required on failover for Disaster Recovery by using the same host name on the active and standby sites.
  • Avoid rewiring or recloning the database and application tiers due to network configuration changes, such as host name change.
  • Seamlessly support data center migration by keeping the same logical host name.
  • Simulate multiple machines on the same physical hardware for hosting external and internal sites.
  • Use logical host name to bind and physical host name to access the application.

Section 1.2: Terminology

This section describes the definitions of frequently used terms in this document:

Host Name

A host name is a label assigned to a device that is connected to a computer network. The label is used to identify the machine in various forms of communication protocols supported in the network.

Physical Host Name

The physical host name of a computer is typically the name returned by the hostname command. For example,
$ hostname
acme.example.com

Logical Host Name

The logical host name of a computer is typically the name assigned to an IP address in the /etc/hosts file. For example,
$ cat/etc/hosts
127.0.0.1 localhost.localdomain localhost
123.1.2.111 db.example.com db acme.example.com acme
db.example.com is the logical host name of the host.

Section 2: Basic Deployment Options

This section describes the following deployment options:

Section 2.1: Configuration Using Logical Host Name Only

In this configuration, a logical host name is used to install the Oracle E-Business Suite database tier and application tier. The physical host name is nowhere configured or used on the machine including the context file. For example, the hostname and uname -n commands return the logical host name rather than the physical host name.

Section 2.2: Configuration Using Combination of Physical and Logical Host Names

In this configuration, a logical host name is used to install the Oracle E-Business Suite database tier and application tier, but the hostname and uname -n commands return the physical host name instead of the logical host name.
Note: This configuration is supported for Oracle E-Business Suite Release 12.2 environments at the AD-TXK Delta 9 codelevel.

Section 3: Required Patches for Oracle E-Business Suite Release 12.2

The following table lists the required patches for configuring Oracle E-Business Suite Release 12.2:
Patch Number/Minimum Code Level
Description
Instructions

Patch 25178222:R12.AD.C.Delta.9
Patch 25180736:R12.TXK.C.Delta.9
Oracle E-Business Suite AD/TXK Delta 9 patches
Follow the instructions described in My Oracle Support Knowledge Document 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2, to apply the required patches.
Patch 17075726:R12.FND.CPatch to support concurrent managers on a host configured to use virtual host names.Follow the instructions in the patch readme to apply the patch.

Section 4: Common Configuration Steps For All Deployment Types

This section describes the general configuration steps that apply to any deployment model described in this document. Certain common configuration steps must be carried out regardless of which deployment model is used. Some of them may have already been executed as part of a setup you already have. Review the steps and perform the appropriate configuration steps wherever necessary.

Section 4.1: Configuring Machine to Use Logical Host Name Only

Configure the machine to use a logical host name using the supplied utilities by the operating system vendor.
For example, perform the following steps to configure a machine running Oracle Linux to use a logical host name:

Section 4.1.1: Database Tier Procedure

  1. Configure the machine on the database tier:
    Physical host name of DB Tier: physicaldb.example.com
    Logical host name of DB Tier: logicaldb.example.com
    Specify the logical host name in the /etc/hosts file:
    127.0.0.1 localhost.localdomain localhost
    123.1.2.111 logicaldb.example.com logicaldb
    Note that the fully-qualified logical host name of the server has to be the first entry after the IP address and then followed by the aliases, such as logicaldb in this example. The aliases can include the physical host name if DNS (Domain Name System) is not used to resolve the host name.
    Specify the network configuration in the /etc/sysconfig/network file:
    NETWORKING=yes
    HOSTNAME=logicaldb.example.com
  2. Once you complete the configuration, reboot the database tier machine and run the following commands to verify that the database tier machine is fully configured to the use the physical host name:
    Physical host name of DB Tier: physicaldb.example.com
    Logical host name of DB Tier: logicaldb.example.com

    $ echo $HOSTNAME
    logicaldb.example.com
    $ hostname
    logicaldb.example.com
    $ uname -n
    logicaldb.example.com
  3. Run nslookup from an external machine. This should return the physical host name of the server, so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.111
    nslookup 123.1.2.111
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = physicaldb.example.com

    $ ping $HOSTNAME
    PING logicaldb.example.com (123.1.2.111) 56(84) bytes of data.
    64 bytes from logicaldb.example.com (123.1.2.111): icmp_seq=1 ttl=64 time=0.020 ms

Section 4.1.2: Application Tier Procedure

  1. Configure the machine on the application tier:
    Physical host name of Apps Tier: physicalapps.example.com
    Logical host name of Apps Tier: logicalapps.example.com
    Specify the logical host name in the /etc/hosts file:
    127.0.0.1 localhost.localdomain localhost
    123.1.2.111 logicaldb.example.com logicaldb
    123.1.2.112 logicalapps.example.com logicalapps
    Note that the fully-qualified logical host name of the server has to be the first entry after the IP address, and followed by the aliases. The aliases can include the physical host name if DNS is not used to resolve the host name. The application tier's /etc/hosts file must list the database tier logical host name so that the application tier can connect to the database tier using its logical host name.
    Specify the network configuration in the /etc/sysconfig/network file:
    NETWORKING=yes
    HOSTNAME=logicalapps.example.com
  2. Once you complete the configuration, reboot the application tier machine and run the following commands to verify that the application tier machine is fully configured to the use the physical host name:
    Physical host name of Apps Tier: physicalapps.example.com
    Logical host name of Apps Tier: logicalapps.example.com

    $ echo $HOSTNAME
    logicalapps.example.com
    $ hostname
    logicalapps.example.com
    $ uname -n
    logicalapps.example.com
  3. Run nslookup from the application tier machine. This should return the physical host name of the server, so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.112
    nslookup 123.1.2.112
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = physicalapps.example.com

    $ ping $HOSTNAME
    PING logicalapps.example.com (123.1.2.112) 56(84) bytes of data.
    64 bytes from logicalapps.example.com (123.1.2.112): icmp_seq=1 ttl=64 time=0.020 ms
    $ ping logicaldb.example.com
    PING logicaldb.example.com (123.1.2.111) 56(84) bytes of data.
    64 bytes from logicaldb.example.com (123.1.2.111): icmp_seq=1 ttl=64 time=0.020 ms
    The physical host name physicaldb.example.com for the database tier and physicalapps.example.com for the application tier are public host names that are resolvable through DNS on your network. They are respectively assigned to the IP addresses 123.1.2.111 and 123.1.2.112 in DNS.

Section 4.2: Configuring Machine to Use Both Physical and Logical Host Names

Use the operating system utilities to configure the machine to use a combination of logical and physical host names.
Note: If your system administrator has already set a desired physical host name on the server, you may not need to perform the following steps.
The following example list the steps needed to configure a machine running Oracle Linux to use a logical host name:

Section 4.2.1: Database Tier Procedure

  1. Configure the machine to use both physical and logical names.

    The following example configuration illustrates how a combination of physical and logical names can be used with Oracle E-Business Suite.
    Physical host name of DB Tier:
    physicaldb.example.com
    Logical host name of DB Tier:
    logicaldb.example.com
    Specify the logical host name in the /etc/hosts file:
    127.0.0.1 localhost.localdomain localhost
    123.1.2.111 logicaldb.example.com logicaldb
    The /etc/hosts file must include the fully qualified logical host name of the server, followed by the alias. In this example, the second line of the /etc/hosts file shows that these are logicaldb.example.com and logicaldb respectively. It is optional to include the physical host name as well.

    Specify the network configuration in the /etc/sysconfig/network file:
    NETWORKING=yes
    HOSTNAME=physicaldb.example.com
    In the above example, note that the HOSTNAME parameter is used to set the physical host name: this is because in such a configuration, end users may want to see the physical host name on the prompt, and it may also be used by some system utilities.
  2. Once you complete the configuration, reboot the database tier machine and run the following commands to verify that the database tier machine is fully configured to the use the physical host name:
    Physical host name of DB Tier:
    physicaldb.example.com
    Logical host name of DB Tier:
    logicaldb.example.com

    $ echo $HOSTNAME
    physicaldb.example.com
    $ hostname
    physicaldb.example.com
    $ uname -n
    physicaldb.example.com
  3. Run nslookup from an external machine. This should return the physical host name of the server, so that external machines can connect to the database tier using a well-defined, resolvable address in DNS. If that cannot be accomplished, you could also resolve the addresses locally, but you may have to add the IP and host information to the client hosts file.
    $ nslookup 123.1.2.111
    nslookup 123.1.2.111
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = physicaldb.example.com    From your database tier machine:

    $ ping $HOSTNAME
    PING physicaldb.example.com (123.1.2.111) 56(84) bytes of data.
    64 bytes from physicaldb.example.com (123.1.2.111):
    icmp_seq=1 ttl=64 time=0.020 ms
    $ ping logicaldb.example.com
    PING logicaldb.example.com (123.1.2.111) 56(84) bytes of data.
    64 bytes from logicaldb.example.com (123.1.2.111):
    icmp_seq=1 ttl=64 time=0.020 ms

Section 4.2.2: Application Tier Procedure

  1. Configure the machine to use both physical and logical names.

    The following example configuration illustrates how a combination of physical and logical names can be used with Oracle E-Business Suite.
    Physical host name of DB Tier:
    physicalapps.example.com
    Logical host name of DB Tier:
    logicalapps.example.com
    Specify the logical host name in the /etc/hosts file:
    127.0.0.1 localhost.localdomain localhost
    123.1.2.111 logicaldb.example.com logicaldb
    123.1.2.112 logicalapps.example.com logicalapps
    The /etc/hosts file must include the fully qualified logical host name of the server, followed by the alias. In this example, the third line of the /etc/hosts file shows that these are logicalapps.example.com and logicalapps respectively. It is optional to include the physical host name as well.
    The application tier's /etc/hosts file must include the database tier's logical host name, so that the application tier can connect to the database tier using the database tier's logical host name.

    Specify the network configuration in the /etc/sysconfig/network file:
    NETWORKING=yes
    HOSTNAME=physicalapps.example.com
    In the above example, note that the HOSTNAME parameter is used to set the physical host name: this is because in such a configuration, end users may want to see the physical host name on the prompt, and it may also be used by some system utilities.
  2. Once you complete the configuration, reboot the application tier machine and run the following commands to validate the configuration and verify that the application tier machine is fully configured to the use the physical host name:
    Physical host name of Apps Tier: physicalapps.example.com
    Logical host name of Apps Tier: logicalapps.example.com

    $ echo $HOSTNAME
    physicalapps.example.com
    $ hostname
    physicalapps.example.com
    $ uname -n
    physicalapps.example.com
  3. Run nslookup from an external machine. This should return the physical host name of the server, so that external machines can connect to the application tier machine using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.112
    nslookup 123.1.2.112
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = physicalapps.example.com    From your application tier machine:

    $ ping $HOSTNAME
    PING physicalapps.example.com (123.1.2.112) 56(84) bytes of data.
    64 bytes from physicalapps.example.com (123.1.2.112):
    icmp_seq=1 ttl=64 time=0.020 ms

    $ ping logicalapps.example.com
    PING physicalapps.example.com (123.1.2.112) 56(84) bytes of data.
    64 bytes from logicalapps.example.com (123.1.2.112):
    icmp_seq=1 ttl=64 time=0.020 ms
    $ ping logicalapps.example.com
    PING logicaldb.example.com (123.1.2.111) 56(84) bytes of data.
    64 bytes from logicaldb.example.com (123.1.2.111):
    icmp_seq=1 ttl=64 time=0.020 ms
The physical host names (physicaldb.example.com for the database tier and physicalapps.example.com for the application tier) are public host names that are resolvable through DNS on your network. They are assigned to the IP addresses 123.1.2.111 and 123.1.2.112 respectively in DNS.

Section 5: Configuring Oracle E-Business Suite with Different Supported Topologies

Note: This document focuses on enterprise deployment in Oracle Linux environments. The same deployment may also be configured on certified UNIX and Windows platforms.
This section provides the instructions on configuring Oracle E-Business Suite with supported technologies. The section includes the following topics:

Section 5.1: Two-Node Installation Using Logical Host Names on Database and Application Tiers

This section explains how to deploy the Oracle E-Business Suite database and application tiers on two different hosts, configured to use logical host names. An overview of the setup is illustrated in the following diagram:
In this diagram, the Oracle E-Business Suite application tier and the database tier are deployed to a separate host with a different logical host name. For example, the application tier and the database tier are assigned to the IP addresses 123.1.2.112 and 123.1.2.111 respectively in DNS. The logical host name for the application tier is "apps.example.com", and the name for the database tier is "db.example.com". These host names, IP addresses, and configuration files used in this example diagram explain how this type of the installation can be configured. Replace these sample values with your actual setup parameter values for your environment.
Additionally, the topology shown in this diagram assumes the following configuration:
Tier Type
Logical Host Name
Physical Host Name
IP Address
Web Entry Point
Database Tier
logicaldb.example.com
physicaldb.example.com
123.1.2.111
N/A
Primary Application Tier
logicalapps.example.com
physicalapps.example.com
123.1.2.112
https://global-ebusiness.example.com:443
To further understand how to configure Oracle E-Business Suite using logical host names with two-node installation, this section includes the following topics:

Section 5.1.1: Installing Oracle E-Business Suite Database and Application Tiers

Use Rapid Install or Rapid Clone to establish the file system after you complete the system configuration as described in Section 4.1: Configuring Machine to Use Logical Host Name. The hostname and uname -n commands must return the logical host name, instead of the physical host name. The database tier and the application tier need to be installed with the logical host names when running rapidwiz or rapidclone. Ensure the logical host names are displayed during the installation phase.
  • On the database tier, run the following command to launch Rapid Install:
    $ /startCD/Disk1/rapidwiz/rapidwiz
    In the Install Oracle E-Business Suite - Database Node screen, enter the logical host name (such as "logicaldb"), in the Database Host Name field.
    Note that the example screenshots shown in this section are for Oracle E-Business Suite Release 12.2, but the installation process is the same for Oracle E-Business Suite Releases 12.0 and 12.1.
  • On the application tier, run the following command to launch Rapid Install:
    $ /startCD/Disk1/rapidwiz/rapidwiz
    In the Install Oracle E-Business Suite - Primary Applications Node page, enter the primary host name (such as "logicalapps") in the Primary Host Name field.
For detailed instructions on using Rapid Install, see the Oracle E-Business Suite Installation Guide: Using Rapid Install.

Section 5.1.2: Configuring the Web Entry Point on Application Tier Nodes

The logical host name configured for the application tier may not be visible to the clients that are external to the node. To access the Oracle E-Business Suite application login page from external clients, you need to configure the web entry point related variables on the application tier to point to the physical host name that is resolvable on the network using DNS.
For example, configure Oracle E-Business Suite with the configuration given in the following table:
Tier Type
Logical Hostname
Physical Hostname
IP Address
Web Entry Point
Database Tier
logicaldb.example.com
physicaldb.example.com
123.1.2.111
N/A
Primary Application Tier
logicalapps.example.com
physicalapps.example.com
123.1.2.112
https://global-ebusiness.example.com:443
Set the following variables in the applications context file of the run file system to point to the physical host name and then execute AutoConfig. Ensure that there are no patching cycles open when performing this configuration. The prepare phase of a subsequent online patching cycle will propagate the changes from the run edition context file to the patch edition context file.
Context Variable
Current Value
Changed Value
Comments
s_webentryurlprotocol
http
https
Use http for Non-SSL connections.
s_webentryhost
logicalapps
global-ebusiness
s_webentrydomain
example.com
example.com
s_active_webport
8000
443
The default value for port pool is 0. This value may differ on your instance depending on what port pool is chosen during the installation.
s_login_page
http://logicalapps.example.com:8000/OA_HTML/AppsLogin
https://global-ebusiness.example.com:443/OA_HTML/AppsLogin
s_external_url
http://logicalapps.example.com:8000
https://global-ebusiness.example.com:443
Restart the application tier services and ensure that users can log in using the URL containing the physical host name (https://global-ebusiness.example.com:443/OA_HTML/AppsLogin) of the application tier server from the client browser.

Section 5.2: Multi-node Installation Using Logical Host Names on Database and Application Tiers

This section explains how to deploy the Oracle E-Business Suite database tier and application tier on two different hosts, configured to use logical host names.
The following diagram represents the high level architecture for Oracle E-Business Suite in a multimode environment. In this diagram, a hardware load balancer configuration to load balance the application running on a primary application tier and a secondary application tier, as well as the database running on the database tier. In this configuration, the database tier and the application tier are on two different hosts with logical host names.
The host names, IP addresses, and configuration files used in this example diagram explain how this type of installation can be configured. Specifically, these values used in the diagram for each tier are listed in the following table. Replace these sample values with your actual setup parameter values for your environment.
Tier Type
Logical Hostname
Physical Hostname
IP Address
Web Entry Point
Database Tier
logicaldb.example.com
physicaldb.example.com
123.1.2.111
N/A
Primary Application Tier
logicalapps.example.com
physicalapps.example.com
123.1.2.112
https://global-ebusiness.example.com:443
Secondary Application Tier
logicalsecapps.example.com
physicalsecapps.example.com
123.1.2.113
https://global-ebusiness.example.com:443
Perform Rapid Install or Rapid Clone on the database tier first, and then followed by the primary application tier as described in Section 5.1.1: Installing the Oracle E-Business Suite Database and Application Tiers. The secondary application tier can be added as a hybrid or a shared application tier node by using the Rapid Clone add node feature.
For information on adding a node to the shared application tier file system in Oracle E-Business Suite Release 12.2, refer to:
  • My Oracle Support Knowledge Document 1375769.1, Sharing The Application Tier File System in Oracle E-Business Suite Release 12.2
For information on using Rapid Clone, refer to:
  • My Oracle Support KnowledgeDocument 1383621.1, Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone.

Section 5.2.1: Configuring the Web Entry Point on Application Tier Nodes

The logical host name configured for the application tier may not be visible to the clients that are external to the node. For example, a browser that runs on a client machine which is used to access the Oracle E-Business Suite application home page. To access the Oracle E-Business Suite application login page from external clients, configure the web entry point related variables on the application tier to point to the load-balancing device for this specific configuration.
For example, configure Oracle E-Business Suite in 1a multi-node environment with the configuration given in the following table:
Tier Type
Logical Hostname
Physical Hostname
IP Address
Web Entry Point
Database Tier
logicaldb.example.com
physicaldb.example.com
123.1.2.111
N/A
Primary Application Tier
logicalapps.example.com
physicalapps.example.com
123.1.2.112
https://global-ebusiness.example.com:443
Secondary Application Tier
logicalsecapps.example.com
physicalsecapps.example.com
123.1.2.113
https://global-ebusiness.example.com:443
Set the following variables in the applications context file of the run file system to point to the physical host name and execute AutoConfig. Ensure that there are no patching cycles open when performing this configuration. The subsequent "prepare" phase of an online patching cycle will propagate the changes from the run edition context file to the patch edition context file.

Section 5.2.1.1: On Primary Application Tier

Context Variable
Current Value
Changed Value
Comments
s_webentryurlprotocol
http
https
Use http for Non-SSL connections.
s_webentryhost
logicalapps
global-ebusiness
-
s_webentrydomain
example.com
example.com
-
s_active_webport
8000
443
The default value for port pool is 0. This value may differ on your instance depending on what port pool is chosen during the installation.
s_login_page
http://logicalapps.example.com:8000/OA_HTML/AppsLogin
https://global-ebusiness.example.com:443/OA_HTML/AppsLogin
-
s_external_url
http://logicalapps.example.com:8000
https://global-ebusiness.example.com:443
-

Section 5.2.1.2: On Secondary Application Tier

Context Variable
Current Value
Changed Value
Comments
s_webentryurlprotocol
http
https
Use http for Non-SSL connections.
s_webentryhost
logicalsecapps
global-ebusiness
-
s_webentrydomain
example.com
example.com
-
s_active_webport
8000
443
The default value for port pool is 0. This value may differ on your instance depending on what port pool is chosen during the installation.
s_login_page
http://logicalsecapps.example.com:8000/OA_HTML/AppsLogin
https://global-ebusiness.example.com:443/OA_HTML/AppsLogin
-
s_external_url
http://logicalsecapps.example.com:8000
https://global-ebusiness.example.com:443
-
Ensure that the load-balancing device that the connection coming on to the external web entry point URL needs to be routed to the correct public IP address of the application tier servers. For example, the public IP address for the logicalapps and logicalsecapps servers are 123.1.2.112 and 123.1.2.113 respectively.

Section 5.3: Multi-node Installation Using Physical and Logical Host Names on Database and Application Tiers

This section describes how to deploy the Oracle E-Business Suite database and application tier on two different hosts, configured to use a combination of  physical and logical host names.
The following diagram illustrates the high level architecture of Oracle E-Business Suite in a multi-node environment, with a a hardware load balancer configured to load-balance applications running on a primary application tier and a secondary application tier. In this configuration, the database tier and application tier are on two different hosts, with a combination of logical host names.
The host names, IP addresses, and configuration files used in the example diagram show how this type of installation can be configured. The values used for each tier are listed in the following table. Replace these example values with the actual setup parameter values for your environment.
Tier Type
Logical Hostname
Physical Hostname
IP Address
Web Entry Point
Database Tier
logicaldb.example.com
physicaldb.example.com
123.1.2.111
N/A
Primary Application Tier
logicalapps.example.com
physicalapps.example.com
123.1.2.112
https://global-ebusiness.example.com:443
Secondary Application Tier
logicalsecapps.example.com
physicalsecapps.example.com
123.1.2.113
https://global-ebusiness.example.com:443
The configuration described in this section requires the patches mentioned in Section 3: Required Patches for Configuring Oracle E-Business Suite Release 12.2 of this document. These patches need to be applied before proceeding with this configuration. You can apply the patches in a test or development system, and then clone to a production system that is configured to use a combination of physical and logical host names. Refer to the standard Oracle E-Business Suite cloning documentation for more details on how to clone the database and application tier nodes.
When cloning the database and application tiers to the target system, ensure you enter the logical host name when prompted by the clone utility. Do not enter the physical host name.
For example:
  • During a database tier clone flow, adcfgclone will prompt for the following:
    • Target System Hostname (virtual or normal) [physicaldb]: logicaldb
  • During an application tier clone flow, adcfgclone will prompt for the following:
    • Target System Hostname (virtual or normal) [physicalapps]: logicalapps
    • Target System Database Server Node [physicalapps]: logicaldb
    • Target System Database Domain Name [example.com]: example.com
The subsequent nodes can be added by as a hybrid or shared application tier node by using the Add Node option of Rapid Clone. Follow the same approach for the additional application tier nodes.
For information on adding a node to the shared application tier file system in Oracle E-Business Suite Release 12.2, refer to:
  • My Oracle Support Knowledge Document 1375769.1, Sharing The Application Tier File System in Oracle E-Business Suite Release 12.2
For information on using Rapid Clone, refer to:
  • My Oracle Support Knowledge Document 1383621.1, Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone

Section 5.3.1: Configuring the Web Entry Point on Application Tier Nodes

The logical host name configured for the application tier may not be visible to the clients that are external to the node: for example, a browser that runs on a client machine used to access the Oracle E-Business Suite login page. To access the Oracle E-Business Suite login page from external clients, configure the web entry point variables on the application tier to the load balancing device for the specific configuration.
For example, you could configure Oracle E-Business Suite in a multi-node environment with a configuration like the one shown in the following table:
Tier Type
Logical Hostname
Physical Hostname
IP Address
Web Entry Point
Database Tier
logicaldb.example.com
physicaldb.example.com
123.1.2.111
N/A
Primary Application Tier
logicalapps.example.com
physicalapps.example.com
123.1.2.112
https://global-ebusiness.example.com:443
Secondary Application Tier
logicalsecapps.example.com
physicalsecapps.example.com
123.1.2.113
https://global-ebusiness.example.com:443
With no online patching cycle in progress, set the variables in the application tier context file of the run file system to point to the physical host name. Then run AutoConfig. The prepare phase of a subsequent online patching cycle will propagate the changes from the run edition context file to the patch edition context file.

Section 6: Use Case Scenarios

This section provides business scenarios on configuring Oracle E-Business Suite using logical host names.
The following use case scenarios are included in this section:

Section 6.1: Scenario 1 - Using Logical Host Names in Creation of Identical Clone

This section provides an overview of the way logical host names can be used in creation of an identical clone. This assumption is that you have copied the database and application tier file systems to the target machine, and maintained exactly the same configuration on the target as the source.

In this scenario, changes can be made to certain parts of the network configuration, such as the IP addresses of the logical and physical hosts. Changes cannot be made to other parts, such as the logical host names of the application and database tiers.
The following table describes the source instance configuration in the above diagram:
Tier Type
Logical Host Name
Physical Host Name
Install Base
SID
IP Address
Database Tier
logicaldb.example.com
physicaldb.example.com
/u01/install/DB
EBSDB
123.1.2.111
Primary Application Tier
logicalapps.example.com
physicalapps.example.com
/u01/install/APPS
EBSDB
123.1.2.112
Secondary Application Tier
logicalsecapps.example.com
physicalsecapps.example.com
/u01/install/APPS
EBSDB
123.1.2.113
The following table describes the target instance configuration in the above diagram:
Tier Type
Logical Hostname
Physical Hostname
Install Base
SID
IP Address
Database Tier
logicaldb.example.com
physicaldb1.example.com
/u01/install/DB
EBSDB
123.1.2.114
Primary Application Tier
logicalapps.example.com
physicalapps1.example.com
/u01/install/APPS
EBSDB
123.1.2.115
Secondary Application Tier
logicalsecapps.example.com
physicalsecapps1.example.com
/u01/install/APPS
EBSDB
123.1.2.116
Note that from the source instance and target instance tables mentioned here, the logical host names are the same across the source and target instances, whereas the physical host names and IP addresses are different. The Installation directory, SID name, and port pool are kept the same between the source and target instances to avoid running the clone utility. This helps in provisioning new environments with a fast turnaround time, but no errors.
The following table describes the web entry point configuration on the source instance in this diagram:
Context Variable
Value
Comments
s_webentryurlprotocol
https
Use http for Non-SSL connections.
s_webentryhost
global-ebusiness
-
s_webentrydomain
example.com
-
s_active_webport
443
The default value for port pool is 0. This value may differ on your instance depending on what port pool is chosen during the installation.
s_login_page
https://global-ebusiness.example.com:443/OA_HTML/AppsLogin
-
s_external_url
https://global-ebusiness.example.com:443
-
The following table describes the web entry point configuration on the target instance in this diagram:
Context Variable
Value
Comments
s_webentryurlprotocol
https
Use http for Non-SSL connections.
s_webentryhost
global-ebusiness-test
-
s_webentrydomain
example.com
-
s_active_webport
443
The default value for port pool is 0. This value may differ on your instance depending on what port pool is chosen during the installation.
s_login_page
https://global-ebusiness-test.example.com:443/OA_HTML/AppsLogin
-
s_external_url
https://global-ebusiness-test.example.com:443
-
Notice that the web entry point on the source instance and target instance are different as shown in the tables here.

Section 6.2: Scenario 2 - Using Logical Host Names to Avoid Rewiring After Changes in Network Configuration

When the network topology changes, a common requirement is to change some part of the network configuration, such as the host name of the application or database tier. This is a very costly operation in that you need to perform a complete reclone of the environment with the new host name, in addition to making operating system changes.
Guidelines for Handling Host Name Changes
Host name changes could happen in the database tier, the primary application tier node, or the secondary application tier node. This section describes the guidelines for handling the following host name changes:

Section 6.2.1: Changing Host Name of Database Tier Node

Case 1 (Recommended)
  1. Treat the current host name of the database tier as the logical name of the host.
  2. Change the host name of the server only in DNS for external access.
For example, if the current name of the database tier machine is "mydb.example.com" and you want to change the host name to "mynewdb.example.com", perform the following steps to change the host name only (the IP address does not change):
Current host name of DB Tier: mydb.example.com
New host name of DB Tier: mynewdb.example.com
current IP address of DB Tier: 123.1.2.111
  1. Update your DNS system to reflect the new host name (mynewdb.example.com) for the IP address 123.1.2.111.
    $ echo $HOSTNAME
    mydb.example.com
    $ hostname
    mydb.example.com
    $ uname -n
    mydb.example.com
    The output indicates that the internal logical name remained the same, but the external name has changed as described in the next step.
  2. Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.111
    nslookup 123.1.2.111
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = mynewdb.example.com

    From within the same host

    $ ping $HOSTNAME
    PING mydb.example.com (123.1.2.111) 56(84) bytes of data.
    64 bytes from mydb.example.com (123.1.2.111): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.111 mydb.example.com mynewdb.example.com mydb mynewdb
Perform the following steps to change both the host name and IP address:
Current host name of DB Tier: mydb.example.com
New host name of DB Tier: mynewdb.example.com
Current IP address of DB Tier: 123.1.2.111
Changed IP address of DB Tier: 123.1.2.112
  1. Update your DNS system to reflect the new host name (mydb.example.com) for the IP address 123.1.2.112.
    $ echo $HOSTNAME
    mydb.example.com
    $ hostname
    mydb.example.com
    $ uname -n
    mydb.example.com
    The output indicates that the internal logical name remained the same, but the external name has changed as described in the next step.
  2. Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.112
    nslookup 123.1.2.112
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = mynewdb.example.com

    From within the same host

    $ ping $HOSTNAME
    PING mydb.example.com (123.1.2.112) 56(84) bytes of data.
    64 bytes from mydb.example.com (123.1.2.112): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.112 mydb.example.com mynewdb.example.com mydb mynewdb
    Note that the host file on the application tier may also have to be changed depending on whether each of the application tier uses a DNS or file-based resolution to resolve host names.
Case 2 (Not Recommended)
  1. Execute a preclone and a postclone on the database tier with the new host name, assuming that you can take a downtime and reimplement any customization to the configuration.
  2. Execute a preclone before the host name of the database tier is changed, and a postclone on the application tier after the host name of the database tier is changed, starting with the primary application tier.
If there are other instances running on the same machine sharing the same Oracle inventory, you must use the detachHome script to detach the Oracle Home from the central inventory instead of removing the complete inventory. Once the primary application tier is cloned, add all the secondary nodes back into the system using the add node API.
Note: Based on the tasks listed here, this approach is considered a complete reimplementation of the installation. This is not a best practice and is not recommended.

Section 6.2.2: Changing Host Name of Primary Application Tier Node

Case 1 (Recommended)
  1. Treat the current host name of the application tier as the logical name of the host.
  2. Change the host name of the server only in DNS for external access.
For example, if the current name of the application tier machine is "myapps.example.com"" and you want to change the host name to ""mynewapps.example.com", perform the following steps to change the host name only (the IP address does not change):
Current host name of Apps Tier: myapps.example.com
New host name of Apps Tier: mynewapps.example.com
Current IP address of Apps Tier: 123.1.2.113
  1. Update your DNS system to reflect the new host name (mynewapps.example.com) for the IP address 123.1.2.113.
    $ echo $HOSTNAME
    myapps.example.com
    $ hostname
    myapps.example.com
    $ uname -n
    myapps.example.com
    The output indicates that the internal logical name remained the same, but the external name has changed as described in the next step.
  2. Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.113
    nslookup 123.1.2.113
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = mynewapps.example.com

    From within the same host

    $ ping $HOSTNAME
    PING myapps.example.com (123.1.2.113) 56(84) bytes of data.
    64 bytes from myapps.example.com (123.1.2.113): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.113 myapps.example.com mynewapps.example.com myapps mynewapps
Perform the following steps to change both the host name and IP address:
Current host name of Apps Tier: myapps.example.com
New host name of Apps Tier: mynewapps.example.com
Current IP address of Apps Tier: 123.1.2.113
Changed IP address of Apps Tier: 123.1.2.114
  1. Update your DNS system to reflect the new host name (myapps.example.com) for the IP address 123.1.2.114.
    $ echo $HOSTNAME
    myapps.example.com
    $ hostname
    myapps.example.com
    $ uname -n
    myapps.example.com
    The output indicates that the internal logical name remained the same, but the external name has changed as described in the next step.
  2. Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.114
    nslookup 123.1.2.114
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = mynewapps.example.com

    From within the same host

    $ ping $HOSTNAME
    PING myapps.example.com (123.1.2.114) 56(84) bytes of data.
    64 bytes from myapps.example.com (123.1.2.114): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.114 myapps.example.com mynewapps.example.com myapps mynewapps
Case 2 (Not Recommended)
  1. Execute a preclone before the host name of the application tier is changed, and a postclone on the application tier after the host name of the application tier is changed on the primary application tier.
  2. The FMW_Home, instance Oracle Home and OraInventory directory must be cleaned up before you execute the postclone script. If other instances are running on the same machine and sharing the same Oracle inventory, use the detachHome script to detach the Oracle Home from the central inventory (rather than removing the complete inventory). Once the primary application tier has been cloned, add all the secondary nodes back into the system using the add node API.
Note: Based on the tasks listed here, this approach is considered a complete reimplementation of the installation. This is not a best practice and is not recommended.

Section 6.2.3: Changing Host Name of Secondary Application Tier Node

Case 1 (Recommended)
  1. Treat the current host name of the secondary application tier node as the logical name of the host.
  2. Change the host name of the server only in DNS for external access.
For example, if the current name of the application tier machine is "secondary.example.com" and you want to change the host name to "newsecondary.example.com"", perform the following steps to change the host name only (the IP address does not change):
Current host name of Apps Tier: secondary.example.com
New host name of Apps Tier: newsecondary.example.com
Current IP address of Apps Tier: 123.1.2.115
  1. Update your DNS system to reflect the new host name (newsecondary.example.com) for the IP address 123.1.2.115.
    $ echo $HOSTNAME
    secondary.example.com
    $ hostname
    secondary.example.com
    $ uname -n
    secondary.example.com
    The output indicates that the internal logical name remained the same, but the external name has changed as described in the next step.
  2. Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.115
    nslookup 123.1.2.115
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = newsecondary.example.com

    From within the same host

    $ ping $HOSTNAME
    PING secondary.example.com (123.1.2.115) 56(84) bytes of data.
    64 bytes from secondary.example.com (123.1.2.115): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.115 secondary.example.com newsecondary.example.com secondary newsecondary
Perform the following steps to change both the host name and IP address:
Current host name of Apps Tier: secondary.example.com
New host name of Apps Tier: newsecondary.example.com
Current IP address of Apps Tier: 123.1.2.115
Changed IP address of Apps Tier: 123.1.2.116
  1. Update your DNS system to reflect the new host name (newsecondary.example.com) for the IP address 123.1.2.116.
    $ echo $HOSTNAME
    secondary.example.com
    $ hostname
    secondary.example.com
    $ uname -n
    secondary.example.com
    The output indicates that the internal logical name remained the same, but the external name has changed as described in the next step.
  2. Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.116
    nslookup 123.1.2.116
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = newsecondary.example.com

    From within the same host:

    $ ping $HOSTNAME
    PING secondary.example.com (123.1.2.116) 56(84) bytes of data.
    64 bytes from secondary.example.com (123.1.2.116): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.116 secondary.example.com newsecondary.example.com secondary newsecondary
Case 2 (Not Recommended)
  1. Perform a delete node action using the delete node API.
  2. Reconfigure the machine to use the new host name and IP address.
  3. Perform an add node action using the add node API.
Note: Based on the tasks listed here, this approach is considered a complete reimplementation of the installation. This is not a best practice and is not recommended.

Section 6.2.4: Changing IP Addresses of Database and Application Tier Nodes

Note: The procedure in this section only applies to single-node systems, and should not be used with Oracle RAC systems.
Changing the IP addresses of the database and application tier nodes involves the following steps:

Section 6.2.4.1: Change IP address of Database Tier Server

Perform the following steps to change the IP address of the database tier server:
  1. Change the DNS record to reflect the IP address for the same host name.  For example:
    Current host name of DB Tier: mydb.example.com
    Current IP address of DB Tier: 123.1.2.111
    Changed IP address of DB Tier: 123.1.2.112
  2. Update your DNS system to reflect the new IP address of 123.1.2.112.Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the database tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.112
    nslookup 123.1.2.112
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = mydb.example.com

    From within the same host

    $ ping $HOSTNAME
    PING mydb.example.com (123.1.2.112) 56(84) bytes of data.
    64 bytes from mydb.example.com (123.1.2.112): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.112 mydb.example.com mydb
  3. Log in to the primary and secondary application tier nodes to ensure that you can ping the database host and it returns the new IP address. Execute a sqlplus command to ensure that SQL*Net connections work without any errors. The hosts file on each of the application tier nodes may also need amendment, depending on how tname resolution is configured in your Oracle E-Business Suite environment.

To change the IP address of the application tier server(s)

Perform the following steps to change the IP address of the application tier server(s):
Current host name of Apps Tier: myapps.example.com
Current IP address of Apps Tier: 123.1.2.113
Changed IP address of Apps Tier: 123.1.2.114
  1. Update your DNS system to reflect the new IP address 123.1.2.114.Run nslookup from an external machine. This should return the new host name of the server so that external machines can talk to the application tier using a well-defined, resolvable address in DNS.
    $ nslookup 123.1.2.114
    nslookup 123.1.2.114
    Server: 123.35.249.41
    Address: 123.35.249.41#53

    Non-authoritative answer:
    76.88.210.10.in-addr.arpa name = myapps.example.com

    From within the same host

    $ ping $HOSTNAME
    PING myapps.example.com (123.1.2.114) 56(84) bytes of data.
    64 bytes from myapps.example.com (123.1.2.114): icmp_seq=1 ttl=64 time=0.020 ms

    /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    123.1.2.114 myapps.example.com myapps
  2. Log in to all the application tier nodes for which the IP address was changed and execute AutoConfig from the run edition file system to complete the configuration.
  3. Log in to the primary and secondary application tier nodes to ensure that you can ping the database host and other application tier nodes. Execute a sqlplus command to ensure that SQL*Net connections work without any errors. The hosts file on each of the application tier nodes may also need amendment, depending on how name resolution is configured in your Oracle E-Business Suite environment.
  4. If you have wired your application tier for which the address was changed to external components, for example a reverse proxy server or a load balancer, the IP information needs to be updated in the external device configuration as well to complete the configuration.

Section 6.3: Scenario 3 - Using Logical Host Names to Enable Oracle WebLogic Administration Server High Availability

The Oracle WebLogic Administration Server cannot be deployed in an active-active configuration. By default, the Administration Server is only available on the first installed node, which is called the primary application tier node. If this node becomes unavailable, you cannot access the Administration Server from Oracle Enterprise Manager Fusion Middleware Control Console, and will potentially be unable to start an online patching cycle. To avoid this scenario, the primary application tier server must have a standby server with the same network configuration. Creating the standby primary application tier server can be done either as part of the disaster recovery setup, or as a local standby.
The high level tasks you need to perform are:
  1. Complete the installation of the primary application tier server and any secondary application tier nodes.
  2. Create a clone of the primary application tier server on an installation using a virtual server environment, such as Oracle VM Server. This can be accomplished on a virtual server environment by cloning the primary application tier guest virtual machine. The cloned VM also needs to be configured with the same host name and IP address. This guest VM will be on a standby mode, and no application tier processes should be brought up unless a failure of the primary application tier node occurs.
  3. If you do not set up a virtual server, configure a secondary physical server with the same host name and IP address. This server will be in a standby mode, and no application tier processes should be brought up unless a failure of the primary application tier node occurs.
  4. Mount the storage that holds the application tier file system on the standby server.
Note: Some installations may require the IP address of the standby server to be different from the primary application tier. This is allowed, based on your DNS setup, but the host name should remain the same.
Configuring a secondary application tier node as a primary node in case of the primary application tier node failure is not supported at present.

Change Log

at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Database Options/Management Packs Usage Reporting for Oracle Databases 11.2 and later (Doc ID 1317265.1)

  Database Options/Management Packs Usage Report You can determine whether an option is currently in use in a database by running options_pa...