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

Manual integration with Tomcat

This section contains instructions for integrating the Java EE agent with a Tomcat Application Server on UNIX® and Windows® operating systems:

The manual integration instructions are OS-specific for the target system:

Integrating with Tomcat on UNIX

The following exceptions are not mutually exclusive. If all exceptions apply to your environment, complete all of the following exceptions.

The catalina.sh script uses six different versions of the startup command line. Sometimes, you must modify all these scripts.
The Java command line includes
-Djava.endorsed.dirs=...<tomcat_home>\bin
The catalina.sh script uses six different versions of the startup command lines. Sometimes, you must modify all these commands.
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.
1
2
Complete a Generic installation only on Windows, as described in Creating a Generic Installation for Manual Java EE Agent Integration .
3
Open the catalina.sh script in a text editor and change the following:
4
Set <integrate.sh> to the name of the integration task you created in step 2. For example: integrate-Generic_installation_only_on_UNIX_Install_Configs_and_pre-instrument.cmd.
5
Set the QUEST_DEPLOYMENT_DIRECTORY variable to the Deployment Directory specified by the Java EE Integration Agent instance that is activated on this host.
In addition, the log file for the Tomcat Agent contains an INFO message stating that it has connected to the Foglight Management Server.

Integrating with Tomcat on Windows

Follow these instructions to integrate Tomcat with Foglight for Java EE Technologies by modifying your Tomcat startup script.

Review the following exception before you configure your server. If this exception applies to your environment, complete these instructions.

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.
1
Make a copy of the catalina.bat script.
2
Complete a Generic installation only on Windows, as described in Creating a Generic Installation for Manual Java EE Agent Integration .
3
Open the catalina.bat script in a text editor and update the script.
4
Set <integrate.cmd> 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.
In addition, the log file for the Tomcat Agent contains an INFO message stating that it has connected to the Management Server.

Configuring a Tomcat Windows Service that requires manual integration

If you have chosen not to specify the Java home, or you have set the Startup mode to jvm and Java to Use Default, complete the following procedure after an installation-only setup.

1
Complete a Generic installation only on Windows, as described in Creating a Generic Installation for Manual Java EE Agent Integration . Specify the JVM used by the service in the Java_Home box in the setup wizard.
The generic installation creates a bootstrap.jar file and an integrationid that are needed later in this integration procedure.
b
Type ./tomcat#w.exe //ES//<WindowsServiceIDname>.
e
Replace <VERSIONED_SUBDIRECTORY> with the absolute path of the deployment directory and the current agent directory version.
Example of a <VERSIONED_SUBDIRECTORY>:
The Installation Directory is specified in the Java EE Integration Agent Startup Parameters, which you can see in the Edit Properties interface. If the Installation Directory path is specified as a relative path, as it is by default, you may need to examine the agent machine to determine the absolute path.
f
Replace both instances of <INTEGRATIONID> with the integrationid produced in Step 1. The integrationid can be found in the integrate scripts generated by the generic installation, which are placed in the Installation Directory. Locate the scripts corresponding to your generic installation, open the .cmd script, and look for a command similar to the following:
g
Replace <BOOTSTRAP_FILENAME> with the name of the pre-instrumentation .jar filename that was created in step 1. corresponds to the JRE/JDK that the Tomcat service uses. This name can be found in your agent machine bootstrap directory, in the <VERSIONED_SUBDIRECTORY>.
Here is an example where <INTEGRATIONID>, <VERSIONED_SUBDIRECTORY> and <BOOTSTRAP_FILENAME> are updated:
h
Click OK to save the changes to the Windows Service made within tomcat#w.exe.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating