立即与支持人员聊天
与支持团队交流

Foglight for Java EE Technologies 5.9.9 - Installation Guide

Install and Configure Foglight for Java EE Technologies Integrate with JBoss Integrate with Apache Tomcat Integrate with WebLogic Domain Startup Scripts Integrate with WebSphere Integrate with Oracle AS Create a Generic Installation for Manual Java EE Agent Integration Manage Java EE Agent Installations, Integrations, and Configurations Managing Java EE Agent Configurations Java EE Installation Management Java EE Integration Configuration FAQ and Troubleshooting Manual Application Server Integrations AppendixB: Managing Permissions for the Java EE Integration Agent Appendix A: Java EE Application Methods

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:
1
Make a backup copy of your WebLogic Server startup script before proceeding with the steps below.
2
Complete the Generic installation only on Windows, as described in Create a Generic Installation for Manual Java EE Agent Integration .
3
Copy the following block of code to your WebLogic Server startup script. Insert the block just before the WebLogic startup line.
* 
NOTE: For WebLogic 9 and 10, modify the startup script in <domain_home>/bin.
Windows®:
@rem set QUEST_PREINST_OPTS=* OPTIONAL pre-instrumentor Options *
set QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation Directory *
set QUEST_JAVA_ENV_OPTS=WEBLOGIC:SERVER
call "%QUEST_DEPLOYMENT_DIRECTORY:"=%\<integrate.cmd>" || (
echo Java EE agent not enabled )
UNIX®:
# QUEST_PREINST_OPTS=* OPTIONAL pre-instrumentor Options *
# export QUEST_PREINST_OPTS
QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation Directory *
if [ -f "$QUEST_DEPLOYMENT_DIRECTORY/<integrate.sh>" ]
then
QUEST_JAVA_ENV_OPTS=WEBLOGIC:SERVER
. "$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. This agent instance was created in step 2.
* 
IMPORTANT: In Unix, quote this path if it contains spaces.
6
Before saving this new startup script, ensure that your environment does not meet any of the exceptions listed at the beginning of this section, then save the new script.
7
If it is not already running, start the Management Server. The instrumented WebLogic Server attempts to connect to it when starting using the new script.
8
Restart the WebLogic Server using the new script.
A Java EE agent is started for each instrumented server. When the Java EE agent connects to the Management Server, the Management Server displays a message in the console to confirm that a Java EE agent has connected. The message is similar to the following:
INFO agent licenses assigned; Type: websphere, Host: <hostName>, CPUs: 1; CPU licenses in use:
INFO Accepted DCE connection from agent "server1 (WebSphere)" (WebSphere 6.X)
In addition, the log file for the Java EE agent contains an INFO message stating that it has connected to the Management Server:
<timestamp> INFO Accepted connection from agent “<agent name> (WebLogic)”, (WebLogic <version>) on host: <hostname>

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, Domain agent (version 7.x only), 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 6.x and 7.x servers requires three steps:
1
WebSphere 6.x and 7.x environments .
2
Creating WebSphere 6.x and 7.x services .
3
Modifying the WebSphere 6.x and 7.x startup scripts .
Other topics include:
•
Running WebSphere with security enabled
•
Setting the PMI levels on WebSphere 6.x and 7.x
* 
CAUTION: Before you attempt to integrate WebSphere 6, ensure that the Disable JIT check box is not selected on the Java Virtual Machine page in the WebSphere Administrative Console. Disabling the JIT drastically slows down the server’s startup and operation. Disabling metrics or changing metric sets while you are collecting data is not recommended. If you do so, Foglight may be unable to collect the necessary WebSphere metrics. In addition, if you disable metrics or change metric sets while data collection is in progress, Foglight cannot restore the original set of metrics that you configured.

WebSphere 6.x and 7.x environments

