Chat now with support
Chat with Support

Foglight for Java EE Technologies 5.9.12 - 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

Manual integration with WebLogic

This section contains instructions for integrating the Java EE agent with a WebLogic® Server. You must modify your WebLogic startup script by adding lines to set the variables that the Java EE agent requires.

Manually configuring WebLogic for integration

Use the steps in this section to manually configure a WebLogic® Server or a WebLogic Express Startup for integration with the Java EE agent.

To configure WebLogic server or WebLogic Express startup:
2
Complete the Generic installation only on Windows, as described in Creating a Generic Installation for Manual Java EE Agent Integration .
UNIX®:
4
Set <integrate.cmd/sh> to the name of the integration task you created in step 2. For example: integrate-Generic_installation_only_on_Windows_Install_Configs_and_pre-instrument.cmd.
5
Set the QUEST_DEPLOYMENT_DIRECTORY variable to the Installation Directory specified by the Java EE Integration Agent instance activated on this host. This agent instance was created in step 2.

Manual integration with IBM WebSphere Application Server

IMPORTANT: Review the section Understanding what should be instrumented before you begin manually integrating WebSphere®.

This section contains instructions for integrating the Java EE agent with WebSphere Server. You either need to create Windows® services that start instrumented servers, Admin agents, Node agents, and WebSphere Deployment Managers; or modify the startup scripts.

If you want to instrument the servers that a Node agent starts, configure integration with the Node agent.

If you want to collect cell-wide configuration information and application server states, configure the integration with the WebSphere Deployment Manager.

Using Foglight for Java EE Technologies with your WebSphere servers requires three steps:

Other topics include:

WebSphere environments

WebSphere® are configured to use profiles. Therefore, configuration with the Java EE agent involves two steps. The first is to edit to the global setupCmdLine script. These changes only take effect if the environment variable QUEST_DEPLOYMENT_DIRECTORY has been set in your user profile setupCmdLine script. All other profiles ignore the code in the global setupCmdLine script.

Review the following exceptions before you configure your server.

Set the environment variable QUEST_PREINST_OPTS with the desired VM options. The environment variable QUEST_PREINST_OPTS is passed to the Java EE agent pre-instrumentor script.
UNIX®:

Complete the following steps to configure a WebSphere® environment.

By default, this script can be found in the <websphere_home>/bin/ directory.
3
Open the global setupCmdLine script in a text editor and make the following modifications:
Windows® Only — Add the following code to the end of the script:
UNIX® — Add the following code to the end of the script:
if [ -f "$QUEST_DEPLOYMENT_DIRECTORY/<integrate.sh>" -a -n "$QUEST_JAVA_ENV_OPTS" ];
then
. "$QUEST_DEPLOYMENT_DIRECTORY/
<integrate.sh>"
else
echo Java EE agent is NOT enabled
fi
4
Set <integrate.cmd/sh> to the name of the integration task you created in step 2. For example: integrate-Generic_installation_only_on_Windows_Install_Configs_and_pre-instrument.cmd.
5
Save your modified setupCmdLine script file.
6
Locate your profile setupCmdLine script. The default installation places it in WAS_HOME/profiles/<profile_name>/bin. Set the QUEST_DEPLOYMENT_DIRECTORY at the end of the profile script to the Installation directory defined in step 2 to enable monitoring for that profile.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating