Bookshelf Home | Contents | Index | PDF |
Siebel Reports Guide > Administering Siebel Reports > Optimizing the Performance of Siebel Reports > Optimizing Reports That Include Thousands of RecordsThis topic describes how you can optimize performance for reports that include a lot of records, such as 10,000 records. CAUTION: It is recommended that you do the work that this topic describes on a separate, named subsystem that only the XMLP Report server component uses. For example, reportsdatascr. If you do not do this, then the Application Object Manager (AOM) on the client might fail if it gets a large amount of data. If a report includes a lot of records, then it is recommended that the user schedule this report to run on the Oracle BI Publisher Server. It is recommended that the user run this report immediately. For more information, see Scheduling Reports. Modifying the HTTP Sleep TimeThe integration from Siebel CRM to Oracle BI Publisher uses an outbound Web service call that calls the PublicReportServiceService Web service on the Oracle BI Publisher Server. The outbound Web service uses the EAI HTTP Transport business service to send the HTTP request for this call. Siebel CRM sets the HTTPSleepTime argument of this business service to two minutes (120000 milliseconds), by default. If a report requires over two minutes to finish, and if you do not schedule this report, then the report times out and Siebel CRM adds an entry that is similar to the following error message. It adds this message in the XMLPReportServer .log file: SBL-EAI-04311: Operation 'runReport' is expecting a response but no response was received. This error typically occurs only with a large or complex report, and it does not occur if you schedule the report. To avoid this error, you can increase the default sleep time for the EAI HTTP Transport business service so that the EAI component keeps the HTTP requests that are open through the Outbound Web Service long enough so that Siebel CRM can finish running the report. To modify the sleep time for all reports
Using the Business Service Simulator to Test the Sleep Time for a Single ReportYou can use the Business Service Simulator to test the timeout for a single report without affecting other reports. You can use it to do a variety of tasks, such as to run a workflow process that creates a report. You can test the sleep time for a single report only through the XMLP Driver Service business service. For more information about using a business service, see , and . To use the Business Service Simulator to test the sleep time for a single report
Setting Server ParametersThis topic describes how to set server parameters. This task is a step in Optimizing Reports That Include Thousands of Records and is applicable with a connected client. To set server profile parameters Preloading the Siebel Repository FileThis topic describes how to preload the Siebel Repository File. It is recommended to preload the Siebel Repository File during start up instead of loading it each time a report is generated. This task is a step in Optimizing Reports That Include Thousands of Records and is applicable with a connected client. To preload the Siebel Repository File
Enabling Scalable ModeThis topic describes how to set the scalable mode for all reports. Setting the scalable mode prepares the BI Publisher-FO Processor to handle a large amount of data, longer processing times, time-outs, and so on. Scalable mode is slower than nonscalable mode but it makes sure data loss does not occur even with a large, complex report. It is recommended that you enable scalable mode only if many users must access the same, large report at the same time. Scalable mode consumes more resources and might degrade performance. If your deployment commonly uses large reports, then it is recommended that you set the scalable mode for all reports. For information about the BI Publisher-FO Processor, see Overview of How Siebel CRM Runs Reports in Clients.
Configuring a Temporary FolderYou can configure a temporary folder that Siebel CRM can use if you run a large number of reports. To configure a temporary folder
Increasing Memory for the Java Virtual MachineThe Java virtual machine heap is the area of memory that the Java Virtual Memory uses for dynamic memory. If users must run a report that includes a large data set, then the WebLogic process might consume too much Java Virtual Memory. To avoid a reports failure, you can increase the allocation that the Java Virtual Memory uses for the WebLogic process. To increase memory for the Java Virtual Machine
|
Siebel Reports Guide | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |