4-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
■
Instance Name: webn
■
OHS Component Name: ohsn where n is a sequential number for your installation; for example, 1 for
WEBHOST1, 2 for WEBHOST2, and so on.
Click Next. 6.
In high-availability implementations, although it is not mandatory, it is simpler if all ports used by the various components are synchronized across hosts. You can
bypass automatic port configuration by specifying the ports you want to use in a file.
In the Configure Ports screen, select a file name and then click ViewEdit. The file looks similar to the following:
[OHS] Listen port for OHS component
OHS Port = 7777
[OPMN] Process Manager Local port no
OPMN Local Port = 1880
You can find a sample staticports.ini file in the Disk1stageResponse directory.
Click Next. 7.
In the Specify Security Updates screen, choose whether you want to receive security updates from Oracle support and if you do, enter your e-mail address.
8.
In the Installation Summary screen, review the selections to ensure they are correct. If they are not, click Back to modify selections on previous screens. When
you are ready, click Configure.
9.
Multiple configuration assistants are launched in succession; this process can be lengthy. When it completes, click Next, and the Installation Complete screen
appears.
10. In the Installation Complete screen, click Finish to exit.
4.2 Validating the Installation
After the installation is complete, check that it is possible to access the Oracle HTTP Server home page using the following URLs:
http:webhost1.mycompany.com:7777 http:webhost2.mycompany.com:7777
4.3 Configuring Oracle HTTP Server with the Load Balancer
Configure your load balancer to route all HTTP requests to the hosts running Oracle HTTP Server WEBHOST1, WEBHOST2. You do not need to enable sticky sessions
insert cookie on the load balancer when Oracle HTTP Server is front-ending Oracle WebLogic Server. You need sticky sessions if you are going directly from the load
balancer to Oracle WebLogic Server, which is not the case in the topology described in this guide. Also, you should set monitors for HTTP.
Configuring the Web Tier 4-3
4.4 Configuring Virtual Hosts
For Oracle Business Intelligence to work with the load balancer, a virtual host must be created in the Oracle HTTP Server configuration. Edit the httpd.conf file located at
ORACLE_INSTANCEconfigOHScomponent_name and add the following virtual host sections:
NameVirtualHost :7777 VirtualHost :7777
ServerName https:bi.mycompany.com:443 RewriteEngine On
RewriteOptions inherit VirtualHost
NameVirtualHost :7777 VirtualHost :7777
ServerName admin.mycompany.com:80 ServerAdmin youyour.address
RewriteEngine On RewriteOptions inherit
VirtualHost NameVirtualHost :7777
VirtualHost :7777
ServerName biinternal.mycompany.com:80 ServerAdmin youyour.address
RewriteEngine On RewriteOptions inherit
VirtualHost
After modifying the httpd.conf file, you must restart both Oracle HTTP Servers, as follows:
WEBHOST cd ORACLE_BASEadmininstance_namebin WEBHOST opmnctl stopall
WEBHOST opmnctl startall
Access the following URLs to ensure that your load balancer and Oracle HTTP Server are configured properly:
■
http:bi.mycompany.comindex.html
■
http:admin.mycompany.comindex.html
■
http:biinternal.mycompany.comindex.html
Note: Perform this step for both WEBHOST1 and WEBHOST2.
4-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
5
Creating a Domain with the Administration Server and First Managed Server 5-1
5
Creating a Domain with the Administration Server and First Managed Server
This chapter describes how to create a domain and the first Oracle Business Intelligence Managed Server using the Oracle Business Intelligence Configuration
Assistant, Oracle WebLogic Server Administration Console, and Oracle Enterprise Manager Fusion Middleware Control. Later, you will scale out the domain to add
additional components. This is addressed in later chapters in this document.
This chapter contains the following topics:
■
Section 5.1, Creating a Domain and the bi_server1 Managed Server on APPHOST1
■
Section 5.2, Configuring JMS for Oracle BI Publisher
■
Section 5.3, Creating boot.properties for the Administration Server on APPHOST1
■
Section 5.4, Starting the Administration Server on APPHOST1
■
Section 5.5, Enabling Administration Server High Availability
■
Section 5.6, Validating the Administration Server
■
Section 5.7, Setting the Listen Address for bi_server1 Managed Server
■
Section 5.8, Disabling Host Name Verification for the bi_server1 Managed Server
■
Section 5.9, Validating Oracle Business Intelligence on APPHOST1
■
Section 5.10, Configuring Oracle HTTP Server
■
Section 5.11, Registering Oracle HTTP Server with Oracle WebLogic Server
■
Section 5.12, Setting the Frontend URL for the Administration Console
■
Section 5.13, Validating Access Through Oracle HTTP Server
■
Section 5.14, Manually Failing Over the Administration Server to APPHOST2
■
Section 5.15, Backing Up the Installation
Important: Oracle strongly recommends that you read Oracle
Fusion Middleware Release Notes for any additional installation and deployment considerations before starting the setup process.
5-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
5.1 Creating a Domain and the bi_server1 Managed Server on APPHOST1
