Choosing Single or Multiple-Machine Configurations

2-16 Publishing Reports to the Web with Oracle Reports Services

2.5 Setting Up a High Availability Environment

11g Release 1 11.1.1 provides numerous high availability HA enhancements, as listed in Table 2–1 in Section 2.1, What’s New In This Release? . This section discusses the following topics pertinent to establishing a high availability environment: ■ Maintaining High Availability ■ Configuring the rwservlet.properties file ■ Configuring Reports Server for High Availability

2.5.1 Maintaining High Availability

Oracle Fusion Middleware consists of many components that can be deployed in distributed topologies. The underlying paradigm used to enable high availability for Oracle Fusion Middleware is clustering, which unites various Oracle Fusion Middleware components in certain permutations to offer scalable and unified functionality, and redundancy should any of the individual components fail.

2.5.2 Configuring the rwservlet.properties file

Perform the following steps to configure the rwservlet.properties file: 1. Make sure that the in-process server has a unique name. You can check the server sub-element of the rwservlet.properties to verify the unique server name. 2. Configure cluster in the rwservlet.properties file. cluster clustername=ha_cluster clusternodes=ha_server2 cluster name should be same in all rwservlet.properties files. Cluster nodes should include in-process server names which are part of the cluster except the current one. More than one server should be separated by a colon. 3. Save the servlet configuration file. Alternatively, you can configure a cluster through Oracle Enterprise Manager: 1. Navigate to the Reports Application Home Page in Enterprise Manager.

2. From the Reports menu, select System MBean Browser.

The System MBean Browser page is displayed. 3. From the left content pane, expand Application Defined MBeans oracle.reportsApp.config Server: WLS_REPORTS Application: reports ReportsApp .

4. Select rwservlet from the list.

The Application Defined MBeans: Report sApp:rwservlet page is displayed. 5. Click the Operations tab. 6. Select addCluster. Note: Refer to the Oracle Fusion Middleware Enterprise Deployment Guide for Java EE and Oracle Fusion Middleware High Availability Guide for more information on the various solutions and techniques to achieve high availability in Oracle Fusion Middleware. Understanding the Oracle Reports Services Architecture 2-17 The Operation:addCluster page is displayed. 7. Enter valid values in the Cluster Name and Node fields. 8. Click Invoke. For more information about the rwservlet.properties file, refer to Section 8.3.1.1, rwservlet

2.5.3 Configuring Reports Server for High Availability

To configure Reports Server for high availability by using the database as the job repository, perform the following steps for each instance: 1. Configure the database job repository for in-process Reports Servers in all instances in the rwserver.conf file of all Reports Servers. Note that in 11g Release 1 11.1.1 the server configuration file must correspond to the rwserverconf.xsd file refer to Section 8.2.1, Reports Server Configuration Elements , which means that the order in which different entries appear inside the server configuration file is no longer random, but fixed by the XSD. As a result, the following element must be added immediately before the connection element in the server configuration file: jobRepository property name=dbuser value=dbuser property name=dbpassword value=csf:reports:dbpasswdKey property name=dbconn value=dbconn jobRepository For information about adding a password key in the credential store, see Section 15.1.4, Credential Store . 2. Save the server configuration file. Alternatively, you can configure the database job repository through Oracle Enterprise Manager: a. Navigate to the Reports Application home page in Enterprise Manager.

b. From the Reports menu, select Administration Advanced Configuration.

The Reports Application Advanced Configuration page is displayed. c. Locate the Job Repository content pane in the Advanced Configuration page. d. Select the Enable Job Repository DB checkbox. e. Enter valid values in the Username, Password Key and Database fields. f. Click Apply. 3. Configure a folder to which all instances have access write access is needed, read access is not enough by adding the CacheDir or JOCCacheDir property to the cache element of each of the server configuration files, For example, on Windows: property name=JOCCacheDir value=folder_name property name=CacheDir value=folder_name on UNIX: property name=JOCCacheDir value=netmachine_nameusrstmp