Chatta subito con l'assistenza
Chat con il supporto

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

Manually Integrating Application Server

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 section that are specific to the application server you want to integrate with.
•
JBoss remote agent integration from the command-line
•
Manual integration with Wildfly, JBoss AS and EAP
•
Manual integration with Tomcat
•
Manual integration with WebLogic
•
Manual integration with 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.

Manual integration with Wildfly, JBoss AS and EAP

This section contains instructions for manually integrating the Java EE agent with a Wildfly, JBoss® Application Server (AS) or Enterprise Application Platform (EAP).
* 
IMPORTANT: Foglight for Java EE Technologies version 5.9.x is the last major release that supports JBoss AS (all versions), 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 exceptions apply to your environment, 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 integrating the Wildfly and 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 preinstrumentor 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 preinstrumentor to 256MB, specify the following: QUEST_PREINST_OPTS=-Xmx256m
* 
IMPORTANT: Use a single space to separate multiple options. Do not use quotes.

Manually integrating the Wildfly and JBoss application server

Use the following procedure to manually configure the Wildfly and JBoss® server startup script for integration with the Java EE agent.
To manually configure the Wildfly and JBoss application server:
1
Make a backup copy of your original server startup script.
Standalone mode:
JBoss AS 6.x and earlier: <jboss-home>\bin\run.bat (Windows®) or <jboss-home>/bin/run.sh (UNIX®)
Wildfly, JBoss EAP, and JBoss AS 7.1.x: <jboss-home>\bin\standalone.bat (Windows®) or <jboss-home>/bin/standalone.sh (UNIX®)
Domain mode:
Wildfly, JBoss AS, and JBoss EAP: <jboss-home>\bin\domain.bat (Windows®) or <jboss-home>/bin/domain.sh (UNIX®)
2
Complete 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 server startup script. Insert the block just before the Java command line that starts the Wildfly or JBoss application server, but after any commands that set or modify the JAVA_HOME and JAVA_OPTS environment variables.
Windows (standalone mode):
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
 
Windows (domain mode):
set QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation directory *
set QUEST_JAVA_ENV_OPTS=JBOSS:DOMAIN
call "%QUEST_DEPLOYMENT_DIRECTORY:"=%\<integrate.cmd>" %*
if ERRORLEVEL 1 echo Java EE agent NOT enabled
 
UNIX (standalone mode):
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
 
UNIX (domain mode):
QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation directory *
if [ -f "$QUEST_DEPLOYMENT_DIRECTORY/<integrate.sh>" ]
then
QUEST_JAVA_ENV_OPTS=JBOSS:DOMAIN
. "$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 that your environment does not meet any of the exceptions in the Exception list and then save the new script.
7
If it is not already running, start the Management Server. The instrumented Wildfly or JBoss application server attempts to connect to Foglight for Java EE Technologies when started using the new script.
8
Start the Wildfly or JBoss application server using the new script.
Foglight for Java EE Technologies starts 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 , for example:
<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.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione