Sample system-jazn-data.xml File

Configuring Oracle Reports Services 8-83 jazn-policy application applications policy-store

8.13 Configuring Reports Managed Server

By default, the Oracle Reports application is deployed on a Managed Server. You can modify the start-up properties of a Reports Managed Server through the SetDomainEnv.sh file or the WebLogic Server Administration Console. However, some properties like -Xmx and -Xms, which are already defined in the setDomainEnv.sh file would take precedence and the changes made through the WebLogic Server Administration Console do not take effect. Also, the start-up properties of WLS_REPORTS that are modified using the WebLogic Server Administration Console do not take effect when WLS_REPORTS is started using startManagedServer.sh. Hence it is recommended that you use SetDomainEnv.sh for UNIX or SetDomainEnv.bat for Windows to modify the start-up properties for Managed Servers. You can modify the system or runtime properties for a Managed Server using the SetDomainEnv.sh for UNIX or SetDomainEnv.bat for Windows which is located in DOMAIN_HOMEbin. You can modify the runtime properties using the EXTRA_JAVA_PROPERTIES variable inside the [ {SERVER_NAME} = WLS_REPORTS ] block. You must add any new environment variable for WLS_REPORTS Managed Server inside the if[ {SERVER_NAME} = WLS_REPORTS ] block in the SetDomainEnv.sh script. As the default setting is done for all components that use setDomainEnv.sh, the -Xmx and -Xms settings are added multiple times to the command line of a Managed Server. Hence you must add the -Xmx and -Xms settings at the end of EXTRA_JAVA_PROPERTIES variable in the [ {SERVER_NAME} = WLS_ REPORTS ] block. For example, consider the following snippet: if [ {SERVER_NAME} = WLS_REPORTS ] ; then EXTRA_JAVA_PROPERTIES=-Xms256m Xmx512m ... -Doracle.home=fmwhomeas1 ... {EXTRA_JAVA_PROPERTIES} If you want to add the -Djobid=random property and change the -Xmx and -Xms settings for WLS_REPORTS to 512m and 1024m, you must modify the snippet as follows: if [ {SERVER_NAME} = WLS_REPORTS ] ; then EXTRA_JAVA_PROPERTIES= -Doracle.home=fmwhomeas1 ... {EXTRA_JAVA_ PROPERTIES} -Xms512m -Xmx1024m -Djobid=random Note: WLS_REPORTS is the name of the Managed Server where the Reports application is deployed during installation. For expand cluster cases, Managed Servers can be named as WLS_REPORTS1, WLS_REPORTS2, and so on. 8-84 Publishing Reports to the Web with Oracle Reports Services

8.14 Enabling HTTPS for Oracle Reports

For enabling HTTPS for Oracle Reports, the WebLogic Plug-In Enabled option in the WebLogic Administration Console should be selected for the WLS_REPORTS server by performing the following steps: 1. Log in to the WebLogic Administration Console.

2. If you have not already done so, in the Change Center pane, click Lock Edit.

3. In the Domain Structure pane, expand the Environment node, and select Servers.

A list of servers configured in the domain is displayed.

4. Click the WLS_REPORTS server.

5. Expand the Advanced link near the bottom of the page.

6. Select the WebLogic Plug-In Enabled option.

7. Click Save.

Part III Part III Managing Runtime Behavior Part III contains information that will help you to manage the runtime behavior of Oracle Reports: ■ Chapter 9, Managing Fonts in Oracle Reports ■ Chapter 10, Printing on UNIX with Oracle Reports ■ Chapter 11, Using PDF in Oracle Reports ■ Chapter 12, Font Model and Cross-Platform Deployment ■ Chapter 13, Configuring Destinations for Oracle Reports Services ■ Chapter 14, Configuring and Using the Pluggable Data sources ■ Chapter 15, Securing Oracle Reports Services ■ Chapter 17, Configuring and Administering OracleAS Single Sign-On ■ Chapter 16, Deploying Reports in Oracle Portal