Runtime topology

The runtime topology is an interactive visual view of your application server environment. From this panel you can view the utilization of any given node group, as well as a charted breakdown of the node group information. To view this page, click Runtime Operations > Runtime Topology.

The visualization panels are supported by a runtime component in the deployment manager which caches statistical and topological data about the runtime environment for quick display. The Force data update option re-initializes the caches with the current data for the environment. If the runtime topology seems to be out of synchronization with the current runtime environment, use this option to obtain the current state.

The following list includes the interactive features of the runtime topology:
Select a perspective This list contains node groups, applications and the operational policy from which you can set the type of the root object in the topology tree. Selecting an item from this list displays the allowable items based on your selection in the next list.
Select a node group This list contains the node groups in your environment. After you select a node group, you can view its details in the interactive tree following this list. The following information contains the viewable details:
Nodes
You can expand the node view to show the nodes that are active for the node group, as well as the applications that are on each of the server instances. To the right of each node, a utilization bar contains the data on the percentage of the node resources being consumed. Hovering your mouse over the node enables a pop-up, which indicates the number of running server instances for the node. You can fully expand the node tree to display the instances for each node. You can hover over the instances to display such data as the dynamic workload manager weight and the process ID.
Dynamic clusters
You can expand the dynamic cluster to display the dynamic clusters that are associated with the node group, as well as the specific applications, in WebARchive (WAR) file format, that are installed and running on each cluster.
In some cases, you can click an item from the tree to generate a chart in the main frame.
Select a service policy This list contains the service policies in your environment. After you select a service policy, you can view its details in the interactive tree following this list. Hover help is available for the service policy in the topology tree. The following are the viewable details:
Transaction classes
You can expand the transaction classes to show the Web modules that have mapped URIs in the transaction class. Hover help is also available for the Web module.
In some cases, you can click an item from the tree to generate a chart in the main frame.
Select an application This lists the applications installed in your environment. After you select an application, you can view details about it in the interactive tree following this list. Hover help is also available for the application in the topology tree. The following are the viewable details:
J2EE modules
You can expand the Java 2 Platform, Enterprise Edition (J2EE) module view to show the J2EE modules in this application. Hover help is also available for the J2EE module.
Target mappings
You can expand the target mappings view to show where the application is deployed.
In some cases, you can click an item from the tree to generate a chart in the main frame.
Set refresh rate The refresh rate is the time, in seconds, between topology refreshes. If your environment is very active, you might want to set a lower refresh value.
Charting options By default a chart is created on installation. As you build your application server environment and add node groups, service policy, dynamic clusters, and cells, the charting configurations update for you to customize your preferred view of the environment. Hover over the chart tabs in the main frame to view the details about each chart, such as the metrics that are involved, the type of chart and the scope. The following contains the list options:
Data scope
This option feeds the scope of the chart. For example, if you select transaction class as your data scope, the data name and data set options are fed by the properties that are associated with the configured transaction classes in your environment. The data scope determines the overall performance data that you are attempting to chart.
Data name
The data name options are determined by the value that you select for data scope. For example, if you select Node group as the data scope, the data name list shows the titles of the node groups configured in your environment.
Data set type
The data set options are determined by the value that you select for data scope. This value determines the collective nature of the chart. For example, selecting a data scope of Node group populates this list with the relevant service policy content and dynamic clusters.
Data set
The data set options are determined by the value that you select for data scope. This value determines the collective nature of the chart. For example, selecting a data scope of Node group populates this list with the relevant service policy content and dynamic clusters.
Data metric
This option is based on an average calculation and is a predetermined set of values. The options for this value are:
  • Concurrent requests

    This metric measures the number of concurrent requests per the defined data set selection within the data name selection.

  • Avg throughput

    The average throughput metric is calculated in seconds based on the total workflow requests to the on demand router, as defined by the data scope, data name and data set.

  • Avg response times (ms)

    The average response time metric is the time in milliseconds it takes for a work request to complete. This metric includes the request from inception, until the request is returned to the client, and is the equivalent of the service time metric plus the wait time in queue metric.

  • Avg wait times in queue (ms)

    This metric is the average time in milliseconds that a work request spends waiting to service.

  • Avg service times (ms)

    The time in milliseconds to service a request for the on demand router. This metric indicates the time that the on demand router spends getting work to the node where it is completed.

  • Avg queue length

    This metric is the average time, in milliseconds, for any work queue in the environment that is defined by the data scope, data set and data name.

  • Avg drop rate

    The average drop rate is calculated based on the number of work requests that are not processed due to a full queue. Work requests that encounter a full queue are returned to the requestor with an error.

  • Avg relative performance

    The relative performance of the configured goal compared to the actual goal value.

  • Percentile response time

    The percentage of requests of the service policy percentile goal that meet the specified response time.

  • Concurrency requests

    The number of seats desired for a given dynamic cluster's load coming through a given gateway.

  • Used memory

    Memory used by a process.

  • CPU utilization

    CPU utilization by a process.

  • Total requests

    Total requests for Web modules deployed to a process.

  • Up time (secs)

    Total time in milliseconds that the process has been running.

  • Total EJB method calls

    Total method calls for EJB modules deployed to a process.

  • Total transactions

    Total transactions for a partition.

  • Free memory

    Free memory on a node.

  • Utilization

    The percentage of the resources that are being used and how much resource is available. Utilization measures the node speed and process CPU.

  • Jobs requested

    The number of jobs that arrive at the execution environment (endpoint application) for processing.

  • Jobs completed

    The number of jobs which run to completion at the execution environment.

  • Execution time

    The total time in milliseconds time in milliseconds that jobs spend executing.

  • Maximum concurrency

    The maximum concurrency level that is attained.

  • Jobs queued

    The number of jobs that are queued at the scheduler.

  • Jobs dispatched

    The number of jobs that are dispatched by the scheduler.

  • Jobs failed

    The number of jobs that failed in the execution environment.

  • Jobs error

    The number of dispatch errors that occurred for jobs.

  • Queue time

    The time in milliseconds jobs spent in the queue.

  • Dispatch time

    The total time in milliseconds jobs spent being dispatched.

  • Dispatch error time

    The time in milliseconds for jobs spent being dispatched when dispatch errors occurred.

  • Total CPU capacity

    A floating-point number of MHz of the reference instruction set specified for each node.

  • CPU consumption by WebSphere processes

    CPU consumption by WebSphere processes on a node.

  • CPU consumption by non-WebSphere processes

    CPU consumption by non-WebSphere processes on a node.

  • Available CPU capacity

    Available CPU capacity of a node. This is the total CPU capacity minus the consumption by WebSphere and non-WebSphere processes

  • Total memory

    Total memory of a process or node.

  • Work coefficient

    A work factor characterizes the average amount of computational work required to serve a request of a given kind

  • CPU demand

    The desired processing power for a given deployment target.

  • High memory watermark

    The expected memory consumption of a server instance to be started.

  • Resident memory

    Resident memory of a process.

  • Power coefficient

    The average amount of computing power consumed on a given processing tier by one active request of a given flow, averaged from (a) the time when the ARFM gateway forwarded the request to the target server and (b) the time the reply came back from the target server.

Data Filter
From the Data filter field, you can select existing proxies (on demand routers) and filter the map accordingly. This selection is useful for troubleshooting issues in your environment.
Hover help Hover help is available across many of the features in the panel. The areas with enabled hover help are the nodes and instances in the menu, as well as the chart tabs in the main frame.