Optimizing the Deployment of Reports

Configuring Oracle Reports Services 8-81 ■ Callback timeout Reports Server-side: Callback timeout is the measure that Reports Server uses to determine the time that it must wait for a response from the engine before timing out. You can specify this value in the rwserver.conf file. This time out period is in milliseconds. For example: engine id=rwEng class=oracle.reports.engine.EngineImpl initEngine=1 maxEngine=1 minEngine=0 engLife=50 maxIdle=30 callbackTimeOut=90000

8.12 Sample system-jazn-data.xml File

The system-jazn-data.xml is an XML file which is configured by the user to use as an ID store andor policy store. The file is located in DOMAIN_ HOMEconfigfmwconfig. Sample system-jazn-data.xml file: ?xml version=1.0 encoding=UTF-8 standalone=no? jazn-data jazn-realm realm namejazn.comname users user nameweblogicname guid23AAB190021911DDBF86C74F01C202FBguid credentialsPN0Qr+dpDRV+jSWP378EdjxWDS0PuAs=credentials user users realm jazn-realm policy-store applications application namereportsname app-roles app-role namerw_administratorname display-nameReports Administratordisplay-name classoracle.security.jps.service.policystore.ApplicationRoleclass members member classoracle.security.jps.internal.core.principals.JpsXmlUserImplclass nameweblogicname member member class weblogic.security.principal.WLSUserImpl class nameweblogicname member members app-role app-role namerw_operatorname Note: Increase the callbackTimeOut value when the machine is very slow. 8-82 Publishing Reports to the Web with Oracle Reports Services display-nameReports Operatordisplay-name classoracle.security.jps.service.policystore.ApplicationRoleclass app-role app-role namerw_monitorname display-nameReports Monitordisplay-name classoracle.security.jps.service.policystore.ApplicationRoleclass app-role app-roles jazn-policy grant grantee principals principal classoracle.security.jps.service.policystore.ApplicationRoleclass namerw_administratorname principal principals grantee permissions permission classoracle.reports.server.ReportsPermissionclass namereport= server= destype= desformat= allowcustomargs=truename actionsactions permission permission classoracle.reports.server.WebCommandPermissionclass namewebcommands= server=name actionsexecuteactions permission permissions grant grant grantee principals principal classoracle.security.jps.service.policystore.ApplicationRoleclass nameRW_BASIC_USERname principal principals grantee permissions permission classoracle.reports.server.ReportsPermissionclass namereport=test.rdf server= destype= desformat= allowcustomargs=truename actionsactions permission permission classoracle.reports.server.WebCommandPermissionclass namewebcommands=showmyjobs,getjobid,showjobid server=name actionsexecuteactions permission permissions grant 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.