apm_9.5--apm for oracle weblogic portal guide

7/27/2019 APM_9.5--APM for Oracle WebLogic Portal Guide

1/48

for Oracle WebLogic Portal GuideRelease 9.5

CA Application PerformanceManagement


2/48

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to

as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, withoutthe prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed

by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing

your use of the CA software to which the Documentation relates; or (i i) a separate confidentiality agreement between you and

CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may

print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your

employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced

copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable

license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to

certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY

KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,

DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST

INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE

POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such

license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions

set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or

their successors.

Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong totheir respective companies.


3/48

CA Technologies Product References

This document references the following CA Technologies products and features:

CA Application Performance Management (CA APM)

CA Application Performance Management ChangeDetector (CA APM

ChangeDetector)

CA Application Performance Management ErrorDetector (CA APM ErrorDetector)

CA Application Performance Management for CA Database Performance (CA APM

for CA Database Performance)

CA Application Performance Management for CA SiteMinder (CA APM for CA

SiteMinder)

CA Application Performance Management for CA SiteMinder Application ServerAgents (CA APM for CA SiteMinder ASA)

CA Application Performance Management for IBM CICS Transaction Gateway (CA

APM for IBM CICS Transaction Gateway)

CA Application Performance Management for IBM WebSphere Application Server

(CA APM for IBM WebSphere Application Server)

CA Application Performance Management for IBM WebSphere Distributed

Environments (CA APM for IBM WebSphere Distributed Environments)

CA Application Performance Management for IBM WebSphere MQ (CA APM for

IBM WebSphere MQ)

CA Application Performance Management for IBM WebSphere Portal (CA APM forIBM WebSphere Portal)

CA Application Performance Management for IBM WebSphere Process Server (CA

APM for IBM WebSphere Process Server)

CA Application Performance Management for IBM z/OS (CA APM for IBM z/OS)

CA Application Performance Management for Microsoft SharePoint (CA APM for

Microsoft SharePoint)

CA Application Performance Management for Oracle Databases (CA APM for Oracle

Databases)

CA Application Performance Management for Oracle Service Bus (CA APM for

Oracle Service Bus) CA Application Performance Management for Oracle WebLogic Portal (CA APM for

Oracle WebLogic Portal)

CA Application Performance Management for Oracle WebLogic Server (CA APM for

Oracle WebLogic Server)

CA Application Performance Management for SOA (CA APM for SOA)


4/48

CA Application Performance Management for TIBCO BusinessWorks (CA APM for

TIBCO BusinessWorks)

CA Application Performance Management for TIBCO Enterprise Message Service

(CA APM for TIBCO Enterprise Message Service)

CA Application Performance Management for Web Servers (CA APM for Web

Servers)

CA Application Performance Management for webMethods Broker (CA APM for

webMethods Broker)

CA Application Performance Management for webMethods Integration Server (CA

APM for webMethods Integration Server)

CA Application Performance Management Integration for CA CMDB (CA APM

Integration for CA CMDB)

CA Application Performance Management Integration for CA NSM (CA APM

Integration for CA NSM)

CA Application Performance Management LeakHunter (CA APM LeakHunter)

CA Application Performance Management Transaction Generator (CA APM TG)

CA Cross-Enterprise Application Performance Management

CA Customer Experience Manager (CA CEM)

CA Embedded Entitlements Manager (CA EEM)

CA eHealth Performance Manager (CA eHealth)

CA Insight Database Performance Monitor for DB2 for z/OS

CA Introscope

CA SiteMinder

CA Spectrum Infrastructure Manager (CA Spectrum)

CA SYSVIEW Performance Management (CA SYSVIEW)


5/48

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the

information that you need for your Home Office, Small Business, and Enterprise CA

Technologies products. Athttp://ca.com/support,you can access the following

resources:

Online and telephone contact information for technical assistance and customer

services

Information about user communities and forums

Product and documentation downloads

CA Support policies and guidelines

Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you

can send a message [email protected].

To provide feedback about CA Technologies product documentation, complete our

short customer survey which is available on the CA Support website at

http://ca.com/docs.
http://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/supportmailto:[email protected]:[email protected]:[email protected]://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docsmailto:[email protected]://www.ca.com/support


6/48


7/48

Contents 7

Contents

Chapter 1: Overview 9

About the CA APM for Oracle WebLogic Portal ........................................................................................................... 9

CA APM for Oracle WebLogic Portal Components ..................................................................................................... 10

How CA APM for Oracle WebLogic Portal components work with each other .......................................................... 10

Monitoring WebLogic Portal functions ...................................................................................................................... 10

Chapter 2: Installing and Configuring the CA APM for Oracle WebLogicPortal 13

Before you begin ........................................................................................................................................................ 13

Installing and Configuring CA APM for Oracle WebLogic Portal ................................................................................ 14Installing Enterprise Manager Components of the CA APM for Oracle WebLogic Portal ................................... 14

Installing the Agent Components of the CA APM for Oracle WebLogic Portal ................................................... 15

Configuring the PBL Fi le for Typical, Full, and Errors PBDs ................................................................................. 17

Configuring PBDs for Version Compatibility........................................................................................................ 21

(Optional) Creating an exclude list for URLs ....................................................................................................... 22

Clustering PowerPack for WebLogic Portal ................................................................................................................ 22

Running JavaScript Calculators on the MOM ...................................................................................................... 23

Disabling CA APM for Oracle WebLogic Portal ........................................................................................................... 23

Chapter 3: Using the CA APM for Oracle WebLogic Portal 25Monitoring WebLogic Portal ...................................................................................................................................... 25

WebLogic Portal Metrics ..................................................................................................................................... 25

Worst Performing Components .......................................................................................................................... 26

Viewing Dashboards ................................................................................................................................................... 27

Dashboards ......................................................................................................................................................... 29

Viewing Metrics .......................................................................................................................................................... 31

Viewing worst performing components..................................................................................................................... 32

Sample Operation Scenario ........................................................................................................................................ 36

Customer says: "We have a problem" ................................................................................................................ 36

Appendix A: Metrics 39

Metrics path ............................................................................................................................................................... 39

Metric categories ....................................................................................................................................................... 39

Authentication .................................................................................................................................................... 39

Content Management ......................................................................................................................................... 39


8/48

8 for Oracle WebLogic Portal Guide

Desktops .............................................................................................................................................................. 40

Entitlements ........................................................................................................................................................ 41

Java Page Flows ................................................................................................................................................... 41

J2EE Portlet API ................................................................................................................................................... 41

NetUIx Controls ................................................................................................................................................... 41

Personalization .................................................................................................................................................... 41

Presentation Contexts ......................................................................................................................................... 42

Profile Factory ..................................................................................................................................................... 42

Profile Manager .................................................................................................................................................. 42

Workshop Controls ............................................................................................................................................. 42

WSRP ................................................................................................................................................................... 42

Chapter 4: Enable IPv6 Addresses- 43

Appendix B: Frequently Asked Questions 45

How can I customize the metrics created by the Product? ........................................................................................ 45

Why am I not seeing method level metrics with the product? .................................................................................. 45

Why am I getting error message in Enterprise Manager log that says "An Agent is illegally reporting data

against the calculator metric"? Why does a null node appear in investigator tree too? .......................................... 45

Why am I seeing wrong relations between books, pages and desktops? .................................................................. 46

Why am I seeing the Average Response Time of Page less than the Average Response Time of the Worst

Performing Portlet within the page? .......................................................................................................................... 46

If I click one page/portlet, why am I seeing values on many Books/Pages/Portlets in Investigator? Why am

I seeing Average Response Time as 0 for many of the components? ........................................................................ 46

Why am I seeing the value of Responses Per Interval as more than 1 even though I accessed the

page/book once? ........................................................................................................................................................ 46

I have a portlet which is part of many pages (Similarly, a page part of many books). Why am I not seeing

