Chat now with support
Chat with Support

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

Manually Integrating Oracle WebLogic Application Server and WebLogic Express

This section contains instructions for integrating the Java EE agent with a WebLogic Server version 8.1, 9.0, 9.1, 9.2, 10.0, or 10.3 You must modify your WebLogic startup script by adding lines to set the variables required by the Java EE agent.
* 
NOTE: WebLogic versions earlier than 9.x do not provide Query Cache metrics for EJBs.

Before You Begin

Review the exceptions listed below for variations before configuring your server.
Exception List
The following exceptions are not mutually exclusive. If all apply to your environment, you must complete all exceptions listed below.
•
If you have spaces in the Unix QUEST_DEPLOYMENT_DIRECTORY path:
Edit the startup script and insert the following code in the Java command-line before {SERVER_CLASS} or weblogic.Server:
•
WebLogic 9.x and 10.x:
"${PERFORMASURE_BOOTSTRAP}" "${PERFORMASURE_JAVA5}" ${PERFORMASURE_OPTIONS}
•
WebLogic 8.x:
"${PERFORMASURE_BOOTSTRAP}" ${PERFORMASURE_OPTIONS}
•
If you are using JRockit, and any one of the following conditions is true:
•
You are running the default WebLogic 8.1 startup scripts on any platform
•
You are running the default WebLogic 9.x or 10.x startup scripts on a Unix platform
•
You are using a customized startup script that does not place the WebLogic main class name into an environment variable
•
You are using a customized startup script that places the WebLogic main class into an environment variable other than SERVER_CLASS, but you have not provided the name of that environment variable to the integrate integration script (which is done by setting the additional environment variable APPSERVER_CLASS_VAR to the name of your custom environment variable.
For example, set APPSERVER_CLASS_VAR=WLS_MAIN_CLASS, if your custom mainclass variable is WLS_MAIN_CLASS).
Edit the startup script and insert the following code on the Java command line before weblogic.Server:
Unix:
${PERFORMASURE_BOOTAGENT}
Windows:
%PERFORMASURE_BOOTAGENT%

Manually Configuring a WebLogic Server or a WebLogic Express Startup 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
Perform a Generic installation only on Windows, as described in Creating 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 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 launched using the new script.
8
Restart the WebLogic Server using the new script.
A Java EE agent is launched 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>

Manually Integrating 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 versions 6.1, 6.1 ND, 7.0 and 7.0 ND. You either need to create new 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 are started by a Node agent, you must configure integration with the Node agent.
If you want to collect cell-wide configuration information and application server states, you must 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
Configuring the WebSphere 6.x and 7.x environment .
2
Creating New 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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating