Several kbase articles concerning monitoring Sametime are already available. The only missing part till now was, what IBM Sametime things you can check/monitor on the WebSphere Level itself.

This article should give you some sort of idea what you can do with GreenLight



First of all please verify that you have the core setup foor WebSphere monitoring in place

for v3.2 appliance

WebSphere for GL v3.2 - setup


for v3.5 appliance

WebSphere for GL v3.5 - setup



1) Download Sametime Shell Script Sensors

IBM Sametime:

Download and Extract the files to /opt/panagenda/scripts/gl_sensor

Download Sametime Sensors



2) Create Linux Shell Script Sensor - GreenLight UI

-create a LinuxShellScript Sensor

-Script Filename: WasAppStatus

This is one of the files which you have copied over to /opt/panagenda/scripts/gl_sensor in Step1





-Define on Targetlevel your Sametime FQDN (e.g. MeetingServer Url, ..)




You are going to get for ANY installed application within the WAS Cell the Status (running, stopped, not available)


What other Scripts are available?

You can do now the same steps for the remaining Scripts

  •  (

Monitors each WAS server


  •  (

Monitors WAS Datasource Connectivity (e.g. is WAS able to connect to the DB2 Datasource of Connections?


  • WebSrvStatus (

Monitors all Webservers within the Cell (stopped, running)


  • (

Retrieves pending messagebus information from any queue!


  •  (

Retrieves JVM Information such as Xmx, Xms, etc...


  •  (

Retrieves PMI Information of JVM processes and Webpools (ActiveCount, Poolsize,...)



Retrieves PMI Information of JVM Processes (Used Memory, Free Memory,. ...)



Lists all WAS Variables