all of them in the graph? ............................................................................................................................................ 47

Why am I not seeing an edge from a parent to a child (book - page, page - portlet), even though the graph

has both the components? ........................................................................................................................................ 47

Why am I not seeing all the components from the table in the graph? .................................................................... 47

Why am I seeing multiple Portal typeviews? Within that, only one is performing as expected. ............................... 47

Why am I not seeing data for some of the components in the Dashboard? ............................................................. 48


9/48


Chapter 1: Overview

This chapter provides an overview of CA APM for Oracle WebLogic Portal.

This section contains the following topics:

About the CA APM for Oracle WebLogic Portal(see page 9)

CA APM for Oracle WebLogic Portal Components(see page 10)

How CA APM for Oracle WebLogic Portal components work with each other(see page

10)

Monitoring WebLogic Portal functions(see page 10)

About the CA APM for Oracle WebLogic Portal

CA APM for Oracle WebLogic Portal provides continuous performance monitoring and

management of your portal framework during development, QA, staging, and

production. You can also identify performance problems in the portal and critical

back-end systems.

The CA APM for Oracle WebLogic Portal collects and analyzes metrics from the

WebLogic Portal in real time. If metrics show availability, performance, or health

problems, you can customize the alert according to the problem. You can configure

alerts to meet the needs of an individual WebLogic Portal deployment. The CA APM for

Oracle WebLogic Portal is built on the CA Introscope enterprise monitoring platform

and shares all its key benefits.

You can view the overall health, performance, and availability of the portal using the

dashboards. To view details for the component causing the problem, double-click the

alerts and links. The Investigator tree also provides a list of the top worst performing

components. To understand how the worst performing components affect the other

components, generate a graphical view to show the relationships.


10/48

CA APM for Oracle WebLogic Portal Components


CA APM for Oracle WebLogic Portal Components

The CA APM for Oracle WebLogic Portal includes the following components:

CA IntroscopeForms the foundation for the CA APM for Oracle WebLogic Portal.It includes the Enterprise Manager, Introscope agent, Workstation, and WebView.

For more information about Introscope and its components, see CA APM

Configuration Administration Guide.

Agent Extension, PBL, and PBD filesCollect WebLogic Portal metric data and pass

on the data for metrics to Introscope Enterprise Manager.

Management Module, Enterprise Manager plug-ins, and Workstation

plug-inAnalyze and aggregate the metric data and pass on the data to

Workstation for display.

Introscope Workstation and DashboardsDisplay overall health, performance, and

availability of WebLogic Portal based on WebLogic Portal-specific metrics.

How CA APM for Oracle WebLogic Portal components work witheach other

The CA APM for Oracle WebLogic Portal components work with each other as follows:

The Introscope Agent Extension that resides in the WebLogic Portal and Applicationserver collects metrics and passes them to the Enterprise Manager.

The Enterprise Manager analyzes the metrics and aggregates them with the help of

Enterprise Manager plug-ins.

The Introscope Workstation displays these metrics and the worst performing

components according to the metrics. The Workstation also displays the overall

health, performance, and availability of the Portal Server.

Monitoring WebLogic Portal functions

WebLogic Portal functional workflow, which starts with incoming requests and endswith the display of a portal page.


11/48



The CA APM for Oracle WebLogic Portal collects and reports the metrics that are related

to these functions under metric categories. The key sequences, functions, and metric

categories correspond to WebLogic Portal functions and are listed in the following table:

Workflow

Sequence

WebLogic Portal Function Metric Categories

1 Transaction Request sent None

2 Authentication Access Checks, Adjudicate Results, Authenticate

Users, Basic User Form Authentication, Get

Roles, Validate Principal, Run as Users

3 Content Management (not illustrated in

the diagram)

Node, Node Ops, Search, Search Ops, Repository

Manager, Expression Helper

4 Entitlements Get Roles, Is User in Role, Is Access Allowed

5 Java Page Flows (not illustrated in the

diagram)

Java Page

Flows|{packagename}|{classname}|{method}

6 J2EE Portlet API Render

7 NetUIx Controls (not illustrated in the

diagram)

NetUIx Control|{classname}|{method}

8 Personalization (not illustrated in the

diagram)

Advisor, Advislet

9 Presentation Contexts (not illustrated in

the diagram)

Presentation Contexts|{classname}|Render

10 Profile Factory (not illustrated in the

diagram)

Get Profile, Create Profile Identity

11 Profile Manager (not illustrated in the

diagram)

Get Properties, Get Property as String, Set

Property

12 Workshop Controls (not illustrated in the

diagram)

Create User Control, User Login Control, User

Profile Control, User Info Control

13 Web Services for Remote Portlets (WSRP)

(not illustrated in the diagram)

Consumer, Producer


12/48



The CA APM for Oracle WebLogic Portal also monitors and reports metrics for the

components of the WebLogic Portal. The components and the corresponding lifecycle

methods that the CA APM for Oracle WebLogic Portal monitors are listed in the

following table:

WebLogic Portal

component

Lifecycle methods corresponding to the component

displayed by the CA APM for Oracle WebLogic Portal

Desktops None

Books loadState, handlePostbackData, raiseChangeEvents,

preRender, and saveState

Pages loadState, handlePostbackData, raiseChangeEvents,


Portlets loadState, handlePostbackData, raiseChangeEvents,


A complete list of WebLogic Portal metrics are available.


13/48

Chapter 2: Installing and Configuring the CA APM for Oracle WebLogic Portal 13

Chapter 2: Installing and Configuring theCA APM for Oracle WebLogic Portal

This chapter provides instructions for installing and configuring CA APM for Oracle

WebLogic Portal.


Before you begin(see page 13)

Installing and Configuring CA APM for Oracle WebLogic Portal(see page 14)

Clustering PowerPack for WebLogic Portal(see page 22)

Disabling CA APM for Oracle WebLogic Portal(see page 23)

Before you begin

Verify the following information before you begin the installation procedure:

Verify you have a supported version of the WebLogic Portal installed by checking

the CA APM Compatibility Guide at https://support.ca.comhttps://support.ca.com.

To find the Compatibility Guide:

1.

Go to https://support.ca.comhttps://support.ca.comand log in.

2. From the drop-down list, select CA APM.

3. Click Product Status.

4. Click Application Performance Management Compatibility Guide.

5. Click the appropriate guide for your release.

Identify the following directory locations in your network:

WebLogic machinethe installation directory for WebLogic is referred to as

and is specified during installation.

Enterprise Manager machinethe home directory for the Enterprise Manager

is referred to as .

Workstation machinethe home directory for the Introscope Workstation is

referred to as .

Verify that the Java Virtual Machine installed with your WebLogic Portal is at least

version 1.5.
https://support.ca.com/https://support.ca.com/https://support.ca.com/https://support.ca.com/https://support.ca.com/https://support.ca.com/https://support.ca.com/https://support.ca.com/https://support.ca.com/


14/48

Installing and Configuring CA APM for Oracle WebLogic Portal



Installing and configuring CA APM for Oracle WebLogic Portal involves the following

high-level steps:

1.

Install Enterprise Manager. SeeInstalling Enterprise Manager components of the CA

APM for Oracle WebLogic Portal(see page 14).

2. Install agent components. SeeInstalling the agent components of the CA APM for

Oracle WebLogic Portal(see page 15).

3. Configure the agent in either typical or full mode using the PBL file. SeeConfiguring

the PBL file for typical, full, and errors PBDs(see page 17).

4.

Configure the PBDs for version compatibility if you are using WebLogic Portal Server

9.2. SeeConfiguring PBDs for version compatibility(see page 21).

5. (Optional) Create an exclude list for the URLs you want excluded from monitoring.

SeeOptional: Creating an exclude list for URLs(see page 22).

Installing Enterprise Manager Components of the CA APM for Oracle WebLogicPortal

If you are using the same Enterprise Manager for different agents, you do not have to

