Server Optimization

At a high level, the purpose of this article is to provide you with a basic understanding of a flexible mechanism for the optimization of the platform or Operating System.

First of all, via the command-line, type the appropiate command for deteminate Memory (using Solaris as a Operating System) that is available (depend on current tasks running on your Server). By entering the command below and then pressing Enter:

# vmstat 1 2 tail -1 awk ‘{ print $5/1024 , “MB” }’ for instance:

Using “Server Manager” allows to detect which component is being used. As it’s shown below, we stopped three components that could be started puntually:

stop comp EIM
stop comp AsgnSrvr
stop comp WfProcBatchMgr

Once EIM, AsgnSrvr and WfProcBatchMgr are stopped, then increase the availability of memory, if it’s required, these components can be started again.

Tracking workflow process using Server Manager

In this case, it’s required to activate server log level, using a sentence such as:

Change evtloglvl %=5 for Comp wfprocmgr

Once the log level is 5, it’s required use server manager again, using a sentence like the next one:

run task for component WFPROCMGR server SERVER_NAME with ProcessName=‘WF_EXAMPLE', SearchSpec='([Id]=“Id_EXAMPLE")'

It will write all generated actions into a log file located in server. When this file is examined, a considerable amount of preprocessing will be seen. In order to look for an error, each action should be identified in the log.

Examine the SQL statements - Performance analysis

For performance analysis on specific views, it’s useful to examine the SQL statements that the applications generate.

In this way, command line parameters can be specified when Siebel Applications is invoked. The /S option causes Siebel applications to spool all generated SQL. The /S parameter should be specified with a filename into which the generated SQL will be written.

An example of the invocation of a Siebel application with this parameter is:
c:\siebel\bin\siebel.exe /C "c:\siebel\bin\siebel.cfg" /S "c:\temp\spool.sql"

In this example, the application is invoked with siebel.cfg as the configuration file and will write all generated SQL into a file called spool.sql located in c:\temp.