AnsweredAssumed Answered

Urgent Help Needed - WebSphere Portal Doesn't Appear in Metric Browser

Question asked by prejo12 Employee on Jun 24, 2015
Latest reply on Jun 24, 2015 by DavidLewis

Hi all.

 

Urgent help would be greatly appreciated.

 

We followed the process for installing a WebSphere Portal agent (as found at https://wiki.ca.com/display/APMDEVOPS97/IBM+WebSphere+Portal)

 

When restarting the portal instance it seems that the Agent is not starting (we can't see a log file for the agent) - this also means that there are no metrics found in the metric browser.

 

One thing that seems missing from the installation instructions is how WebSphere Portal starts the agent.

 

Can anyone please offer some guidance?

 

The process we sent to the client is as follows:

 

Install Agent Components of the CA APM for IBM WebSphere Portal

-----------------------------------------------------------------------------------

 

Please follow these steps to install the agent on a WebSphere portal instance:

 

1. Extract the IntroscopeJavaAgentFilesForAllApplicationServers-No InstallerR9.7.1.tar file to <WAS_Home>/PortalServer as the installation directory.

The result will be a folder new folder named wily.

Verify that the <WAS_Home>/PortalServer/wily directory has the following files:

                * <WAS_Home>/PortalServer/wily/core/config/powerpackforwebsphereportal-legacy.pbl

                * <WAS_Home>/PortalServer/wily/core/config/powerpackforwebsphereportal-legacy.pbd

                * <WAS_Home>/PortalServer/wily/core/config/powerpackforwebsphereportal_typical.pbd

 

 

2. Set up IntroscopeAgent.profile

2.1 Rename <WAS_Home>/PortalServer/wily/core/config/IntroscopeAgent.websphere.NoRedef-legacy.profile to IntroscopeAgent.profile

2.2 Edit <WAS_Home>/PortalServer/wily/core/config/IntroscopeAgent.profile:

2.3 Locate the property introscope.autoprobe.directivesFile.

2.4 Update the property to reflect the following:

                                introscope.autoprobe.directivesFile=websphere-full-NoRedef-legacy.pbl,hotdeploy,powerpackforwebsphereportal-legacy.pbl,powerpackforwebsphereportal_errors-legacy.pbd

2.5 Update the IP address of the EM to be: 10.1.18.27

 

 

3. Copy the PowerPackforWebspherePortal_ext.jar file from the <WAS_Home>/PortalServer/wily/examples/<PowerPackForWebspherePortal>/ext directory to the <WAS_Home>/PortalServer/wily/core/ext directory.

 

4. Set up full monitoring:

4.1 Copy <WAS_Home>/PortalServer/wily/core/config/websphere-typical-NoRedef-legacy.pbl to websphere-full-NoRedef-legacy.pbl

4.2 In websphere-full-NoRedef-legacy.pbl

4.2.1 Update "toggles-typical-NoRedef.pbd" to "toggles-full-NoRedef.pbd"

4.2.2 Uncomment "#ServletHeaderDecorator.pbd"

 

5. Configure Authentication

5.1 Update <WAS_Home>/PortalServer/wily/core/config/powerpackforwebsphereportal-legacy.pbd.

5.1.1 Search for “SetFlag: WASPAuthenticationTracing”, uncomment the Authentication Method depending on the Portal Version, e.g.:

 

Enable this section for WAS Portal 7 and previous versions when Custom Login Command is used for authentication.

IdentifyClassAs: com.ibm.wps.engine.commands.LoginUserAuth WASPAuthenticationTracing

TraceOneMethodIfFlagged: WASPAuthenticationTracing doAuthenticate CustomBlamePointTracer "WebSphere Portal|Authentication|Login"

 

Enable this section for WAS Portal versions that are previous to version 7 when Servlet Filters are used for authentication.

IdentifyClassAs: com.ibm.wps.auth.impl.DefaultLoginFilter WASPAuthenticationTracing

TraceOneMethodIfFlagged: WASPAuthenticationTracing doLoginWithExceptions CustomBlamePointTracer "WebSphere Portal|Authentication|Login"

 

Enable this section for WAS Portal 7 and later versions when Servlet Filters are used for authentication.

IdentifyClassAs: com.ibm.wps.auth.impl.LoginDefaultFilter WASPAuthenticationTracing

TraceOneMethodIfFlagged: WASPAuthenticationTracing internalLogin CustomBlamePointTracer "WebSphere Portal|Authentication|Login"

 

 

6. Restart

 

Kind regards,

Johan

Outcomes