This chapter includes the following sections:
You can improve system performance by passing properties to Oracle WebLogic Server that specify how long a SOAP request waits for a response from the Oracle BI Server before timing out.
Pass the following properties to Oracle WebLogic Server to tune how long a SOAP request waits for a response from Oracle BI Server before timing out. Note that the initial recommended setting is approximately 60 seconds. The value that you specify should always be less than what is configured for stuck thread detection in Weblogic Server.
For more information about configuring stuck thread detection, see "Tuning the Stuck Thread Detection Behavior" in Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server.
For more information, see "Examples of Timeout Settings".
The following examples show how to set the timeout value to 60 seconds.
commEnv.cmd set CONFIG_JVM_ARGS=-Dsun.net.client.defaultReadTimeout=60000 -Dsun.net.client.defaultConnectTimeout=6000
commEnv.s setenv CONFIG_JVM_ARGS -Dsun.net.client.defaultReadTimeout=60000 -Dsun.net.client.defaultConnectTimeout=60
The Oracle BI ADF integration code supports automatically closing sessions when the ADF HTTP session is closed or times out.
Use the following procedure to modify the application's weblogic.xml so that the application automatically closes.
In JDeveloper, go to the Application Navigator, open the Projects tab, navigate to the project's WEB-INF subdirectory, and open the weblogic.xml document.
Add the following to the document:
<listener> <listener-class>oracle.bi.presentation.listener.BIADFServletSessionListener </listener-class> </listener>
Use the following procedure to specify static resources preferences for a saved Oracle BI Presentation Services connection.
For information about setting up static resources in Oracle BI EE, see "Improving Oracle BI Web Client Performance" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
For information about creating a new connection and specifying static resources, see "Creating an Oracle BI EE Presentation Services Connection".
In JDeveloper, go to either the Application Resources tab within the Application Navigator or to the Resource Palette and select the Oracle BI Presentation Services connection that you want to modify.
Right-mouse click the selected data connection and select Properties. The Edit BI Presentation Services Connection wizard displays.
In the BI Presentation Services page, specify the static resources settings. Note the following fields:
Static Resources Mode– Specify from where to retrieve static resources.
Select Auto to direct all requests to Oracle BI Presentation Services rather than to the Oracle BI proxy. Selecting Auto results in a significant increase in performance. Note that Auto mode provides the best performance if Oracle WebLogic Server resides behind Oracle HTTP Server or Apache HTTP Server and you are bypassing Oracle WebLogic Server for serving static files.
Select Manual to direct requests to another location. If you select Manual, you must specify a URL in the Static Resources Location field.
Click Finish to save your changes.
Use the following procedure to test that your static resources location settings (URL) are valid.
Create an application that uses the Oracle BI Presentation Services connection in which you specified static resources settings.
From the data connection, browse for an analysis and drag and drop it onto a .jspx page.
Save the application.
Deploy and run the application.
Using a tool such as Firebug, validate that requests for .js and .png files are loaded directly from the static resource URL that you specified in the connection. Note that if you receive 404 (or Not Found) error messages that you have specified an invalid URL in your static resources settings.