ERPI Deployed on Weblogic: Multiple Sets of ODI Scenarios Are Triggered When Running a Single ERPI Data Load Rule From FDM
Posted by Priya Doyle on 04 February 2011 12:33 PM
Applies to:Hyperion Financial Data Quality Management - Version: 188.8.131.52.00
Oracle Weblogic Server - Version: 8.1 to 9.2]
Oracle Data Integrator - Version: 10.1.3.5.0 and later [Release: 10gR3 and later]
Information in this document applies to any platform.
1. IIS HTTP Server
Locate the iisproxy.ini file for ERPI on the IIS web server. The exact location of this file depends on how you initially configured the WebLogic plugin. See this document for more information:
Once you have located it, add the two following option to the iisproxy.ini file:
The WLIOTimeoutSecs option defines the amount of time the WebLogic plug-in waits for a response to a request from WebLogic Server. The plug-in waits for 'HungServerRecoverSecs' for the server to respond and then declares that server dead. The value should be set to a value larger than the time the ERPI data load rule takes to execute. The above example shows a setting of 30 minutes (1800 seconds).
2. Apache HTTP Server
Increase the timeout setting in the HYSL-Weblogic.conf file located in %HYPERION_HOME%\common\httpServers\Apache\<version>
This sets the timeout to 1800 seconds or 30 minutes.
NOTE:1050602.1 - Workspace/Planning/Business Rules Deployed on WebLogic Timing Out