reinstall the Enterprise Manager components. These components are already installed

in the \examplesfolder.

Follow these steps:

Note: If you are using the same Enterprise Manager for different agents, start at step

two.

1.

To install the Enterprise Manager components of the CA APM for Oracle WebLogic

Portal onto the Enterprise Manager, run the main Enterprise Manager installer.

The Enterprise Manager installer places the files into the

\examples\PowerPackforWeblogicPortaldirectory.

For details, see the CA APM Installation and Upgrade Guide.


15/48



2. Verify that the \examples\PowerPackforWeblogicPortal

directory has the following files:

Note:The following section uses the Microsoft Windows directory syntax. For other

installation platforms, such as UNIX, replace "\" with "/".

.\product\enterprisemanager\plugins\com.wily.powerpack.weblogicportal.em.ex

t.jar

Plug-in for Enterprise Manager extension.

.\product\enterprisemanager\plugins\com.wily.powerpack.weblogicportal.em.se

rvice.jar

Plug-in for Enterprise Manager service.

.\ws-plugins\com.wily.powerpack.weblogicportal.ws.ext.jar

Plug-in for Workstation extension.

.\config\modules\PowerpackForWeblogicPortal_ManagementModule_typical.jar

Management Module JAR for typical configuration for displaying performance

metrics in dashboards.

\config\modules\portal\PowerpackForWeblogicPortal_ManagementModule_full.

jar

Management Module JAR for full configuration for displaying performance

metrics in dashboards.

3. Copy all the files to the correct location, which is based on how they are organized

in the \examplesdirectory.

For example, copy the plug-in for Enterprise Manager extension

com.wily.powerpack.weblogicportal.em.ext.jarfrom the

\examples\PowerPackforWeblogicPortal

\product\enterprisemanager\plugins\directory to the

\product\enterprisemanager\plugins\directory.

Installing the Agent Components of the CA APM for Oracle WebLogic Portal

Run the in-process agent installer to install the agent for WebLogic.

Follow these steps:

1.

To install the agent for WebLogic, run the in-process agent installer.

For details, see the CA APM Installation and Upgrade Guide.


16/48



2. Perform one of the following tasks:

a. To only install the CA APM for Oracle WebLogic Portal, select WebLogic as the

Application Server, and specify as the installation directory.

All the agent files are copied to the \wilydirectory.PowerPackforWeblogicPortal_ext.jaris copied to the

\wily\examples\\extdirectory.

b.

To install and enable the CA APM for Oracle WebLogic Portal, select WebLogic

as the Application Server, choose CA APM for Oracle WebLogic Portal to install,

and specify as the installation directory.

All the agent files are copied to the \wilydirectory.

PowerPackforWeblogicPortal_ext.jaris moved to the

\wily\core\ext directory.

3. Verify that the \wilydirectory has the following files:

Note:The following section uses the Microsoft Windows directory syntax. For other

installation platforms, such as UNIX, replace "\" with "/".

powerpackforweblogicportal.pbl in \wily\core\config

ProbeBuilder list that has all the PBDs listed in it.

powerpackforweblogicportal.pbdin \wily\core\config

PBD that has definitions for al l the classes and methods for the tracers for

WebLogic Portal.

powerpackforweblogicportal_typical.pbd in \wily\core\config

PBD that has only critical tracers enabled to monitor the performance of critical

components of the portal server.

powerpackforweblogicportal_full.pbd in \wily\core\config

PBD that has all the tracers enabled to monitor the performance of all the

components of the portal server.

powerpackforweblogicportal_errors.pbd

PBD that has the tracers for reporting Errors Per Interval metric.

.\examples\\ext\PowerPackforWeblogicPortal_ex

t.jar

Agent extension that collects metric data.

4. If you have installed and enabled the CA APM for Oracle WebLogic Portal, verify

that the PBL file is added to the introscope.autoprobe.directivesFileproperty in theIntroscopeAgent.profilefile that is located in the \wily\core\config

directory as follows:

introscope.autoprobe.directivesFile=powerpackforweblogicportal.pbl


17/48



5. If you have not enabled the CA APM for Oracle WebLogic Portal during the agent

installation, perform the following tasks to enable it:

a. Add the following PBL file to the introscope.autoprobe.directivesFileproperty in

the IntroscopeAgent.profilefile that is located in the \wily

directory as follows:

introscope.autoprobe.directivesFile=powerpackforweblogicportal.pbl

b. Copy the PowerPackforWeblogicPortal_ext.jarfile from the

\wily\examples\\extdirectory to

the \wily\core\extdirectory.

Configuring the PBL File for Typical, Full, and Errors PBDs

You can configure the CA APM for Oracle WebLogic Portal for either typical or full

configuration:

For a typical configuration, you enable powerpackforweblogicportal_typical.pbd.This PBD has only critical tracers that are enabled to monitor the performance of

critical components of the portal server.

For a full configuration, you enable powerpackforweblogicportal_full.pbd. This PBD

has all the tracers enabled to monitor the performance of all the components of the

portal server.

By default, the PBL file for the CA APM for Oracle WebLogic Portal has typical

configuration (powerpackforweblogicportal_typical.pbd) enabled and full configuration

(powerpackforweblogicportal_full.pbd) disabled.

When you use powerpackforweblogicportal_typical.pbd, you see the following nodes in

the Investigator tree:

Authentication, Content Management, Desktops, Entitlements, and WSRP nodes

are available under the WebLogic Portal node.

Method level tracing is not available for books, pages, and portlets. All the metrics

appear directly under the component, that is, either book, page, or portlet, rather

than corresponding lifecycle methods when you use

powerpackforweblogicportal_typical.pbd.

For portlets, only Average Response Time and Responses Per Interval metrics are

available for typical configuration. For books and pages, only Average Response

Time, Incremental Response Time, and Responses Per Interval metrics are available

for typical configuration. If any stalls are reported, they appear under the respective

nodes.

Note:If you have enabled powerpackforweblogicportal_error.pbd, then Errors Per

Interval are reported under the respective nodes for typical configuration.


18/48



When you use powerpackforweblogicportal_full.pbd, you see the following nodes in the

Investigator tree:

Authentication, Content Management, Desktops, Entitlements, J2EE Portlet API,

Java Page Flows, NetUIx Control, Personalization, Presentation Contexts, Profile

Factory, Profile Manager, WSRP, and Workshop Controls nodes are available under

the WebLogic Portal node.

Note:To view the J2eePortlet and NetUIxControls nodes, turn on the flag

NetUIxControl and J2eePortlet in the powerpackforweblogicportal_typical.pbd or

powerpackforweblogicportal_full.pbd for your mode.

Method level tracing is available for books, pages, and portlets. All the metrics

appear directly under the corresponding lifecycle methods when you use

powerpackforweblogicportal_full.pbd.

For portlets five metrics, namely, Average Response Time, Responses Per Interval,

Concurrent Invocations, Errors Per Interval, and Stall Count metrics are available for

full configuration. For books and pages six metrics, namely, Average Response Time,

Responses Per Interval, Incremental Response Time, Concurrent Invocations, Errors

Per Interval, and Stall Count are available for full configuration.

Note:To display Errors Per Interval, enable

powerpackforweblogicportal_errors.pbd in the powerpackforweblogicportal.pbl

file.

For pages under the WebLogic Portal > Desktops> > Book >

> Page > node, only Average Response Time, Incremental

Response Time, and Responses Per Interval metrics are available for typical and full

configuration.

For portlets under the WebLogic Portal > Desktops> > Page >

>Portlet > node, only Average Response Time and

Responses Per Interval metrics are available for typical and full configuration.

Note:Incremental Response Time is available only for pages and books. Portlets do not

have Incremental Response Time.

For portlets under the WebLogic Portal > WSRP > Producer >

-node, only Average Response Time and Responses

Per Interval metrics are available for typical and full configuration.

View Metrics in a Typical Configuration

