Tracking Siebel Memory Use

Siebel Components use generic process names, so keeping track of specific Siebel components performance can be difficult. The example below shows the tracking of the Memory use of a particular component, or the entire Siebel Server. You can also read an article on Siebel Memory and CPU tracking. The code below gives you a method to track Siebel Memory use with VA2.It is usually most interesting to track the memory use of Siebel Object managers, and this code can be customized for any Component. Options in the rule let you track the memory by Physical, virtual, or both.

You will have to customize the $enterprise and $appserver parameters to your environment to use this Satistic.

use siebsrvobj;

my $enterprise = 'siebel';
my $appserver = 'compaqamd';
my $memtype = 1;                               # memtype 1 = physical, 2 =virtual, 3 = physical + virtual
my $cc_name = 'TxnMerge';


my $entobj = siebsrvobj->newobj($datasession,$debug,$enterprise);  	#initialize the enterprise object

$retval = $entobj->memuse_forappsrvrcomp($appserver,$cc_name,$memtype);	   #get memory for component

Another interesting method is to track the memory use of the entire Siebel appserver. In that case, you can call the method memuse_forappsrvr, as seen in the code sample below.

use siebsrvobj;

my $enterprise = 'siebel';
my $appserver = 'compaqamd';
my $memtype = 1;                               # memtype 1 = physical, 2 =virtual, 3 = physical + virtual
my $cc_name = 'TxnMerge';


my $entobj = siebsrvobj->newobj($datasession,$debug,$enterprise);  	#initialize the enterprise object

$retval = $entobj->memuse_forappsrvrcomp($appserver,$cc_name,$memtype);	              #get memory for


You can also download this Statitic as XML and import it into VA2. Download Here.

Or see the Vault for other rules.