Skip Headers
Oracle® Enterprise Manager Getting Started with Oracle Fusion Middleware Management
11g Release 1 (11.1.0.1)

E17558-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

16 Exploring Application Dependency and Performance

This chapter examines the following:

Exploring the User Interface

This section explores the ADP User Interface. Topics include:

Accessing ADP

To access Enterprise Manager's Application Dependency and Performance (ADP) feature, do the following:

  1. From the Grid Control Home page, click the Targets tab.

  2. On the Targets page, click the Middleware tab.

  3. On the Middleware page, either:

    • Click the Application Dependency and Performance link which is located in the Related Links section at the bottom of the page, or

    • Click the target in which you are interested. In the tree view, select a target under Application Deployments. In the right pane, expand the Application Deployment menu, select Monitoring, and then select Application Dependency and Performance.

General ADP UI Elements

ADP UI consists of the following core components:

  • Navigation Pane (left)

    There are three types of workspaces in the ADP navigation pane: Monitoring, Configuration, and Registration. In the Monitoring workspace, you can navigate the managed environment and monitored applications in a tree.

    • Use the Monitoring workspace to traverse the ADP tree model and identify abnormal activities.

    • Use the Configuration workspace to create, modify, and review various configuration settings for ADP.

    • Use the Registration workspace to register a Remote Method Invocation (RMI) manager.

  • Main Display Window (right)

    As you navigate through the ADP tree model and configuration categories, detailed performance information and configuration settings are displayed in the Main Display Window. You can refresh the Main Display Window at anytime by clicking the Refresh icon.

Drill Down in Operational Dashboard

The Operational Dashboard displays the health indicators for various key entities in the managed environment. ADP uses traditional traffic light colors to represent the health of these various key entities.

For each component, ADP uses the following health indicators to provide a comprehensive view. These health indicators are:

  • Performance

    The performance health indicator depicts the relative responsiveness of the monitored entity to the configured threshold.

  • Availability

    The availability health indicator informs you to what extent a particular entity is available to service requests.

  • Errors

    The errors health indicator informs you if the number of errors and exceptions encountered by this entity are approaching or violating the configured threshold.

  • Load

    The load health indicator depicts how many operations have been performed and requests have been served by a particular entity.

ADP is aware of clusters. As such, these indicators display overall health of a particular entity across the entire cluster.

Configuring Service Level Objectives (SLOs)

In ADP, thresholds configured for various measurements are called Service Level Objectives (SLOs). Configuring SLOs is a key activity for establishing and maintaining an effective performance monitoring system. It is easy to configure SLOs in ADP. Click the Configuration tab and select the Service Level Objective Configuration option.

Create New SLO

When you select Service Level Objectives Configuration, ADP displays the Service Level Objective Configuration window. This window allows you to apply existing SLOs or create new ones. When you click Create New SLO, ADP guides you through the process of setting up a new SLO.

The steps for SLO creation are as follow:

  1. Either select a SLO file or create a new SLO file. ADP can store SLO configurations in different files to improve configuration portability.

  2. Define the SLO Entity Type. ADP automatically selects the appropriate entity type for you based on the selected monitoring element. For example, if you want to set a SLO on a Portal Desktop element, ADP automatically sets the Entity Type for you.

  3. Other information is filled in by default. Normally, there is no need to modify the SLO Entity values.

  4. When you are done setting the SLO Entity Type values, click Create New SLO to go to the second step of the SLO creation process, Defining the SLO Parameters. Note: The (*) character means Select All. It is recommended that you do not use the (*) character.

Defining SLO Parameters

Follow these steps to define the SLO parameters:

  1. Type in the name of the SLO parameter.

  2. Select the performance metric.

  3. Define the monitoring window size, which determines how long the condition must persist before generating an alert.

  4. Set threshold values for the SLO.

  5. Select what actions to take when a trigger is fired. A list of preconfigured actions is available in the view pane.

  6. Add new actions by going to the Action Configuration node in the Configuration Workspace.

  7. Click Save to set the SLO for this monitored element.

  8. You can delete unwanted SLOs for any element from this window.

Propagating Threshold Violation Events

ADP is designed to propagate threshold violation events up the hierarchy. Therefore, when a SLO is set on a lower level metric, the higher level health indicator light becomes activated. Additionally, the health indicator light for the application server that hosts this component also becomes active. Oracle calls this containment approach to SLO event propagation. When a lower level SLO is violated, the violation event propagates all the way up the hierarchy and changes the status of all containers for this event.

For example, say we defined a performance threshold on the average response time metric of the CaseManagement portlet. We would expect the css portal and cgServer health indicator lights to become active because the CaseManagement portlet is part of the css portal, css portal is part of the cssdemo application, and cssdemo application is deployed on cgServer.

Types of SLOs

In addition to the containment concept, ADP categorizes SLOs into the following types:

  • Performance

  • Availability

  • Error

  • Load

In the example, the average response time metric is correctly categorized into the performance type.

If you set a SLO on a metric in the load category such as Portal Desktop Visit Count, you will see the activation of load health indicators for all containers of the desktop. In our example, we set a SLO on the Portal Desktop Visit Count of the csr desktop. This activates the load health indictors for css portal, cssdemo application, and cgServer instance.

SLO Events Viewer

Right-click on any tree node and select View Service Level Objective Events to open a new window. You can see all the SLO violation events triggered for the selected entity. ADP automatically applies a filter to show only relevant events.

Once new SLOs are added, ADP updates the relevant graphs to visually display these new thresholds. Table 16-1, "SLO Line Types" explains the different line types.

Table 16-1 SLO Line Types

Line Description Description

Solid Red Line

A violation threshold that triggers on high.

Solid Yellow Line

A cautionary threshold that triggers on high.

Dashed Red Line

A violation threshold that triggers on low.

Dashed Yellow Line

A cautionary threshold that triggers on low.


Configuring SLO Blackouts

Use this option to specify blackout time frames to prevent having a specified number of SLOs from being evaluated. You can prevent having unwanted alerts being fired during planned or unplanned down time.

  1. From the Grid Control home page, click the Targets tab. On the targets page, click the Middleware tab. On the Middleware page, locate the Related Links section and click the Application Dependency and Performance link. Ensure the Configuration tab is highlighted

  2. Select SLO Blackout Configuration.

  3. You can view any existing SLO blackout.

  4. Use this window to create, delete, or view the details of existing blackouts.

Deleting SLO Blackout

  1. Select an existing event on the list.

  2. Click Delete SLO Blackout.

  3. Confirm that you want to delete the entry and click Yes.

Viewing SLO Blackout Summary List

  1. Click SLO Blackout Summary List.

  2. View the details on the existing SLO Blackout events.

  3. Click Show SLO Blackout List to return to the previous window.

Creating SLO Blackout

  1. Click Create SLO Blackout to view the detail window.

  2. On the SLO Blackout File page, type the name of the blackout in the New SLO Blackout File field. Click Continue.

  3. On the SLO Blackout Configuration page, fill in the fields. Refer to Table 16-2, "SLO Blackout Configuration" for details.

    Table 16-2 SLO Blackout Configuration

    Column/Metric Description

    Blackout Name

    Type in the name.

    Description

    Type in the description of the SLO you are creating.

    Blackout By SLO File

    Use to blackout at the file level. The SLO files display in a list where you can select them or cancel out of the window.

    This option restricts the blackout to the SLO file name.

    Blackout By SLOs

    Use to blackout at the SLO level. The SLOs display in a list where you can select them or cancel out of the window.

    This option restricts the blackout to the SLO name.

    Blackout By Entity

    Use to blackout at the entity type level. Click the Blockout by Entity: button to view the list of entity types. Select the entity.

    This option restricts the blackout to the entity type selected.

    year, month, date, hour, minute, duration

    Use the guidelines to the right of these columns to enter the appropriate information.

    recurring

    Select how often you would like to run this blackout event from the list.


Time Frame

In ADP, you can specify the length of the time the window information is to be displayed. To specify the length of this time window, select the appropriate length in the Time Frame list. The following Time Frame values are available:

  • 1 hour

  • 2 hours

  • 4 hours

  • 8 hours

  • 12 hours

  • 24 hours

Note:

The ADP default data collection interval is 60 seconds. As you adjust the data collection interval, ADP automatically adjusts the display time frames.

ADP automatically adjusts information displayed to fit the specified time window. You can drill down to see detailed performance information for a specific range of time.

For example, visualize the drill down process with two screen shots of the same graph with different Time Frames of the average response time for Portal campaign. The first graph has a Time Frame of 24 hours. The second graph has a Time Frame of 1 hour. By increasing the granularity of the Time Frame, you are performing a drill down operation.

For example, an IT Operations staff noticed abnormally high response time with Portal campaign subsystem. The person decided to investigate further to evaluate the extent of the problem. By changing the Time Frame from 24 hours to 1 hour, this user is able to see that between 14:17 and 14:18, the Portal campaign response time jumped from an average of 1000 milliseconds to 5000 milliseconds. While the problem did not persist, it may warrant additional investigation.

Display Interval

Display Interval, located above the Main Display window, indicates the start and end time for the data displayed in the Main Display Window. Display Intervals change as you change the following settings:

  • Time Frame

  • Interval Context

  • Turning Off Time Frame Limitation

Time Frame

When you select a new Time Frame, the Display Interval automatically changes to fit the selected Time Frame. For example, if you were to change the Time Frame from 1 hour to 2 hours, the Start value of the Display Interval changes.

Interval Context

Display Interval can also be changed by setting the Interval Context. The settings for the Interval Context are:

  • End Time Is Current System Time

    The default Interval Context for ADP is to use the current system time as End value for the Display Interval. In this default setting, you have a sliding Display Interval and can see the latest performance information in the Main Display Window.

  • End Time Is Fixed

    You can also change the Interval Context setting to use a fixed time as the End value for the Display Interval. By selecting the fixed Interval Context, you can create a fixed time window to display performance data. The fixed time window is particularly useful for performing analytical tasks.

  • Date/Time Selector

    When you select to fix the End time for the Interval Context, the ADP UI enables a pair of Date/Time Selectors to allow you to set Start or End values for the Display Interval. Click the icon next to the Start and End times to open up the Date/Time Selector.

    The Date/Time Selector allows you to set a specific Display Interval to fit your needs. Additionally, the Date/Time Selector enables ADP to compare current performance trends with historical data.

Note:

Changing the start and end time do conceptually different things. Users are advised to always change their time frame by modifying the end time first, and then the start time. Changing the end time moves the window in time, whereas changing the start time increases/decreases the size of the window.

Turning Off Time Frame Limitation

To support the display of data for more than twenty four hours, ADP allows you to specify your own time frame for data display. To enable this feature, set Interval Context to End time is fixed and make sure the Use time frame: check box is unchecked. Turning off time frame limitation allows ADP to display eight days worth of data.

For example, when you specify the time frame to be eight days by adjusting the start and end times through the Date/Time Selector, ADP then adjusts its view to display eight days worth of data in a single graph. This feature allows you to perform trending analysis over time.

Graphs and Data Items

ADP displays performance information in various formats. Most commonly used display formats in ADP are tables and graphs.

  • On graphs, you can gain more information about a data item by pointing the mouse over the interested item.

  • Minimum and maximum response time measurements are stored in their database in addition to average response time measurements. The min and max metrics, if present, are displayed visually in the UI.

  • For tables, you can perform a table sort by clicking the blue up/down arrow located in the column headings.

  • On some screens, you can define the zoom in area using a click and drag operation. To zoom in, click and drag the mouse to the right. To zoom out, click and drag the mouse to the left.

    Tip:

    For graphs with extreme outliers, graph details are lost due to automatic graph scaling. To work around this problem, you can use the graph zoom in feature to review these details. This feature is only available on some screens.

Right-Click Operations on Tables and Graphs

There are several simple operations you can perform on various tables and graphs in ADP. The following is a list of the right-click operations associated with tables and graphs.

Note that these operations are only available in Applet views.

Table 16-3 Right-click on Tables and Graphs

Right-Click Operation Description

Copy cell value

The right-click operation is available for tables only. This operation copies the cell value to enable common copy/paste operation (table only).

Export as CSV...

This right-click operation is available for both tables and graphs. This operation saves all the values in the table or graph as a comma separated value (CSV) file. The CSV file can later be imported into other applications such as Microsoft Excel.

Count number of rows

This right-click operation is available for tables only. This operation returns a count for the number of rows in the selected table (table only).

Fit to View

Make the table or graph file the entire pane.

Restore View

Restore the layout to the default state

Show/Hide Table Columns

Remove or un-remove columns from a table (table only)

Enable/Disable Series

Remove or un-remove a line from a graph (graphs only)


For example, you can use the Count number of rows right-click operation to get a total row count for any table.

Comparative View

ADP provides a number of analytical tools to enable performance analysis. One of these tools is the Comparative View. To access Comparative View, right-click the ADP Main Display Window and select Create Comparative View.

Note that this tool is only available in Applet views.

After the Comparative View window appears, you can use the Date / Time Selector to specify start and end times for each of the two windows in the Comparative View. You can use this tool to compare performance statistics of two different time frames.

Tip:

You can use comparative views to determine if current performance of a specific application or component differs greatly from historical performance or baseline performance captured previously.

Comparative views are useful to evaluate current performance characteristics against historical performance characteristics.

Save as PDF

To improve collaboration among those who work on application performance issues, ADP provides the ability to save any view as a PDF file. To save a specific view as a PDF file, right-click on the ADP Main Display Window and select Save this view as a PDF file.

Note that this feature is only available in Applet views.

Easy Scroller

Easy Scroller is a feature to help you navigate different views in ADP. To bring up Easy Scroller, right-click on a view in the Main Display pane and select the Easy Scroller option. Drag the box within Easy Scroller to navigate.

Note that this feature is only available in Applet views.

Zoom In and Zoom Out Toolbar

For some of the views, ADP provides the zooming ability. This capability enables you to zoom into diagrams for more fine-grain details and zoom out for more coarse-grain structure.

On the Zoom In/Zoom Out Toolbar, the icon zooms in on the view by 10%, the icon zooms out on the view by 10%, and the icon returns the view back to normal size (100%). You can use the drop-down box to quickly zoom in or zoom out of the view.

Note that this feature is only available in Applet views.

Custom Metrics

While ADP intelligently selects relevant performance metrics based on its Application Schema model, you can further customize the monitoring environment by configuring additional custom metrics. In addition, you can use custom metrics in problem diagnostic situations where additional visibility is needed to pinpoint problem root cause.

To configure a new custom metric:

  1. Click Custom Metric Configuration on the Configuration tab

  2. Click the Create Custom Metric button.

  3. On the Custom Metric File page, either choose an existing custom metric file or provide the name of a new custom metric file. Click Continue. ADP walks you through the configuration process.

Custom Metric Configuration page includes the following fields, see Table 16-4, "Custom Metric Configuration Page".

Table 16-4 Custom Metric Configuration Page

Field Description

