5 Next Steps After Configuring the Domain

The topics in this section describe common tasks you might want to perform on a newly created product domain.

5.1 Performing Basic Administrative Tasks

Administering an Oracle Business Intelligence system involves the following tasks:
Task Description
Configuring a system for deployment after installation Configuring metadata and content, general preferences, and default system settings.
Starting and stopping the system when required Bringing the system up and down during system maintenance tasks.
Configuring security Securing access to the Oracle Business Intelligence system, metadata, and data, configuring Secure Sockets Layer (SSL) and Single Sign-On (SSO), and integration with identity management systems.
Scaling out and configuring for high availability Configuring the Oracle Business Intelligence system for linear scale-out (increasing capacity with more components on a machine) and identifying and removing single points of failure (adding more machines).
Managing performance and availability Monitoring service levels and tuning performance.
Managing and resolving issues Diagnosing errors and establishing resolutions.
Moving a system from test to production Managing the steps for moving from a test to a production environment.
Backing up and recovering data Preparing for and recovering from unexpected events.

For more information, see "Getting Started with Managing Oracle Business Intelligence" in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

5.2 Performing Additional Domain Configuration Tasks

Table 5-1 lists additional tasks you will likely want to perform on your new domain.

Table 5-1 Additional Domain Configuration Tasks

Task Description More Information

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 Installing and Configuring Oracle HTTP Server.

Also, see "Installing Multiple Products in the Same Domain" in Planning an Installation of Oracle Fusion Middlewarefor important information.

5.3 Preparing Your Environment for High Availability

Table 5-2 lists tasks to perform if you want to scale out your standard installation environment for high availability.

Table 5-2 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 consumers of your deployed applications.

See "Scaling Your Deployment" in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Configuring high availability for Web Tier components

If you added a Web Tier front-end, you must configure it for high availability, and the WebLogic Server software.

See "Configuring High Availability for Web Tier Components" in High Availability Guide.

Configuring high availability for Oracle BI components To configure Oracle BI for high availability, you must 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 type, 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.

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" and "Configure Load Balancer" in High Availability Guide.

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 apparent performance of the system for users, particularly for commonly used dashboards, but 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.

Configuring Node Manager

Node Manager enables you to start, shut down, and restart the Administration Server and Managed Servers from a remote location. The Configuration Assistant creates a per domain Node Manager.

For information on advanced Node Manager configuration options and features, see Administering Node Manager for Oracle WebLogic Server.