In the Change Center, click Lock Edit to enable configuration changes. Click domain_name, then Security, then General, and then expand the Click Save. Click Activate Changes.

5-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence 1. Log into the Administration Console.

2. In the Domain Structure window, expand the Services node and then click the

Persistent Stores node. The Summary of Persistent Stores page is displayed.

3. In the Change Center, click Lock Edit.

4. Click BipJmsStore and enter a directory that is located in the shared storage. This

shared storage is accessible from both APPHOST1 and APPHOST2: ORACLE_BASEadmindomain_namebi_clusterjms

5. Click Save and then click Activate Changes.

6. The changes will not take effect until the Managed Server is restarted. Restart the Managed Server.

5.3 Creating boot.properties for the Administration Server on APPHOST1

Create a boot.properties file for the Administration Server on APPHOST1. This file enables the Administration Server to start without prompting you for the administrator username and password. 1. Go to the following directory: ORACLE_BASE admindomain_nameaserverdomain_nameserversAdminServersecurity 2. In this directory, create a file called boot.properties using a text editor and enter the following lines in the file: username=Admin_Username password=Admin_Password 3. Save the file and close the editor.

5.4 Starting the Administration Server on APPHOST1

The Administration Server is started and stopped using Node Manager. However, the first start of the Administration Server with Node Manager requires changing the default username and password that the Configuration Assistant set for Node Manager. Follow these steps to start the Administration Server using Node Manager: 1. Use the Administration Console to update the Node Manager credentials: a. Open a Web browser and go to http:APPHOST1:7001console. b. Log in as the administrator.

c. In the Change Center, click Lock Edit to enable configuration changes.

d. Click domain_name, then Security, then General, and then expand the

Advanced options at the bottom. Note: When you start the Administration Server, the username and password entries in the file get encrypted. You start the Administration Server in Section 5.4, Starting the Administration Server on APPHOST1. For security reasons, you want to minimize the time the entries in the file are left unencrypted. After you edit the file, you should start the server as soon as possible so that the entries get encrypted. Creating a Domain with the Administration Server and First Managed Server 5-5 e. Enter a new username for Node Manager, or make a note of the existing one and update the Node Manager password.

f. Click Save.

g. Click Activate Changes.

2. Stop the Administration Server process using one of the following methods: ■ Use Ctrl+C in the shell where it was started ■ Use the standard process identification and kill commands in the operating system ■ Log in to the Administration Console and click Servers under the Environment heading, then click the Control tab. Select AdminServeradmin and click Shutdown. 3. Stop and restart Node Manager and enable dynamic registration, as follows: a. Stop the running NodeManager process. b. Run the setNMProps.sh script, which is located in the ORACLE_COMMON_ HOMEcommonbin directory, to set the StartScriptEnabled property to true before starting Node Manager: APPHOST1 cd ORACLE_COMMON_HOMEcommonbin APPHOST1 .setNMProps.sh c. Restart Node Manager and enable dynamic registration using the following commands: APPHOST1 cd WL_HOMEserverbin APPHOST1 export JAVA_OPTIONS=-DDomainRegistrationEnabled=true APPHOST1 .startNodeManager.sh 4. Start the Oracle WebLogic Scripting Tool WLST and connect to Node Manager with nmconnect and the credentials set in step 1, and start the Administration Server using nmstart: APPHOST1 cd ORACLE_COMMON_HOMEcommonbin APPHOST1 .wlst.sh In the WLST shell, execute the following command: wls:offlinenmConnectAdmin_User,Admin_Pasword, APPHOST1,9556, domain_name,Domain_Home wls:nmdomain_name nmStartAdminServer Note: You must use the StartScriptEnabled property to avoid class loading failures. Note: It is important that you set -DDomainRegistrationEnabled=true whenever you start a Node Manager which must manage the Administration Server. If there is no Administration Server on this computer, and if this computer is not an Administration Server failover node, then Node Manager can be started as follows: APPHOST1 .startNodeManager.sh 5-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence For example: wls:offlinenmConnectweblogic, my_password, APPHOST1 , 9556, bifoundation_domain ,u01apporacleadminbifoundation_domainaserver bifoundation_domain wls:nmbifoundation_domain nmStartAdminServer

5.5 Enabling Administration Server High Availability