Name

This text field is for defining the display name for the custom metric.

Resource Name

This list is for defining the resource where the custom metric will be collected.

Class Name

This text field is for defining the fully qualified class name (package + class) associated with the custom metric.

Method Name

This optional text field is for defining the method name associated with the custom metric.

Usage:

  1. Type in * - ADP will instrument all methods.

  2. Provide comma separated list of methods with no wildcards - ADP will create method entities and only instruments these methods in the agent.

  3. Provide comma separated list of methods with wildcard prefixes or suffixes - ADP will instruct the agent to instrument the methods specified along with the wildcards.

  4. Provide 1) or 2) preceded by "!" to create an excluded list - ADP will instruct the agent to instrument all methods in the class not defined in the exclude list.

Method field examples:

  1. methodA,methodB,methodC

  2. ejb*,*context,methodA

  3. !ejb*,*context,methodA


After you define the custom metrics, restart the application server instances associated with these customizations. The new custom metrics will be listed under the Custom Metrics node in the ADP navigation tree.

The newly configured custom metric provides class level performance data, for example invocation count and response time.

Functional View

Functional View is a type of Application Schema Visualization - a visual way for ADP to represent the information stored in its Application Schema model. This view is designed to help you understand how business functions are assembled with various functional building blocks. Table 16-5, "Functional View" provides a list of functional views currently available in ADP.

Table 16-5 Functional View

Entity Type Function View Description

Process

Process Workflow View

This functional view depicts the workflow associated with the selected WLI and Oracle BPEL business process. It shows all the process nodes and the relationships among them.

Pageflow

Pageflow Functional View

This functional view depicts the logical flow associated with a JPS or Struts pageflow. It shows all the pages in a pageflow and the relationships among them.

OSB Proxy Service

Proxy Service Functional View

This functional view depicts the pipeline and stage flow associated with an OSB Proxy Service.


Depending on the type of entity selected, ADP displays different functional views. Right-click and select Display Functional View to bring up the relevant Functional View associated with the selected entity.

Topology View

Topology View is another type of Application Schema Visualization - a visual way for ADP to represent the information stored in its Application Schema model. This view is designed to help you understand how application environments are assembled with various applications, application server instances, and shared resources. This information helps you map composite applications and their building blocks to application server instances and share resources.

The highest level topology view graphically depicts domains, external resources, and shared database resources. The applications used in the following examples are CSS and MedRec demos.

For example, you can have a topology with two ADP managed resources, CSS Domain and MedRec Domain, two external resources, and a shared database resource. The lines connecting various entities in the Topology Views depict calls made from one entity to another. You can get more information about a specific call by pointing the mouse over a specific line.

It is possible to hide different types of lines in the Topology View. To the line types, right-click the Topology View and highlight the Edge types option to reveal a list of different edge (arrow) types associated with the current Topology View.

Architecture View

Architecture View is another type of Application Schema Visualization; a visual way for ADP to represent the information stored in its Application Schema model. This view is designed to help you understand the structure and behaviors of Java EE, SOA, and Portal applications at the module and component level. Some Architecture Views also include built-in delay analysis to help identify potential bottlenecks in a given call path.

The Architecture View in ADP is capable of showing application structure and component relationships at two levels: module and component levels. At each level, ADP can show both active and potential call paths. Table 16-6, "Various Types of Architecture View" describes various types of Architecture Views.

Drill down on a specific application to launch into the Architecture View. This action demonstrates the logical progression of drilling from high level resource-centric topology view, down through application-centric topology view, to module-centric architecture view. Using this logical drill down, you can understand the structure of your application runtime environments and diagnose problems.

Table 16-6 Various Types of Architecture View

Tab Name Description

Module Level Execution

This is the default Architecture View at the module level. The Module Level Execution view shows the active calling relationships among various Java EE modules (EAR, WAR, JAR, and so on). Shared resources are also included.

Module Level

The Module Level view shows the potential calling relationships among various Java EE modules. Shared resources are also included. It should also be noted that any object that is not connected within the static view will not be included at this level and if there are no static connections at all between objects, every potential object relationship will be displayed. By default, the Module Level view is not enabled.

Component Level Execution

This is the default Architecture View at the component level. The Component Level Execution view shows the active calling relationships among different Java EE components (EJB, servlet, JSP, and so on). Shared resources are also included.

Component Level

The Component Level view shows the potential calling relationships among various Java EE components. Shared resources are also included. Similar to the module level, any object that is not connected within the static view will not be included at this level and if there are no static connections at all between objects, every potential object relationship will be displayed. By default, the Component Level view is not enabled.


These various types of architecture views are color coded in order to provide additional information. Table 16-7, "Architecture View Color Codes" lists color codes and their meanings.

Table 16-7 Architecture View Color Codes

Background Color Description

Orange

The orange background color represents entry points into the application or module. The orange color also represents that these entities belong to the same application or module currently selected (in context).

Green

The green background color represents entry points into the application or module. The green color also represents that these entities belong to other applications or modules (out of context). The green color is also used to represent share resources.

White

The white background color represents that these entities belong to the same application and module currently selected (in context).

Blue

The blue background color represents that these entities belong to other applications and modules (out of context). The blue color also represents shared resources.


ADP graphically depicts active calling relationships among various Java EE modules and shared resources.

Accessing the Architecture View

There are several ways to access the Architecture View. One way is through the Deployments node associated with a specific application under the Application Node. Application specific Architecture View can be accessed using the Deployments node on the Oracle Tree.

The last way to access the Architecture View is by right-clicking a managed entity and selecting the Architecture View. Right-click and select Architecture View to start the drill down process.

Arrows in Architecture Views

The arrows connecting various entities in the Architecture Views depict calls made from one entity to another. You can get more information about a specific call by pointing the mouse over a specific arrow. Mousing over arrows shows the details of a specific call in Architecture View

It is possible to hide different types of arrows in the Architecture View. To do this, right-click on the Architecture View and highlight the Edge types option to reveal a list of different edge (arrow) types associated with current Architecture View. Unchecking a specific edge type hides all lines of that type in the Architecture View. Checking a specific edge type makes these lines appear.

To hide all lines not connected with a specific entity, select a monitored entity in the Architecture View, right-click and select Hide other edges. Highlight an entity and select Hide other edges to hide all arrows not connected to the managed entity.

Architecture View Summary

The Architecture View Summary provides the delay analysis associated with the active call path displayed. The table and pie chart displayed in the right pane guides you to leading delay contributors in the displayed call path. Selecting a specific component in the call path brings up component specific information. You will see the following tabs:

  • Summary tab first which includes high-level delay data for both inbound and outbound calls.

  • The Instrumentation tab shows detailed method level performance data associated with the selected component. Click the Instrumentation tab to see detailed performance measurements and information at the method level.

  • The Errors/Exceptions tab shows the errors metrics associated with the selected portal or BPEL process.

  • The SQL Statement tab shows SQL statements and their performance data associated with the selected component.

  • The Transactions tab shows the transaction events associated with the selected portal and children below. By default, the Transactions tab is not enabled.

Metric Types

Table 16-8, "Metric Types" describes various types of metrics provided by ADP.

Table 16-8 Metric Types

Examples Metric Type Metric Description

Active Sessions

Completions

Pending Requests

Running Instances

Max Capacity

Messages High

Snapshot Count

A count of the monitored entity at a point in time. ADP plots these snapshot counts in trend graphs.

Requests Serviced

Total Sessions

[Processes] Aborted

[Processes] Terminated

[Method] Invocation Count

Bytes Received

Aggregated Count

A count of the monitored entity incrementally aggregated from the beginning of display time window. ADP shows these aggregated counts in summary tables.

Response Time

Elapse Time

Connection Delay

Average Timing

Calculated every sampling period (default 60 seconds), the average timing is calculated by dividing the total amount of time needed to complete the monitored business unit of work by the number of completed business units of work.

ADP uses this data in the following two ways:

  1. Plot the average timings in trend graphs.

  2. Calculate average timing of this business unit of work for the display time window and display in a summary table.

Min/Max

Minimum and Maximum Response Time Measurement

Minimum and maximum response time measurements found per collection sampling intervals. These are stored in their embedded database in addition to average response time measurements. The default is 60 seconds.


Exploring the Monitoring Tab

When ADP is pointed to a Oracle WebLogic domain, IBM WebSphere cell, or an Oracle SOA Suite cluster, it automatically discovers information about this particular domain including all deployed applications, configuration, resources, and others. ADP displays this information in the Monitoring tab under Oracle Enterprise Manager.

Each node represents a construct in the platforms monitored by ADP. Each construct is described in this section.

This section includes the following topics:

Oracle WebLogic Portals

The Portals node under Oracle Enterprise Manager contains information about all deployed WebLogic Portal applications in the managed domains. The Portals node is organized hierarchically using the same framework developers use to build these Portal applications. The minimum and maximum response time measurements are stored in the database in addition to the average response time measurements. These metrics, if present, display visually in the Main Display Window on the right.

For WebLogic Portal, this hierarchy contains the following (Table 16-9, "WebLogic Portal Hierarchy"):

Table 16-9 WebLogic Portal Hierarchy

Component Description

Portals

The Portal is the logical containment unit for a Portal application. A typical Portal can contain a few desktops, several books, tens of pages, and hundreds of portlets.

Desktops

The desktop is the top-level container for the portal components included in that specific view of the portal.

Portal administrators can create new desktops beyond what portal developers create in WebLogic Workshop.

Books

The top-level book contains all sub-books, pages, and portlets. The top-level book defines the initial menu navigation style used for the desktop. For each sub-book you add to a desktop you can select a different navigation style.

Pages

Pages and sub-books are the navigable containers used for organizing portlets.

Portlets

Portlets are the containers that surface Web content and applications in your desktops.


When you click the Portals node under Oracle Enterprise Manager, ADP displays summary information on active portal applications. This summary includes the following (Table 16-10, "Tree Summary"):

Table 16-10 Tree Summary

Metric Description

Portal web application activity

A summary of user sessions for a specific portal application

Portal completions

Total number of requests fulfilled by a specific portal application

Portal response time (ms)

Average response time for a specific portal application

Portal entitlement response time

Average response time of WebLogic Portal entitlement subsystem for a specific portal application

Portal campaign response time

Average response time of WebLogic Portal campaign subsystem for a specific portal application


For Portal web application activity and Portal performance, ADP displays information in both table and graph formats. For the other metrics, ADP shows the information in graph format. When you click the plus (+) icon next to the Portals node, ADP expands the tree to show all managed portal applications currently deployed on the WebLogic domain.

You can also see information specific to a particular portal application. By selecting a specific portal application, all information displayed in the Main Display Window changes to only show data relevant to this new context. For example, when a user selects a particular portal application under the Portals node, the Main Display Window only shows information specific to that portal application.

At the Portal level, you can navigate to different levels of the portal application by using different tabs. Use the tabs available to quickly access lower level components. Table 16-11, "Portal Level Tab Description" provides a list of the tabs available for portal level nodes and their descriptions.

Table 16-11 Portal Level Tab Description

Tab Description

Summary

Performance summary specific to the selected portal.

Desktops

Performance summary for all the desktops associated with the selected portal.

Headers

Performance summary for all the headers associated with the selected portal.

Books

Performance summary for all the books associated with the selected portal.

Pages

Performance summary for all the pages associated with the selected portal.

Portlets

Performance summary for all the portlets associated with the selected portal.

Footers

Performance summary for all the footers associated with the selected portal.

WSRP Topology

View WSRP consumer-producer relationships and WSRP deployment topology.

Analysis

Two performance analytics - Multi-Point Regression Analysis performed at the portal level and Entity Performance Ranking performed at the portlet level.

Events

SLO violation events associated with the selected portal.

Errors/Exceptions

Errors metrics associated with the selected portal.

Transactions

Transaction events associated with the selected portal and children below. Be default, the Transactions tab is not enabled. To enable the Transactions tab, enable the UIProvider.Modes=product,trace property in the Acsera.properties file before starting the manager.


Desktops

Expand a particular portal application further to reach the Desktops node. By selecting the Desktops node, ADP provides a list of currently active desktops associated with that portal application.

This Desktop Summary includes the following metrics:

Table 16-12 Desktop Summary Metrics

Metrics Description

Desktop arrivals

Total number of requests for a specific desktop

Desktop completions

Total number of requests fulfilled by a specific desktop

Desktop response time (ms)

Average response time for a specific desktop.


Note:

Portal desktops are end-user facing entities. Metrics such as Desktop hits and response time represents request arrival rate and application performance respectively. Violations in thresholds set on these metrics would indicate unacceptable end-user experience.

ADP displays these metrics in both table and graph formats.

For example, when you have two active desktops, you can drill down further to a specific desktop by expanding the Desktops node. Again, clicking on the plus (+) icon expands the tree view for you.

When you select a node in the expanded tree to get more information specific for that desktop, ADP changes information in the Main Display Window to reflect the new context.

ADP not only shows the performance metrics associated with a specific node, but it also displays other relevant settings for that node. For example, there can be pre-configured Service Level Objectives (SLOs). These SLOs are displayed in the graphs as red lines.

Expand the desktop node to see Header, Footer, and Books. You can see detailed information for these components by clicking on the appropriate nodes.

Display Portal Desktop - Desktop Structure Viewer

One of the unique capabilities of ADP is its automatic discovery and modeling of deployed applications. The Desktop Structure Viewer provides visibility into how a portal desktop is organized. To activate the Desktop Structure Viewer, right-click on a specific desktop. Select the Display Portal Desktop menu option to access the Desktop Structure Viewer.

After the Desktop Structure Viewer appears, you can navigate through the portal desktop structure by clicking on the appropriate book, page, or portlet. The ability to see portal desktop structure using the same perspective as portal end-users is a unique value especially for the IT support staff.

With the Desktop Structure Viewer, the IT support staff can speak the same language with end-users while at the same time looking at performance oriented information for a specific component. The IT support staff can also use the Desktop Structure Viewer to isolate a particular performance problem. By drilling down from the top-level desktop to individual portlets, the IT support staff can get more insight into which components are having performance problems.

The Desktop Structure Viewer consists of two main panes. The pane on the left is the Desktop Structure pane. This pane allows you to graphically navigate the portal desktop. The pane on the right is called the Main Display Window. The Main Display window displays performance information in the context of the selected component in the Desktop Structure pane. As you navigate through the portal desktop and click different components, the Main Display Window provides information relevant for that selected context.

The Main Display Window shows relevant performance metrics for different portal desktop components - desktop, books, pages, and portlets.

Since ADP understands the WebLogic Portal framework and knows that a pageflow can be associated with a portlet, it is designed to allow easy access to the Pageflow Viewer from the Desktop Structure Viewer.

To activate the Pageflow Viewer, double-click the interesting portlet. In turn you can double-click the portlet in the Desktop Structure pane to open the appropriate pageflow in the Pageflow Viewer.

Portlet Drill Down

