Modifying Default Timeout Settings for Lifecycle Management

If you are using Oracle Hyperion Enterprise Performance Management System Lifecycle Management to import large models, the import may take longer to process than the time specified in the default timeout settings on the Oracle WebLogic Server.

To work around this issue, you must reset the default timeout settings.

To modify the default timeout for WebLogic Server:

1. Navigate to

   %Middleware_HOME%\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf.

2. In the configuration file, locate the section LocationMatch/profitability:

   <LocationMatch /profitability>
   SetHandler weblogic-handler 
   PathTrim / 
   KeepAliveEnabled ON 
   KeepAliveSecs 20 
   WLIOTimeoutSecs 3000
   Idempotent OFF
   WeblogicCluster servername:6756 
   </LocationMatch>
   

   SetHandler weblogic-handler

   PathTrim

   KeepAliveEnabled ON

   KeepAliveSecs 20

   WLIOTimeoutSecs 3000

   WeblogicCluster servername:6756

3. Add the following lines within the LocationMatch/profitability section:

   WLIOTimeoutSecs 3000
   Idempotent OFF
   

4. Navigate to

   %Middleware_HOME%\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\htppd.conf

5. Set Timeout to 3000, as shown in the following text:

   # Timeout: The number of seconds before receives and sends time out. Timeout 3000

   Note:

   The server timeout shown above is a suggested limit, and may be modified to suit the specific timeout settings provided in the documentation for your application server.