Chat now with support
Chat with Support

Foglight for Java EE Technologies 5.9.13 - Installation Guide

Installing and Configuring Foglight for Java EE Technologies Integrating with JBoss Integrating with Apache Tomcat Integrating with WebLogic Domain Startup Scripts Integrating with WebSphere Integrating with WebSphere Liberty Integrating with Oracle AS Integrating with Spring Boot for Embedded Tomcat Creating a Generic Installation for Manual Java EE Agent Integration Managing Java EE Agent Installations, Integrations, and Configurations Managing Java EE Agent Configurations Managing Java EE Installation Java EE Integration Configuration FAQ and Troubleshooting Manually Integrating Application Server Appendix A: Java EE Application Methods AppendixB: Managing Permissions for the Java EE Integration Agent

Integrating with WebLogic Domain Startup Scripts

You can use the Java EE Integration Agent to integrate the Java EE agent with WebLogic® domain startup scripts. Supply a description and the domain home path for the application server with which you want to integrate. If you are integrating with WebLogic running as a Windows® Service, specify the name of the Windows Service.

To integrate with WebLogic on Solaris®, Linux®, HP-UX®, or AIX®, or on Windows®
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
3
In the menu that opens, select Java. The Java — Setup New Application Server Integration wizard opens.
4
On the Setup Options page, select the type of integration. This example describes how to Setup a new application server integration (the default selection).

Windows Service

Integrates a WebLogic Server or NodeManager Windows Service.

Domain Startup Script

Integrates the startWebLogic.sh/.cmd scripts within a WebLogic Domain (DOMAIN_HOME/bin/startWebLogic).

NodeManager Startup Script

Integrates the startNodeManager.sh/.cmd scripts within a WebLogic installation (WL_HOME/server/bin/startNodeManager).

Managed Server Startup Script

Integrates the startManagedWebLogic.sh/.cmd scripts within a WebLogic 12.1.1 or earlier installation (WL_HOME/common/bin/startManagedWebLogic).

Non-Domain startWLS Startup Script

Integrates the startWLS script within a WebLogic 10.0 or earlier installation (WL_HOME/server/bin/startWLS).

All Non-Domain Scripts

Combines the NodeManager, Managed Server, and startWLS Startup Script tasks into a single integration.

c
Click Next.
a
For most WebLogic integrations, type or select the absolute path to the WebLogic Home directory. WebLogic Home is the installation directory of a particular WebLogic version.
If you are integrating using startWebLogic as the startup method, type or select the absolute path to the Domain Home. Domain Home is the directory containing a WebLogic Domain.
b
Optional — If your application server uses startup scripts with customized names, click the arrow beside Other Options to open a list of script paths and names. Type the custom names in the appropriate boxes.
d
Click Next.
Click Next.
Click New log configuration. The New Log Configuration dialog box opens.
TIP: If you are uncertain about how to adjust these settings, click Help for an overview of log targets and their purposes. For details, see Creating or editing logging properties .
Click Next.
a
b
Click Next.
b
Click Finish.

The agent starts collecting data after the application server has restarted and the agent is successfully integrated. Use the Application Servers Monitor dashboard to view the application servers status. For more information about the Application Servers Monitor dashboard, see the Foglight for Application Servers User Guide.

 

Integrating with WebSphere

Before you begin remote agent integration with an IBM® WebSphere® application server, first review the following sections:

Next, follow the procedure in Integrating with WebSphere startup scripts , as appropriate for your system.

Understanding what should be instrumented

The following guidelines identify the components in a WebSphere® domain that require instrumentation to ensure that the Nexus can do a full data collection.

For standalone servers:

To collect WebSphere metrics on the average size of an HTTP session, enable Average Size (b) Current in the Show columns list and then restart your WebSphere application server using the
-Dquest.configfilter.httpsessionsize=true command. For more information about show and hide columns, see the Foglight for Application Servers User Guide.

For WebSphere Servers federated in a WebSphere Cell:

Each Node agent must be integrated with the agent, and must remain running during the monitored period. Any interruption in the service of an instrumented nodeagent results in incomplete data collection, and possible false alarms. Individual application servers started by an instrumented Node agent are instrumented automatically.

Running WebSphere with security enabled

Set security levels and define PMI levels before configuring your environment.

If you want to run WebSphere® while J2EE security or Global security is enabled, edit the WebSphere's server.policy file to prevent problems between WebSphere and the Java EE agent.

To edit the server.policy file:

1
Open the server.policy file located in <websphere_home>/properties or in <websphere_profile_home>/properties.
TIP: To understand what metrics Foglight for Java EE Technologies collects, review the agent_collector_<SERVER>.config files for your server type. For example, agent_collector_websphere-6.config. You can access these files from the Application Servers Administration > Java Administration > Advanced Configuration view.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating