Scaling Out the Oracle Business Intelligence System 6-9
RTD Batch Manager service must be stopped and restarted. To do this, follow these steps:
1. In Fusion Middleware Control, expand the WebLogic Domain node in the left
pane. Then, right-click bifoundation_domain and select System MBean Browser. 2.
Locate the BatchManager MBean, under either Application Defined MBeans OracleRTD Server:bi_server1 Server
or under Application Defined MBeans OracleRTD Server:bi_server2 Server
. It should be in one of these locations, but not both.
3. Locate the corresponding MBean attribute BatchManagerEnabled under
SDPropertyManager Misc
. For example, if the BatchManager MBean is located
in bi_server1, then select Application Defined MBeans OracleRTD Server:bi_ server1 SDPropertyManager Misc : BatchManagerEnabled
.
4. Set the BatchManagerEnabled attribute to false and click Apply.
5. Set the BatchManagerEnabled attribute back to true and click Apply. Performing
this task causes the Batch Manager to stop and be restarted. When it restarts, it will be running on either the same server as before, or on a
different server.
6.
After restarting Batch Manager, note that the corresponding MBean does not always immediately get refreshed on the server where Batch Manager comes back
up, so this is not a concern. Instead, verify that Batch Manager is now operational by using the Batch Console tool, as follows:
a.
Locate the zip file for the Oracle RTD client tools in the following location: ORACLE_HOMEclientsrtdrtd_client_11.1.1.zip
b.
Because most Oracle RTD client tools do not run on UNIX, unzip this file in a location on a Windows computer referred to here as RTD_HOME. Then,
locate the batch console jar file in:
RTD_HOME clientBatchbatch-console.jar
c.
Change to this directory and execute the jar, passing to it the URL and port of either the Managed Server, or of the cluster proxy:
java -jar batch-console.jar -url http:SERVER:PORT
d.
When prompted, enter the user name and password of a user who is a member of the Administrator role, BI_Adminstrator role, or some other role
authorized to administer Oracle RTD batch jobs.
e.
When prompted for a command, enter bn: Checking server connection...
command: bn CrossSellSelectOffers
command:quit If Batch Manager has successfully restarted, then the bn command lists the
names of all batch implementations hosted by all deployed RTD Inline Services.
The commonly deployed example, CrossSell, hosts a batch implementation named CrossSellSelectOffers, shown in the preceding example.
6-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
6.5.3 Additional Configuration Tasks for Oracle BI Publisher
This section contains the following topics:
■
Section 6.5.3.1, Setting the Location of the Shared Oracle BI Publisher Configuration Folder
■
Section 6.5.3.2, Setting Scheduler Configuration Options
■
Section 6.5.3.3, Configuring Integration with Oracle BI Presentation Services
■
Section 6.5.3.4, Setting the Oracle BI EE Data Source
■
Section 6.5.3.5, Configuring JMS for Oracle BI Publisher
■
Section 6.5.3.6, Updating the Oracle BI Publisher Scheduler Configuration
6.5.3.1 Setting the Location of the Shared Oracle BI Publisher Configuration Folder
Follow these steps to set server configuration options for Oracle BI Publisher:
1.
Copy the contents of the DOMAIN_HOMEconfigbipublisherrepository directory to the shared configuration folder location.
2.
On either APPHOST1 or APPHOST2, log in to BI Publisher with Administrator credentials and select the Administration tab.
3. Under System Maintenance, select Server Configuration.
4. In the Path field under Configuration Folder, enter the shared location for the
Configuration Folder.
5.
Apply your changes and restart your BI Publisher application, as follows:
a.
Log in to the Administration Console.
b. Click Deployments in the Domain Structure window.
c. Select bipublisher11.1.1.
d. Click Stop.
e. After the application has stopped, click Start.
6.
Because Oracle BI Publisher reads its configuration from the Administration Server central location rather than from the Managed Servers configuration
directory when the Managed Servers are restarted, you must copy the XML configuration file for Oracle BI Publisher from the Managed Server to the
Administration Server location.
To do this, on APPHOST1, copy the file xmlp-server-config.xml from: ORACLE_BASE
admindomain_namemserverdomain_nameconfigbipublisher to:
ORACLE_BASE admindomain_nameaserverdomain_nameconfigbipublisher
6.5.3.2 Setting Scheduler Configuration Options
Follow these steps to set Scheduler configuration options:
1.
On APPHOST1, log in to BI Publisher with Administrator credentials and select the Administration tab.
2. Under System Maintenance, select Scheduler Configuration.
3. Select Quartz Clustering under the Scheduler Selection.