You can drill down on a portlet in the portal desktop view to activate the Display Architecture View.

  1. Select a portlet under a node.

  2. Double-click on a name to see the Portal Desktop Status page.

  3. In the Portal Desktop Status window, right-click on a service box to select Display Architecture View.

  4. See Drill Down - Bottleneck Analysis on how to use the architecture view.

Pageflow Viewer

The Pageflow Viewer has two panes. The pane on the right is the Main Display Window. The Main Display Window shows information corresponding to the item selected in the left pane. The left pane shows either the Flow View or the Component View. You can choose to see either the Flow View or the Component View by selecting the appropriate tab.

The Main Display Window changes to show information relevant to the selected item in either the Flow View or the Component View.

Books

Expand a particular portal desktop further to see the Books node. By selecting the Books node, ADP provides a list of currently active books associated with the specific desktop.

This Books Summary includes the following metrics (Table 16-13, "Book Summary Metrics"):

Table 16-13 Book Summary Metrics

Metrics Description

Book completions

Total number of requests fulfilled by a specific book

Book response time (ms)

Average response time for a specific book


ADP displays these metrics in both table and graph formats. For example, you can have two active books for the portal desktop. These active books are listed in the table and plotted in the graphs.

You can drill down further to a specific book by expanding its node. Click the plus (+) icon to expand the tree view. Expand the Books node to see a list of specific books configured.

When you select a particular active book, the Main Display Window shows the relevant information in that context.

Pages

Expand a particular book to see the Pages node. By selecting the Pages node, ADP provides a list of currently active pages associated with the specific book.

This Pages Summary includes the following metrics (Table 16-14, "Pages Summary Metrics"):

Table 16-14 Pages Summary Metrics

Metrics Description

Page completions

Total number of requests fulfilled by a specific page

Page response time (ms)

Average response time for a specific page


ADP displays these metrics in both table and graph formats. For example, you can have one active page for a book. The active page is listed in the table and plotted in the graphs.

You can drill down further to a specific page by expanding the Pages node. Click the plus (+) icon to expand the tree view. This reveals the next level of components - Portlets.

Portlets

Expand a particular page to see the Portlets node. Select a Portlets node to view a list of currently active portlets associated with the specific page.

This Portlets Summary includes the following metrics (Table 16-21, "Portlet Metrics"):

Table 16-15 Portlet Metrics

Metrics Description

Portlet completions

Total number of requests fulfilled by a specific portlet.

Portlet response time (ms)

Average response time for a specific portlet.


ADP displays these metrics in both table and graph formats. For example, you can have four active portlets for a particular page. These active portlets are listed in the table and plotted in the graphs.

Drill down further to a specific page by expanding the Portlets node. Click the (plus) + icon to expand the tree view. This provides additional information about the page.

WebSphere Portals

The Portals node under Oracle Enterprise Manager contains information about all deployed WebSphere Portal applications in the managed cells. The Portals node is organized hierarchically using the same framework developers use to build these Portal applications. The minimum and maximum response time measurements are stored in the database in addition to the average response time measurements. These metrics, if present, display visually in the window on the right pane.

For WebSphere Portal, this hierarchy contains the following (Table 16-16, "WebSphere Portal Hierarchy"):

Table 16-16 WebSphere Portal Hierarchy

Component Description

Portals

The Portal is the logical containment unit for a Portal application. A typical Portal can contain a few desktops, several of books, tens of pages, and hundreds of portlets.

WebSphere

The WebSphere is the top-level container for the portal components included in that specific view of the portal.

Portal administrators can create new desktops beyond what portal developers create in WebLogic Workshop.

Virtual Portals

The top-level book contains all sub-books, pages, and portlets. The top-level book defines the initial menu navigation style used for the desktop. For each sub-book you add to a desktop you can select a different navigation style.

Content Root

Pages and sub-books are the navigable containers used for organizing portlets.

Header

Portlets are the containers that surface Web content and applications in your desktops.

Pages

Pages are containers within virtual portals, books, and sub-books. Pages often contain labels and portlets.

Labels

Labels are markers defining content within page containers.


When you click the Portals node under Oracle Enterprise Manager, ADP displays summary information on active portal applications. This summary includes the following (Table 16-17, "WebSphere Tree Summary"):

Table 16-17 WebSphere Tree Summary

Metrics Description

Portal web application activity

A summary of user sessions for a specific portal application.

Portal completions

Total number of requests fulfilled by a specific portal application.

Portal response time (ms)

Average response time for a specific portal application.


For Portal web application activity and Portal performance, ADP displays information in both table and graph formats. For the other metrics, ADP shows the information in graph format.

When you click the plus (+) icon next to the Portals node, ADP expands the tree to show all managed portal applications currently deployed on the WebLogic domain.

You can also see information specific to a particular portal application. By selecting a specific portal application, all information displayed in the Main Display Window changes to only show data relevant to this new context. For example, when a user selects the WebSphere portal application under the Portals node, the Main Display Window only shows information specific to WebSphere portal application.

At the Portal level, you can navigate to different levels of the portal application by using different tabs. Use the tabs available to quickly access lower level components.

The following is a list of the tabs available for portal level nodes and their descriptions (Table 16-18, "Portal Level Tab Descriptions").

Table 16-18 Portal Level Tab Descriptions

Tab Description

Summary

Performance summary specific to the selected portal

Analysis

Two performance analytics - Multi-Point Regression Analysis performed at the portal level and Entity Performance Ranking performed at the portlet level

Events

SLO violation events associated with the selected portal

WSRP Topology

View WSRP consumer-producer relationships and WSRP deployment topology

Errors/Exceptions

Errors metrics associated with the selected portal

Instrumentation

Includes performance data by different types of instrumentation probe points. There are different tabs available: Class, Method, Errors/Exceptions and Transactions. Each tab includes basic information such as Probe Point Name, Invocation Count, and Response Time. This detailed performance data can help you identify low-level bottlenecks. Refer Instrumentation for more details.


Virtual Portals

To reach the Virtual Portals node, further expand a particular portal application. By selecting this node, ADP provides a list of currently active portals associated with that portal application. See to view the Summary for the WebSphere portal application.

This Summary includes the following metrics (Table 16-19, "Virtual Portals Summary Metrics"):

Table 16-19 Virtual Portals Summary Metrics

Metrics Description

Virtual Portal Completions

Total number of requests fulfilled by a specific portal.

Virtual Portal Response Time (ms)

Average response time for a specific portal.


ADP displays these metrics in both table and graph formats. For example, you can have one active portal for the WebSphere portal application. The Content Root is listed in the table and Plotted in the graphs.

You can drill down further to specific portlets by expanding the Content Root node. Again, clicking on the plus (+) icon expands the tree view for you. ADP changes information in the Main Display Window to reflect new context - portlet.

ADP not only shows the performance metrics associated with a specific node, but it also displays other relevant settings for that node.

Display Virtual Portal - Structure Viewer

One of the unique capabilities of ADP is its automatic discovery and modeling of deployed applications. The Structure Viewer provides visibility into how a portal desktop is organized. To activate the Virtual Portal Viewer, right-click on a specific portal. Select the Display Virtual Portal menu option to access the viewer.

After the Structure Viewer appears, you can navigate through the portal structure by clicking the appropriate header. The ability to see the portal structure using the same perspective as portal end-users is a unique value especially for the IT support staff.

With the Structure Viewer, the IT support staff can speak the same language with end-users while at the same time looking at performance oriented information for a specific component. The IT support staff can also use the Structure Viewer to isolate a particular performance problem. By drilling down from the top-level desktop to individual portlets, the IT support staff can get more insight into which components are having performance problems.

The Structure Viewer consists of two main panes. The pane on the left is the Structure Viewer pane. This pane allows you to graphically navigate the portal desktop. The pane on the right is called the Main Display Window. The Main Display window displays performance information in the context of the selected component in the Desktop Structure pane. As you navigate through the portal desktop and click different components, the Main Display Window provides information relevant for that selected context.

The Main Display Window shows relevant performance metrics for different portal components.

Pages

Expand a particular portal to see the Pages node. By selecting the Pages node, ADP provides a list of currently active pages associated with the specific book.

This Pages Summary includes the following metrics (Table 16-20, "Pages Summary Metrics"):

Table 16-20 Pages Summary Metrics

Metrics Description

Page Completions

Total number of requests fulfilled by a specific page

Page Response Time (ms)

Average response time for a specific page


ADP displays these metrics in both table and graph formats.

Portlets

Expand a particular page to see the Portlets node. Select a Portlets node to view a list of currently active portlets associated with the specific page.

This Portlets Summary includes the following metrics (Table 16-21, "Portlet Metrics"):

Table 16-21 Portlet Metrics

Metrics Description

Portlet Completions

Total number of requests fulfilled by a specific portlet

Portlet Response Time (ms)

Average response time for a specific portlet


ADP displays these metrics in both table and graph formats. For example, you can have four active portlets for the Content Root page. These active portlets are listed in the table and plotted in the graphs.

Drill down further to a specific page by expanding the Portlets node. Click the plus (+) icon to expand the tree view.

Oracle BPEL Processes

The BPEL Processes node in the navigation tree contains information about all deployed Oracle BPEL processes within the managed domain. ADP organizes information for various process nodes into domains.

In the right-hand pane, you can view the minimum and maximum response time measurements stored in the database in addition to the average response time, arrivals, errors, and completions measurements. These metrics, if present, display visually in the window on the right pane.

When you select the root of the BPEL Processes tree, ADP displays the BPEL Processes Summary in the Main Display Window.

The BPEL Process Summary includes the following (Table 16-22, "BPEL Process Summary Metrics"):

Table 16-22 BPEL Process Summary Metrics

Metrics Description

Domain

Name of the OC4J domain container

Process

Name of the BPEL process

Arrivals

Total number of currently running instances for a specific BPEL process

Response Time (ms)

Average response time in milliseconds for a specific BPEL process

Completions

Total number of fulfilled requests for a specific BPEL process. A Completed status represents a BPEL process instance that has finished normally.

Errors

Total number of aborted instances of a specific BPEL process

Min Response Time (ms)

Minimum average response time in milliseconds for a specific BPEL process

Max Response Time (ms)

Maximum average response time in milliseconds for a specific BPEL process


ADP presents these metrics in a table format in the Main Display Window when you select the BPEL Processes node. Graphical representations of two metrics, Arrivals and Completions, are displayed below the table.

When you click the plus (+) icon next to the domains sub-node under the main BPEL Processes node, ADP expands the tree to show all managed BPEL domains currently deployed on that particular Oracle SOA Suite instance.

You can see information specific to a particular process. By selecting a specific process, all information displayed in the Main Display Window changes to only show data relevant to this new context.

To see the BPEL process work flow associated with a BPEL process, select the node, right-click and select the Display Functional View option. ADP displays the appropriate functional work flow diagram and associated performance data in a new pop-up window.

See Table 16-23, "BPEL Functional View Summary" for BPEL Functional View summary.

Table 16-23 BPEL Functional View Summary

Column/Metric Description

Activity

Name of a specific activity in the BPEL process

Type

Control Type for a specific node

Arrivals

Number of requests that have arrived for a specific node

Response Time (ms)

Average response time for a specific node

Completions

Number of completed requests for a specific node

Errors

Number of aborted instances for a specific node

Response Time Min (ms)

Minimum response time for a specific node

Response Time Max (ms)

Maximum response time for a specific node


By looking at this summary table, you can determine which BPEL process node is running slowly and whether there are errors.

In addition to the summary, the following views are available for a node:

  • Delay Analysis view

  • Metadata view

  • Partner Links view

  • Partner Link Type Role view

  • Partner Link Bindings view

  • Modeled Entities view

  • Topology view

You can get to these views by selecting the appropriate tab.

Delay Analysis View

Delay Analysis gives you a bird's eye view of a specific BPEL process. You can see what nodes in the BPEL process are taking up a majority of the average elapsed time. The red bar indicates the slowest BPEL process group or BPEL process node. The blue represents the time spent for the particular nodes.

Metadata View

The Metadata view displays the tables containing specific metadata associated with the selected active BPEL process being displayed in the left-hand pane. Information provided in this view includes caller and called class metadata information as well as general summarized metadata in relation to the BPEL process and the associated web services. Table 16-24, "Metadata View Summary" explains the metadata.

Table 16-24 Metadata View Summary

Column/Metric Description

SummaryTable -Process

Name of the BPEL process node

SummaryTable -Web Service

Name of the web service being called from the BPEL process

SummaryTable -Version

Version of the web service being called from the BPEL process

SummaryTable -Location

Location of the web service being called from the BPEL process

Caller Table - Caller Class

Class name for the caller class that is calling the BPEL process

Caller Table - Caller Method

Class method for the caller class that is calling the BPEL process

Caller Table -Target Host

Target host that the caller class targeted to instantiate the BPEL process

Caller Table -Target Port

Target port that the caller class targeted to instantiate the BPEL process

Caller Table -Target URL

Target URL that the call class targeted to instantiate the BPEL process

Caller Table - Invocation Count

Number of invocations of the BPEL process instantiated by the caller class

Caller Table - Response Time

Average response time of the BPEL process instantiated by the caller class

Called Clients Table - Called Class

Class name of the class that was called by the BPEL process

Called Clients Table - Target URL

Target URL of the class that was called by the BPEL process

Called Clients Table - Invocation Count

Number of invocations made from the BPEL Process to the called class.

Called Clients Table - Response Time

Response time of the called class


Partner Links View

The partner links view provides detailed information on the various roles related to how and why the partner link service is being utilized. The information provided includes both the caller and callee roles, as well as the partner link type. See Table 16-25, "Partner Links View Summary".

Table 16-25 Partner Links View Summary

Column/Metric Description

Partner Link

Name of the partner link

My Role

Role in regards to the BPEL process calling the partner link service

Partner Role

Role of the partner link service

Partner Link Type

Partner link category (type) of the service being called


Partner Link Type Role View

See Table 16-26, "Partner Link Type Role View Summary" describes the columns in the Partner Link Type Role view.

Table 16-26 Partner Link Type Role View Summary

Column/Metric Description

Name

Name of the partner link

Link Type Name

Category (type) of the partner link

Port Type

Partner link service URL


Partner Link Bindings View

The Partner Link Bindings view provides insight into the actual roles and types of the partner link instances which represent web services that have been bound by the BPEL process. See Table 16-27, "Partner Link Bindings View Summary".

Table 16-27 Partner Link Bindings View Summary

Column/Metric Description

Partner Link Role

Defines the web service role that the BPEL process will communicate with

Partner Link Type

Defines the web service type that the BPEL process will communicate with

WebService PortType

Name of the web service

WebService Port Namespace ID

URL of the webservice instance


Modeled Entities View

The modeled entities view consist of a list and count of the general entities as catalogued during the discovery phase of the resource configuration. The tables contain both a total entity count as well as a breakdown of the entity count by entity type. See Table 16-28, "Modeled Entities Summary".

Table 16-28 Modeled Entities Summary

