1. Using Siebel Tools
  2. Flattening Workspace Versions

Flattening Workspace Versions

A Workspace Administrator who is also the owner of the MAIN Workspace (root, parent, or master Workspace) can perform the process of flattening Workspace versions using the Command Prompt. No other users can perform this process.

The flattening of Workspaces collapses the MAIN branch to a single version with all the latest changes and subsequently deletes all the child Workspaces.

The only time that flattening Workspaces is required is after the addition of a new language using the Siebel Database Configuration Wizard and before MLOV conversion. There are no other situations that require a flattening Workspace operation.

When flattening a Workspace before an MLOV conversion, the sequence of events is as follows:

  1. Add a new language to the database.

  2. Deliver Workspaces that have been completed and tested and MAIN.

  3. Archive any Workspaces which contain in progress development work so that they can be re-imported into a Workspace after the FullPublish completes.

  4. Run FlattenWorkspace, see the following procedure.

  5. Run MLOV conversion (which you must do for the new language to work correctly).

  6. Run EnableWorkspace, see Enabling Workspaces.

    Note: The EnableWorkspace utility should only be run in the case where a new language has been added as part of this process. There is no other time that the EnableWorkspace utility should be run.

  7. Run FullPublish, see Executing the Full Publish Process.

Note: Although there is no requirement to do so, it is possible to flatten Workspaces at any time, for example, to clear out all old Workspaces. However, this is not typically recommended for the following reasons:

  1. It will collapse all Workspaces, even those that have not been delivered. If there are other integration branches or Developer Workspaces in which active parallel development is taking place, those would be lost. The recommended approach to clean up old integration branches is to delete them see Deleting Integration Workspaces.

  2. After a flatten Workspace operation, it is required to run Full Publish for these two scenarios. You do not have to run Full Publish if you are flattening Workspaces just to clean up.

    1. You have added a new language to the application as specified above.

    2. You are performing an IRM upgrade.

    After running Flatten Workspace, which in turn requires that the next migration to any downstream Runtime Repository Database be a Full Migration. That is, it eliminates the possibility for incremental migration.

Caution: In order for the flattening process to run successfully, the parameter ServerDbODBCDataSource under the [Siebel] section in the Tools.cfg file must point to the correct data source.
The following example shows the setting of the parameter ServerDbODBCDataSource under the [Siebel] section in the tools.cfg file:

[Siebel]
…
ReportsODBCDataSource    = Siebel Reports: Access
LocalDbODBCDataSource    = m:/siebel Local DB
ServerDbODBCDataSource   = "ORAJQ141"
DockRepositoryName       = Siebel Repository
HoldExportOdbcConnection = FALSE
…

To flatten the Workspace versions using the Command Prompt

  1. Open the Command Prompt window on your machine by clicking the Start button and selecting the Run option.

  2. In the Run window that opens, enter the value CMD in the Open field.

  3. In the Command Prompt window that opens, change directory to the $SIEBEL_HOME\BIN folder.

  4. Run the following flatten Workspace command:

    siebdev /c tools.cfg /u <User ID> /p <password> /d ServerDataSrc /FlattenWorkspace

    Or, to flatten a specific Integration Workspace hierarchy:

    siebdev.exe /c tools.cfg /l enu /d ServerDataSrc /u <User ID> /p <password> /flattenWorkspace 
<INTEG NAME>

    For example:

    $SIEBEL_HOME\BIN>siebdev /c tools.cfg /d ServerDataSrc /u sadmin /p ******** 
/FlattenWorkspace

    or

       $SIEBEL_HOME\BIN>siebdev.exe /c tools.cfg /l enu /d ServerDataSrc /u sadmin /p ********    
/flattenWorkspace “Int_Oct_2024”

  5. Confirm that the flatten Workspace version process shows the process is successfully completed.

After flattening Workspaces, you must run the Full Publish process if you have added a new language or are performing an IRM upgrade. You do not have to perform a Full Publish if you have simply flattened a Workspace of other reasons. For more information, see Executing the Full Publish Process.