Configure Virtual Hosts For the site to function properly with the load Create boot.properties File Create a boot.properties file for the

Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-37 ■ User Name : cn=orcladmin ■ Password : Password for Oracle Internet Directory’s orcladmin account

12. In the Summary screen, click Install to begin the creation process.

14.6.4.4 Validation

Validate the initial installation by performing the following tests:

14.6.4.5 Generic Configuration

The following steps are required regardless of the product being configured:

14.6.4.5.1 Set Admin Server Listen Address In servers where multiple network cards

exist, it is important to bind the Administration Server to the network card that you wish to use. To do this:

1. Log in to the WebLogic Console using the URL

http:apphost1.mycompany.com:7001console

2. In the Domain Structure menu, select Environment, and then Servers.

3. Click AdminServer admin

4. In the Change Center, click Lock Edit.

5. Set the listen address to the DNS name referring to the network card you wish to

use. This is generally the public server name.

6. Click Save.

7. Click Activate Changes from the change center.

8. Stop the Administration Server using the stopWebLogic.sh script, located in the

DOMAIN_HOMEbin directory. Start the Administration Server using the startWebLogic.sh script, also located in DOMAIN_HOMEbin directory.

14.6.4.5.2 Configure Virtual Hosts For the site to function properly with the load

balancer, you must add two virtual hosts. You can configure the virtual hosts using Oracle Enterprise Manager Fusion Middleware Control, or you can edit the file ORACLE_INSTANCEconfigOHSohs1httpd.conf or create a file called virtual_ hosts.conf in the directory ORACLE_INSTANCEconfigOHSohs1moduleconf. To add two virtual hosts to the virtual_hosts.conf file, in a text editor, add the following entries to the file: NameVirtualHost :7778 VirtualHost :7778 ServerName http:mysite.mycompany.com:80 Test URL Result Portal http:apphost1.mycompany.com:7777portalplsportal Portal Home page opens Forms http:apphost1.mycompany.com:7777formsfrmservlet Forms Servlet Home page opens Reports http:apphost1.mycompany.com:7777reportsrwservletsh owjobs Job Queue opens Discoverer http:apphost1.mycompany.com:7777discovererviewer Discoverer Viewer Home page opens 14-38 Oracle Fusion Middleware High Availability Guide RewriteEngine On RewriteOptions inherit UseCanonicalName On VirtualHost VirtualHost :7778 ServerName apphost1.mycompany.com:7777 RewriteEngine On RewriteOptions inherit UseCanonicalName On VirtualHost Restart the Web Tier using these commands: opmnctl stopall opmnctl startall

14.6.4.5.3 Create boot.properties File Create a boot.properties file for the

Administration Server on APPHOST1. The boot.properties file enables the Administration Server to start without prompting you for the administrator username and password. In a text editor, create a file called boot.properties in the directory DOM_ HOMEserversAdminServersecurity, and enter the following lines in the file: username=adminuser password=password Restarting the Administration Server encrypts the values in this file, for that reason it is recommended that the Administration Server is restarted on each node that can host it. Stop the Administration Server using the script stopWebLogic.sh, which is located in DOMAIN_HOMEbin, or by using the script startWebLogic, also located in DOMAIN_HOMEbin.

14.6.4.5.4 Configure sqlnet.ora Create a file called sqlnet.ora in the directory