1. Database Upgrade Guide
  2. Migrated Configuration Data Is Available to the Runtime Repository Without User Re-Login

Migrated Configuration Data Is Available to the Runtime Repository Without User Re-Login

When configuration is migrated to Runtime Repositories such as in Test/QA/UAT/Production using Incremental Runtime Repository Merge, that configuration is available to logged in users after the poll time that looks for new configuration. The poll time could be fifteen minutes which is the default setting or a different duration if you configured it differently. After the new configuration is loaded the application presents the new configuration when the next navigation occurs such as navigating to a new view.

Note: This functionality is enabled by default but can be disabled by setting the below parameters.

This fuctionality allows:

  • Changed objects such as Views, Applets, Business Components, Server Script, Browser script, PickList values.

  • New objects such as Views, Controls on Applets, new Applets, Menu Items, Page Tabs, Find Items, Toolbar Items.

  • Deleted/Inactivated objects such as Views, Applets, Fields.

  • Changed or added Runtime Events.

  • Pausing Task/Workflow Processes will resume under old definition.

Note: In-flight processes, such as Workflow Processes or Tasks continues to completion using the version of the process, loaded to start the process. For Example, if a Task or Workflow Process started in Version 1 the running instance of the Task or Workflow Process continues to use Version 1 until it completes. The next invocation of that same Task or Workflow Process uses the updated version.

About the Parameters

Poll Time

This Object Manager Parameter sets the poll time that is used to detect the migration of new configuration. In this example, the parameter is set for the Call Center Object Manager, but you would set this for the Object Manager that you are using. The default is 900 seconds, that is 15 minutes.

change param ServerSessionLoopSleepTime=900 for comp SCCObjMgr_enu
Note: Do not set the ServerSessionLoopSleepTime value less than 60.

Related Object Manager Parameters

These two parameters are necessary to enable this functionality and should automatically be set when the Monthly Update is installed in your Runtime Repository environment. These parameters are documented here for completeness but changing these parameters is not supported unless directly advised by Oracle Support. This example is for the Call Center Object Manager.

change param ServerSessionBusSvc=CSSWSUtilityService for comp SCCObjMgr_enu
change param ServerSessionBusSvcMethod=GetLatestWSVersion for comp SCCObjMgr_enu

Pausing/Resuming This Feature

You would not want to pause this feature as it removes an inconvenience to the users. Without this feature enabled the logged in users will not be able to use the latest configuration, until they log out and login back again. However, in case you find some situation where you want the users to re-login to receive your latest updates, the following parameters can be changed to disable/enable the feature.

To pause this feature and not receive the latest Workspace Configurations, set the following Object Manager Parameter:

change param ServerSessionLoopRunning=FALSE for comp SCCObjMgr_enu

To resume receiving latest Workspace Configurations set the following Object Manager Parameter:

change param ServerSessionLoopRunning=TRUE for comp SCCObjMgr_enu
Note: After setting these parameters there is no need to restart the Object Manager. The parameters will take effect immediately.