Column/Metric Description

Total Entities Modeled Table - Total

Total entities (static label)

Total Entities Modeled Table - Count

Total number of entities catalogued during the discovery phase of the BPEL process

Modeled Entities Table - Entity Type

Entity type being catalogued as part of the discovery phase of the BPEL process

Modeled Entities Table - Count

Total number of entities catalogued during the discovery phase of the BPEL process for a particular entity type


Topology View

The Topology View utilizes the modeled entities that were captured during the discovery process to provide a bird's eye view of all of the various high-level relationships between BPEL processes, web services, and business services. You can toggle between static and dynamic relationship views using the tabs at the top of the Topology pane.

Node Hierarchy

Expanding a particular BPEL process further, the first item you see is the Node Hierarchy node. By selecting the Node Hierarchy node, ADP provides a list of nodes associated with the specific process.

When you click the plus (+) icon next to a specific Node Hierarchy node, ADP expands the tree to show BPEL process nodes in the Node Hierarchy. Click an individual BPEL process node to see the load and performance of the selected node in the Main Display Window.

The BPEL process node information also includes the name of the method invoked. This information is displayed as part of the summary table at the top of the main view window.

Oracle ESB

The Oracle ESB node under Oracle Enterprise Manager contains information about all of the deployed Oracle ESB servers running in the managed domain. ADP organizes the information for various Oracle ESB nodes into various categories.

When you select the root of the ESB tree, ADP displays the ESB Summary in the Main Display Window.

The ESB Summary includes the following (Table 16-29, "ESB Summary Metrics"):

Table 16-29 ESB Summary Metrics

Metric Description

ESB System

Name of ESB System

ESB Service

Name of the ESB Service identifier

Arrivals

Total number of ESB service instance arrivals

Completions

Total number of ESB service instance completions

Response Time

Total number of completed instances for a specific BPEL process. A Completed status represents a BPEL process instance that has finished normally.


ADP presents these metrics in a table format in the Main Display Window when you select the ESB node. When you click the plus (+) icon next to the ESB Systems sub-node under the main ESB node, ADP expands the tree to show all managed ESB Systems currently deployed on that particular Oracle SOA Suite instance.

You can see information specific to a particular ESB System. By selecting a specific ESB System, all information displayed in the Main Display Window changes to only show data and the topology relevant to this new context.

By looking at the summary table, you can find out which ESB node is running slowly and whether there are errors.

Besides the summary, the following views are available for the Node Hierarchy node:

  • Service Details view

  • Service Parent Details view

  • Service Definition view

  • Service Operations view

  • Operation Routing Rules view

  • Topology view

You can get to these views by selecting the appropriate tab.

Service Details View

The Service Details view provides specific information related to the details of the bound service process instances. Instance IDs and other descriptive details are included as part of this view. See Table 16-30, "Service Details View Summary".

Table 16-30 Service Details View Summary

Column/Metric Description

Service Name

Name of the ESB service

GUID

GUID of the ESB service

Qname

Canonical qualified name for the bound ESB service

Description

Description of the ESB service


Service Parent Details View

The Parent Service Details view provides specific information related to the details of the parent of the bound service process instances. Instance IDs, roles, and other descriptive details are included as part of this view. See Table 16-31, "Service Parent Details View Summary".

Table 16-31 Service Parent Details View Summary

Column/Metric Description

Service Name

Name of the parent ESB service

ParentGUID

GUID of the parent ESB service

ParentQname

Canonical qualified name for the parent of the bound ESB service

ParentType

Parent type of the parent ESB service

MyRole

Role of the caller of the parent ESB service instance

ParentRole

Role of the callee of the parent ESB service instance


Service Definition View

The Service Definition view contains information regarding the bound ESB service including the Business Service (ESB) WSDL and Port Type as well as the associated URLs. See Table 16-32, "Service Definition View Summary".

Table 16-32 Service Definition View Summary

Column/Metric Description

Service Name

Name of the ESB service

BusinessServiceWSDL

URL of the Business Service WSDL

BusinessServicePortType

Port type of the Business Service

ConcreteServiceWSDL

URL of the Concrete Service WSFL

ConcreteServiceURI

URI for the concrete service


Service Operations View

The Service Operations views provides details regarding the various method operations being executed. All information is provided in regards to the metadata associated with a specific business service instance. See Table 16-33, "Service Operations View Summary".

Table 16-33 Service Operations View Summary

Column/Metric Description

Service Name

Name of the ESB service

Name

Service operation name being executed

GUID

GUID of the ESB service

Qname

Canonical qualified name for the bound ESB service

Element

Associated element within the ESB Service

SchemaLocation

Schema location for the associated ESB service

Type

Type of ESB service operation


Operation Routing Rules View

The Operation Routing Rules view provides various details regarding the operation routing rules for Business Service operations. This includes the specific instance business service names being utilized for operations. See Table 16-34, "Operation Routing Rules View Summary".

Table 16-34 Operation Routing Rules View Summary

Column/Metric Description

Service Name

Name of the ESB service

Name

Instance name ID of the ESB service instance

GUID

GUID of the ESB service instance


Oracle WebCenter

Oracle WebCenter provides a set of features and services (for example, portlets, customization, and content integration) that simplify the process of reaching a solution with JSF applications. This solution brings information from multiple sources into a single interface, simplifying transactions and providing everything users need to support a given task within the application itself.

Table 16-35 WebCenter Tree Summary

Component Description

ADF Taskflows

ADF task flows provide a modular approach for defining control flow in an application. See ADF Task Flows.

JSF Pages

JSF page definition files define the binding objects that populate the data in UI components at runtime. See JSF Pages.

Portlets

Portlets are the containers that surface Web content and applications on desktops. See Portlets.


ADF Task Flows

Instead of representing an application as a single large JSF page flow, you can break it up into a collection of reusable task flows. Each task flow contains a portion of the application's navigational graph. The nodes in the task flows are activities. An activity node represents a simple logical operation such as displaying a view, executing application logic, or calling another task flow. The transactions between the activities are called control flow cases. A task flow consists of activities and control flow cases that define the transitions between activities.

User-Defined Taskflows

The following taskflows are available in WebCenter.

Table 16-36 Taskflow Activities

Activity Name Description

Managed Beans

A backing bean that is managed by the JSF framework and used during the JSF page lifecycle.

Taskflow Method Calls

Invokes a method, typically a method on a managed bean.

Taskflow Views

Displays a JSF page or page fragment. Multiple view activities can represent the same page or same page fragment.

Taskflow URL Views

Redirects the root view port (for example, a browserpage) to any URL-addressable resource, even from within the context of an ADF region.

Taskflow Calls

Calls an ADF bounded task flow from an ADFunbounded task flow or another bounded task flow

Routers

Evaluates an EL expression and returns an outcome based on the value of the expression. For example, a router in a credit check task flow might evaluate the return value from a previous method call and generate success, failure, or retry outcomes based on various cases. These outcomes can then be used to route control to other activities in the task flow.


Web 2.0 Service

Oracle WebCenter provides a wide range of Web 2.0 capabilities, including discussion forums, wikis, blogs, content services, RSS, presence, instant messaging, linking, tagging, and search. Both developers and business users can easily add these services to their pages to maximize productivity.

Table 16-37 Taskflow Activities

Activity Name Description

Managed Beans

A backing bean that is managed by the JSF framework and used during the JSF page lifecycle.

Taskflow Method Calls

Invokes a method, typically a method on a managed bean.

Taskflow Views

Displays a JSF page or page fragment. Multiple view activities can represent the same page or same page fragment.

Taskflow URL Views

Redirects the root view port (for example, a browserpage) to any URL-addressable resource, even from within the context of an ADF region.

Taskflow Calls

Calls an ADF bounded task flow from an ADFunbounded task flow or another bounded task flow

Routers

Evaluates an EL expression and returns an outcome based on the value of the expression. For example, a router in a credit check task flow might evaluate the return value from a previous method call and generate success, failure, or retry outcomes based on various cases. These outcomes can then be used to route control to other activities in the task flow.


JSF Pages

A typical JSF application couples a backing bean with each page in the application. The backing bean defines properties and methods that are associated with the UI components used on the page. The UI component's value is bound to the bean's property.

A Managed Bean is a backing bean that is managed by the JSF framework and used during the JSF page lifecycle.

Portlets

Portlets can display excerpts of other Web sites, generate summaries of key information, perform searches, and access assembled collections of information from a variety of data sources. You can use the portlets that Oracle or third parties provide, or create your own programmatically. Oracle WebCenter supports WSRP 1.0, WSRP 2.0, JSR 168, and Oracle PDK-Java. You can include any portlets adhering to those standards in your WebCenter applications.

Processes

The Processes node under Oracle Enterprise Manager contains information about all deployed WebLogic business processes in the managed domain. ADP organizes information for various process nodes into the following major categories:

  • Node Hierarchy

  • Persistent Containers

  • Instrumentation

The minimum and maximum response time measurements are stored in the database in addition to the average response time measurements. These metrics, if present, display visually in the window on the right pane.

When you select the root of the Processes tree, ADP displays the Processes Summary in the Main Display Window. See Table 16-38, "Process Summary Metrics".

Table 16-38 Process Summary Metrics

Metrics Description

Process

Name of process

Running

Total number of currently running instances for a specific process

Suspended

Total number of suspended instances for a specific process. A Suspended request from a user is a common cause for a process instance to go into a Suspended state.

Frozen

Total number of frozen instances for a specific process

Completed

Total number of completed instances for a specific process. A Completed status represents a process instance that has finished normally.

Aborted

Total number of aborted instances for a specific process

Terminated

Total number of terminated instances for a specific process. An external Terminate request would terminate a process instance.

Average Execution Time (ms)

Average execution completion time for a specific process


Tip:

Statistics on the number of process instances with Terminated, Aborted, and Frozen states can indicate abnormal operation of the WebLogic Integration application or container. It is possible to unfreeze Frozen process instances from WLI Console.

ADP presents these metrics in a table format in the Main Display Window when you select the Processes node. Graphical representations of two metrics, Running Instances and Average Execution Time, are displayed below the table.

When you click the plus (+) icon next to the Processes node, ADP expands the tree to show all managed processes currently deployed on the WebLogic domain.

You can see information specific to a particular process by selecting a specific process. All information displayed in the Main Display Window changes to only show data relevant to this new context.

To see the process work flow associated with a particular process, select the process node, right-click and select the Display Functional View option. ADP displays the appropriate functional work flow diagram and associated performance data in a new pop-up window.

Node Hierarchy

When expanding a particular process further, the first item you see is the Node Hierarchy node. By selecting the Node Hierarchy node, ADP provides a list of nodes associated with the specific process. See Table 16-39, "Node Hierarchy Summary".

Table 16-39 Node Hierarchy Summary

Column/Metric Description

Node

Name of a specific node

ID

Process Node ID for a specific node

Type

Control Type for a specific node

Method

Node Method Name for a specific node

Arrivals

Number of Requests Arrived for a specific node

Active

Number of Active Instances for a specific node

Elapsed Time (ms)

Average Time Elapsed to Complete an Instance for a specific node

Completions

Number of Completed Instances for a specific node

Aborts

Number of Aborted Instances for a specific node

Exceptions

Number of Exception Encountered for a specific nod.


By looking at this summary table, you can determine which process node is running slowly and whether there are aborts or exceptions.

The following additional views are available for the Node Hierarchy node:

  • Delay Analysis view

  • Events view

You can get to these views by selecting the appropriate tab.

Delay Analysis View

Delay Analysis gives you a bird's eye view of a specific process. You can see what nodes in the process are taking up a majority of the average elapsed time. The red bar indicates the slowest process group or process node. The blue represents the time spent for the particular nodes.

Events View

The Events view shows a list of SLO violations events relevant to this process in a table format. The Events view table includes the following information (Table 16-40, "Events View Summary"):

Table 16-40 Events View Summary

Column/Metric Description

Start Time

Start time for the process instance that violated a SLO

Entity Name

Name of the process node that violated a SLO

SLO Name

Name of the violated SLO

Service URI

URI of the process that violated a SLO

Application

Name of the application that violated a SLO

Event Type

Violation type (violation or cautionary)

Entity Type

Violation Metric type

SLO Threshold

Type of threshold (high or low)

SLO Trigger Value

Value that triggered a SLO violation


When you click the plus (+) icon next to a specific Node Hierarchy node, ADP expands the tree to show process nodes in the Node Hierarchy. Click an individual process node to see the load and performance of the selected node in the Main Display Window.

The process node information also includes the name of the method invoked. This information is displayed as part of the summary table at the top of the main view window.

Persistent Containers

When you expand a particular process further, the Persistent Containers node is included. By selecting the Persistent Containers node, ADP provides a list of persistence performance statistics relevant to the selected process.

As you select the root of the Persistent Containers tree, a summary of all Persistent Containers relevant to the selected process is presented. For example, a summary can contain the following high level items:

  • Container persistence invocations

  • Container persistence response time (milliseconds)

  • Entity EJB activity

  • Entity EJB cache

  • Entity EJB transactions

  • Entity EJB locking

These items are displayed in both table and graph formats.

The Persistent Containers Summary includes different tables:

  • Entity EJB Activity

  • Entity EJB Cache

  • Entity EJB Transactions

  • Entity EJB Locking

Entity EJB Activity Table

Entity EJB Activity table (Table 16-41, "Entity EJB Activity Table") includes the following information:

Table 16-41 Entity EJB Activity Table

Metrics Description

EJB

Name of the Entity EJB

In Use

Number of instances for a specific Entity EJB currently being used from the free pool. [Snapshot Count]

Idle

Number of instances for a specific Entity EJB currently in the idle state in the free pool. These bean instances are available for use. [Snapshot Count]

Waits

Number of Threads currently waiting for a specific Entity EJB bean instance from the free pool [Snapshot Count]

Timeouts

Total number of Threads that have timed out waiting for an available bean instance from the free pool [Aggregated Count]


Tip:

Pay attention to Waits and Timeouts metrics. Activities in the Waits metric and increasing count in the Timeouts metric are signs that requests waiting to be serviced by the EJB container. Ideally, 0 should be indicated for these metrics.
Entity EJB Cache Table

Entity EJB Cache table (Table 16-42, "Entity EJB Cache Table") includes the following information:

Table 16-42 Entity EJB Cache Table

Metrics Description

EJB

Name of the Entity EJB

Hits

Total number of times an attempt to access the Entity EJB instance from the cache succeeded [Aggregated Count]

Accesses

Total number of attempts to access the Entity EJB instance from the cache [Aggregated Count]

Size

Number of beans instances from this EJB Home currently in the EJB cache [Snapshot Count]

Activations

Total number of beans from this EJB Home that have been activated [Aggregated Count]

Passivations

Total number of beans from this EJB Home that have been passivated [Aggregated Count]


Tip:

Passivation (serializing EJB state information to disk) and activation (reconstituting EJB state information from disk) are resource intensive operations. Ideally, it is preferable to see low level of activity in these metrics.
Entity EJB Transactions Table

