Oracle WebLogic

Oracle WebLogic deployments can include clusters to distribute workload across multiple WebLogic servers. Turbonomic recommended actions respect the cluster architecture. For example, if you have enabled horizontal scaling for your WebLogic servers, then Turbonomic can recommend provisioning new servers for a given cluster.

The typical WebLogic deployment is a managed domain with one Administration Server that provides a single point of entry for administration and management of the domain. The domain can include other WebLogic Servers which are the Managed Servers. You set the WebLogic Administration Server as a Turbonomic target.

For a standalone WebLogic deployment, the single server acts as its own Administration Server — You can set the standalone server as a Turbonomic target.

Prerequisites

  • Oracle WebLogic 12c

  • A service user account

    To execute actions the service account must have an Admin role. For read-only monitoring and analysis, you can set the target with a more restricted role, but then you will have to execute all recommended actions manually, through the WebLogic interface.

  • The Turbonomic IP address and all WebLogic server IP addresses must be resolvable by your local DNS server

  • Discovered infrastructure

    Turbonomic discovers WebLogic servers that are running on VMs or containers. The hosting VM or container must already be in your Turbonomic inventory.

    To set the target for a server running on a VM, you must have first discovered the hosting VM through a hypervisor target. To set the target for a server running in a container, you must have configured container discovery for WebLogic applications.

    • For information about container platform targets, see this topic.

    • For information about hypervisor targets, see this topic.

Finding the T3 listen port

To configure a WebLogic target, you need to know the port that the server listens on for administrative communications. Launch the WebLogic Administration Console:

  • Navigate to Domain Structure and display the domain you’re interested in

  • Navigate to Environment > Servers and select the Domain Administration Server you’re setting as a target

    The console displays configuration information for the server, including the T3 listen port.

Adding a WebLogic target

Note:

This topic describes features that are available in the new design of the user interface. This new design is enabled by default. If you switched to the legacy design, click New Feature Toggle button in the navigation bar of the user interface and then turn on the toggle to re-enable the new design. For more information, see New Design for the User Interface.

You can add one or more WebLogic targets in a given scope, including both standalone servers and domain managers.

  1. Click Settings > Target Configuration.

  2. On the Target configuration page, click Add Target.

  3. On the Select target page, click WebLogic.

  4. In the side panel, review the connection requirements and then click Connect Target.

  5. Configure the following settings:

    • Display name

      Specify a name that uniquely identifies this connection.

      This name is for display purposes only and does not need to match any name in WebLogic.

    • Username

      Specify the username of an account with the Admin role.

    • Password

      Specify the password of an account with the Admin role.

    • Scope

      Specify the scope Turbonomic uses for application discovery.

      The scope is a group of applications that are stitched to the underlying VMs when the VMs are discovered as part of a separate Turbonomic target.

      If you set a scope, Turbonomic searches for virtual machines in the selected group.

      Turbonomic can monitor up to 500 virtual machines in a group. If you have more than 500 virtual machines in your environment, split them across smaller groups and then add those groups as individual targets.

    • Port number

      Specify the WebLogic remote port number. By default, the port is 7001.

    • Authenticate all database servers

      If you select this option, Turbonomic attempts to authenticate all database servers in the selected scope. If Turbonomic is unable to authenticate a database server, the target is not added and no data is collected.

Monitored resources

Turbonomic monitors the following resources:

  • Service

    • Transaction

      Transaction is a value that represents the per-second utilization of the transactions that are allocated to a given entity.

  • Application Component

    • Virtual Memory (VMem)

      Virtual Memory is the measurement of memory that is in use.

    • Virtual CPU (VCPU)

      Virtual CPU is the measurement of CPU that is in use.

    • Transaction

      Transaction is a value that represents the per-second utilization of the transactions that are allocated to a given entity.

    • Heap

      Heap is the portion of a VM or container’s memory allocated to individual applications.

    • Response Time

      Response Time is the elapsed time between a request and the response to that request. Response Time is typically measured in seconds (s) or milliseconds (ms).

    • Threads

      Threads is the measurement of thread capacity utilized by applications.

    • Connection

      Connection is the measurement of database connections utilized by applications.

    • Remaining GC Capacity

      Remaining GC capacity is the measurement of Application Component uptime that is not spent on garbage collection (GC).

Actions

Turbonomic supports the following actions:

  • Service

    Turbonomic does not recommend actions to perform on the Service itself, but it does recommend actions to perform on the Application Components and hosting VMs. For example, assume a Service that manages three SQL databases. If a surge in requests degrades performance across all three databases, then Turbonomic can start a new application component to run another instance of the database application, and bind it to the service. On the other hand, if SQL requests drop off so that the load balancer only forwards requests to two of the databases, Turbonomic can suspend the dormant database and unbind it.

  • Application Component

    • Resize Heap

      This action can only be executed by Turbonomic if the entity is running in a domain controller. Actions for standalone entities can only be executed outside Turbonomic.

    • Resize Connection Capacity

      This action can only be executed outside Turbonomic.

  • Virtual Machine

    • Provision additional resources (VMem, VCPU)

    • Move Virtual Machine

    • Reconfigure Storage

    • Suspend VM