WebSphere® 6.x and 7.x 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.
Before you begin
Review the following exceptions before you configure your server.
Exception list
•
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 used for the pre-instrumentor to 256MB, specify the following:
Windows®:
QUEST_PREINST_OPTS=-Xms256m -Xmx256m
UNIX®:
QUEST_PREINST_OPTS=”-Xms256m -Xmx256m”
Configuring WebSphere 6.x and 7.x environments
Complete the following steps to configure a WebSphere® 6.x and 7.x environment.
To configure a WebSphere 6.x and 7.x environment:
1
Make a backup copy of your original global setupCmdLine script (.bat or .sh).
By default, this script can be found in the <websphere_home>/bin/ directory.
2
Create a Generic Installation Only integration on the host. For more information, see Create a Generic Installation for Manual Java EE Agent Integration.
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:
if %1==-Dquest.agent.websphere.server set QUEST_JAVA_ENV_OPTS=WEBSPHERE:SERVER
if %1==-Dquest.agent.websphere.nodeagent set QUEST_JAVA_ENV_OPTS=WEBSPHERE:NODEAGENT
if %1==-Dquest.agent.websphere.dmgr set QUEST_JAVA_ENV_OPTS=WEBSPHERE:DMGR
Add the following code before the line goto :EOF:
if defined QUEST_DEPLOYMENT_DIRECTORY if defined QUEST_JAVA_ENV_OPTS (
call "%QUEST_DEPLOYMENT_DIRECTORY%\<integrate.cmd>"
if ERRORLEVEL 1 echo Java EE agent NOT enabled
)
•
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.
Windows:
rem Enable Java EE agent monitoring for this profile
set QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation Directory *
Unix:
# Enable Java EE agent monitoring for this profile
QUEST_DEPLOYMENT_DIRECTORY=* SET JavaEE Installation Directory *
export QUEST_DEPLOYMENT_DIRECTORY
7
Save the changes to your profile-specific setupCmdLine script.
8
Restart your application server.

Creating WebSphere 6.x and 7.x services

If you are starting your servers, Node agents, or WebSphere® Deployment Managers as a service, create a Windows® Service to use the Java EE agent instrumentation. See the IBM® documentation for instructions on creating and installing a Windows Service with the WASService.exe tool. You can keep your old Windows Service, but ensure that only one service for a particular WebSphere server, Node agent, or WebSphere Deployment Manager has a startup type of Automatic. All others should be set to Manual or Disabled.
When creating a Windows Service to integrate with the Java EE agent, provide an extra argument to the -startArgs option:
For WebSphere server use:
" -Dquest.agent.websphere.server"
For WebSphere Node agent use:
" -Dquest.agent.websphere.nodeagent"
For WebSphere Deployment Manager use:
" -Dquest.agent.websphere.dmgr"
* 
NOTE: Quotes are required. The space between the first quote and the dash is also required.

A caret (^) character is required at the end of a line (other than the last) to correctly wrap the DOS command on multiple lines. A space is a required before the caret character to ensure proper spacing when copying and pasting the following code blocks.
Examples:
WebSphere Server:
WAS_HOME\bin\WASService.exe -add "BASE server1 - with agent" ^
-servername server1 ^
-profilePath "C:\WebSphere6\profiles\AppSrv01" ^
-startArgs " -Dquest.agent.websphere.server" ^
-startType automatic
WebSphere Node agent:
WAS_HOME\bin\WASService.exe -add "ND nodeagent - with agent" ^
-servername nodeagent ^
-profilePath "C:\WebSphere6\profiles\AppSrv01" ^
-startArgs " -Dquest.agent.websphere.nodeagent" ^
-startType automatic
WebSphere Deployment Manager:
WAS_HOME\bin\WASService.exe -add "ND dmgr - with agent" ^
-servername dmgr ^
-profilePath "C:\WebSphere6\profiles\Dmgr01" ^
-startArgs " -Dquest.agent.websphere.dmgr" ^
-startType automatic
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级