Entity EJB Transactions table (Table 16-43, "Entity EJB Transactions Table") includes the following information:

Table 16-43 Entity EJB Transactions Table

Metrics Description

EJB

Name of the Entity EJB

Commits

Total number of transactions that have been committed for this EJB. [Aggregated Count]

Rollbacks

Total number of transactions that have been rolled back for this EJB. [Aggregated Count]

Timeouts

Total number of transactions that have timed out for this EJB. [Aggregated Count]


Tip:

High number of EJB Transaction Rollbacks may indicate problems with the data used - for some reason the target database is unable to commit the change. High number of EJB Transaction Timeouts may indicate problems accessing the database including network outage, database lock contention, database outage, and more.
Entity EJB Locking Table

Entity EJB Locking table (Table 16-44, "Entity EJB Locking Table") includes the following information:

Table 16-44 Entity EJB Locking Table

Metrics Description

EJB

Name of the Entity EJB

Entries

Number of Entity EJB instances currently locked [Snapshot Count]

Lock Accesses

Total number of attempts to obtain a lock on an Entity EJB instance [Aggregated Count]

Current Waiters

Number of Threads that currently waiting for a lock on an Entity EJB instance [Snapshot Count]

Total Waiters

Total number Threads that have waited for a lock on an Entity EJB instance [Aggregated Count]

Timeouts

Total number Threads that have timed out waiting for a lock on an Entity EJB instance [Aggregated Count]


Tip:

Pay attention to Current Waiters and Timeouts. These metrics can indicate possible performance problems caused by EJB Locking. Ideally, 0s should be displayed for these metrics.

By looking at the activities related to Persistence Containers, you can determine if EJB persistence calls are causing performance problems.

Instrumentation

When expanding a particular process further, the last item you see is the Instrumentation node. Click the plus (+) icon next to Instrumentation to expand the tree to reveal the following categories of instrumentation:

  • Class

  • Methods

  • Errors/Exceptions

  • Transactions

The Class node in the Instrumentation tree provides the following information (Table 16-45, "Class Node"):

Table 16-45 Class Node

Column/Metric Description

Probe Point

Class name in which instrumentation probe point is inserted

Response Time (ms)

Average response time for a specific class

Invocation Count

Number of times a specific class is called


The Method node in the Instrumentation tree provides the following information (Table 16-46, "Method Node"):

Table 16-46 Method Node

Column/Metric Description

Probe Point

Method name in which instrumentation probe point is inserted

Response Time (ms)

Average response time for a specific method

Invocation Count

Number of times a specific method is called


The Errors/Exceptions and Transactions are described in Architecture View.

Web Services

The Web Services node in the navigation tree contains information about all deployed Web Services in the managed domain. By selecting the Web Services node under Oracle Enterprise Manager, ADP shows the Web Services Summary in the Main Display Window.

This summary view lists all discovered web services and their associated URL entry points. Below this list, ADP lists out all active web services and their performance data (invocation count and response time).

When you click the plus (+) icon next to the Web Services node, ADP expands the tree to show all monitored web services currently deployed on the WebLogic domain.

When you select a specific web service, ADP displays performance data associated with the selected web service. Click the plus (+) icon next to a specific web service to expand the tree to show all public operations associated with that web service.

The Operations table provides the following information (Table 16-47, "Operations Table"):

Table 16-47 Operations Table

Column/Metric Description

Operation

Name of the web service operation

Invocation Count

Number of times the operation is called

Response Time (ms)

Average response time for the operation in milliseconds

Delay (ms)

Overall delay contributed by the operation in milliseconds


Pageflows

The Pageflows node in the navigation tree contains information about all deployed pageflows in the managed domain. By selecting the Pageflows node under Oracle Enterprise Manager, ADP shows the Pageflows Summary in the Main Display Window.

Services

The Services node in the navigation tree contains information about all external entry points into the managed domain. ADP currently monitors the following types of services:

  • HTTP

  • EJBs

  • JDBC

Selecting each service type reveals service summary in the Main Display Window.

The minimum and maximum response time measurements are stored in the database in addition to the average response time measurements. These metrics, if present, display visually in the window in the right pane.

ADP displays entry point activity summary associated with the selected EJB service.

Tip:

Setting thresholds at some of these entry points enables ADP to monitor the performance of key business services. When a violation event occurs, you can begin investigating from the Service node.

HTTP

Expanding the HTTP node under the Services node reveals a list of discovered HTTP based entry points into the managed domain. HTTP service end points include JSPs, struts actions, and servlet mappings. These discovered HTTP entry points are listed by their root context. When you select a specific HTTP entry point, ADP displays the associated summary in the Main Display Window.

When a specific file is selected, ADP displays more detailed performance data.

Method level performance data is displayed when you select a specific HTTP service entry point.

Table 16-48 HTTP Performance Summary

Column/Metric Description

Servlet

Name of the servlet associated with the selected service

Method

Name of the method invoked by external call

Arrivals

Total number of requests received by this method

Invocation Count

Total number of method invocations

Response Time (ms)

Average method response time in milliseconds


EJBs

To view the performance summary for EJBs invoked from outside the JVM, click the EJBs node.

Table 16-49 EJB Performance Summary

Column/Metric Description

EJB

Name of the EJB

Invocation Count

Number of times the EJB is called

Response Time (ms)

Average response time for the EJB in milliseconds

Delay (ms)

Overall delay contributed by the EJB in milliseconds


Tip:

As a general rule, external calls that terminate in EJBs are RMI calls. Web services calls that ultimately terminate in EJBs use SOAP and enter the application server via HTTP.

JDBCs

To bring up the performance summary for JDBC operations invocated from outside of the JVM, click the JDBC node.

Table 16-50 JDBC Performance Summary

Column/Metric Description

SQL Statement

Generalized SQL Statement executed by the JDBC operation

Class

Name of the class used in the JDBC operation

Method

Name of the method used in the JDBC operation

Invocation Count

Number of times the JDBC operation is called

Response Time (ms)

Average response time for the JDBC operation in millisecond

Delay (ms)

Overall delay contributed by the JDBC operation in milliseconds


WSRP Producers

The Web Services Remote Portlet (WSRP) Producers node in the navigation tree contains information about the WebLogic WSRP consumer - producer relationships in the managed domain. By selecting an entity in the WSRP node, ADP displays the performance measurements for the associated WSRP consumer or producer.

WebLogic Portal can act as either a WSRP remote producer or as a consumer. When acting as a consumer, WebLogic Portal's remote--or proxy--portlets are WSRP-compliant. These portlets present content that is collected from WSRP-compliant producers, allowing you to use external sources for portlet content, rather than having to create its content or its structure yourself.

The following types of portlets can be exposed with WSRP inside a WebLogic portal:

  • Page flow portlets

  • JavaServer Pages (JSP) portlets

  • Struts portlets

  • Java portlets (JSR168; supported only for complex producers)

  • JavaServer Faces (JSF) portlets

The minimum and maximum response time measurements are captured in addition to the average response time measurements. These metrics, if present, display visually in the window in the right pane.

WSRP Summary

To view the WSRP Producers Summary:

  1. Select the WSRP Producers node to show the WSRP Producers Summary tab.

    The WSRP Producers summary includes the following table (Table 16-51, "WSRP Producers Summary"):

    Table 16-51 WSRP Producers Summary

    Column Description

    WSRP Producer

    Name of the producer portlet

    WSDL URL

    URL of the WSD.


  2. To view the portlet details, click the Consumer Portlets node under the WSRP Producers.

    The following tables are in this view:

    • WSRP Producer Information

    • WSRP Consumer Portlet Performance

      Select the portlet name and right click. Select Open to drill down to more detailed view.

    • WSRP Producer Portlets

      Select the portlet name and right click. Select Open to drill down to more detailed view.

    Table 16-52 WSRP Producers Information

    Column Description

    TestPortlets

    Defined by the user for the Producer, for example description, handle, and more

    URL

    Lists the details of each item under the TestPortlet column


    Table 16-53 WSRP Consumer Portlet Performance

    Column Description

    Portal

    The Portal is the logical containment unit for a Portal application. A typical Portal can contain a few desktops, several of books, tens of pages, and hundreds of portlets.

    Desktop

    The desktop is the top-level container for the portal components included in that specific view of the portal.

    Portal administrators can create new desktops beyond what portal developers create in WebLogic Workshop.

    Book

    The top-level book contains all sub-books, pages, and portlets. The top-level book defines the initial menu navigation style used for the desktop. For each sub-book, you add to a desktop you can select a different navigation style.

    Page

    Pages and sub-books are the navigable containers used for organizing portlets.

    Portlet

    Portlets are the containers that surface Web content and applications in your desktops.

    Response Time (ms)

    Average response time in milliseconds.

    Completions

    Number of Completed Instances for a specific node.

    Response Time Min (ms)

    Minimum response time in milliseconds.

    Response Time Max (ms)

    Maximum response time in milliseconds.


    Table 16-54 WSRP Producer Portlets

    Column Description

    Producer Portlet

    Name of the producer portlet

    Producer

    Name of the producer


  3. Click a portlet name in the tree view to see the performances associated with the consumer and producer portlets.

WSRP Topology

Use this option to visually explore WSRP consumer - producer relationships and the WSRP deployment topology.

To view the WSRP Topology:

  1. Select the WSRP Producers node to show the WSRP Topology tab.

  2. Click the WSRP Topology tab to view the details.

Display Portal Desktop

The portal desktop is described in Display Portal Desktop - Desktop Structure Viewer.

Access the Architecture View:

  1. To view the portal desktop for a specific portlet, right-click the portlet name under the Consumer Portlet node.

  2. Select Display Portal Desktop.

  3. You can drill down to view the Architecture View from this view. See the instructions in Portlet Drill Down.

Integration

The Integration node under Oracle Enterprise Manager contains information about the WebLogic Integration resources in the managed domain. By selecting the Integration node under Oracle Enterprise Manager, ADP displays the Integration Summary.

The Integration Summary includes the following (Table 16-55, "Integration Summary"):

Table 16-55 Integration Summary

Metric Description

Process

Name of process

Running

Total number of currently running instances for a specific process

Suspended

Total number of suspended instances for a specific process

Frozen

Total number of frozen instances for a specific process

Completed

Total number of completed instances for a specific process

Aborted

Total number of aborted instances for a specific process

Terminated

Total number of terminated instances for a specific process

Average Execution Time

Average execution completion time for a specific process


Tip:

Statistics on the number of process instances with Terminated, Abort, and Frozen states can indicate abnormal operation of WebLogic Integration application or container. It is possible to unfreeze Frozen process instances from WLI Console.

ADP presents these metrics in a table format in the Main Display Window when you select the Integration node. Graphical representations of these metrics, Running Instances, Completed Instances, and Average Execution Time, are displayed below the table.

Expand the Integration tree by clicking on the plus (+) icon next to Integration node.

The expanded Integration tree allows you to look at various components of WebLogic Integration and help identify performance bottlenecks. This section explains the nodes under the Integration Tree.

Health

In the expanded Integration tree, the first node you see is the Health node. Under the Health node, ADP lists various subsystems in WebLogic Integration. By expanding the Health node, you can see the following:

  • Execute Queues

  • Async Dispatchers

  • Sync Dispatchers

  • JMS Destinations

  • Stateless Containers

  • Persistent Containers

You can get to the health information specific to each of these subsystems by clicking the appropriate node. Also, you can get to a particular instance of a subsystem.

Execute Queues

In the Execute Queues node, ADP provides operational statistics of each execute queues configured for WebLogic Integration. Select the Execute Queues node in the Monitor Workspace to display the Execute Queues Summary in the Main Display Window.

The Execute Queues Summary provides the following information (Table 16-56, "Execute Queues Summary"):

Table 16-56 Execute Queues Summary

Metric Description

Execute Queue

Execute Queue ID

Aggregated Execute Queue

Aggregated execute queue statistics per resource

Idle Threads

Current number of idle threads in a specific Execute Queue

Pending Threads

Current number of pending threads in a specific Execute Queue

Requests

Total number of requests serviced for a specific Execute Queue

Total Threads

Total number of threads configured in a specific Execute Queue


Tip:

Pay attention to Idle Threads and Pending Threads counts. Rapidly decreasing Idle Threads count combined with rapidly increasing Pending Threads count can indicate a backup in the Execute Queue.

Use the following guidelines to adjust the Execute Queue Thread Count (Table 16-57, "Guidelines to Adjust the Execute Queue Thread Count"):

Table 16-57 Guidelines to Adjust the Execute Queue Thread Count

Execute Queue Is Backed Up? Application Is CPU Bound? Adjustment Guideline

Yes

No

Increase execute queue thread count.

Yes

Yes

Decrease thread count and explore JVM or application issues that may be causing high CPU utilization.


ADP presents these metrics in a table format in the Main Display Window when you select the Health node. Graphical representations of these metrics, Idle Treads, Pending Threads, and Requests, are displayed below the table.

Expand the Health tree by clicking on the plus (+) icon next to Health node. You can get the same summary as previously described for a specific execute queue.

Async Dispatchers

In the Async Dispatcher node, ADP provides operational statistics of each of the Async Dispatchers configured in WebLogic Integration. Select the Async Dispatchers node in the Monitor Workspace to show the Async Dispatchers Summary in the Main Display Window.

The Async Dispatcher Summary includes the following information (Table 16-58, "Async Dispatcher Summary"):

Table 16-58 Async Dispatcher Summary

Metric Description

EJB

Name of the Message Driven EJB

In Use

Number of instances for a specific Message Driven EJB currently in use

Idle

Number of instances for a specific Message Driven EJB currently in the idle state

Waits

Number of instances for a specific Message Driven EJB currently in the wait state

Timeouts

Number of instances for a specific Message Driven EJB currently in the timeout state

Commits (Transaction)

Total number of commits performed for a specific Message Driven EJB

Rollbacks (Transaction)

Total number of transaction rollbacks performed for a specific Message Driven EJB

Timeouts (Transaction)

Total number of transaction timeouts performed for a specific Message Driven EJB


Tip:

Rapidly increasing counts in MDB Waits and Timeouts metrics may indicate a tuning opportunity for the MBD container. Furthermore, increasing numbers in the Transaction Rollbacks and Timeouts metrics may indicate issues interacting with the database. Ideally, these metrics should not increase rapidly.

ADP presents these metrics in a table format in the Main Display Window when you select the Async Dispatchers node. Graphical representation of one metrics, Message Driven EJB in use, is displayed below the table.

Expand the Async Dispatchers tree by clicking the plus (+) icon next to Async Dispatchers node. You can get the same summary as previously described for a specific async dispatcher.

Sync Dispatchers

In the Sync Dispatchers node, ADP provides operational statistics of each of the Sync Dispatchers used by WebLogic Integration. Select the Sync Dispatchers node in the Monitor Workspace to show the Sync Dispatchers Summary in the Main Display Window.

