1. Installing and Configuring Oracle HTTP Server
  2. Next Steps After Configuring the Domain

6 Next Steps After Configuring the Domain

After you configure a product domain, there are additional tasks that you may want to perform.

Next Steps for Oracle HTTP Server in a WebLogic Server Domain

After configuring Oracle HTTP Server in a WebLogic Server domain, there are additional tasks that you may want to perform.

Note:

A WebLogic Server domain can be scaled out to multiple physical machines and be centrally managed by the administration server. See Oracle HTTP Server Release Topologies in Administering Oracle HTTP Server.

Table 6-1 Basic Administration Tasks for Oracle HTTP Server in a WebLogic Server Domain

Task Description More Information

Getting familiar with Fusion Middleware administration tools
Get familiar with the various tools available, which you can use to manage your environment.

Note:

The WebLogic Server Administration Console has been removed. For comparable functionality, you will use the WebLogic Remote Console.

See:

Oracle HTTP Server Directory Structure in a Collocated Domain

Oracle HTTP Server Directory Structure in a Standalone Domain

Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.

Starting and stopping products and servers
Learn how to start and stop Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components.

Note:

Depending on your existing security settings, you may need to perform additional configuration before you can manage a domain with secured production mode enabled. For more information, see Connecting to the Administration Server using WebLogic Remote Console.

See Starting and Stopping Oracle Fusion Middleware in Administering Oracle Fusion Middleware.

Configuring Secure Sockets Layer (SSL)

Learn how to set up secure communications among between Oracle Fusion Middleware components using SSL.

See Configuring SSL in Oracle Fusion Middleware in Administering Oracle Fusion Middleware.

Deploying Applications

Learn how to deploy your applications to Oracle Fusion Middleware.

See Deploying Applications in Administering Oracle Fusion Middleware.

Monitoring Oracle Fusion Middleware

Learn how to keep track of the status of Oracle Fusion Middleware components.

See Monitoring Oracle Fusion Middleware in Administering Oracle Fusion Middleware.

Understanding Backup and Recovery Procedures

Learn the recommended backup and recovery procedures for Oracle Fusion Middleware.

See Introducing Backup and Recovery in Administering Oracle Fusion Middleware.

Tuning and configuring Coherence for your topology.

The standard installation topology includes a Coherence cluster that contains storage-enabled Managed Coherence Servers. This configuration is a good starting point for using Coherence, but depending upon your specific requirements, consider tuning and reconfiguring Coherence to improve performance in a production environment.

See Configuring and Managing Coherence Clusters in Administering Clusters for Oracle WebLogic Server.

For information on tuning Coherence, see Performance Tuning in Administering Oracle Coherence.

For information on storing HTTP session data in Coherence, see Using Coherence Web with WebLogic Server in Administering HTTP Session Management with Oracle Coherence*Web.

For more about creating and deploying Coherence applications, see Getting Started in Developing Oracle Coherence Applications for Oracle WebLogic Server.

Wiring Oracle HTTP Server to the Administration Server.

Learn how to connect Oracle HTTP Server to the Administration Server so that you can access Fusion Middleware Control Console through the Oracle HTTP Server.

See Wiring Oracle HTTP Server to the Administration Server in Administering Oracle Fusion Middleware.

Routing Applications Through Oracle HTTP Server to Oracle WebLogic Server.

Perform these steps to connect Oracle HTTP Server so that requests are routed through Oracle HTTP Server to Oracle WebLogic Server

See Routing Applications Through Oracle HTTP Server to Oracle WebLogic Server in Administering Oracle Fusion Middleware.

Routing requests to managed servers in a WebLogic Server domain

Learn how to configure Oracle WebLogic Server Proxy Plug-In to proxy requests from Oracle HTTP Server to Oracle WebLogic Server.

See Configuring the Plug-In for Oracle HTTP Server.

Next Steps for Oracle HTTP Server in a Standalone Domain

After configuring Oracle HTTP Server in a standalone domain, there are additional tasks that you may want to perform.

Table 6-2 Basic Administration Tasks for Oracle HTTP Server in a Standalone Domain

Task Description More Information

Getting familiar with Oracle HTTP Server management tools

Get familiar with the various tools available, which you can use to manage your environment.

See Understanding Oracle HTTP Server Management Tools in Administering Oracle HTTP Server.

Starting and stopping Oracle HTTP Server instances

Learn how to start and stop Oracle HTTP Server instances in a standalone domain.

See Performing Basic Oracle HTTP Server Tasks in Administering Oracle HTTP Server.

Routing requests to managed servers in a WebLogic Server domain

Learn how to configure Oracle WebLogic Server Proxy Plug-In to proxy requests from Oracle HTTP Server to Oracle WebLogic Server.

See Configuring the Oracle WebLogic Server Proxy Plug-In Manually.

Preparing Your Environment for High Availability

Scaling out for high availability requires additional steps.

Table 6-3 provides a list of tasks to perform if you want to scale out your standard installation environment for high availability.

Note:

BAM domains that were created using WLST, and will be used in a high availability configuration, require additional provisioning scripts after the installation. The default / internal Data Objects are missing in BAM Composer when the domain is created using WLST and the scripts provide the pre-seeded data that is required for high availability BAM domains. For more information, My Oracle Support document ID 2190789.1.

.

Table 6-3 Tasks Required to Prepare Your Environment for High Availability

Task Description More Information

Scaling out to multiple host computers

To enable high availability, it is important to provide failover capabilities to another host computer. That way, if one computer goes down, your environment can continue to serve the consumers of your deployed applications.

See Scaling Out a Topology (Machine Scale Out) in High Availability Guide.

Configuring high availability for your Web Tier components.

If you have added a Web tier front-end, then you must configure the Web Tier for high availability, as well as the WebLogic Server software.

See Configuring High Availability for Web Tier Components in HTTP Server Administration Guide.

Setting up a front-end load balancer

You can use a load balancer to distribute requests across servers more evenly.

See Server Load Balancing in a High Availability Environment in High Availability Guide.

Configuring Node Manager

Node Manager enables you to start, shut down, and restart the Administration Server and Managed Server instances from a remote location. This document assumes you have configured a per-domain Node Manager. Review the Node Manager documentation, for information on advanced Node Manager configuration options and features.

See Advanced Node Manager Configuration in Administering Node Manager for Oracle WebLogic Server.