Turbo Tip: Adding IBM WebSphere as a Target

Blog Post created by eva.tuczai on Nov 18, 2014

Recently introduced in Turbonomic v5.0 is the ability to add your Java Application Servers into Turbonomic by leveraging for IBM WebSphere, the single interface of the Deployment Manager.  This means a much easier configuration, discovery and management of your WebSphere Application Servers.  This methodology also provides more information of heap, thread pool utilization, and average servlet response times - information used to drive decisions to resize heap or the thread pool, or clone to scale out horizontally.


This article describes some tips on adding a Deployment Manager server as a target, and terminology used.

Looking for information on Oracle WebLogic support introduced in Turbonomic 5.1? Go to this post: Turbo Tip: Application Control Module and adding Oracle WebLogic as a Target



License key for Application Control Module or Application Edition is required and Turbonomic v5.0 or higher to see IBM WebSphere as a target.  You will not be using the old JMX configuration, rather leveraging the IBM PMI (Performance Management Infrastructure interface) that will use SOAP connections.  We support WebSphere v8.0.0.2 and higher. Note I have seen this working on 7.x, but we know the PMI default settings are different so keep that in mind as you add WAS ND Deployment Manager targets.

  • Monitoring Levels: PMI settings need to be set for Basic, and enabled.
  • Credentials: wasadmin role is required to monitor and take actions; wasmonitor role is supported to monitor and recommend actions, but cannot execute.
  • Target Details: Have the WAS Deployment Manager SOAP Connector Port information, and IP Address / Host Name where the Deployment Manager is running.
  • Other info: We will only discover Application Servers that are running on VMs or Containers.  Those targets need to be added and discovered FIRST.

Overview: IBM WebSphere

Some important terminology for you to understand based on the following picture depicting a typical WebSphere implementation:

Figure 1: Typical WAS installation shown across 2 virtual machines with a Cell, Deployment Manager, 3 Nodes and 6 individual JVMs = Application Servers


Network Deployment Manager: An administrative server that will provide centralized configuration management, deployment and monitoring of a Cell.

Cell: A group of managed application servers all part of a domain managed by a single Deployment Manager. A cell consists of multiple nodes.

Node: A logical group of servers that are on the same VM, and can make up an application or set of services.  Each node will have a nodeagent running that facilitates the communication between the node and the Deployment Manager server.

Server:  A single instance of a java virtual machine, aka JVM or WebSphere Application Server.  Each server has its own configuration (can be shared with other servers in a node) and application or services deployed on it.

WebSphere Integrated Solutions Console: the web based administration application you can use to see PMI configuration settings, SOAP Port information, and validate credentials have access.  Common URL to access is:

            Secure: https://DMgrIPAddress:9043/ibm/console/login.do

            Unsecure: http://DMgrIPAddress:8043/ibm/console/login.do

PMI: WebSphere’s Performance Management Infrastructure = the monitoring interface, where there are different groups and levels of settings - for more information read this post.

Application (IBM): Services that make up a business function that is based on code that will run in an n-tier infrastructure made up of runtimes like a JVM, web server, Messaging, and/or a DB.

Application (Turbonomic):  A single process, a single JVM.


WebSphere Target Configuration

The server you will identify here is the Deployment Manager as pictured in Figure 1.  Enter the FQN hostname or IP Address of the WAS Deployment Manager, the SOAP Port Number (8880 or 8879 are typical defaults and rarely changed) and then the credentials of roles of either wasadmin role is required to monitor and ability to take actions, and wasmonitor role is supported to monitor and recommend actions, but cannot execute.


Note: you can also specify a single WebSphere Application Server (JVM) this way, and instead use the SOAP Port of the individual JVM.  However when available you should use the Deployment Manager to discover all the JVMs managed.



WebSphere Configuration Validation

Check credentials and settings by logging into the IBM WebSphere Integrated Console.  Default URL for secure connection: https://{IPaddress}:9043/ibm/console/logon.jsp

Use the credentials that will be used in the target set up.  You can at this point validate the SOAP port and the PMI settings.


To find the SOAP Port of the Deployment Manager, navigate to System administration -> Deployment Manager

Expand the “Ports” level under “Additional Properties” and use the number specified in the “SOAP Connector Address”

To view PMI Settings, navigate to “Monitoring and Tuning”, and select “Performance Monitoring Infrastructure (PMI)”, and then navigate to view the nodeagent – which will represent the monitoring for all JVMs on that Node.  We minimally need “Basic”.

Note that adding more levels of monitoring does not increase the type of data collected by Turbonomic.



For an individual JVM, the SOAP Port can be found by navigating to Servers -> Server Types -> WebSphere application servers -> select a server

Then open Ports to find the SOAP Connector Address:

We will connect to this port for individual WAS Servers if they are standalone as separate targets.


PMI Settings can be checked at the individual JVM levels, navigating to Monitoring & Tuning –> Performance Monitoring Infrastructure (PMI) -> select a server

PMI Settings that need to be minimal set include checking “Enable Performance Monitoring Infrastructure” and “Basic” option.

Note that adding more levels of monitoring does not increase the type of data collected by Turbonomic.


Troubleshooting Tips

If you are having trouble adding the WebSphere target, then consider the following:

  1. Look at the response message and look in the /var/log/tomcat/catalina.out log.  Is it a credentials issues, or target not found, or an exception?
  2. Credentials? Start with wasadmin level credentials and make sure you can log into the IBM WebSphere console with these same credentials.
  3. DNS issues? Add the Deployment Manager Server’s IP and Host names into the Turbonomic Server’s /etc/hosts file
  4. Firewall issues? We will need to be allowed HTTP/SOAP bidirectional communication between the Turbonomic Server and the Target
  5. Make sure you have:
    1. Connecting to a supported version of IBM WebSphere Application Server
    2. Correct SOAP Port
    3. PMI enabled and minimally set to Basic
    4. Already discovered the underlying virtualized infrastructure
    5. Understand the security levels required, and any firewall considerations
    6. Clicked Rediscover after adding the WAS Target



Hope this helps to demystify some of the settings for your WebSphere environment.

Stay Green!