The Sync Dispatcher Summary includes the following information (Table 16-59, "Sync Dispatcher Summary"):

Table 16-59 Sync Dispatcher Summary

Metric Description

EJB

Name of the Stateless EJB

In Use

Number of instances for a specific Stateless EJB currently in use

Idle

Number of instances for a specific Stateless EJB currently in the idle state

Waits

Number of instances for a specific Stateless EJB currently in the waits state

Timeouts

Number of instances for a specific Stateless EJB currently in the timeouts state


Tip:

Rapidly increasing counts in Stateless EJB Waits and Timeouts metrics may indicate performance issues and a tuning opportunity for the EJB container. Ideally, these metrics should not increase at a rapid pace.

ADP presents these metrics in a table format in the Main Display Window when you select the Sync Dispatchers node. Graphical representation of one metrics, Stateless EJB in use, is displayed below the table.

Expand the Sync Dispatchers tree by clicking on the plus (+) icon next to Sync Dispatchers node. You can get the same summary as previously described for a specific sync dispatcher.

JMS Destinations

In the JMS Destination node, ADP provides operational statistics of each of the JMS Destinations used by WebLogic Integration. Select the JMS Destinations node in the Monitor Workspace to show the JMS Destinations Summary in the Main Display Window.

JMS Destination Summary includes the following tables: JMS destination message statistics and JMS destination byte statistics. The JMS destination message statistics table includes the following information (Table 16-60, "JMS Destination Message Statistics").

Table 16-60 JMS Destination Message Statistics

Column/Metric Description

JMS Destination

Name of the JMS destination

Message Current

Number of JMS messages currently at a specific JMS destination

Message High

Maximum number of JMS messages at a specific JMS destination

Message Pending

Number of JMS messages pending to be delivered to a specific JMS destination

Message Received

Total number of JMS messages at a specific JSM destination


Tip:

Pay attention to Message Pending metric. Too many pending messages in a specific JMS destination could result in a performance slowdown. Rapidly increasing count for the Message Pending metric may indicate a performance problem and a JMS destination tuning opportunity.

The JMS destination byte statistics table includes the following information (Table 16-61, "JMS Destination Byte Statistics").

Table 16-61 JMS Destination Byte Statistics

Column/Metric Description

JMS Destination

Name of the JMS destination

Byte Current

Byte count of JMS messages currently at a specific JMS destination

Byte High

Maximum byte count of JMS messages at a specific JMS destination

Byte Pending

Byte count of JMS messages pending to be delivered to a specific JMS destination

Byte Received

Total Byte count of JMS messages at a specific JMS destination


ADP presents these metrics in table format in the Main Display Window when you select the JMS Destinations node. Graphical representations of the following metrics, Message pending and Byte pending, are displayed below the table.

Expand the JMS Destinations tree by clicking on the plus (+) icon next to JMS Destinations node. You can get the same summary as described above for a specific JMS destination.

Stateless Containers

In the Stateless Containers node, ADP provides operational statistics of each of the Stateless Containers used by WebLogic Integration. Select the Stateless Containers node in the Monitor Workspace to show the Stateless Containers Summary in the Main Display Window.

The Stateless Containers Summary includes the following information (Table 16-62, "Stateless Containers Summary"):

Table 16-62 Stateless Containers Summary

Metric Description

EJB

Name of the Stateless EJB

Stateless EJB Transactions

Runtime statistics. You can monitor stateless session EJBs using the metrics in this table.

In Use

Number of instances for a specific Stateless EJB currently being used from the free pool [Snapshot Count]

Idle

Number of instances for a specific Stateless EJB currently in the idle state in the free pool. These bean instances are available for use. [Snapshot Count]

Waits

Number of Threads currently waiting for a specific Stateless EJB instance from the free pool [Snapshot Count]

Timeouts

Total number of Threads that have timed out waiting for an available bean instance from the free pool [Aggregated Count]


ADP presents these metrics in a table format in the Main Display Window when you select the Stateless Containers node. Graphical representation of one metrics, Stateless EJB in use, is displayed below the table.

Expand the Stateless Containers tree by clicking on the plus (+) icon next to Stateless Containers node. You can get the same summary as previously described for a specific stateless container.

Persistent Containers

In the Persistent Containers node, ADP provides operational statistics of each of the Persistent Containers used by WebLogic Integration. Select the Persistent Containers node in the Monitor Workspace to show the Persistent Containers Summary in the Main Display Window.

The Persistent Containers Summary includes the following tables:

  • Entity EJB Activity

  • Entity EJB Cache

  • Entity EJB Transactions

  • Entity EJB Locking

Entity EJB Activity table includes the following information (Table 16-63, "Entity EJB Activity"):

Table 16-63 Entity EJB Activity

Metrics Description

EJB

Name of the Entity EJB

In Use

Number of instances for a specific Entity EJB currently being used from the free pool [Snapshot Count]

Idle

Number of instances for a specific Entity EJB currently in the idle state in the free pool. These bean instances are available for use. [Snapshot Count]

Waits

Number of Threads currently waiting for a specific Entity EJB bean instance from the free pool [Snapshot Count]

Timeouts

Total number of Threads that have timed out waiting for an available bean instance from the free pool [Aggregated Count]


Tip:

Pay attention to Waits and Timeouts metrics. Activities in the Waits metric and increasing count in the Timeouts metric are signs that requests waiting to be serviced by the EJB container. Ideally, 0 should be indicated for these metrics.

Entity EJB Cache table includes the following information (Table 16-64, "Entity EJB Cache"):

Table 16-64 Entity EJB Cache

Metrics Description

EJB

Name of the Entity EJB

Hits

Total number of times an attempt to access the Entity EJB instance from the cache succeeded [Aggregated Count]

Accesses

Total number of attempts to access the Entity EJB instance from the cache [Aggregated Count]

Size

Number of beans instances from this EJB Home currently in the EJB cache [Snapshot Count]

Activations

Total number of beans from this EJB Home that have been activated [Aggregated Count]

Passivations

Total number of beans from this EJB Home that have been passivated [Aggregated Count]


Tip:

Passivation (serializing EJB state information to disk) and activation (reconstitute EJB state information from disk) are resource intensive operations. Ideally, Oracle recommends low level of activity in these metrics.

Entity EJB Transactions table includes the following information (Table 16-65, "Entity EJB Transactions"):

Table 16-65 Entity EJB Transactions

Metric Description

EJB

Name of the Entity EJB

Commits

Total number of transactions that have been committed for this EJB [Aggregated Count]

Rollbacks

Total number of transactions that have been rolled back for this EJB [Aggregated Count]

Timeouts

Total number of transactions that have timed out for this EJB [Aggregated Count]


Tip:

High number of EJB Transaction Rollbacks may indicate problems with the data used - for some reason the target database is unable to commit the change. High number of EJB Transaction Timeouts may indicate problems accessing the database including network outage, database lock contention, database outage, and more.

Entity EJB Locking table includes the following information (Table 16-66, "Entity EJB Locking"):

Table 16-66 Entity EJB Locking

Metric Description

EJB

Name of the Entity EJB

Entries

Number of Entity EJB instances currently locked [Snapshot Count]

Lock Accesses

Total number of attempts to obtain a lock on an Entity EJB instance [Aggregated Count]

Current Waiters

Number of Threads that currently waiting for a lock on an Entity EJB instance [Snapshot Count]

Total Waiters

Total number Threads that have waited for a lock on an Entity EJB instance [Aggregated Count]

Timeouts

Total number Threads that have timed out waiting for a lock on an Entity EJB instance [Aggregated Count]


Tip:

Pay attention to Current Waiters and Timeouts. These metrics can indicate possible performance problems caused by EJB Locking. Ideally, 0s should be displayed for these metrics.

ADP presents these metrics in a table format in the Main Display Window when you select the Persistent Containers node. Graphical representations of three metrics, Entity EJB in use, Entity EJB cache access, and Entity EJB lock access, are displayed below the table.

Expand the Persistent Containers tree by clicking on the plus (+) icon next to Persistent Containers node. You can get the same summary as previously described for a specific persistent container.

Performance

In the expanded Integration tree, the second node you see is the Performance node. ADP provides the Performance Summary for WebLogic Integration in the Main Display Window when the Performance node is selected.

The Performance Summary includes the following tables: Process Node and Events. The Process Node table provides performance information for various process nodes running in WebLogic Integration. It includes the following information (Table 16-67, "Performance - Process Node Summary"):

Table 16-67 Performance - Process Node Summary

Column/Metric Description

Node

Name of a specific node

ID

Process Node ID for a specific node

Type

Control Type for a specific node

Method

Node Method Name for a specific node

Arrival

Number of Requests Arrived for a specific node

Active

Number of Active Instances for a specific node

Elapsed Time

Average Time Elapsed to Complete an Instance for a specific node

Completions

Number of Completed Instances for a specific node

Aborts

Number of Aborted Instances for a specific nod.

Exceptions

Number of Exception Encountered for a specific node


Tip:

You can use Arrivals and Elapsed Time data collected by ADP to characterize the performance of your installation. Since ADP measures performance at cluster level, you are capturing the actual performance of your configuration. You can also perform simple capacity planning analysis by plotting Arrivals versus Elapsed Time (arrival rate versus response time). Ask your Oracle consultant for more information.

The Events table provides a list of SLO violations triggered relevant to WebLogic Integration. It includes the following information (Table 16-68, "Performance - Events Node Summary"):

Table 16-68 Performance - Events Node Summary

Column/Metric Description

Start Time

Start time for the process instance that violated a SLO

Entity Name

Name of the process node that violated a SLO

SLO Name

Name of the violated SLO

Service URI

URI of the process that violated a SLO

Application

Name of the application that violated a SLO

Event Type

Violation type (violation or cautionary)

Entity Type

Violation Metric type

SLO Threshold

Type of threshold (high or low)

SLO Trigger Value

Value that triggered a SLO violation


Channels

In the expanded Integration tree, the third node you see is the Channels node. ADP shows the Channels Summary for various channels configured for WebLogic Integration.

The Channels Summary includes the following information (Table 16-69, "Channels Summary"):

Table 16-69 Channels Summary

Column/Metric Description

Channel

Name of channel

Type

Channel type

Message Count

Total number of messages processed for a specific channel

Dead Message Count

Total number of dead messages for a specific channel


Tip:

Increasing count in the Dead Message Count metric may indicate a configuration issue. When the Message Broker is unable to determine the URI to send a message to, the message is sent to the appropriate deadletter channel. Ensure the URI configured for the channel is reachable.

Expand the Channels tree by clicking the plus (+) icon next to Channels node. You can get the same health summary as previously described for a specific channel.

Subscribers

In the expanded Integration tree, the fourth node you see is the Subscribers node. ADP shows the Subscribers Summary for various subscribers configured for WebLogic Integration.

Expand the Subscribers tree by clicking the plus (+) icon next to Subscribers node. You can get specific information about an individual subscriber.

Applications

The Applications node in the navigation tree contains information about all deployed applications in the managed domain. By selecting the Applications node, ADP displays the Applications Summary.

The Applications Summary includes the following information (Table 16-70, "Applications Summary"):

Table 16-70 Applications Summary

Column/Metric Description

Application

Name of application

Status

Operations status for a specific application

Response Time (ms)

Average response time in milliseconds for a specific application. This is the average of response times of all JSPs and servlets contained in the deployment archive.

Invocation Count

Total number of invocations for a specific application. This is the total invocation count of all JSPs and servlets contained in the deployment archive.


Tip:

Application is a packaging unit in Java EE. Each EAR, WAR, and JAR files deployed to the application server is considered an individual application. These metrics track performance and arrival rate of these entities.

ADP presents these metrics in a table format in the Main Display Window when you select the Applications node. Graphical representations of the following metrics, Response Time, Invocation Count, and Active Sessions, are displayed below the table.

Expand the Applications tree by clicking the plus (+) icon next to Applications node. You can get more information about a specific application.

ADP displays performance summary for the selected application in the Main Display Window. You can obtain additional performance data by clicking different tabs in the Main Display Window.

The Applications Summary includes the following tabs (Table 16-71, "Applications Summary Tabs"):

Table 16-71 Applications Summary Tabs

Tab Name Description

Summary

Includes performance data at the application level including time-based trend graphs of Application Response Time, Application Invocation Count, and Application Active Sessions. The invocation count and response time for the top 10 slowest servlets, the usual application entry points, are also included.

Response Times

Includes time-based trend graphs of component response times. Graphs include Servlet Response Time, EJB Response Time, and JDBC Response Time.

Invocations

Includes time-based trend graphs of component invocation counts. Graphs include Servlet Invocation Count, EJB Invocation Count, and JDBC Invocation Count.

Errors/Exceptions

Errors metrics associated with the selected portal.

Transactions

Transaction events associated with the selected portal and children below.By default, the Transactions tab is not enabled.

Modeled Entities

Includes a catalog of entities modeled by ADP. Only the modeled entities associated with the selected application are included.

Instrumentation

Includes performance data by different types of instrumentation probe points. There are different tabs available: Class, Method, and SQL. Each tab includes basic information such as Probe Point Name, Invocation Count, and Response Time. This detailed performance data can help you identify low-level bottlenecks.

Topology

Includes the topology view associated with the selected application.


Under each named application node, ADP displays performance and other relevant information specific to that application. For example, by clicking the children nodes, the relevant data is displayed in the Main Display Window. Application response time and invocations measurements can be reached by clicking the panes in the Main Display Window.

In this section, we will further expand on the following nodes:

  • Services

  • Dependencies

  • Deployments

  • Workshop Projects

  • Web Applications

  • Stateless Beans

  • Stateful Beans

  • Entity Beans

  • Message Driven Beans

Note:

The number of children nodes available under each application node depends solely on the complexity of the selected application. Simple Java EE web applications will not have nodes like Workshop Projects, Stateless Beans, Stateful Beans, Entity Beans, and Message Driven Beans.

Services

The Services node includes all the external entry points associated with the selected application. When this node is selected, ADP displays a summary view in the Main Display Window. ADP displays the performance data associated with various entry points associated with the selected application.

Tip:

The children nodes under the Services node include entry point specific performance data.

Dependencies

The Dependencies node shows a list of internal and external components and share resources that a specific application depends on for its normal operation. When the Dependencies node is selected, ADP displays all external references made by the application in the Main Display Window. The following is a list of columns and their descriptions (Table 16-72, "Dependencies Column Descriptions"):

Table 16-72 Dependencies Column Descriptions

Column/Metric Description

Name

Display name of the component or resource used by the application. If this is undefined in the Deployment Descriptor, the reference name for the component is used.

Reference

Reference name of the component or resource used by the application.

Reference Type

Component or resource type.

Referer Component

Name of the component that is part of the application which obtained the reference to external component or resource.

Referer Module

Name of the module that is part of the application which obtained the reference to external component or resource.


ADP displays all the references associated with components in the selected application.

