Using Siebel Tools > Parallel Development Using Workspaces > Administering Parallel Development using Workspaces >

Setting an Integration Workspace as the Default Workspace Branch

When users access the Siebel application after they set an integration branch as the default workspace branch, the system loads the application based on the latest metadata changes of the integration workspaces that they have set as the default workspace instead of the values in the MAIN workspace. This setting enables the Siebel application to display the latest metadata values that are stored in the run-time repository tables. Every time the integration workspace is incremented by one version, the latest metadata values are stored in the run-time repository tables. When the application is reloaded, changes are reflected in the Siebel application window based on the latest version of integration workspace.

Administrators can set any integration workspace as their default workspace branch where their changes do not impact other users who are branched out from the other integration workspaces. Meanwhile, developers can work in parallel on multiple features of Siebel application without disturbing other features. Moreover, developers can verify how their latest metadata configuration appears in the Siebel application window without delivering their changes to the MAIN workspace.

To set up an integration workspace in the environment as the default workspace branch, administrators must update the parameter WorkspaceBranchName at the component level as shown in the following example. Notice that administrators must run this parameter by connecting to the server manager:

Command:

change param WorkspaceBranchName=<workspace_name> for comp <OBjMgr_lang>

Example:

change param WorkspaceBranchName=int_ip2017rel for comp SCCOBjMgr_enu

To reflect the changes, administrators must restart the services of the Siebel server.