Monitoring the Siebel application IV

When a Siebel user accesses the application using a browser, a TCP session is established between the users workstation and the webserver running the Siebel Web Server Extensions (SWSW). If the user is not actively using the application for a certain amount of time the session is closed by the webserver due to a session timeout.
Given this information the number of active and inactive users can be monitored by counting the number of TCP sessions to the Siebel webserver on the port whereon the webserver is publishing the application. The number of sessions in another state than “ESTABLISHED” or “LISTEN” do represent the sessions which are pending closed, the inactive user sessions.

I wrote two very straightforward scripts, which must be executed on the Siebel webserver, to monitor the number of active an inactive sessions. The first script is "
mon_tcp.sh" which monitors the number of sessions in a established or listen state to a specific port. Therefore it counts the number of active Sievel users on that specific webserver. The second script is "mon_halftcp.sh" which counts all sessions which er in a state other than established ot listen. It therefore counts the number of Siebel users who's sessions is closed or closed pending. Those users have not actively used the Siebel application for a period longer than the defined session timeout. Those users are inactive or have left the Siebel application without logging out.

The syntax for both scrips is shown below;


mon_tcp.sh

Syntax: ./mon_tcp.sh {portnr}

{portnr} TCP Poort number, e.g. “80”

Returns: Integer value
<0 error
>=0 Number of active TCP sessions


mon_halftcp.sh

Syntax: ./mon_halftcp.sh {portnr}

{portnr} TCP Poort number, e.g. “80”

Returns: Integer value
<0 error
>=0 Number of half closed TCP sessions

blog comments powered by Disqus