Turbo Tip: Adding Oracle WebLogic as a Target

Blog Post created by eva.tuczai on Dec 31, 2014

Recently introduced in the Turbonomic Early Access v5.1 Announcement: Are you in? for 5.1 (which is in Early Access only) is the ability to add your Java Application Servers into Turbonomic by leveraging the Oracle WebLogic Domain Admin Server as a single interface.  This means a much easier configuration, discovery and management of your WebLogic 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 the heap, or clone to scale out horizontally.


This article describes some tips on adding a WebLogic Domain Admin Server as a target, and terminology used.

Looking for IBM WebSphere Information? Go to this post: Turbo Tip: Application Control Module and adding IBM WebSphere as a Target




License key for Application Control Module or Application Edition is required (applications feature key) and Turbonomic v5.1 or higher to see Oracle WebLogic as a target.  You will not be using the old JMX configuration, rather leveraging the WebLogic Domain Admin Server’s T3 Listen Port to access the JMX API to discover and monitor all the WL Servers managed in a single Domain.  We support WebLogic 11g, 12c and higher.  Note 11g uses Java 6 and Engineering has provided support to be able to switch between Java 6 (11g) or Java 7 (12c), but 12c is the most current version.


  • Monitoring Levels: default monitoring is sufficient
  • Credentials: admin role (wluser) is required to monitor and take actions; a read-only role is supported to monitor and recommend actions, but cannot execute.
  • Target Details: Have the WebLogic Domain Admin Server T3 Listen Port information, and IP Address / Host Name where the Domain Admin Server 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: Oracle WebLogic

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

Figure 1: Typical WebLogic installation shown across 3 virtual machines that make up a Domain and Cluster, along with the Domain Administration Server. Shown are 2 Nodes with 4 individual JVMs = Application Servers



Domain Admin Server: An administrative server that will provide centralized configuration management, deployment and monitoring of a Domain.

Domain: A group of managed application servers all part of a domain managed by a single management server. A domain consists of multiple nodes and can have clustered servers.

Node: A physical group of servers that are on the same VM, and can make up an application or set of services.  Each node will have a Node Manager that will communicate between the Admin Server.

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

Cluster: a set of Application Servers in a Domain that are clustered and replicate between each other.

WebLogic Adminstration Console: the web based administration application you can use to see servers in a Domain, configuration settings, T3 Listen Port information, and validate credentials have access.  Common URL to access is:

            Unsecure: http://DomainServerIPAddress:7001/console/

            Secure: https://DomainServerIPAddress:7002/console/

T3: WebLogic’s proprietary internal protocol for inter-server communications and to collect information about a server.

WebLogic Diagnostics Framework (WLDF): provides a set of built-in system diagnostic modules, which are preconfigured to monitor the main components of a server instance, such as the JVM, the WebLogic Server run time, and key components and services.   Additional modules are available to be configured but not required by Turbonomic.


Application (Oracle): 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.


WebLogic 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 WebLogic Domain Admin Server, the T3 Protocol Listen Port Number (7001 is a typical default, 7002 for SSL and rarely changed) and then the credentials of roles of an admin role is required to monitor and ability to take actions, and a read-only role is supported to monitor and recommend actions, but cannot execute.


Note: you can also specify a single WebLogic Server (JVM) this way, and instead use the Listen Port of the individual JVM.  However when available you should use the Domain Admin Server to discover all the JVMs managed.



WebLogic Configuration Validation

Check credentials and settings by logging into the Oracle WebLogic Administration Console.  Default URL for secure connection: http://{IPaddress}:7001/console


Use the credentials that will be used in the target set up.  You can at this point validate the Listen Port and to confirm seeing monitored performance data.


To find the Listen Port of the Domain Admin or any Server if wanting to add individually, navigate to Domain Structure -> the Domain (mydomain in this example) -> Environment -> Servers and select the one that is indicated as admin (myserver(admin) in this example).

Note you can see the Listen Port in this table for the Admin Server, and individual Servers if you want to configure separately:


If you want more details, selecting the admin server you can see the settings Listen Port or SSL Listen Port if enabled under Configuration - General :


Note that monitoring should be enabled by Default.  The WebLogic Diagnostics Framework (WLDF) provides a set of built-in system diagnostic modules, which are preconfigured to monitor the main components of a server instance, such as the JVM, the WebLogic Server run time, and key components and services. You will be able to see these Monitoring when navigating to a Server and then selecting Monitoring -> Performance to see evidence that data is being collected.


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 WebLogic 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 admin level credentials and make sure you can log into the WebLogic admin console with these same credentials.
  3. DNS issues? Add the Domain Admin Server’s IP and Host name 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 Oracle WebLogic Application Server
    2. Correct Listen Port for the admin server
    3. You can see Monitoring Performance Metrics
    4. Already discovered the underlying virtualized infrastructure
    5. Understand the security levels required, and any firewall considerations
    6. Clicked Rediscover after adding the WebLogic Target