In a typical configuration, you can view all six metrics for critical components or metrics

for components other than the critical components that are being traced.


19/48



Follow these steps:

1. Modify the entries in the powerpackforweblogicportal_typical.pbd file for blame

point metrics fromfalse to true as follows:

SetTracerParameter:PortalBlamePointTracer forcestandardblamemetrics true

SetTracerParameter:PortalServletTracer forcestandardblamemetrics true

SetTracerParameter:ControlBlamePointTracer forcestandardblamemetrics true

SetTracerParameter:TLRControlWalkerAwareBlamePointTracer

forcestandardblamemetrics true

SetTracerParameter:WSRPProxyBlamePointTracer forcestandardblamemetrics

true

2. Restart the Portal Server for the changes to take effect.

Important! When you enable the typical configuration, copy

PowerpackForWeblogicPortal_ManagementModule_typical.jar to the

\config\modules directory.

For books and pages under the WebLogic Portal > Desktops> Book node and

WebLogic Portal > Desktops> Book > Page node, only Average Response Time,

Incremental Response Time, and Responses Per Interval metrics are available for

typical and full configuration.

For pages and portlets under the WebLogic Portal > Desktops> Page node and

WebLogic Portal > Desktops> Page > Portlet node, only Average Response Time and

Responses Per Interval metrics are available for typical and full configuration.

Note:Incremental Response Time is available only for pages and books. Portlets do

not have Incremental Response Time.

You can trace more WebLogic Portal components in typical configuration.

Follow these steps:

1. Enable the relevant tracer in powerpackforweblogicportal_typical.pbd by

uncommenting the tracer.


View Metrics in a Full Configuration

In a full configuration, you can monitor the performance of all the components of the

portal server.

Follow these steps:

1. Comment out or disable powerpackforweblogicportal_typical.pbd entry and

uncomment or enable powerpackforweblogicportal_full.pbd entry in

powerpackforweblogicportal.pbd.


20/48




Note: When you enable the full configuration, copy

PowerpackForWeblogicPortal_ManagementModule_full.jar to the

\config\modules directory to view the dashboards for full

configuration.

By enabling the full configuration, you can further triage, diagnose and detect the

component responsible, and rectify the error.

Note: Do not enable powerpackforweblogicportal_typical.pbd and

powerpackforweblogicportal_full.pbd at the same time. If you do so, a conflict can

occur in displaying the aggregated metrics at the parent level node in the

Investigator tree. As a result, Introscope Enterprise Manager can throw exceptions.

Disable Tracing for Typical and Full Configuration

You can also disable the tracing of a component in the typical or full configuration.

Follow these steps:

1.

Disable the relevant tracer in powerpackforweblogicportal_typical.pbd or

powerpackforweblogicportal_full.pbd by commenting the tracer.


Find Errors

You can find errors that any of the lifecycle methods report in the Investigator tree.

Follow these steps:

1.

Uncomment or enable the powerpackforweblogicportal_errors.pbd entry in thepowerpackforweblogicportal.pbl file.

2.

Restart the Portal Server for the change to take effect.

powerpackforweblogicportal_errors.pbd reports how many errors that the agent

records by catching a Java exception in a 15-second time slice. The errors are recorded

for the methods of the classes that are being traced in the PBD.

If you enable the powerpackforweblogicportal_errors.pbd file, the errors are reported

for both, typical and full configuration. If you enable the

powerpackforweblogicportal_errors.pbd file, the errors are reported for typical

configuration. However, for full configuration, the node for Errors Per Interval is present

in the investigator tree but does not report any values.

When you enable the powerpackforweblogicportal_errors.pbd file in the full

configuration, you get metrics for Errors Per Interval with other metrics available with

method-level tracing. This setup helps you to get all the required details to triage the

problem in a better way. Hence, it is recommended that you use the

powerpackforweblogicportal_errors.pbd file in the full configuration.


21/48



Enable Debugging

Use caution when enabling debugging for WSRP because it causes a considerable

amount of overhead. This tracer is useful for getting all the details, but is too invasive

for most production environments.

Follow these steps:

1.

Uncomment or enable the WsrpHighOverheadDebug tracer in the

powerpackforweblogicportal_typical.pbd or powerpackforweblogicportal_full.pbd.

2. Restart the Portal Server for the change to take effect.

Note:If you enable the WsrpHighOverheadDebug tracer, you can see the Debug node

under WSRP in the Investigator.

Configuring PBDs for Version CompatibilityIf you are using WebLogic Portal Server 9.2, disable a tracer for WebLogic Portal Server

10.x and enable a tracer for 9.2 frompowerpackforweblogicportal_typical.pbd and

powerpackforweblogicportal_full.pbd files. Otherwise, errors that are related to the

tracer get reported in the agent logs.

Follow these steps:

1. Disable or comment out the following tracer from

powerpackforweblogicportal_typical.pbdandpowerpackforweblogicportal_full.pbd

files:

TurnOn: WSRPConsumerTracing10

2. Enable or uncomment the following tracer from

powerpackforweblogicportal_typical.pbdandpowerpackforweblogicportal_full.pbd

files:

TurnOn: WSRPConsumerTracing92

You have now configured the PBDs for version compatibility.


22/48

Clustering PowerPack for WebLogic Portal


(Optional) Creating an exclude list for URLs

You can define a list of URLs to exclude from monitoring.

To create an exclude list for URLs:

1. Create and add the com.wily.wlp.excludelist.overridesystem property to your

application startup file.

-Dcom.wily.wlp.excludelist.override=""

Use commas to separate the URLs. For example:

-Dcom.wily.wlp.excludelist.override="http://abc-xyz/console/console.portal,

http://abc-xyz/contentpresenter/"

Note:The application startup script is named as startWeblogic.cmdfor Windows

and as startWeblogic.shfor UNIX. The script is located in the

\samples\domains\portal\bin\directory.

2.

Save the startup script and restart the portal server.

Clustering PowerPack for WebLogic Portal

Clustering allows an Enterprise Manager to manage other Enterprise Managers, serving

as a Manager of Managers (MOM). The managed Enterprise Managers are called

collectors. In a clustered environment, install and configure the CA APM for Oracle

WebLogic Portal on each collector.

Follow these steps:

1. Install Enterprise Manager components of the CA APM for Oracle WebLogic Portal

(see page 14).

Note:All Enterprise Manager extensions and calculators for the CA APM for Oracle

WebLogic Portal must be placed on all the collectors.

2. Install the agent components of the CA APM for Oracle WebLogic Portal.

Note:The agents configured in the clustered environment must be connected to

MOM using the properties in the IntroscopeAgent.profilefile.

3. Configure the PBL file for typical, full, and errors PBDs.

4.

Configure PBDs for version compatibility(see page 21).

5. Create an exclude list for URLs(see page 22).


23/48

Disabling CA APM for Oracle WebLogic Portal


Running JavaScript Calculators on the MOM

You can run a JavaScript calculator on the MOM to produce metrics for the MOM agent.

The calculator cannot produce metrics for agents that are connected to a collector, but

it can see input metrics from agents in the collectors.

If a calculator is added, modified, or deleted in a clustered environment, the MOM

propagates the change to all collectors unless you turn off the automatic update. For

more information, see the CA APM Workstation User Guide.

Using the runOnMOM function

A JavaScript calculator that should not run on the MOM must implement a runOnMOM

function that returns false, such as in the following example:

// return false if the script should not run on the MOM

// default is true.

function runOnMOM(){

return false;

}

If the runOnMOMfunction returns true, the JavaScript calculator runs on the MOM.


Delete the files that you copied while installing the CA APM for Oracle WebLogic Portal.

Also delete the relevant entries for properties and environment variables from the

IntroscopeAgent.profilefile and application startup script.

Follow these steps:

1.

Delete the following files from the relevant directories on the agent system:

PowerPackforWeblogicPortal_ext.jarfrom \wily\ext.

