지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Java EE Technologies 5.9.7.5 - Installation Guide

Installing and Configuring Foglight for Java EE Technologies Integrating with JBoss Integrating with Tomcat Integrating with WebLogic Domain Startup Scripts Integrating with WebSphere Integrating with Oracle AS 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 Installations Foglight for Java EE Integration Configuration FAQ and Troubleshooting Performing Manual Application Server Integrations Appendix: Managing Permissions for the Java EE Integration Agent Appendix: Foglight for Java EE Application Methods

Performing Manual Application Server Integrations

You can use the application server agent setup wizard to configure and integrate the Java EE agent and the Java EE Integration Agent to work with most application servers. If for any reason you need to manually integrate, follow the instructions in this chapter that are specific to the application server you want to integrate with.
•
JBoss Remote Agent Integration from the Command-line
•
Manually Integrating with Tomcat
•
Manually Integrating Oracle WebLogic Application Server and WebLogic Express
•
Manually Integrating IBM WebSphere Application Server

JBoss Remote Agent Integration from the Command-line

As an alternative to configuring agent integration through the agent setup wizard in the Foglight browser interface, you can use the fglcmd command-line scripts that are available on the Management Server.
If you are using the command-line interface and
•
the JBoss .jar files are in a lib/endorsed directory: add the ‑Dquest.agent.instrument.bootstrap=true option to the QuestAgentOpts parameter
•
you want to specify preinstrumentor options: add them to the QuestPreinstOpts parameter
* 
NOTE: Use a single space to separate options on the command-line. Do not use quotes.

Manually Integrating JBoss AS and EAP

This section contains instructions for manually integrating the Java EE agent with a JBoss Application Server version 4.2.[0-3], 5.0.[0-1], 5.1.0, 6.0.0, and 6.1.0, or Enterprise Application Platform (EAP) version 4.3, 5.0, 5.1, 6.0.0, and 6.1.0.
* 
IMPORTANT: Foglight for Java EE Technologies version 5.9.x is the last major release that supports JBoss AS 4.2 and 5.0, and JBoss EAP 4.3. Support for these versions of JBoss will be discontinued after this release.
* 
IMPORTANT: Review the following exceptions before configuring your server.
Exception List
The following exceptions are not mutually exclusive. If all apply to your environment, you must complete the exception configurations for all of them.
•
If JBoss JARs are moved to a lib/endorsed directory:
A system property must be added to the application server command-line to properly instrument classes. Add the following line before the code block documented in Step 3 of Manually Configuring the JBoss Application Server .
Windows:
set PERFORMASURE_OPTIONS=-Dquest.agent.instrument.bootstrap=true
Unix:
PERFORMASURE_OPTIONS=-Dquest.agent.instrument.bootstrap=true
•
If you want to set pre-instrumentor options specific to the JVM you are running:
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.
For example, to set the memory limit for the pre-instrumentor to 256 MB, specify the following: QUEST_PREINST_OPTS=-Xmx256m
* 
IMPORTANT: Use a single space to separate multiple options. Do not use quotes.

Manually Configuring the JBoss Application Server

Use the following procedure to manually configure the JBoss server startup script for integration with the Java EE agent.
To manually configure the JBoss application server:
1
Make a backup copy of your original JBoss server startup script <jboss-home>\bin\run.bat (Windows) or <jboss-home>/bin/run.sh (Unix).
2
Perform a Generic installation only on Windows or a Generic installation only on Solaris, Linux, HP-UX, or AIX, as described in Creating a Generic Installation for Manual Java EE Agent Integration .
3
Copy the following block of code into your JBoss server startup script. Insert the block just before the Java command line that starts the JBoss application server, but after any commands that set or modify the JAVA_HOME and JAVA_OPTS environment variables.
Windows:
set QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation directory *
set QUEST_JAVA_ENV_OPTS=JBOSS:SERVER:JAVA_OPTS
call "%QUEST_DEPLOYMENT_DIRECTORY:"=%\<integrate.cmd>" %*
if ERRORLEVEL 1 echo Java EE agent NOT enabled
Unix:
QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation directory *
if [ -f "$QUEST_DEPLOYMENT_DIRECTORY/<integrate.sh>" ]
then
QUEST_JAVA_ENV_OPTS=JBOSS:SERVER:JAVA_OPTS
. "$QUEST_DEPLOYMENT_DIRECTORY/<integrate.sh>"
else
echo Java EE agent 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
Set the QUEST_DEPLOYMENT_DIRECTORY variable to the Installation Directory specified by the Java EE Integration Agent instance activated on this host. In Unix, quote this path if it contains spaces.
6
Ensure your environment does not meet any of the exceptions in the Exception List at the beginning of this section, then save the new script.
7
If it is not already running, start the Management Server. The instrumented JBoss application server attempts to connect to Foglight for Java EE Technologies when launched using the new script.
8
Start the JBoss application server using the new script.
Foglight for Java EE Technologies launches a Java EE agent for each instrumented server. When the Java EE agent connects to the Management Server, the Management Server console confirms that a Java EE agent has connected by displaying a message such as:
<timestamp> INFO Accepted connection from agent “<agent name> (JBoss)”, (JBoss <version>) on host: <hostname>
In addition, the log file for the Java EE agent contains an INFO message stating that it has connected to the Management Server.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택