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

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

Creating New WebSphere 6.x and 7.x Services

If you are starting your servers, Node agents, or WebSphere Deployment Managers as a service, you need to create a new Windows Service to use the Java EE agent instrumentation. Refer to the IBM documentation for instructions on creating/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 new Windows Service to be integrated with the Java EE agent, provide an additional 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

Modifying the WebSphere 6.x and 7.x Startup Scripts

Use the steps in this section to modify the WebSphere 6.x and 7.x startup scripts.
* 
NOTE: The following procedures are not required if you are starting your servers, Node agent, or Deployment Manager using Windows services.
Before You Begin
Review the exceptions listed below 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 256 MB, specify the following:
Windows:
QUEST_PREINST_OPTS=-Xms256m -Xmx256m
Unix:
QUEST_PREINST_OPTS=”-Xms256m -Xmx256m”
Modifying WebSphere 6.x or 7.x Startup Scripts
Complete the following steps to modify a WebSphere 6.x and 7.x startup script.
To modify the WebSphere 6.x or 7.x startup scripts:
1
Locate your profile-specific startServer, startNode, or startManager script. Save a backup copy before continuing.
2
Open your profile-specific startServer, startNode, or startManager script. Before the call to the WebSphere Installation startServer, startNode, or startManager script, add the following environment variable as appropriate:
Windows:
a
In startServer add:
set QUEST_JAVA_ENV_OPTS=WEBSPHERE:SERVER
b
In startNode add:
set QUEST_JAVA_ENV_OPTS=WEBSPHERE:NODEAGENT
c
In startManager add:
set QUEST_JAVA_ENV_OPTS=WEBSPHERE:DMGR
Unix:
a
In startServer add:
QUEST_JAVA_ENV_OPTS=WEBSPHERE:SERVER
export QUEST_JAVA_ENV_OPTS
b
In startNode add:
QUEST_JAVA_ENV_OPTS=WEBSPHERE:NODEAGENT
export QUEST_JAVA_ENV_OPTS
c
In startManager add:
QUEST_JAVA_ENV_OPTS=WEBSPHERE:DMGR
export QUEST_JAVA_ENV_OPTS
3
Complete the next procedure, Restarting Modified WebSphere 6.x or 7.x Servers , to restart your application server.

Restarting Modified WebSphere 6.x or 7.x Servers

After you have modified the startup script, you must restart the WebSphere 6.x or 7.x server.
To start the WebSphere 6.x or 7.x modified server:
1
If it is not already running, start the Foglight Management Server.
2
Stop and restart the WebSphere server using the instructions for the server type you modified:
•
If you are using a standalone WebSphere server, stop the server and restart it with the modified script or the new Windows Service.
•
When starting WebSphere 6 servers managed by a WebSphere Deployment Manager, stop the WebSphere node agent and restart the node agent with the modified script or with the new Windows Service. Restart any managed WebSphere Application Server instances after restarting the modified WebSphere node agent.
•
When starting a standalone WebSphere 7 Server managed by a WebSphere Admin Agent, stop the WebSphere Admin Agent and restart the Admin Agent with the modified script or with the new Windows Service. Restart any managed WebSphere Application Server instances after restarting the modified WebSphere Admin Agent.
* 
CAUTION: For any server with a corresponding Windows service:Attempts to start a server by using a startup script may launch a Windows service instead. If the startup script is instrumented with the Foglight for Java EE Technologies, then the resulting WebSphere process will be instrumented as well. Otherwise, the integration properties of the Service are used. This release changes the behavior of services launched as a result of a start script invocation.
* 
CAUTION: Foglight launches a Java EE agent for each instrumented server. When the Java EE agent connects to the Management Server, the Management Server console displays a message to confirm that a Java EE agent has connected. For example: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)The log file for the Java EE agent also contains an INFO message stating that it has connected to the Management Server.
 
 
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택