Siebel Server Manager (srvrmgr) commands

Listing some everyday srvrmgr commands that can be useful for Siebel Admins, will keep updating this list as I come upon different scenarios.

List Component
srvrmgr> list comp sccobjmgr_enu

List Component for specific server
srvrmgr> list comp sccobjmgr_enu for server SERVER1

List Active sessions for a component
srvrmgr> list active sessions for comp sccobjmgr_enu

List Active sessions for a user
srvrmgr> list active sessions for login tom_siebel

List all sessions for a component
srvrmgr> list sessions for comp sccobjmgr_enu

List all sessions for a user
srvrmgr> list sessions for login tom_siebel

To connect to a specific server within the Enterprise
srvrmgr> set server SERVER2

To disconnect from a server session and go back to Enterprise
srvrmgr:SERVER2> unset server

Starting a Siebel component
srvrmgr> start comp wfprocmgr

Stopping a Siebel component
srvrmgr> stop comp wfprocmgr

Starting a component for a specific server
srvrmgr> start comp wfprocmgr for server SERVER1

Stopping a component for a specific server
srvrmgr> stop comp wfprocmgr for server SERVER2

Kill a stuck/non-responsive component
srvrmgr> kill comp wfprocbatchmgr

How to change startup mode for a component
srvrmgr> manual start comp SCCObjMgr_enu
srvrmgr> auto start comp SCCObjMgr_enu
srvrmgr> manual start comp wfprocmgr for server SERVER1
srvrmgr> auto start comp wfprocbatchmgr for server SERVER2

Listing component parameters
srvrmgr> list param for comp wfprocmgr
To list a specific parameter
srvrmgr> list param <parameterAliasName> for comp wfprocmgr
To list a hidden/advanced parameter
srvrmgr> list advanced param ConnForwardAlgorithm for comp SCBroker

How to Drop and Generate Triggers in Siebel

If there are changes to a Workflow policy, you might be asked to either 'Generate' the triggers or 'Recreate' them for the changes to take effect. This task can be accomplished in two ways, one through the Siebel Application and the other via Server Manager command line.

The main parameter to consider to Generate or Drop the triggers is 'Remove' which can be set to TRUE or FALSE depending upon the purpose.

Server Manager Commands:

1. Drop Triggers
run task for comp GenTrig with EXEC=True,Remove=True,PrivUser=SIEBEL,PrivUserPass=<siebelpassword>

2. Generate Triggers
run task for comp GenTrig with EXEC=True,Remove=False,PrivUser=SIEBEL,PrivUserPass=<siebelpassword>



Siebel Application:

Login to the Siebel application and navigate to the 'Administration - Server Management' and then 'Jobs'.
Create a new job 'Generate Triggers' and add the parameters as shown:

Change the parameter value of 'Remove' to 'True' if you want to drop the triggers. The ideal sequence for re-creating the triggers is to drop them first and then create. So you would have to run the job with the 'Remove' parameter set to 'True' first and then run the job again with the parameter set to 'False'.

You can also include additional logging parameters like 'ErrorFlags', 'SQLFlags','TraceFlags' etc for capturing additional information in the logs.

Oracle bookshelf link related to this topic:

http://docs.oracle.com/cd/E14004_01/books/BPFWorkflow/administering_policies4.html

Thanks,
Shyam