IBM WebSphere

Versions 7.5 and 8.x are known to be working. Version 6.1 with JDK 5+ possibly works but agent has to be converted to JDK5 bytecode format.

Directory convention:

${was.install.root}   - installation directory
${user.install.root}  - instance directory

Copy agent files to ${user.install.root}/zorka directory. Edit file and set proper startup scripts:

scripts = jvm.bsh, zabbix.bsh, ibm/was.bsh

If websphere server has Java 2 Security enabled, create monitoring user with Monitor role and add the following
lines to

was.user = <username>
was.pass = <password>

Add zorka agent args to ${user.install.root}/config/cells/<cell-name>/nodes/<node-name>/servers/<server-name>/server.xml:

<jvmentries xml:id="..." ... genericJvmArguments="-javaagent:${USER_INSTALL_ROOT}/zorka/zorka.jar=${USER_INSTALL_ROOT}/zorka">

Edit ${user.install.root}/properties/server.policy file and add the following section:

// Allow ZORKA agent
grant codeBase "file:${user.install.root}/zorka/-" {

Start server using ${user.install.root}/bin/

# cd ${user.install.root}/bin
# ./ <server-name>

IBM management console URL: https://localhost:9043/ibm/console/

Configuration settings

WebSphere integration script implement standard HTTP/EJB monitoring, so standard options for HTTP and EJB apply. Also, consider SQL and/or LDAP monitoring if your applications use SQL database(s) or LDAP. There are no other specific settings for JBoss.

Zabbix templates

The following zabbix templates are dedicated for WebSphere:

  • Template_Zorka_WebSphere_JdbcConnections.xml - monitors JDBC JCA connections;

  • Template_Zorka_WebSphere_ThreadPools.xml - monitors server thread pools (all of them, not only HTTP handling threads);

  • Template_Zorka_WehSphere_WebSessions.xml - monitors HTTP sessions for WebSphere server;