5 Next Steps After Configuring the Domain

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

• Performing Basic Administrative Tasks
  After you configure your new domain, there are administration tasks that Oracle recommends you perform on the domain.
• Performing Additional Domain Configuration Tasks
  Review additional configuration tasks you will likely want to perform on a new domain.
• Preparing Your Environment for High Availability
  Scaling out for high availability requires additional steps.

Performing Basic Administrative Tasks

After you configure your new domain, there are administration tasks that Oracle recommends you perform on the domain.

The following table lists common administration tasks to perform on your new domain.

Table 5-1 Basic Administration Tasks for a New Domain

Task	Description	More Information
Getting familiar with Fusion Middleware administration tools	Get familiar with various tools that you can use to manage your environment.	See 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.	See Starting and Stopping Oracle Fusion Middleware in Administering Oracle Fusion Middleware.
Configuring Secure Sockets Layer (SSL)	Learn how to set up secure communications between Oracle Fusion Middleware components using SSL.	See Configuring SSL in Oracle Fusion Middleware 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 recommended backup and recovery procedures for Oracle Fusion Middleware.	See Introducing Backup and Recovery in Administering Oracle Fusion Middleware.

Performing Additional Domain Configuration Tasks

Review additional configuration tasks you will likely want to perform on a new domain.

Table 5-2 Additional Domain Configuration Tasks

Task	Description	More Information
Deploying Applications	Learn how to deploy your applications to Oracle Fusion Middleware.	See Deploying Applications in Administering Oracle Fusion Middleware.
Adding a Web Tier front-end to your domain	Oracle Web Tier hosts Web pages (static and dynamic), provides security and high performance along with built-in clustering, load balancing, and failover features. In particular, the Web Tier contains Oracle HTTP Server.	To install and configure Oracle HTTP Server in the WebLogic Server domain, see Configuring Oracle HTTP Server in a WebLogic Server Domain in Installing and Configuring Oracle HTTP Server. See also Installing Multiple Products in the Same Domain for important information.
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.	For more information about Coherence clusters, 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.

Preparing Your Environment for High Availability

Scaling out for high availability requires additional steps.

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

Table 5-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 the 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 High Availability Guide.
Setting up a front-end load balancer	A load balancer can be used to distribute requests across servers more evenly.	See Server Load Balancing in a High Availability Environment and Configuring Load Balancer Virtual Server Names and Ports 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.
Configuring high availability for Oracle BI components	To configure Oracle BI for high availability, ensure that the system has no single points of failure by scaling out the Oracle BI Server, Presentation Services, and the JavaHost so that you have at least two of each component types, distributed across at least two computers.	See Deploying Oracle Business Intelligence for High Availability in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Managing performance tuning and query caching	For Oracle BI Server database queries to return quickly, the underlying databases must be configured, tuned, and indexed correctly. The BI Server can store query results for reuse by subsequent queries. Query caching can dramatically improve the performance of the system for users, particularly for commonly used dashboards. However, it does not improve performance for most ad-hoc analysis.	See Managing Performance Tuning and Query Caching in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.