8-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
1.
Log in to the Administration Console http:Host:Admin_Portconsole. Typically, Admin_Port is 7001 by default.
2. In the Domain Structure window, expand Environment and select Clusters. The
Summary of Clusters page is displayed.
3.
Click the cluster for which you want to configure migration bi_cluster in the Name column of the table.
4. Click the Migration tab.
5. In the Change Center, click Lock Edit.
6. In the Available field, select the machine to which to allow migration and click the
right arrow. In this case, select APPHOST1 and APPHOST2. 7.
Select the data source to be used for automatic migration. In this case, select the leasing data source.
8. Click Save.
9. Click Activate Changes.
10.
Set the candidate machines for server migration. You must perform this task for all of the Managed Servers as follows:
a.
In the Domain Structure window of the Administration Console, expand Environment
and select Servers.
b.
Click the server for which you want to configure migration.
c. Click the Migration tab.
d. In the Change Center, click Lock Edit.
e. In the Migration Configuration section, for Candidate Machines, select the
machines to which you want to enable migration and click the right arrow. For bi_server1
, select APPHOST2. For bi_server2, select APPHOST1. f.
Select Automatic Server Migration Enabled. This enables Node Manager to start a failed server on the target node automatically.
g. Click Save.
h. Click Activate Changes.
i.
Restart the Administration Server, Node Managers, Managed Servers, and the system components for which server migration has been configured.
8.7 Testing the Server Migration
The eighth and final step is to test the server migration. Perform these steps to verify that server migration is working properly:
From APPHOST1: 1.
Stop the bi_server1 Managed Server. To do this, run this command: APPHOST1 kill -9 pid
Tip: Click Customize this table in the Summary of Servers page and
move Current Machine from the Available window to the Chosen window to view the machine on which the server is running. This will
be different from the configuration if the server gets migrated automatically.
Configuring Server Migration 8-7
where pid specifies the process ID of the Managed Server. You can identify the pid in the node by running this command:
HOST1 ps -ef | grep bi_server1
2.
Watch the Node Manager console. You should see a message indicating that bi_ server1s floating IP has been disabled.
3.
Wait for Node Manager to try a second restart of bi_server1. It waits for a fence period of 30 seconds before trying this restart.
4.
After Node Manager restarts the server, stop it again. Node Manager should now log a message indicating that the server will not be restarted again locally.
From APPHOST2: 1.
Watch the local Node Manager console. After 30 seconds since the last try to restart bi_server1 on node 1, Node Manager on node 2 should prompt that the
floating IP for bi_server1 is being brought up and that the server is being restarted in this node.
2.
Access one of the applications for example, BI Publisher using the same IP.
Verification From the Administration Console Migration can also be verified in the Administration Console:
1.
Log in to the Administration Console.
2. Click Domain on the left console.
3. Click the Monitoring tab and then the Migration subtab.
The Migration Status table provides information on the status of the migration, as shown in
Figure 8–1 .
Figure 8–1 Migration Status Table in the Administration Console
8-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
Note: After a server is migrated, to fail it back to its original
nodecomputer, stop the Managed Server from the Administration Console and then start it again. The appropriate Node Manager will
start the Managed Server on the computer to which it was originally assigned.
9
Integrating with Oracle Identity Management 9-1
9
Integrating with Oracle Identity Management
This chapter describes how to integrate Oracle Business Intelligence with Oracle Identity Management.
Before you perform the steps in this chapter, you must have successfully completed the installation and configuration steps described in both of the following:
■
Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management
■
The previous chapters of this guide
This chapter contains the following topics:
■
Section 9.1, Configuring the Credential and Policy Store