powerpackforweblogicportal.pbl,powerpackforweblogicportal.pbd,

powerpackforweblogicportal_errors.pbd,powerpackforweblogicportal_full.pbd,

andpowerpackforweblogicportal_typical.pbdfrom \wily.


24/48



2. Delete the following files from the relevant directories on Enterprise Manager:

PowerpackForWeblogicPortal_ManagementModule_typical.jarfrom

\config\modules.

PowerpackForWeblogicPortal_ManagementModule_full.jarfrom\config\modules\portal.

com.wily.powerpack.weblogicportal.em.ext.jarand

com.wily.powerpack.weblogicportal.em.service.jarfrom

\product\enterprisemanager\pluginsdirectory.

com.wily.powerpack.weblogicportal.ws.ext.jarfrom

\ws-pluginsand

\config\internal\console\ws-pluginsdirectories.

3. Open the IntroscopeAgent.profilefile located in the \wilydirectory and

delete thepowerpackforweblogicportal.pblfrom the

introscope.autoprobe.directivesFileproperty.

4.

Delete the com.wily.wlp.excludelist.overridesystem property from the application

server startup script, startWeblogic.cmdor startWeblogic.sh, if applicable.

You have now disabled the CA APM for Oracle WebLogic Portal.


25/48

Chapter 3: Using the CA APM for Oracle WebLogic Portal 25

Chapter 3: Using the CA APM for OracleWebLogic Portal

The CA APM for Oracle WebLogic Portal enables you to monitor the WebLogic Portal

components and view its health and availability metrics in Introscope.


Monitoring WebLogic Portal(see page 25)

Viewing Dashboards(see page 27)

Viewing Metrics(see page 31)

Viewing worst performing components(see page 32)

Sample Operation Scenario(see page 36)

Monitoring WebLogic Portal

You can view real-time metric data in the Investigator and Console to monitor the

health, availability, and performance of WebLogic Portal.

WebLogic Portal Metrics

The following metrics appear for each operation in WebLogic Portal:

Average Response Time (ms): average time taken for executing or invoking a

specific operation or action.

Concurrent Invocations: how many requests are going through at a given time

(throughput).

Errors Per Interval: how many errors are recorded by the agent by catching a Java

exception in a 15-second time slice.

Responses Per Interval: the number of invocations that completed during a

15-second time slice.

Incremental Response Time: time taken for executing lifecycle phases during a

15-second time slice.

Stall Count: how many operations, invocations, or calls are taking longer than 30seconds in a 15-second time slice.


26/48

Monitoring WebLogic Portal


In the Investigator tree, under the WebLogic Portal > Desktops node, you can see

Portlets and URLs nodes. Under the WebLogic Portal > Desktops > URLs node, you can

see Control Tree Walker, Books, Pages, JSP Backing Files, and Portlet Servlet nodes.

Under the WebLogic Portal > Desktops > URLs > Books you can see pages that belong to

the books and under the WebLogic Portal > Desktops > URLs > Pages node you can seeportlets that belong to the pages.

The following screenshot illustrates this hierarchy:

Worst Performing Components

The CA APM for Oracle WebLogic Portal displays the worst performing components in a

tabular view. For the Browse tree nodes that display metrics for the components of the

WebLogic Portal, a corresponding tabular view displays relevant components in the

Viewer pane under the Portal tab on right hand side.

Viewing Worst Performing Components

The tabular view displays the following information:

Top worst performing books, pages, and portlets of the WebLogic Portal.

The components are sorted based on their Average Response Time.


27/48

Viewing Dashboards


Graphical view for worst performing components

Identify the worst performing component that is based on the Average Response Time

from the tabular view. Then, look into the overall impact of the worst performing

component on the portal.

A graphical view that is based on the tabular view provides a high-level view of

relationships between the worst performing components and other portal components.

This perspective helps you understand how the worst performing components affect

the other components in the portal server.

Viewing Dashboards

CA APM for Oracle WebLogic Portal dashboards combine and present application

metrics in views that you can use to monitor your application environment. Dashboards

aggregate data across all the deployed agents and deliver the in-depth performanceinformation that is required to diagnose and resolve problems quickly.

The dashboards provide:

Overall application health and status views of the application.

At-a-glance notification of problems in the production application environment.

Data that enables you to identify the problems quickly.

Predefined navigation between high-level and drill-down performance information.

The Management Modules PowerpackForWeblogicPortal_ManagementModule_full.jar

and PowerpackForWeblogicPortal_ManagementModule_typical.jarfiles providepredefined dashboards for CA APM for Oracle WebLogic Portal.

Important!Do not have PowerpackForWeblogicPortal_ManagementModule_full.jarand

PowerpackForWeblogicPortal_ManagementModule_typical.jarin the

\config\modulesdirectory at the same time.

Dashboards are associated with alerts that show the overall health of the application.

Each alert color has a metric value:

Gray indicates that no data is available.

Green indicates OK.

Yellow indicates Caution. Red indicates Danger.


28/48

Viewing Dashboards


Follow these steps:

By default, the PowerpackForWeblogicPortal_ManagementModule_typical.jaris in the

\config\modules directoryand

PowerpackForWeblogicPortal_ManagementModule_full.jaris in the\config\modules\portaldirectory.

1. When you enable the full configuration, copy

PowerpackForWeblogicPortal_ManagementModule_full.jarto the

\config\modulesdirectory. When you enable the typical

configuration, copy PowerpackForWeblogicPortal_ManagementModule_typical.jar

to the \config\modulesdirectory.

2.

Ensure that your applications are instrumented and providing data.

3. Ensure that the Enterprise Manager is running.

4.

Launch the Workstation by clicking Start > Programs > CA APM > Introscope

> Introscope Workstation.

5. Log in to the Workstation.

Introscope Workstation appears.

6. Navigate to the Introscope Workstation Console by clicking Workstation > New

Console.

7. Select one of the following dashboards from the drop-down list.

For typical configuration, the following dashboards are available:

CA APM for Oracle WebLogic Portal (typical)Authentication

CA APM for Oracle WebLogic Portal (typical)Overview

CA APM for Oracle WebLogic Portal (typical)Portal Services

CA APM for Oracle WebLogic Portal (typical)Content Management

CA APM for Oracle WebLogic Portal (typical)Control Tree Processing

CA APM for Oracle WebLogic Portal (typical)Entitlements

CA APM for Oracle WebLogic Portal (typical)Portlets

CA APM for Oracle WebLogic Portal (typical)WSRP


29/48

Viewing Dashboards


For full configuration, the following dashboards are available:

CA APM for Oracle WebLogic Portal (full)Overview

CA APM for Oracle WebLogic Portal (full)Authentication

CA APM for Oracle WebLogic Portal (full)Content Management

CA APM for Oracle WebLogic Portal (full)Control Tree Processing

CA APM for Oracle WebLogic Portal (full)Entitlements

CA APM for Oracle WebLogic Portal (full)JSP Backing Files

CA APM for Oracle WebLogic Portal (full)Java Page Flows

CA APM for Oracle WebLogic Portal (full)Personalization

CA APM for Oracle WebLogic Portal (full)Portal Services

CA APM for Oracle WebLogic Portal (full)Portlets

CA APM for Oracle WebLogic Portal (full)Presentation Contexts

CA APM for Oracle WebLogic Portal (full)User Profiles

CA APM for Oracle WebLogic Portal (full)WSRP

8. To view more information using dashboards, seeTo view more information using

dashboards(see page 31).

Dashboards

The following dashboards are available for typical and full configuration:

When monitoring WebLogic Portal using typical configuration, first view the

Overview dashboard. The dashboard shows the overall performance of the critical

components of WebLogic Portal. Each component is associated with an alert to

show its overall health.

CA APM for Oracle WebLogic Portal (typical)Authentication

The dashboard shows the overall health of the Authentication service.

CA APM for Oracle WebLogic Portal (full)Authentication

The dashboard shows the overall health of Authentication by displaying metrics for

