|
Oracle® Application Server Installation Guide
10g Release 3 (10.1.3) for Microsoft Windows B14438-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Installation Guide
10g Release 3 (10.1.3) for Microsoft Windows B14438-01 |
|
|
Previous |
Next |
This chapter describes what is contained in Oracle Application Server and recommended topologies. It contains the following sections:
Oracle Application Server is made up of a middle tier and OracleAS Infrastructure. You deploy and run your applications on the middle tiers. The infrastructure provides services that are used by middle tiers. These services can be shared by one or more middle tiers.
Oracle Application Server 10g Release 3 (10.1.3) provides a complete Java 2, Enterprise Edition (J2EE) 1.4-compliant environment. Specifically, this release provides a new version of Oracle Containers for J2EE (OC4J). OC4J provides all the containers, APIs, and services mandated by the J2EE specification. This release is designed for administrators who are using OC4J to deploy and manage J2EE applications.
In addition to OC4J, this release also includes new releases of Oracle HTTP Server, Oracle Process Manager and Notification Server (OPMN), and Oracle Enterprise Manager 10g Application Server Control Console.
You can integrate Oracle Application Server 10g Release 3 (10.1.3) with an existing Oracle Application Server environment that includes 10g (9.0.4) or 10g Release 2 (10.1.2) OracleAS Infrastructure, 10g Release 2 (10.1.2) Oracle HTTP Server, or 10g Release 2 (10.1.2) OracleAS Web Cache components.
|
See Also: Oracle Application Server Upgrade and Compatibility Guide for more information about which specific versions are compatible with 10g Release 3 (10.1.3) |
Table 1-1 summarizes the groups of services available with each installation type.
Table 1-1 Oracle Application Server 10g Release 3 (10.1.3) Install Types
| Install Mode | Available Installation Types |
|---|---|
|
Basic |
|
|
Advanced |
|
|
See Also: Oracle TopLink documentation for further information about the Oracle TopLink advanced installation option |
The basic (one-click) installation prompts you with questions on the initial installation screen, and then it proceeds to install the product without any further user interaction. The default values for all the components are used.
The advanced installation provides you with a great degree of customization and flexibility, which enables installation of additional languages, port configuration options, and cluster configuration.
Table 1-2 summarizes the differences in the customization options between basic and advanced installation.
Table 1-2 Basic and Advanced Installation Features
| Action or Option | Basic | Advanced |
|---|---|---|
|
Specify an Oracle Home |
Yes |
Yes |
|
Specify an instance name and |
Yes |
Yes |
|
Select additional languages |
No |
Yes |
|
Specify automatic or manual port configuration |
No |
Yes |
|
Configure Application Server Control |
No |
Yes |
|
Specify default OC4J instance name |
No |
Yes |
|
Configure instance to be part of a cluster |
No |
Yes |
|
Configuration assistants |
Yes |
Yes |
Table 1-3 provides a road map of where to find information about the supported 10g Release 3 (10.1.3) topologies.
Table 1-3 Basic and Advanced Installation Features
| Topology | See This Documentation for Details |
|---|---|
|
|
|
|
A middle tier containing an integrated OC4J instance with Oracle HTTP Server in one Oracle home |
Section 1.3.1, "Installing an Integrated Web Server and OC4J Middle Tier" |
|
Two middle tiers containing an integrated OC4J instance with Oracle HTTP Server in two separate Oracle homes. You establish an OracleAS Clusters configuration for these middle tiers and designate one of the OC4J instances as the Administration OC4J instance for running the Application Server Control Console. You then manage both OC4J instances from this instance of Application Server Control Console. |
Section 1.3.2, "Installing Multiple Integrated Web Server and OC4J Middle Tiers" |
|
Two middle tiers, one containing Oracle HTTP Server and the second containing an OC4J instance |
Section 1.3.3, "Installing a Web Server Middle Tier and OC4J Middle Tier on Separate Hosts" |
|
Three middle tiers, one containing Oracle HTTP Server and two containing OC4J instances. You establish an OracleAS Clusters configuration for the OC4J instances and designate one of the OC4J instances as the Administration OC4J instance for running the Application Server Control Console. You then manage both OC4J instances from this instance of Application Server Control Console. |
Section 1.3.4, "Installing a Web Server Middle Tier and Multiple OC4J Middle Tiers" |
|
An enterprise data center for J2EE applications that use Oracle Application Server Java Authentication and Authorization Service (JAAS) Provider LDAP for user authentication. This topology contains four middle tiers, two containing Oracle HTTP Servers and two containing OC4J instances. In this configuration, Application Server Control Console is available on its own OC4J Web site. A firewall separates the Oracle HTTP Servers from the OC4J instances. |
"myJ2EE," in the Oracle Application Server Enterprise Deployment Guide |
|
|
|
|
An OracleAS Clusters configuration in which two or more middle-tier instances serve the same content. A load balancer distributes requests equally among the active instances. |
Section 6.2, "Creating the Active-Active Topology" |
|
An Oracle Application Server Cold Failover Clusters configuration in which two or more middle-tier instances serve the same content, but only instance is active at any one time. |
Section 6.3, "Creating the Active-Passive Topology" |
|
An OracleAS Disaster Recovery configuration in which a standby site mirrors a production site. During normal operation, the production site handles all the requests. If the production site goes down, the standby site takes over and handles all the requests. |
Section 6.4, "Creating an OracleAS Disaster Recovery Configuration" |
|
10.1.3 Middle Tiers with Existing 9.0.4 or 10.1.2 Environments
|
|
|
10.1.2 Oracle HTTP Server: Two middle tiers, one containing 10g Release 2 (10.1.2) Oracle HTTP Server and OracleAS Web Cache components and the second containing a 10g Release 3 (10.1.3) OC4J instance. Oracle HTTP Server and OracleAS Web Cache are installed as a part of a J2EE and Web Cache middle-tier installation. |
"Configuring Oracle Application Server 10.1.2 with Oracle Application Server 10.1.3" in the Oracle Application Server Administrator's Guide |
|
9.0.4 or 10.1.2 OracleAS Infrastructure: A 10g Release 3 (10.1.3) middle-tier instance using a 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle Identity Management. This topology also supports associating a 10g Release 3 (10.1.3) middle-tier instance with a new 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle Identity Management for the following scenarios:
|
"Configuring Instances to Use a 10.1.2 or 9.0.4 Oracle Identity Management" in the Oracle Application Server Administrator's Guide "Moving 10.1.2 or 9.0.4 Identity Management to a New Host" in the Oracle Application Server Administrator's Guide "Changing from a Test to a Production Environment" in the Oracle Application Server Administrator's Guide |
|
10.1.2 OracleAS Web Cache Instance: A single 10g Release 2 (10.1.2) OracleAS Web Cache acting as a reverse proxy for a 10g Release 2 (10.1.3) middle-tier. The middle tier contains an integrated OC4J instance with Oracle HTTP Server. |
"Configuring 10.1.2 OracleAS Web Cache as a Reverse Proxy" in the Oracle Application Server Administrator's Guide |
|
10.1.2 OracleAS Web Cache Cluster: Two or more 10g Release 2 (10.1.2) OracleAS Web Cache servers configured as a cluster to reverse proxy a 10g Release 2 (10.1.3) middle-tier. The middle tier contains an integrated OC4J instance with Oracle HTTP Server. |
"Configuring 10.1.2 OracleAS Web Cache as a Reverse Proxy" in the Oracle Application Server Administrator's Guide |
The remainder of this section addresses the recommended topologies for installing Oracle HTTP Server and OC4J instances. It contains the following topics:
Section 1.3.1, "Installing an Integrated Web Server and OC4J Middle Tier"
Section 1.3.2, "Installing Multiple Integrated Web Server and OC4J Middle Tiers"
Section 1.3.3, "Installing a Web Server Middle Tier and OC4J Middle Tier on Separate Hosts"
Section 1.3.4, "Installing a Web Server Middle Tier and Multiple OC4J Middle Tiers"
The Basic Installation Mode combines an Oracle HTTP Server and OC4J middle-tier instance in the same Oracle home, as depicted in Figure 1-1. This topology enables you to use OPMN to manage a standalone OC4J instance.
Figure 1-1 Integrated Web Server and OC4J Middle Tier
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
Perform a basic installation, as described in Section 4.2.2, "Installation Steps".
This topology builds upon the example in the previous section, Section 1.3.1. It adds an additional combined Oracle HTTP Server and OC4J middle-tier instance, as shown in Figure 1-2. When you install this cluster topology, you install two middle-tier instances in two different Oracle homes. During installation of the two instances, you cluster the instances using dynamic node discovery. You designate one of the OC4J instances as the Administration OC4J instance for running the Application Server Control Console. You manage both OC4J instances from this instance of Application Server Control Console. This topology provides a highly available environment for testing and production purposes.
Figure 1-2 Cluster with Integrated Web Server and OC4J Middle Tiers
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
To install this topology:
For the first middle tier, install an Administration OC4J instance.
Perform an Integrated Web Server, J2EE Server and Process Management advanced installation, as described in Section 5.2.4, "Installing Integrated Web Server, J2EE Server and Process Management". During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, select Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a password for the oc4jadmin account in the Administrator Account Password fields. Enter a name for the default OC4J instance, such as home, in the OC4J Instance Name field.
Make a note of the OC4J instance name and the password you enter here; you will need them later.
In the Cluster Topology Configuration screen, select Configure this instance to be part of an Oracle Application Server cluster topology and specify a cluster discovery address for the cluster. The multicast address you enter must be within the valid address range, which is 224.0.0.1 to 239.255.255.255.
Make a note of the address and port that you enter on this page; you will need them later.
For the second middle tier, perform an Integrated Web Server, J2EE Server and Process Management advanced installation, as described in Section 5.2.4, "Installing Integrated Web Server, J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, deselect Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a password for the oc4jadmin account in the Administrator Account Password fields. Enter a name for the OC4J instance, such as home, in the OC4J Instance Name field.
If you want this OC4J instance to be part of the same group, specify the same name for the OC4J that you specified in Step 1 of this procedure. Similarly, enter the same password for the Administrator Account Password that you entered in Step 1 of this procedure.
Assigning multiple OC4J instances the same instance name during installation forms a group, making it easy to deploy applications to more than one OC4J instance at time. You can simultaneously execute specific configuration operations on all OC4J instances in a group.
In order to use a group, each OC4J instance in a group must also have the same oc4jadmin password. If they do not, then you will have to reset the password after the installation.
In the Cluster Topology Configuration screen, select Configure this instance to be part of an Oracle Application Server cluster topology and specify the same cluster discovery address as you specified in Step 1 of this procedure.
|
See Also:
|
For larger application deployments spanning three or more nodes, consider your performance and security needs. One strategy is to install and dedicate one node to exclusively run Application Server Control Console and install the other nodes to support applications. To install for this strategy:
For the first middle tier, install an Administration OC4J instance.
Perform an Integrated Web Server, J2EE Server and Process Management advanced installation, as described in Section 5.2.4, "Installing Integrated Web Server, J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, select Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a password for the oc4jadmin account in the Administrator Account Password fields. Enter a unique name for this OC4J instance, such as AdminOC4J, in the OC4J Instance Name field.
In the Cluster Topology Configuration screen, select Configure this instance to be part of an Oracle Application Server cluster topology and specify a cluster discovery address for the cluster. The multicast address you enter must be within the valid address range, which is 224.0.0.1 to 239.255.255.255.
Make a note of the address and port that you enter on this page; you will need them later.
For the second middle tier, perform an Integrated Web Server, J2EE Server and Process Management advanced installation, as described in Section 5.2.4, "Installing Integrated Web Server, J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, deselect Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a password for the oc4jadmin account in the Administrator Account Password fields. Enter a name for the default OC4J instance, such as home, in the OC4J Instance Name field that is different than the one you specified in Step 1 of this procedure.
Make a note of the OC4J instance name and the password you enter here; you will need them later.
In the Cluster Topology Configuration screen, select Configure this instance to be part of an Oracle Application Server cluster topology and specify the same cluster discovery address as you specified in Step 1 of this procedure.
For the additional middle tiers, perform an Integrated Web Server, J2EE Server and Process Management advanced installation, as described in Section 5.2.4, "Installing Integrated Web Server, J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, deselect Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter the same password for the oc4jadmin account in the Administrator Account Password field and instance name in the OC4J Instance Name fields as you specified in Step 2 of this procedure.
Assigning multiple OC4J instances the same instance name during installation forms a group, making it easy to deploy applications to more than one OC4J instance at time. You can simultaneously execute specific configuration operations on all OC4J instances in a group.
In order to use a group, each OC4J instance in a group must also have the same oc4jadmin password. If they do not, then you will have to reset the password after the installation.
In the Cluster Topology Configuration screen, select Configure this instance to be part of an Oracle Application Server cluster topology and specify the same cluster discovery address as you specified in Step 1 of this procedure.
Figure 1-3 shows a topology in which you install Oracle HTTP Server on one computer, and install the OC4J instance on another computer. Then, you cluster the instances using dynamic node discovery. This topology enables Oracle HTTP Server to route requests to OC4J, and OC4J to dynamically notify Oracle HTTP Server of new application bindings when an application is deployed.
Figure 1-3 Cluster with a Web Server Middle Tier and OC4J Middle Tier on Separate Hosts
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
To install this topology:
For the first middle tier, perform a Web Server and Process Management advanced installation, as described in Section 5.2.3, "Installing Web Server and Process Management".
During the installation procedure, follow the prompts. In the Cluster Topology Configuration screen, select Configure this HTTP Server instance to be part of an Oracle Application Server cluster topology and specify a cluster discovery address for the cluster.
For the second middle tier, perform a J2EE Server and Process Management advanced installation, as described in Section 5.2.2, "Installing J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, select Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a name for the OC4J instance, such as home, in the OC4J Instance Name field.
In the Cluster Topology Configuration screen, select Configure this OC4J Server instance to be part of an Oracle Application Server cluster topology and specify the same cluster discovery address as you specified in Step 1 of this procedure.
|
See Also: "Configuring a Web Server and J2EE on Separate Hosts," in the Oracle Application Server Administrator's Guide for further information about configuring this topology |
This topology builds upon the example in the previous section, Section 1.3.3. It adds an additional OC4J middle-tier instance, as shown in Figure 1-4. When you install this cluster topology, you install Oracle HTTP Server on one computer, install OC4J instances on two separate computers, and specify cluster settings. You designate one of the OC4J instances as the Administration OC4J instance for running the Application Server Control Console. You manage both OC4J instances from this instance of Application Server Control Console. This topology provides a highly available environment for testing and production purposes.
This topology also supports using a firewall to separate Oracle HTTP Server from the OC4J instances, as shown in Figure 1-5.
Figure 1-4 Cluster with a Web Server Middle Tier and Multiple OC4J Middle Tiers
Figure 1-5 Cluster with a Web Server Middle Tier and Multiple OC4J Middle Tiers Separated by a Firewall
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
To install this topology:
For the Oracle HTTP Server middle tier, perform a Web Server and Process Management advanced installation, as described in Section 5.2.3, "Installing Web Server and Process Management".
During the installation procedure, follow the prompts. In the Cluster Topology Configuration screen, select Configure this HTTP Server instance to be part of an Oracle Application Server cluster topology and specify a cluster discovery address for the cluster. The multicast address you enter must be within the valid address range, which is 224.0.0.1 to 239.255.255.255.
Make a note of the address and port that you enter on this page; you will need them later.
For the first OC4J middle tier, install an Administration OC4J instance.
Perform a J2EE Server and Process Management advanced installation, as described in Section 5.2.2, "Installing J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, select Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a name for the default OC4J instance, such as home, in the OC4J Instance Name field.
Make a note of the OC4J instance name and the password you enter here; you will need them later
In the Cluster Topology Configuration screen, select Configure this OC4J instance to be part of an Oracle Application Server cluster topology and specify the same cluster discovery address as you specified in Step 1 of this procedure.
For the second OC4J middle tier, perform a J2EE Server and Process Management advanced installation, as described in Section 5.2.2, "Installing J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, deselect Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter the same OC4J instance name in the OC4J Instance Name field as you specified in Step 2 of this procedure.
In the Administration Settings page, enter a password for the oc4jadmin account in the Administrator Account Password fields. Enter a name for the OC4J instance, such as home, in the OC4J Instance Name field.
If you want this OC4J instance to be part of the same group, specify the same name for the OC4J that you specified in Step 2 of this procedure. Similarly, enter the same password for the Administrator Account Password that you entered in Step 2 of this procedure.
Assigning multiple OC4J instances the same instance name during installation forms a group, making it easy to deploy applications to more than one OC4J instance at time. You can simultaneously execute specific configuration operations on all OC4J instances in a group.
In order to use a group, each OC4J instance in a group must also have the same oc4jadmin password. If they do not, then you will have to reset the password after the installation.
In the Cluster Topology Configuration screen, select Configure this OC4J instance to be part of an Oracle Application Server cluster topology, specify the same cluster discovery address as you specified in Step 2 of this procedure.
|
See Also:
|
For larger application deployments spanning three or more nodes, consider your performance and security needs. One strategy is to install and dedicate one node to exclusively run Application Server Control Console and install the other nodes to support applications. To install for this strategy:
For the Oracle HTTP Server middle tier, perform a Web Server and Process Management advanced installation, as described in Section 5.2.3, "Installing Web Server and Process Management".
During the installation procedure, follow the prompts. In the Cluster Topology Configuration screen, deselect Configure this HTTP Server instance to be part of an Oracle Application Server cluster topology and specify a cluster discovery address for the cluster. The multicast address you enter must be within the valid address range, which is 224.0.0.1 to 239.255.255.255.
Make a note of the address and port that you enter on this page; you will need them later.
For the first OC4J middle tier, install an Administration OC4J instance.
Perform a J2EE Server and Process Management advanced installation, as described in Section 5.2.2, "Installing J2EE Server and Process Management". During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, select Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a password for the oc4jadmin account in the Administrator Account Password fields. Enter a unique name for this OC4J instance, such as AdminOC4J, in the OC4J Instance Name field.
In the Cluster Topology Configuration screen, select Configure this OC4J instance to be part of an Oracle Application Server cluster topology and specify the same cluster discovery address as you specified in Step 1 of this procedure.
|
See Also: "Publishing Application Server Control Console to a Separate Web Site" in the Oracle Application Server Administrator's Guide for instructions on making Application Server Control Console accessible on a separate Web site |
For the second OC4J middle tier, perform a J2EE Server and Process Management advanced installation, as described in Section 5.2.2, "Installing J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, deselect Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter a password for the oc4jadmin account in the Administrator Account Password fields. Enter a name for the default OC4J instance, such as home, in the OC4J Instance Name field that is different than the one you specified in Step 2 of this procedure.
Make a note of the OC4J instance name and the password you enter here; you will need them later.
In the Cluster Topology Configuration screen, select Configure this OC4J instance to be part of an Oracle Application Server cluster topology, specify the same cluster discovery address as you specified in Step 1 of this procedure.
For the additional OC4J middle tiers, perform a J2EE Server and Process Management advanced installation, as described in Section 5.2.2, "Installing J2EE Server and Process Management".
During the installation procedure, follow the prompts, ensuring you perform the following:
In the Administration Instance Settings page, deselect Configure this as an Administration OC4J Instance.
In the Administration Settings page, enter the same password for the oc4jadmin account in the Administrator Account Password field and instance name in the OC4J Instance Name fields as you specified in Step 3 of this procedure.
Assigning multiple OC4J instances the same instance name during installation forms a group, making it easy to deploy applications to more than one OC4J instance at time. You can simultaneously execute specific configuration operations on all OC4J instances in a group.
In order to use a group, each OC4J instance in a group must also have the same oc4jadmin password. If they do not, then you will have to reset the password after the installation.
In the Cluster Topology Configuration screen, select Configure this OC4J instance to be part of an Oracle Application Server cluster topology, specify the same cluster discovery address as you specified in Step 1 of this procedure.
