Setting the Listen Address for the bi_server2 Managed Server Disabling Host Name Verification for the bi_server2 Managed Server
6.4.1 Setting the Listen Address for the bi_server2 Managed Server
Ensure that you have performed the steps described in Section 2.2.3.1, Enabling Virtual IPs for the Managed Servers before setting the bi_server2 listen address. Perform these steps to set the listen address for the Managed Server: 1. Log in to the Oracle WebLogic Server Administration Console.2. In the Change Center, click Lock Edit.
3. Expand the Environment node in the Domain Structure window.
4. Click Servers. The Summary of Servers page is displayed.
5. Select bi_server2 in the Names column of the table. The settings page for bi_
server2 is displayed.6. Set the Listen Address to APPHOST2VHN1.
7. Click Save.
8. Click Activate Changes.
The changes will not take effect until the bi_server2 Managed Server is restarted.6.4.2 Disabling Host Name Verification for the bi_server2 Managed Server
This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server see Chapter 7, Setting Up Node Manager . If you have not configured the server certificates, you will receive errors when managing the different Oracle WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again after the EDG topology configuration is complete as described in Chapter 7, Setting Up Node Manager. Perform these steps to disable host name verification: 1. Log in to the Administration Console.2. In the Change Center, click Lock Edit.
3. Expand the Environment node in the Domain Structure window.
4. Click Servers. The Summary of Servers page is displayed.
5. Select bi_server2 in the Names column of the table. The settings page for the
server is displayed. 6. Open the SSL tab.7. Expand the Advanced section of the page.
8. Set host name verification to None.9. Click Save.
10. Click Activate Changes.
11. The change will not take effect until the bi_server2 Managed Server is restarted ensure that Node Manager is up and running: Scaling Out the Oracle Business Intelligence System 6-7a. In the Summary of Servers screen, select the Control tab.
Parts
» Oracle Fusion Middleware Online Documentation Library
» What Is an Enterprise Deployment? Terminology
» Load Balancer Requirements Web Tier
» Oracle Identity Management Application Tier
» Data Tier What to Install Unicast Requirement
» Database Host Requirements Supported Database Versions Database Services
» Loading the Oracle Business Intelligence Schemas in the Oracle RAC Database
» Load Balancers Network Environment Preconfiguration
» On the appropriate host APPHOST1 or APPHOST2, run the ifconfig command
» Firewalls and Ports Network Environment Preconfiguration
» Terminology for Directories and Directory Environment Variables
» Recommended Locations for the Different Directories
» Hardware Requirements Clock Synchronization Software Installation Summary
» Creating a Domain and the bi_server1 Managed Server on APPHOST1
» Enabling ADMINVHN on APPHOST1
» Using the Configuration Assistant to Scale Out the BI System
» Additional Configuration Tasks for Oracle BI Scheduler
» Starting the Oracle Business Intelligence System Components
» About Setting Up Node Manager Changing the Location of the Node Manager Log
» Generating Self-Signed Certificates Using the utils.CertGen Utility
» Enabling Host Name Verification Certificates Editing the Node Manager Properties File
» Overview of Credential and Policy Store Configuration Configuring the Policy Store
» About User GUIDs About GUID Regeneration
» About Oracle Access Manager Integration Updating the Host Identifier
» Updating the WebGate Profile
» Installing and Configuring WebGate
Show more