Basic User Form Authentication, Authenticate Users, Run as Users, Access Checks,

Get Roles, Adjudicate Results, and Validate Principals metric categories.

CA APM for Oracle WebLogic Portal (typical/full)Content Management

The dashboard shows the overall health of Content Management by displaying

metrics for Node Hierarchy - Get Node, Node Properties, and Search metric

categories.


30/48

Viewing Dashboards


CA APM for Oracle WebLogic Portal (typical/full)Control Tree Processing

The dashboard shows the overall health of Control Tree Processing.

CA APM for Oracle WebLogic Portal (typical/full)Entitlements

The dashboard shows the overall health of Entitlements by displaying graphs for

Get Roles, Is Access Allowed, and Is User In Role metric categories.

CA APM for Oracle WebLogic Portal (typical/full)Portal Services

The dashboard shows the overall health of Portal Services.

CA APM for Oracle WebLogic Portal (typical/full)Portlets

The dashboard shows the overall health of the Portlets.

CA APM for Oracle WebLogic Portal (typical/full)WSRP

The dashboard displays the overall health of web services for Remote Portlets

(WSRP) by displaying metrics for the producer and consumer.

CA APM for Oracle WebLogic Portal (full)JSP Backing Files

The dashboard shows the overall health of JSP Backing Files by displaying the

metrics for Init, Handle Postback Data, and Pre-render metric categories.

CA APM for Oracle WebLogic Portal (full)Java Page Flows

The dashboard shows the overall health of Java Page Flows and Page Flow Content.

CA APM for Oracle WebLogic Portal (full)Personalization

The dashboard shows the overall health of Personalization by displaying the metrics

for Advisor and Advislet metric categories.

CA APM for Oracle WebLogic Portal (full)Presentation Contexts

The dashboard shows the overall health of Presentation Contexts.

CA APM for Oracle WebLogic Portal (full)User Profiles

The dashboard shows overall health of User Profiles by displaying the metrics for

Profile Manager and Profile Factory.


31/48

Viewing Metrics


View Dashboards

You can use dashboards to triage problem-causing components, services, or functions

for WebLogic Portal.

Follow these steps:

Double-click an alert to open the dashboard associated with it.

Click Details to view details associated with the component or dashboard.

Right-click a graph or an alert, click Links, and navigate to the corresponding alert in

the Management Module or another dashboard associated with it.

Double-click a metric from the chart displaying top 10 slowest metric data to view

its details in the Investigator.

Viewing MetricsWhen you select a metric in the Investigator tree, the data for the metric is displayed in

a graphical format in the Viewer pane on the right hand side. The metrics that appear in

the Investigator depend on the resources that your application uses.

To view metrics in the Investigator:

1. Ensure that your applications are instrumented and providing data.

2.

Ensure that the Enterprise Manager is running.

3. Access Workstation or WebView and use the Investigator UI.

4.

Metrics that are specific to WebLogic Portal appear under the *SuperDomain* >> WebLogic > WebLogic Agent > WebLogic Portal node.

5. Expand the WebLogic Portal node.

The WebLogic Portal metric data appears under sub-nodes of the WebLogic Portal

node. The sub-nodes that you see depend on the type of configuration you use. For

details, seeConfiguring the PBL file for typical, full, and errors PBDs(see page 17).

6. Expand the sub-nodes for WebLogic Portal node to view the individual portal

components, services, functions and metrics listed under each.

Note:The metrics you see in the Investigator depend on the Portal resources your

application uses. Refer toMetrics(see page 39), for the full list of performance metrics

collected by the CA APM for Oracle WebLogic Portal.


32/48

Viewing worst performing components



You can view the worst performing component of the portal server in the Investigator.

The worst performing books, pages, and portlets are displayed in a table in the Viewer

pane. The components are sorted on the Average Response Time. You can generate a

graphical view that is based on the worst performing components table and view how

they affect other components in the portal.

Follow these steps:

1.

In the Investigator, click the WebLogic Portal node or any of its nodes such as

Desktops, JavaPortlet, Portlet, , ProxyPortlet, Book, or Page for

which you want to view the worst performing components.

In the Viewer pane, the Portal tab is active by default. Depending on the node you

selected, a list of components is displayed in a table. The following section gives

details of the components that are displayed at each node:

WebLogic Portal

Books, Pages, Portlets, Java Portlets, and Proxy Portlets.

WebLogic Portal > Desktops

Books, Pages, Portlets, Java Portlets, and Proxy Portlets.

WebLogic Portal > Desktops > Portlet

All Portlets in the Portal Server.

WebLogic Portal > Desktops > JavaPortlet

All Java Portlets in the Portal Server.

WebLogic Portal > Desktops > ProxyPortlet

All Proxy Portlets in the Portal Server.

WebLogic Portal > Desktops >

Books and Pages that are part of .

WebLogic Portal > Desktops > > Book

All Books that are part of .

WebLogic Portal > Desktops > > Pages

All Pages that are part of .

You can view the component name, component type, the Average Response Time,

and Responses Per Interval for each component.

Note:In the tabular view for worst performing components, only for portlets, you

can see the Desktop to which the portlet belongs under Desktop Name column. For

Books and Pages the actual DeskTop to which Book or Page belongs to can be seen

under Desktop Name column.


33/48



2. If you selected WebLogic Portal node, you can select All, Book, Page, Portlet,

JavaPortlet, or ProxyPortlet from the Component Type drop-down list and a

number from the Top N drop-down list.

Note:Here N is 10, 100, or 500. You can also enter a number other than 10,100, or

500 for Top N.

If you select a number greater than 25 for Top N, it impacts performance on the

workstation.

To view top N worst performing components of the same type, select a component

type and number N. For example, select Book and number N to view top N worst

performing books.

The Component Type drop-down list and Top N drop-down list are available only if

you select the WebLogic Portal or Desktops node. If you select any node other than

WebLogic Portal and Desktops node, the drop-down lists are not available.

3. Perform one of the following tasks:

Select a component and click Detail.

Depending on the component you selected, the Viewer pane displays the

following tables:

The table at the top of the Viewer pane displays the child components for

the selected component.

This table displays only the top ten worst performing child components.

The table also displays the aggregated Average Response Time and

aggregated Responses Per Interval for the child components.

The table at the bottom of the Viewer pane displays the parent

components for the selected component.

This table displays only the top ten worst performing parent components.

The table also displays the Average Response Time and Responses Per

Interval that are Average Response Time and the Responses Per Interval of

the selected component relative to its parent component.

Note:If you select a portlet and click Detail, only a single table is displayed for

the parent components of the selected portlets.

For example, if you select a page in the tabular view and click Detail, you can

view the following details:

The table at the top of the Viewer pane displays the top ten worst

performing portlets for the selected page.

This table displays only the top ten worst performing portlets. The tablealso displays the aggregated Average Response Time and aggregated

Responses Per Interval for the portlets.


34/48



The table at the bottom of the Viewer pane displays the books that the

selected page belongs to. The Average Response Time and the Responses

Per Interval displayed in this table are respective Average Response Time

and the Responses Per Interval of the page relative to the books displayed

in the table.

The following table summarizes the details that you can view for each component:

Component Details

Book Table at the top displays a list of Pages under the selected

Book.

Table at the bottom displays a list of Desktops that contain

the selected Book.

Page Table at the top displays a list of Portlets under the

selected Page.

Table at the bottom displays a list of Books that contain

the selected Page.

Portlet Table at the top displays a list of Pages that contain the

selected Portlet.

Table at the bottom is not displayed.

JavaPortlet Table at the top displays a list of Pages that contain the

selected Java Portlet.


ProxyPortlet Table at the top displays a list of Pages that contain the

selected Proxy Portlet.



35/48



Click Generate Graph.

A graphical view that is based on the table from which you generated the graph

is displayed.

The graphical view has the following details:

Root Name (Weblogic Portal)