The Dependencies node can be further expanded by clicking the plus (+) icon. The children nodes of the Dependencies node are organized by type. Here are the list of dependency types and their descriptions (Table 16-73, "Dependency Types"):

Table 16-73 Dependency Types

Dependency Type Description

Data Sources

All shared data sources used by the application

Entity Beans

All entity beans used by the application

Session Beans

All session beans used by the application

JMS Queues

All JMS queues used by the application for publishing JMS messages

JMS Topics

All JMS topics subscribed by the application

Web Services

All web services used by the application


When a specific node is selected, ADP displays relevant performance summary. These nodes can also be expanded by clicking the plus (+) icons. The expanded tree includes specific components and share resources used by the application.

The Performance summary view associated with the Data Sources node under Dependencies provides information on both connection pools and SQL statements.

For more information on the metric description, refer to Metric Types.

Deployments

The Deployments node shows the architecture of the deployed application. When this node is selected, ADP shows all the modules deployed as part of this application. The default view in the Main Display Window shows the active module-level call path. Table 16-74, "Deployment Tabs" lists the tabs available as part of this summary view and their descriptions.

Table 16-74 Deployment Tabs

Tab Name Description

Module Level Execution

Shows the active calling relationships among various Java EE modules (EAR, WAR, JAR, and more). Shared resources are also included. This is the default Architecture View at the module level.

Module Level

Shows the potential calling relationships among various Java EE modules. Shared resources are also included. By default, the Module Level tab is not enabled.

Instrumentation

Includes detailed performance data at the method level. The table includes caller components, caller method, callee (target) component, callee module, invocation count, and response time.

SQL Statement

Includes all SQL statements executed as part of this application. It also includes performance information such as invocation count and response time.


Active module-level call path is displayed as the default view for the Deployments node of a selected application.

Double-click a specific module to trigger ADP to display the architecture of the selected module.

Expand the Deployments node by clicking the plus (+) icon to reveal all the deployed modules in this application. Further expanding the nodes at the module level reveals components associated with the selected module. Further expanding the nodes at the component level reveals methods associated with the selected component.

When you select one of these children nodes (module, component, and method levels), ADP displays associated tabs for active call path diagram, static call path diagram, instrumentation and SQL statements.

Tip:

Use the active call path diagram as a guide to identify entities with performance data. If an entity does not have performance data, ADP displays No data available for the selected time frame in the Main Display Window.

Workshop Projects

The Workshop Projects node includes performance information about modules and components created using the Oracle WebLogic Workshop. These modules and components include WebLogic Integration processes, WebLogic Integration web services, and WebLogic Portal pageflows.

Workshop Project node and its children nodes provide performance data associated with WLI processes, web services, and WLP pageflows.

When you select a specific children node, ADP displays detailed performance information.

Web Applications

The Web Applications node includes performance information related to the Web Applications modules and components associated with the selected application. Click the Web Applications node to reveal a performance summary in the Main Display Window. Click the plus (+) icon to expand the Web Applications node to reveal various web modules deployed as part of this application.

Click the plus (+) icon to expand on a specific web module and reveal different groupings for web components, for example, Pageflows, Struts Modules and Servlets. Clicking one of these nodes triggers ADP to display rolled up performance summary for the entire grouping. You can further expand these nodes by clicking the plus (+) icon to reveal more detailed information. Fully expanded Web Applications node contains all web modules organized by type.

Detailed performance information at the individual pageflow, struts action, and servlet levels will be displayed when you click the lowest level nodes.

Stateless Beans

The Stateless Beans node includes activity information related to the stateless EJB components associated with the selected application. Click the Stateless Beans node to reveal an activity summary in the Main Display Window. Click the plus (+) icon to expand the Stateless Beans node to reveal various stateless EJBs deployed as part of this application.

You can further select individual nodes to obtain detailed activity information. Selecting a specific Stateless Bean node triggers ADP to display detailed activity metrics.

The detailed view contains the following activity metrics (Table 16-75, "Stateless Beans Detail View"):

Table 16-75 Stateless Beans Detail View

Column/Metric Description

EJB

Name of the stateless EJB.

In Use

Number of instances for a specific stateless EJB currently being used from the free pool. [Snapshot Count]

Idle

Number of instances for a specific stateless EJB currently in the idle state in the free pool. These bean instances are available for use. [Snapshot Count]

Waits

Number of threads currently waiting for a specific stateless EJB bean instance from the free pool. [Snapshot Count]

Timeouts

Total number of threads that have timed out waiting for an available bean instance from the free pool. [Aggregated Count]


Note:

The metrics reported in the Stateless Beans node are reported by the MBean (Management Bean) of the EJB container. These activity metrics can be used for checking the overall health of the EJB container. When the EJB container is restarted, these metrics are reset.

Stateful Beans

The Stateful Beans node includes activity information related to the stateful EJB components associated with the selected application. Click the Stateful Beans node to reveal an activity summary in the Main Display Window. Click the plus (+) icon to expand the Stateful Beans node to reveal various stateful EJBs deployed as part of this application.

You can further select individual nodes to obtain detailed activity information.

The Stateful EJB Summary includes the following tables:

  • Stateful EJB Cache

  • Stateful EJB Transactions

  • Stateful EJB Locking

Stateful EJB Cache

Stateful EJB Cache table includes the following information (Table 16-76, "Stateful EJB Cache"):

Table 16-76 Stateful EJB Cache

Metrics Description

EJB

Name of the Stateful EJB

Hits

Total number of times an attempt to access the Stateful EJB instance from the cache succeeded [Aggregated Count]

Accesses

Total number of attempts to access the Stateful EJB instance from the cache [Aggregated Count]

Size

Number of beans instances from this Stateful Home currently in the EJB cache [Snapshot Count]

Activations

Total number of beans from this Stateful Home that have been activated [Aggregated Count]

Passivations

Total number of beans from this Stateful Home that have been passivated [Aggregated Count]


Tip:

Passivation (serializing EJB state information to disk) and activation (reconstitute EJB state information from disk) are resource intensive operations. Ideally, Oracle recommends low level of activity in these metrics.
Stateful EJB Transactions

Stateful EJB Transactions table includes the following information (Table 16-77, "Stateful EJB Transactions"):

Table 16-77 Stateful EJB Transactions

Metrics Description

EJB

Name of the Stateful EJB

Commits

Total number of transactions that have been committed for this Stateful [Aggregated Count]

Rollbacks

Total number of transactions that have been rolled back for this Stateful [Aggregated Count]

Timeouts

Total number of transactions that have timed out for this EJB [Aggregated Count]


Tip:

High number of EJB Transaction Rollbacks may indicate problems with the data used; for some reason the target database is unable to commit the change. High number of EJB Transaction Time-outs may indicate problems accessing the database including network outage, database lock contention, and database outage.
Stateful EJB Locking

Stateful EJB Locking table includes the following information (Table 16-78, "Stateful EJB Locking"):

Table 16-78 Stateful EJB Locking

Metric Description

EJB

Name of the Stateful EJB

Entries

Number of Stateful EJB instances currently locked [Snapshot Count]

Lock Accesses

Total number of attempts to obtain a lock on an Stateful EJB instance [Aggregated Count]

Current Waiters

Number of Threads that currently waiting for a lock on an Stateful EJB instance [Snapshot Count]

Total Waiters

Total number Threads that have waited for a lock on an Stateful EJB instance [Aggregated Count]

Timeouts

Total number Threads that have timed out waiting for a lock on an Stateful EJB instance [Aggregated Count]


Tip:

Pay attention to Current Waiters and Time-outs. These metrics can indicate possible performance problems caused by EJB Locking. Ideally, 0s should be displayed for these metrics.

ADP presents these metrics in a table format in the Main Display Window when you select the Stateful Beans node. Graphical representations of two metrics, Stateful EJB cache access, and Stateful EJB lock access, are displayed below the table.

By looking at the activities related to Stateful EJBs, you can determine if there any abnormal activities associated with Stateful EJBs.

Note:

The metrics reported in the Stateful Beans node are reported by the MBean (Management Bean) of the EJB container. These activity metrics can be used for checking the overall health of the EJB container. When the EJB container is restarted, these metrics are reset.

Entity Beans

The Entity Beans node includes activity information related to the Entity EJB components associated with the selected application. Click the Entity Beans node to reveal an activity summary in the Main Display Window. Click the plus (+) icon to expand the Entity Beans node to reveal various Entity EJBs deployed as part of this application.

You can further select individual nodes to obtained detailed activity information. Selecting a specific Entity Bean node triggers ADP to display detailed activity metrics.

The Entity EJB Summary includes the following tables:

  • Entity EJB Activity

  • Entity EJB Cache

  • Entity EJB Transactions

  • Entity EJB Locking

Entity EJB Activity

Entity EJB Activity table includes the following information (Table 16-79, "Entity EJB Activity"):

Table 16-79 Entity EJB Activity

Metrics Description

EJB

Name of the Entity EJB.

In Use

Number of instances for a specific Entity EJB currently being used from the free pool. [Snapshot Count]

Idle

Number of instances for a specific Entity EJB currently in the idle state in the free pool. These bean instances are available for use. [Snapshot Count]

Waits

Number of Threads currently waiting for a specific Entity EJB instance from the free pool. [Snapshot Count]

Timeouts

Total number of Threads that have timed out waiting for an available bean instance from the free pool. [Aggregated Count]


Tip:

Pay attention to Waits and Timeouts metrics. Activities in the Waits metric and increasing count in the Timeouts metric are signs that requests are waiting to be serviced by the EJB container. Ideally, 0 should be indicated for these metrics.
Entity EJB Cache

Entity EJB Cache table includes the following information (Table 16-80, "Entity EJB Cache"):

Table 16-80 Entity EJB Cache

Metrics Description

EJB

Name of the Entity EJB

Hits

Total number of times an attempt to access the Entity EJB instance from the cache succeeded [Aggregated Count]

Accesses

Total number of attempts to access the Entity EJB instance from the cache [Aggregated Count]

Size

Number of beans instances from this EJB Home currently in the EJB cache [Snapshot Count]

Activations

Total number of beans from this EJB Home that have been activated [Aggregated Count]

Passivations

Total number of beans from this EJB Home that have been passivated [Aggregated Count]


Tip:

Passivation (serializing EJB state information to disk) and activation (reconstituting EJB state information from disk) are resource intensive operations. Ideally, Oracle recommends a low level of activity in these metrics.
Entity EJB Transactions

Entity EJB Transactions table includes the following information (Table 16-81, "Entity EJB Transactions"):

Table 16-81 Entity EJB Transactions

Metric Description

EJB

Name of the Entity EJB

Commits

Total number of transactions that have been committed for this EJB [Aggregated Count]

Rollbacks

Total number of transactions that have been rolled back for this EJB [Aggregated Count]

Timeouts

Total number of transactions that have timed out for this EJB [Aggregated Count]


Tip:

High numbers of EJB Transaction Rollbacks may indicate problems with the data used; for some reason the target database is unable to commit the change. High numbers of EJB Transaction Timeouts may indicate problems accessing the database including network outage, database lock contention, database outage, and more.
Entity EJB Locking

Entity EJB Locking table includes the following information (Table 16-82, "Entity EJB Locking"):

Table 16-82 Entity EJB Locking

Metric Description

EJB

Name of the Entity EJB

Entries

Number of Entity EJB instances currently locked [Snapshot Count]

Lock Accesses

Total number of attempts to obtain a lock on an Entity EJB instance [Aggregated Count]

Current Waiters

Number of Threads that currently waiting for a lock on an Entity EJB instance [Snapshot Count]

Total Waiters

Total number Threads that have waited for a lock on an Entity EJB instance [Aggregated Count]

Timeouts

Total number Threads that have timed out waiting for a lock on an Entity EJB instance [Aggregated Count]


Tip:

Pay attention to Current Waiters and Timeouts. These metrics can indicate possible performance problems caused by EJB Locking. Ideally, 0s should be displayed for these metrics.

When you select the Entity Beans node, ADP presents these metrics in a table format in the Main Display Window. Graphical representations of the following metrics, Entity EJB in use, Entity EJB cache access, and Entity EJB lock access, are displayed below the table.

Expand the Entity Beans tree by clicking the plus (+) icon next to Entity Beans node. You can get the same summary as previously described for a specific Entity EJB.

By looking at the activities related to Entity EJBs, you can determine if there any abnormal activities associated with Entity EJBs.

Note:

The metrics reported in the Entity Beans node are reported by the MBean (Management Bean) of the EJB container. These activity metrics can be used for checking the overall health of the EJB container. When the EJB container is restarted, these metrics are reset.

Message Driven Beans

The Message Driven Beans node includes activity information related to the message driven EJB components associated with the selected application. Click the Message Driven Beans node reveals an activity summary in the Main Display Window. Click the plus (+) icon to expand the Message Driven Beans node to reveal various message driven EJBs deployed as part of this application.

You can further select individual nodes to obtained detailed activity information.

The Message Driven EJB Summary includes the following tables:

  • Message Driven EJB Activity

  • Message Driven EJB Transactions

Message Driven EJB Activity

Message Driven EJB Activity table includes the following information (Table 16-83, "Message Driven EJB Activity"):

Table 16-83 Message Driven EJB Activity

Metric Description

EJB

Name of the Message Driven EJB.

In Use

Number of instances for a specific Message Driven EJB currently being used from the free pool. [Snapshot Count]

Idle

Number of instances for a specific Message Driven EJB currently in the idle state in the free pool. These bean instances are available for use. [Snapshot Count]

Waits

Number of Threads currently waiting for a specific Message Driven EJB instance from the free pool. [Snapshot Count]

Timeouts

Total number of Threads that have timed out waiting for an available bean instance from the free pool. [Aggregated Count]


Tip:

Pay attention to Waits and Timeouts metrics. Activities in the Waits metric and increasing count in the Timeouts metric are signs that requests are waiting to be serviced by the EJB container. Ideally, 0 should be indicated for these metrics.
Message Driven EJB Transactions

Message Driven EJB Transactions table includes the following information (Table 16-84, "Message Driven EJB Transactions"):

Table 16-84 Message Driven EJB Transactions

Metric Description

EJB

Name of the Message Driven EJB

Commits

Total number of transactions that have been committed for this EJB [Aggregated Count]

Rollbacks

Total number of transactions that have been rolled back for this EJB [Aggregated Count]

Timeouts

Total number of transactions that have timed out for this EJB [Aggregated Count]


Tip:

High numbers of EJB Transaction Rollbacks may indicate problems with the data used; for some reason the target database is unable to commit the change. High numbers of EJB Transaction Timeouts may indicate problems accessing the database including network outage, database lock contention, database outage, and more.

ADP presents these metrics in a table format in the Main Display Window when you select the Message Driven Beans node. Graphical representation of the Message Driven EJB in use metric is displayed below the table.

By looking at the activities related to Message Driven EJBs, you can determine if there are any abnormal activities associated with Message Driven EJBs.

Note:

