Innovation Pack 16: Enable Workspaces in Composer and Siebel Tools

To replace local database concept used for development for years, workspace intoduced in Siebel 16. Developers can work directly against the repository in their independent sandboxes.

Here is the snapshots of workspace in tools and web composer.

[su_slider source=”media: 974,973,972,975,971,970,969″ link=”lightbox” target=”blank” width=”1420″ height=”700″]
You can follow below video to better understand this, Thanks to SIEBEL HUB for their sincere efforts.
Enable Workspace

Well its very attractive for all Siebel developers as they must have bored of traditional way of development or configuration in tools. So, I started installation with high hopes but stuck at each and every step. I followed Siebel Hub and Oracle Support (but they refer back to Siebel Hub. It seems Siebel HUB is the only savior in this dark world of Siebel), It looks pretty simple at first but trust me its not. Even a bug has been raised for their bad documentation.
Documentation defect raised to address this matter: Bug 23697794 – INSUFFICIENT DETAILS ON ENABLING WORKSPACES

With this post, I will try to recollect all my memories and learning in single place.

Workspace Administration

To enable workspace we have to run a utility from Tools folder. Follow this document for detailed steps of running this

Go to <TOOLS_HOME>/BIN to run the EnableWorkspace.exe utility.
This example shows the arguments and parameters that are used to run the EnableWorkspace.exe utility:

C:\Siebel\Tools\BIN>EnableWorkspace -s "C:\Siebel\Tools" -t ORAJQ152 -u ORAJQ152 -p ORAJQ152 -o "SSD default instance" -d Oracle -l EnableWorkspace.log -w SADMIN

The Command Prompt window displays the following arguments and parameters, which you can use to run the EnableWorkspace.exe utility:

-s Siebsrvr/Tools Installation path specified (required)
-t Siebel Table Owner (required)
-u Username (required)
-p Password (required)
-o ODBC Data Source (required)
-d DB Platform Name (Oracle, MSSQL, DB2UDB or DB2390)
-l Log File Name (default: EnableWorkspace.log)
-w Workspace Owner Username (required)

Issues Identified

• Run this command by Siebel User (not by SADMIN)

  C:\Siebel\Tools\BIN>EnableWorkspace -s "C:\Siebel\Tools" -t SIEBEL -u SIEBEL -p SIEBEL -o "SSD default instance" -d Oracle -l EnableWorkspace.log -w SADMIN

• This utility run for hours (4 hrs for me), so have patience
• Go to <TOOLS_HOME>/BIN, there you can find Workspace folder. You have to closely watch logs for all below steps.

  Stage 1 of 7: Setting the Repository ID
  Stage 2 of 7: Validate the Workspace Data
  Stage 3 of 7: Generate the Workspace Data
  Stage 4 of 7: Update the Workspace Data in all Repository Tables
  Stage 5 of 7: Generate the indexes
  Stage 6 of 7: Update the statistics for all Workspace enabled Repository Tables
  Stage 7 of 7: Post Run Cleanup
  

• EnableWorkspace is not supported on thick client. So, Composer link will not work for thick client.

  Run this command on server to enable workspace on composer in thin client.

• This command will eventually fail on step 3. When it will try to generate new row_id and insert in siebel DB, as PACKAGE “S_SEQUENCE_PKG” is missing. So, download this sql file and run below command.

  sqlplus SIEBEL/SIEBEL@Database_Identifier @S_SEQUENCE_PKG.sql

  [su_document url=”http://www.askmesiebel.com/wp-content/uploads/2016/07/S_SEQUENCE_PKG.txt”]

• Add parameters in Thin client to run composer link.Workspaces Dashboard Not Available In The Siebel Thin Client (Doc ID 2141829.1)

  For Call Center Object Component, the following component parameter needs to be set under Administration - Server Configuration > Component > Parameter:
  
  EnableComposer = True
  EnableWorkspace =True

Note:- In comment section below, Darshan suggested that this process should not take more than 30 mins. There must have something wrong with my environment setup.

Guys, you can also share your feedback.

Hope this post will help someone in need.

[su_divider]

@AskmeSiebel