Desktop, Book, Page, and Portlet name in the node

The date and time stamp when the graph is generated.

The number of components being displayed in the graph.

A maximum of top 20 worst performing components from the tabular view

are used to construct the graph.

At each level of the graph, the number of viewable nodes is restricted to

20.

Note:To know how the individual components in the graph view are selected,read the FAQ section.

Nodes in the graph have values for Average Response Time and Responses

Per Interval. These values are from the tabular view from which the graph

was generated.

Edges in the graph have values for Average Response Time and Responses

Per Interval. These values indicate the performance of the child

components relative to its parent component. For example, the Average

Response Time and Responses Per Interval for an edge between portlet1

and page1 indicates the Average Response Time and Responses Per

Interval of the portlet1 in page1.

Each node type is identified with a unique icon for the component.

The components that are taken from the tabular view for generating the

graph view are highlighted with blue colored background.

a. You can perform the following actions on the graph:

b.

To see an overview of the entire graph, select the check box at the bottom

right corner of the graphical view. You can use this overview to pan or

zoom the contents of the graph. If you deselect the check box, the

overview is not displayed.

c.

Click Back to go back to the tabular view that lists the worst performing

components.

The tabular view that is displayed now is a refreshed view. Save the graph before you

click Back.

With the help of the tabular and graphical view in the Investigator, you have viewed the

worst performing components and how they affect other components.


36/48

Sample Operation Scenario



This section describes a typical production setting situation in which the CA APM for

Oracle WebLogic Portal helps resolve the problem.

Customer says: "We have a problem"

The operator on duty receives a problem escalation indicating a performance or

availability problem with one of the monitored systems. The operator does not know

which system is the root cause or how to fix it. Operators only want to know who to call

to fix the problem.

Data center operator: responding to red light

The data center operator notices that the Portlets alert is red on the CA APM for Oracle

WebLogic Portal (typical) -- Overview dashboard, indicating a problem with the Portal.

Respond to the problem escalation by performing the following tasks:

1. Double-click Details in the dashboard and switch to the CA APM for Oracle

WebLogic Portal (typical) -- Portlets dashboard.

This dashboard displays information about the top ten slowest Average Response

Time and Responses Per Interval. One portlet spends a great deal more time in

Pre-Render than any other portlet in the system. Mouse over the bar to get more

information.

2. Copy some of the information on that dashboard and pass it on to the application

support specialist.

Application support specialist: viewing worst performing components for WebLogic Portal

Often the application support specialist receives reports of performance problems. The

support personnel must narrow down the problem further to escalate the issue to t he

proper team.


37/48



The application support specialist performs the following tasks:

1. View the worst performing components in the Investigator from the WebLogic

Portal node to use the table to narrow down the problem.

Specialist observes that the Average Response Time is high for a portlet.

2. To see if this portlet is affecting the other components of the port, select Generate

Graph to generate a graphical view.

Specialist observes that this portlet is causing five other pages, a book, and a

desktop to slow down. None of them would stand out individually.

3. Escalate this problem to the relevant portal development team with information

about the pages and portlets involved in the problem.

Portal developers: resolving the problem using metrics for in-depth diagnosis

Once the Portal developers receives the problem report, they perform the following

task:

They use Introscope Investigator to go beyond the dashboards, tabular and

graphical views for worst performing components, and drill down to the metrics for

the problem causing portlet.

For more information about using Investigator to diagnose application problems, see

the CA APM Workstation User Guide.

Their intimate knowledge of the Portal code combined with Introscope's metrics allow

them to pinpoint the exact method in the portlet that is the root cause. They can rectify

the code and resolve the problem.

Thus the team has used CA APM for Oracle WebLogic Portal dashboards, tabular andgraphical view for worst performing components, and metrics in the Investigator to

detect, triage, diagnose, and resolve the problem.


38/48


39/48


Appendix A: Metrics


Metrics path(see page 39)

Metric categories(see page 39)

Metrics path

All metrics appear in the Introscope Investigator under the WebLogic Portal node in the

format:

WebLogic Portal||.

Metric categories

The following metric categories are available when you monitor your Portal Server using

the CA APM for Oracle WebLogic Portal.

Note:The metrics seen in your Introscope Workstation depend on your environment.

Authentication

WebLogic Portal|Authentication|Access Checks

WebLogic Portal|Authentication|Adjudicate Results

WebLogic Portal|Authentication|Authenticate users

WebLogic Portal|Authentication|Basic User Form Authentication

WebLogic Portal|Authentication|Get Roles

WebLogic Portal|Authentication|Run as Users

WebLogic Portal|Authentication|Validate Principal

Content Management

WebLogic Portal|Content Management|Node|Get Name

WebLogic Portal|Content Management|Node|Get Path

WebLogic Portal|Content Management|Node|Get Created By

WebLogic Portal|Content Management|Node|Get Modified By


40/48

Metric categories


WebLogic Portal|Content Management|Node|Get Created Date

WebLogic Portal|Content Management|Node|Get Modified Date

WebLogic Portal|Content Management|Node Ops|Get Node

WebLogic Portal|Content Management|Search|Expression Helper|Normalize

WebLogic Portal|Content Management|Search|Expression Helper|Parse

WebLogic Portal|Content Management|Search|Search Ops|Get Node

WebLogic Portal|Content Management|Search|Repository Manager|Search

Repository

WebLogic Portal|Content Management|Search|Node Ops|Get Nodes

Desktops

WebLogic Portal|Desktops|JavaPortlet|{definition_label}

WebLogic Portal|Desktops|JavaPortlet|{definition_label}|{method}

WebLogic Portal|Desktops|Portlet|{definition_label}

WebLogic Portal|Desktops|Portlet|{definition_label}|{method}

WebLogic Portal|Desktops|ProxyPortlet|{definition_label}

WebLogic Portal|Desktops|ProxyPortlet|{definition_label}|{method}

WebLogic Portal|Desktops|{request_url}|Book|{book_definition_label}

WebLogic Portal|Desktops|{request_url}|Book|{book_definition_label}|

{method}

WebLogic Portal|Desktops|{request_url}|Book|{book_definition_label}|Page|{page_definition_label}

WebLogic Portal|Desktops|{request_url}|Book|{book_definition_label}|

Page|{page_definition_label}|{method}

WebLogic Portal|Desktops|{request_url}|Page|{page_definition_label}

WebLogic Portal|Desktops|{request_url}|Page|{page_definition_label}|

{method}


|Portlet|{portlet_definition_label}


|Portlet|{portlet_definition_label}|{method}

WebLogic Portal|Desktops|{request_url}|Control Tree Walker| Walk


41/48

Metric categories


WebLogic Portal|Desktops|{request_url}|Control Tree Walker| Walk|Lifecycle

Phases|{lifecycle phase}

WebLogic Portal|Desktops|{request_url}|JSP Backing Files|{classname}|{method}

WebLogic Portal|Desktops|{request_url}|Page FlowContent|{content_url}|{method}

WebLogic Portal|Desktops|{request url}|Portlet Servlet

Entitlements

WebLogic Portal|Entitlements|Get Roles

WebLogic Portal|Entitlements|Is User in Role

WebLogic Portal|Entitlements|Is Access Allowed

Java Page Flows

WebLogic Portal|Java Page Flows|{packagename}|{classname}|

WebLogic Portal|Java Page Flows|{packagename}|{classname}|{method}

WebLogic Portal|Java Page Flows|{packagename}|{controller_name}

WebLogic Portal|Java Page Flows|{packagename}|{controller_name}|{method}

J2EE Portlet API

WebLogic Portal|J2EE Portlet API|Render

NetUIx Controls

WebLogic Portal|NetUIx Control|{classname}|{method}

Personalization

WebLogic Portal|Personalization|Advisor|Get Advice

WebLogic Portal|Personalization|Advislet|Get Advice

WebLogic Portal|Personalization|Advislet|Get Required Attributes