The metrics reported in the Message Driven Beans node are reported by the MBean (Management Bean) of the EJB container. These activity metrics can be used for checking the overall health of the EJB container. When the EJB container is restarted, these metrics are reset.

Oracle WebLogic Resources

The Resources node under Oracle Enterprise Manager contains information for the managed domain organized by logical clusters, machines, servers, and more. You can look for low-level technology metrics organized by technology subsystems for a specific WebLogic Server.

The Resources tree includes the following nodes (Table 16-85, "WebLogic Resources Tree"):

Table 16-85 WebLogic Resources Tree

Example Node Description

CSS Domain

Name of the WebLogic Domain configured

b-15/192.168.128.15

ID of the physical machine

cgServer

Name of the WebLogic Server configured

Applications

Performance measurements of all deployed applications running on this server

JDBC

Information of all configured JDBC resources for this server

JMS Servers

Information of all JMS destinations configuration for this server

Execute Queues

Information of all Execute Queues configured for this server

JVM

JVM information including Heap Size for this server

JRockit

JRockit information including Heap Size for this server

Modeling Status

Entities modeled by ADP for this server

ADP Modules

Status of the ADP Java Agent Module for this server


Expand these nodes by clicking the plus (+) icon next to the node name to get more information.

If the ADP OS Agent is deployed on the machine, clicking on the physical machine ID would show OS metrics collected by the OS Agent. These OS metrics include CPU Usage, Disk Usage, and Physical Memory Usage.

WebSphere Resources

The Resources node under Oracle Enterprise Manager contains information for the managed domain organized by logical clusters, machines, servers, and more. You can look for low-level technology metrics organized by technology subsystems for a specific WebSphere Server.

The Resources tree includes the following nodes (Table 16-86, "WebSphere Resources Tree"):

Table 16-86 WebSphere Resources Tree

Example Node Description

WPSSUn

Resource name, for example, WPSUn

WebSphere Portal

Machine name, for example, WebSphere_Portal

WebSphere Portal

Server name, for example, WebSphere_Portal

Applications

Performance measurements of all deployed applications running on this server

JDBC

Information of all configured JDBC resources for this server

JMS Servers

Information of all JMS destinations configuration for this server

Thread Pools

Performance information about all threads used by the container to process request

JVM

JVM information including Heap Size for this server

WebServices

Performance measurements about web services deployed in the container

Sessions

Information about active HTTP sessions

Transactions

Information about transactions performance

Cache

Information about cache performance

ORB

Information about ORB performance

Modeling Status

Modeled entities for the container

ADP Modules

Status of the ADP Java Agent Module for this server

Applications

Performance information about the applications deployed in the container


Expand these nodes by clicking the plus (+) icon next to the node name to get more information.

Clicking on the physical machine ID would show OS metrics. These OS metrics include CPU Usage, Disk Usage, and Physical Memory Usage.

Oracle Resources

The Resources node under Oracle Enterprise Manager contains information for the managed domain organized by logical clusters, machines, servers, and more. You can look for low-level technology metrics organized by technology subsystems for a specific Oracle AS Server.

The Resources tree includes the following nodes (Table 16-87, "Oracle Resources Tree"):

Table 16-87 Oracle Resources Tree

Example Node Description

Managed System Resource Name

Top-level Resource name, for example, oc4j_soa

Oracle AS Server

Machine name which can be navigated to both within or outside a cluster, for example, oc4j_soa@192.168.1.119 which includes both the server name and the host server IP address

Applications

Performance measurements of all deployed applications running on this server

JDBC

Information of all configured JDBC resources for this server

JMS Servers

Information of all JMS destinations configuration for this server

Thread Pools

Performance information about all threads used by the container to process requests

JVM

JVM information including Heap Size for this server

BPEL Processes

Performance measurements about BPEL Processes deployed in the container

ESB

Performance measurements about ESB services deployed in the container

Modeling Status

Modeled entities for the container

ADP Modules

Status of the ADP Java Agent Module for this server

Applications

Performance information about the applications deployed in the container


Clicking the physical machine ID would show OS metrics. These OS metrics include CPU Usage, Disk Usage, and Physical Memory Usage.

Custom Metrics

The Custom Metrics node under Oracle Enterprise Manager contains all the custom metrics you defined. Currently ADP supports custom metrics for Java classes. When Custom Metrics node is selected, ADP displays various summaries. You can select individual entities to get more detailed performance information.

Expanding the Custom Metrics node reveals a list of Java classes with custom metrics configured.

The following is a list of columns in the Custom Class Performance table and their descriptions (Table 16-88, "Custom Class Performance"):

Table 16-88 Custom Class Performance

Column/Metric Description

Caller Class

Fully qualified name of the class that is making the inbound call

Caller Method

Method name in the class that is making the inbound call

Class

Fully qualified name of the class that is the destination of the inbound call

Invocation Count

Total number of times the inbound call is made

Response Time (ms)

Average response time of the inbound call in milliseconds


CAMM Node

The CAMM node in the navigation tree contains information for the CAMM environment for the monitored WebLogic domain, WebSphere cell, or Oracle AS cluster. Select the CAMM node to see the CAMM Java Agent status for the WebLogic domain.

The CAMM Java Agent status includes the following (Table 16-89, "CAMM Java Agent Status"):

Table 16-89 CAMM Java Agent Status

Column/Metric Description

Server

Name of the WebLogic server, WebSphere cell, or Oracle AS cluster

Container Status

Operational status of the WebLogic, WebSphere, or Oracle AS server (running or not)

Agent In Sync

Version synchronization between CAMM and CAMM Agent status (true or false)

EJB Installed

CAMM EJB installation status (true or false)

Agent Installed

CAMM Java Agent installation status

Agent Activated

CAMM Java Agent activation status

Agent Status

CAMM Java Agent operational status

Server Type

Identifies server as administration, individual, or clustered server

Admin URI

Location of the domain admin server

Manager RMI Registry Host

Host name of the CAMM RMI registry

Manager RMI Registry Port

Port number of the CAMM RMI registry

EJB Major Version

CAMM EJB major version

EJB Minor Version

CAMM EJB minor version

EJB Build ID

CAMM EJB build number - for version synchronization check

Agent Major Version

CAMM Java Agent major version

Agent Minor Version

CAMM Java Agent minor version

Agent Build ID

CAMM Java Agent build number - for version synchronization check


Click the Modeling Status node under CAMM node to see a table of all modeled entities in the managed domain. This table shows all the managed clusters, servers, and applications in the CAMM environment. Mismatches between the Modeling Status table and your environment are indications of configuration problems.

You can use this information to debug and resolve CAMM configuration issues.

Service Component Architecture (SCA)

Service Component Architecture (SCA) provides a set of features and services that simplify the process of detecting the presence of Service-Oriented Architecture (SOA) components.

Table 16-90 SCA Composites

Composite Description

Services

Metrics related to Services defined on the SOA composite.

Wires

Metadata related to Wires defined in the SOA composite

References

Metrics related to References defined in the SOA composite

Components

Metrics related to Components within the SOA composite


Components

The following components make up the Service Component Architecture:

Table 16-91 Components in SCA

Component Description

Decision Services

Metrics related to components in the Decision Services engine

Mediators

Metrics related to components in the Mediator engine

Human Workflows

Metrics related to components in the Human Workflow engine

BPEL

Metrics related to components in the BPEL engine


Exploring the Configuration Tab

Using the Configuration tab you can set up the resources you want to monitor using ADP.

The configurations explained in this section are:

A running ADP manager must be registered in Enterprise Manager. Refer to Chapter 10, "Quick Steps for Installing and Configuring the ADP Manager" for steps of how to perform the registration. After the registration, Enterprise Manager continues to keep the manager as a valid manager even if it is down. When this occurs, the Enterprise Manager UI displays the ADP manager as Unreachable.

Database Configuration

The Database Configuration page lists the databases accessible to ADP which you want to monitor. You can configure a database to be used by ADP, edit an existing database configuration, delete a database configuration, and enable a configuration.

Refer to Setting Up ADP Data Repository for details.

Resource Configuration

The Resource Configuration node in the Configuration tree enables you to create resources (for example, target application server domains) that can be monitored by ADP.

Service Level Objective Configuration

The Service Level Objective Configuration node in the Configuration tree enables you to create service level objectives (SLOs) that can be monitored by ADP. A service level objective is a measurable attribute, for example, availability. Service Level Agreements (SLA) are made up of SLOs.

SLOs are hierarchical which allows you to set service levels at any level within the modeled hierarchy of an application.

Service Level Objectives Configuration

Service Level Objectives Configuration node in the Configuration tree allows you to manage SLOs.

In this window you can:

  • Create and edit a specific SLO to open the Service Level Objective Editor.

  • View or edit the selected SLO.

SLO Blackout Configuration

The SLO Blackout Configuration node in the Configuration tree enables you to create time periods when information will not be monitored for a specific SLO. You can define blackouts by a SLO file, an individual SLO, or by entity.

Action Configuration

Action Configuration node in the Configuration tree allows you to manage actions for ADP. Actions are triggered by a SLO violation event. ADP supports the following actions:

  • Issue a SMNP trap

  • Send an e-mail

  • Execute a script

  • Log to a file

In the Action Configurations window you can:

  • Click Create Action to create a specific type of action.

In the Action Configuration window, double-click on a specific action to see its configuration information. You can edit and copy edit selected action. ADP automatically enforces referential integrity during the deletion process.

Note:

You can include a set of SLO variables into e-mail, script, and log actions. This feature significantly increases the value of these actions by using real-time performance data. See Table 16-92, "List of SLO Variables" for a list of SLO variables.

Table 16-92 List of SLO Variables

SLO Variable Description Example Value

$EventType

SLO event type (Violation or Cautionary)

Event.SLO.Cautionary

$EventAttributes.SLOName

Name of the SLO fired

CSR Portal Desktop Response Time Violation

$Event.Attributes.SLOType

Metric where SLO violation was observed

Metrics.J2EE.JVM.HeapFree

$EventAttributes.TriggerValue

Value of metric when SLO threshold was exceeded

35001

$EventAttributes.TriggerThreshold

Threshold type (High or Low)

High

$Entity.InfrastructureID

Name of the platform

WebLogic

$Entity.NodeID

Server node where SLO violation was observed

B93/192.168.3.93

$Entity.DomainID

Domain in which SLO violation was observed

mydomain

$Entity.ResourceID

Cluster in which SLO violation was observed

my_cluster

$Entity.EntityTypeID

Type of the entity in which the SLO violation was observed

J2EE.JVM

$StartTime

Start time of the SLO violation

1112322030000

$EndTime

Stop time of the SLO violation

1112322045000


Tip:

Customize your alert using SLO variables. The following is an example of a customized message for a Mail Action:
SLO Event:
SLO Name = $EventAttributes.SLOName;
Event Type = $EventType;
Trigger Domain = $Entity.DomainID;
Trigger Application = $Entity.ApplicationID;
Trigger SLO Type = $EventAttributes.SLOType;
Trigger Value = $EventAttributes.TriggerValue;
Trigger Threshold = $EventAttributes.TriggerThreshold;
Trigger Element = $Entity.ElementID;
Event ID = $EventID;

Custom Metric Configuration

There are cases where additional instrumentation is needed based on your specialized requirements. Custom metrics allow you to instrument a class or method of your choice and receive performance metrics collected by the ADP agent.

To create a metric configuration, do the following:

  1. From the Grid Control Home page, click Targets, then click Middleware. In the Related Links sections, select Application Dependency and Performance.

  2. Click the Configuration tab, choose the configuration in which you are interested. Click Custom Metric Configuration.

  3. In the right pane, click the Create Custom Metric button.

  4. On the Custom Metric File page, choose whether to use an existing .xml file or a new file. If you choose a new file, the ADP Manager will create the new .xml file. Click Continue.

  5. On the Custom Metric Configuration page, provide the following information:

    • Resource name is a monitored Weblogic domain or Oracle Application Server or WebSphere cell.

      You created a name when you configured ADP to monitor. The same name is used here during custom metric configuration.

    • Class name is the name of the implementation class in the code. You are required to enter a fully qualified class name.

    • Method name is the name of the implementation method in the code.

Once the custom metric configuration is complete, restart the monitored application server.

Exploring the Registration Tab

The managers perform complex mathematical modeling and statistical calculations with summarized data from all Java Agents.

Using the Registration tab, you can add, edit, and remove Managers configured to Enterprise Manager. By accessing ADP through Remote Method Invocation (RMI), you can manipulate all the managers configured to Enterprise Manager through a secured protocol.

Adding a New Manager (RMI Configuration)

The first time the Registration tab displays there are no managers in the Managers tree. To add a new manager, perform the following steps:

  1. In the Registration tab, click the Managers node in the tree.

  2. Type the new manager information in the Main Display window.

  3. Decide whether to use Request Monitoring.

    Request Monitoring provides end-to-end visibility into requests, localizes end-user performance problems to specific application deployments, and provides a platform for context-based drill down diagnostics.

    When you select Enable Request Monitoring, ADP creates and sets up targets for collecting request performance data in Request Monitoring. If you do not select Enable Request Monitoring, the ADP manager is only registered in Enterprise Manager.

    Note:

    The grayed out information represents configuration data for connecting to the ADP manager by way of a secure protocol, for example Key Store, Trust Store, and passwords. This information is extracted from the ADP manager by way of the RMI call.
  4. If you enable request monitoring on an existing manager, click Upload to populate the manager configuration properties to the ADP target in Request Monitoring.

  5. Click Test Connect to test the connection to the new manager. Should the test connection fail, this may be because the manager is not running or the manager is not yet installed.

  6. Click Add.

Once the manager is added, the name of the manager will display in the Configuration tab under the Managers node in the tree.

Editing a Previously Configured Manager (RMI Configuration)

To add a previously configured manager, perform the following steps:

  1. Click + (plus sign) next to the Managers node in the tree, then select the subnode for the manager you want to edit.

  2. After you make changes to the manager information, click Update. This results in the manager entries in the Enterprise Manager repository to be updated with the new values.

If a manager is configured before using this Enterprise Manager configuration page, Enterprise Manager continues to keep the manager as a valid manager even though the manager may be down or permanently removed.

The list of managers is not refreshed.

Removing or Disabling a Previously Configured Manager

To remove a configured manager:

  1. Click + (plus sign) next to the Managers node in the tree, then select the subnode for the manager you want to remove.

  2. Click Remove in the main pane.

    Deleting a manager from Enterprise Manager does not uninstall and remove the manager from the remote host where the manager is located and may be running. Remove only deletes the manager entry from the Enterprise Manager repository.

To disable a configured manager:

  1. Click + (plus sign) next to the Managers node in the tree, then select the subnode for the manager you want to disable.

  2. Deselect Enable Request Monitoring.

  3. Click Update.

When you deselect the Enable Request Monitoring option, the manager settings are preserved. The UI displays these managers as disabled. There will not be any further information under the disabled manager in the tree.