12 Enterprise Deployments

This chapter provides an overview of the Oracle Application Server recommended enterprise deployments. The topics include:

• Introduction to Oracle Application Server Enterprise Deployments

• Standard Enterprise Deployment for J2EE Applications

• Standard Enterprise Deployment for Portal Applications

12.1 Introduction to Oracle Application Server Enterprise Deployments

The Oracle Application Server enterprise deployment is a configuration that supports large-scale, mission-critical business software applications. The hardware and software in an enterprise deployment delivers the following:

• High quality service:

  • The system workload is managed and balanced effectively.

  • Applications continue to operate when hardware and other resources are added or removed.

  • System maintenance and unexpected failures cause zero downtime.

• Built-in security:

  • All incoming network traffic is received by the load balancing router on a single, secure port and directed to internal IP addresses within the firewall; inside the firewall, functional components are grouped within DMZs.

  • User accounts are provisioned and managed centrally

  • Delegation of administration is performed consistently

  • Security systems are integrated

• Efficient software provisioning and management:

  • Application distribution is simple.

  • Systems are managed and monitored as one logical unit in a central console.

  • Death detection and restart mechanisms ensure availability.

12.2 Standard Enterprise Deployment for J2EE Applications

Figure 12-1 illustrate the enterprise deployment architecture for J2EE applications.

Figure 12-1 Enterprise Deployment Architecture for myJ2EECompany.com

Description of the illustration myj2ee.gif

In the J2EE application enterprise deployment architecture, users access the application through an HTTPS connection to the load balancer for myapp.mycompany.com in the demilitarized zone (DMZ), behind the first firewall. The load balancer accesses OracleAS Web Cache and Oracle HTTP Server instances in the Web tier to route requests through the second firewall to available OracleAS Containers for J2EE (OC4J) instances in the application tier.

As needed, the application tier servers access the data tier through a third firewall. The data tier contains the Oracle Application Server Infrastructure as well as any the customer database.

See Also: Oracle Application Server Enterprise Deployment Guide for detailed information about the enterprise deployment architecture for J2EE applications

12.3 Standard Enterprise Deployment for Portal Applications

Figure 12-1 illustrate the enterprise deployment architecture for OracleAS Portal applications.

Figure 12-2 Enterprise Deployment Architecture for myPortalCompany.com

Description of the illustration myportal.gif

In the OracleAS Portal enterprise deployment architecture, users access the application through an HTTPS connection to the load balancers in the demilitarized zone (DMZ), behind the first firewall. If the user needs to log in, the request will go to login.mycompany.com. If not, the request will go to portal.mycompany.com.

The portal.mycompany.com load balancer routes requests to one of two OracleAS Web Cache servers, which are part of the two application middle tiers deployed in the DMZ.

The login.mycompany.com load balancer routes requests to one of the two Oracle HTTP Servers, which are part of the two Identity Management middle tiers, also deployed in the DMZ.

The middle tier deployments in the DMZ access the data tier through a firewall. The data tier contains a two-node RAC database installation, one for the security infrastructure metadata repository and one for the application metadata repository. The data tier also contains two Oracle Internet Directory standalone servers, which also access the security infrastructure metadata repository.

See Also: Oracle Application Server Enterprise Deployment Guide for detailed information about the enterprise deployment architecture for Portal applications