WebLogic Portal|Personalization|Advislet|Validate Advice Request


42/48

Metric categories


Presentation Contexts

WebLogic Portal|Presentation Contexts|{classname}|Render

Profile Factory

WebLogic Portal|Profile Factory|Get Profile

WebLogic Portal|Profile Factory|Create Profile Identity

Profile Manager

WebLogic Portal|Profile Manager|Get Properties

WebLogic Portal|Profile Manager|Get Property as String

WebLogic Portal|Profile Manager|Set Property

Workshop Controls

WebLogic Portal|Workshop Controls|Create User Control|Create User

WebLogic Portal|Workshop Controls|User Login Control|Login

WebLogic Portal|Workshop Controls|User Login Control|Logout

WebLogic Portal|Workshop Controls|User Profile Control|Get Profile

WebLogic Portal|Workshop Controls|User Profile Control|Get Properties

WebLogic Portal|Workshop Controls|User Profile Control|Get Property

WebLogic Portal|Workshop Controls|User Profile Control|Get Profile For User

WebLogic Portal|Workshop Controls|User Info Control|Get Authenticated User Id

WebLogic Portal|Workshop Controls|User Info Control|Get Available User Roles

WebLogic Portal|Workshop Controls|User Info Control|Get Group Names for User

WebLogic Portal|Workshop Controls|User Info Control|Get User Group Names

WebLogic Portal|Workshop Controls|User Info Control|Is Current User in Role

WSRP

WebLogic

Portal|WSRP|Consumer|{ProxyClass}|{producer_name}-{producer_Handle}|{portle

t_name}

WebLogic Portal|WSRP|Producer|{consumer_host}-{producer_url}|{portlet_name}

WebLogic Portal|WSRP|Debug|{classname}|{method}


43/48

Metric categories


Chapter 4: Enable IPv6 Addresses-

WebLogic Portal Server v9.2, v10.0, v10.2, and v10.3 are certified to use dual stack.

Components of the CA APM for Oracle WebLogic Portal that are installed on WebLogic

Portal Server are IPv6 compliant.

IPv6 support for the CA APM for Oracle WebLogic Portal is dependent upon the

environment (JVM, WebLogic Portal, operating system, hardware stack) in which the CA

APM for Oracle WebLogic Portal is running.

Follow these steps:

On Windows:

1.

Open the Portal Server startup script.

2. Add the following property to the JavaOptions section in the script:

-Djava.net.preferIPv6Addresses=true

On UNIX:

1. Open the Portal Server startup script.

2. Add the following property to the JavaOptions section in the script:

-Djava.net.preferIPv6Addresses=true

Note:When you set -Djava.net.preferIPv6Addresses=true, the Investigator displays the

full IPv6 address under *SuperDomain* | | | Host : IP

Address. If the IPv6 address is not mentioned in the hosts file of the system on which

the agent is running, the Investigator displays 0:0:0:0:0:0:0:1.


44/48


45/48


Appendix B: Frequently Asked Questions

This appendix contains frequently asked questions regarding CA APM for Oracle

WebLogic Portal.

How can I customize the metrics created by the Product?

Two preconfigured pbds are available with the product; they are

powerpackforweblogicportal_typical.pbdandpowerpackforweblogicportal_full.pbd. You

can use any one of them. If you want to enable other modules, uncomment the

corresponding lines from thepowerpackforweblogicportal_typical.pbd. Do not

comment any of the tracer flags which are enabled by default from

powerpackforweblogicportal_typical.pbd. Creation of other metrics is impacted.

Why am I not seeing method level metrics with the product?

Method level metrics are available with thepowerpackforweblogicportal_full.pbd and

are not available with thepowerpackforweblogicportal_typical.pbd. Using

powerpackforweblogicportal_full.pbd creates numerous metrics and more performance

overhead. Avoid using the same unless needed for triaging purposes.

Why am I getting error message in Enterprise Manager log thatsays "An Agent is illegally reporting data against the calculatormetric"? Why does a null node appear in investigator tree too?

You get this error if you enable the following tracer in

powerpackforweblogicportal_typical.pbd:

TurnOn: ControlsWithTitles

Similarly, you get this error if you enable the following tracer in

powerpackforweblogicportal_full.pbd:

TurnOn: OverallPortletComponentTracing

To avoid this error and the null node in the Investigator tree, do not enable the TurnOn:ControlsWithTitlestracer inpowerpackforweblogicportal_typical.pbdand the

TurnOn: OverallPortletComponentTracingtracer in

powerpackforweblogicportal_full.pbd.


46/48

Why am I seeing wrong relations between books, pages and desktops?


Why am I seeing wrong relations between books, pages anddesktops?

This problem is because of the ControlTreeWalkerTracingbeing commented in the pbd.Check to see whether ControlTreeWalkerTracingis uncommented.

Why am I seeing the Average Response Time of Page less thanthe Average Response Time of the Worst Performing Portletwithin the page?

The product captures the number of events (Init, Handle Post Back, Pre Render, Raise

Change Events and Save State) that are fired on these controls during the traversal of

the Control Tree Map.

The Average Response Time of the page is averaged out of its life cycle methods. This

time is less than the Average Response Time of the Worst Performing portlet within that

page.

If I click one page/portlet, why am I seeing values on manyBooks/Pages/Portlets in Investigator? Why am I seeingAverage Response Time as 0 for many of the components?

Responses Per Interval is not an accurate number. This number does not reflect theactual number of times a Page/Book/Portlet is accessed during the last Introscope

interval (15 seconds). This metric is only the number of events (Init, Handle Post Back,

Pre Render, Raise Change Events and Save State) that are examined on these controls

during the traversal of the Control Tree Map. Therefore, the Average Response time is

zero for most of the controls that were not part of the requested control.

Why am I seeing the value of Responses Per Interval as morethan 1 even though I accessed the page/book once?

If you access only one page, it is possible that methods are called for other components(Book/Page/Portlet) during internal rendering. Examples of methods are Init, Handle

Post Back, Pre Render, Raise Change Events, and Save State. This results in having

Responses Per Interval greater than one.


47/48

I have a portlet which is part of many pages (Similarly, a page part of many books). Why am I not seeing all of them in the

graph?


I have a portlet which is part of many pages (Similarly, a pagepart of many books). Why am I not seeing all of them in the

graph?The number of components at each level in the graph has been restricted to 20. The

pages where the portlet is worst performing are present in the graph.

Why am I not seeing an edge from a parent to a child (book -page, page - portlet), even though the graph has both thecomponents?

The graph is used to identify the impact of the worst performing components. Even

though a page and a portlet part of the page are present in the graph, that portletperforms well for that page. For example, a portlet has Average Response Times of 15

and 20 for page 1 and page 2. Even though page 1 is already shown as the worst

performing, the graph shows a relationship from the portlet to page 2. This portlet is

having the worst performance for page 2. Page 1 is the worst performing because of

some other portlet.

Why am I not seeing all the components from the table in thegraph?

The graph shows the impact of the worst performing components within the server. Ifthe relationships for those components are not present, then they cannot be shown in

the graph.

Why am I seeing multiple Portal typeviews? Within that, onlyone is performing as expected.

If you see more than one portal tab coming, the user logged out of the workstation and

in again without exiting. The solution is to exit the workstation, delete the folder

ws-pluginspresent under /config/internal/consoleand start the

workstation. Exit the workstation every time you log out.


48/48

Why am I not seeing data for some of the components in the Dashboard?

Why am I not seeing data for some of the components in theDashboard?

CA APM for Oracle WebLogic Portal contains two Management Module .jar files:

PowerpackForWeblogicPortal_ManagementModule_typical.jar

PowerpackForWeblogicPortal_ManagementModule_full.jar

Use the Management Module that corresponds to the .pbd that you use in

.The other Management Module .jar can be moved to the portal

directory for future use.

apm_9.5--apm for oracle weblogic portal guide

Documents