Foglight for Java EE Technologies 5.9.11

Complete a Generic installation only on Windows, as described in Creating a Generic Installation for Manual Java EE Agent Integration . Specify the JVM used by the service in the Java_Home box in the setup wizard.

The generic installation creates a bootstrap.jar file and an integrationid that are needed later in this integration procedure.

Set the following Java options:

In a command prompt, open the Tomcat installation bin directory.

Type ./tomcat#w.exe //ES//<WindowsServiceIDname>.

For example:

./tomcat5w.exe //ES//Tomcat_Toronto_Host3.

In the Apache Tomcat Properties dialog box, open the Java tab.

Add the following options to the end of the list of existing Java Options:

-Dquest.debug=0

-Dquest.integrationid=<INTEGRATIONID>

-Xbootclasspath/p:<VERSIONED_SUBDIRECTORY>\bootstrap\<INTEGRATIONID>\<BOOTSTRAP_FILENAME>.jar

-javaagent:<VERSIONED_SUBDIRECTORY>\lib\performasure-agent.jar

Replace <VERSIONED_SUBDIRECTORY> with the absolute path of the deployment directory and the current agent directory version.

Example of a <VERSIONED_SUBDIRECTORY>:

C:\Quest Software Inc.\Foglight for Java EE Technologies_Agent_Manager\agents\JavaEE\5.7.0-570-20101210-1400

The Installation Directory is specified in the Java EE Integration Agent Startup Parameters, which you can see in the Edit Properties interface. If the Installation Directory path is specified as a relative path, as it is by default, you may need to examine the agent machine to determine the absolute path.


	TIP: The current version of the subdirectory is indicated within the jee_builds.properties file. It is the value of the set.QUEST_AGENT_HOME parameter.This value already includes the installation directory. The version of the subdirectory portion is the last directory specified in the value.

Replace both instances of <INTEGRATIONID> with the integrationid produced in Step 1. The integrationid can be found in the integrate scripts generated by the generic installation, which are placed in the Installation Directory. Locate the scripts corresponding to your generic installation, open the .cmd script, and look for a command similar to the following:

@set QUEST_INTEGRATIONID=YourCustomizedId

where the word after the '=' is your integrationid. In this example, the integrationid is YourCustomizedId.

Replace <BOOTSTRAP_FILENAME> with the name of the pre-instrumentation .jar filename that was created in step 1. corresponds to the JRE/JDK that the Tomcat service uses. This name can be found in your agent machine bootstrap directory, in the <VERSIONED_SUBDIRECTORY>.

Here is an example where <INTEGRATIONID>, <VERSIONED_SUBDIRECTORY> and <BOOTSTRAP_FILENAME> are updated:

-Dquest.debug=0

-Dquest.integrationid=KEo3JDr6ALaybTu

-Xbootclasspath/p:C:\Quest_Software\Foglight_Agent_Manager\agents\JavaEE\5.9.3-20130815-0923\bootstrap\KEo3JDr6ALaybTu\C--Program_Files_-x86--Java-jdk1.6.0_20.jar

-javaagent:C:\Quest_Software\Foglight_Agent_Manager\agents\JavaEE\5.9.3-20130815-0923\lib\performasure-agent.jar

Click OK to save the changes to the Windows Service made within tomcat#w.exe.

Ensure that the Foglight Management Server is started and the Java EE agent is activated.

For the changes to take effect, stop and restart the Tomcat Windows Service.


	IMPORTANT: If the JVM that the Tomcat Windows Service uses is changed (for example, by installing an updated version of the JRE or JDK on the host), this manual integration must be done again. If Foglight for Java EE Technologies is updated on the Tomcat host, this manual integration must be done again to take advantage of the new release.

Manual integration with WebLogic

This section contains instructions for integrating the Java EE agent with a WebLogic® Server. You must modify your WebLogic startup script by adding lines to set the variables that the Java EE agent requires.


	NOTE: WebLogic versions earlier than 9.x do not provide Query Cache metrics for EJBs.

Before you begin

Review the following exceptions for variations before configuring your server.

Exception list

The following exceptions are not mutually exclusive. If all exceptions apply to your environment, complete all of the following instructions:

•

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 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:

Make a backup copy of your WebLogic Server startup script before proceeding with the steps below.

Complete the Generic installation only on Windows, as described in Creating a Generic Installation for Manual Java EE Agent Integration .

Copy the following block of code to your WebLogic Server startup script. Insert the block just before the WebLogic startup line.


	NOTE: For WebLogic 8.1.x, 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

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.

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. IMPORTANT: The Anonymous Admin Lookup Enabled option needs be selected in WebLogic 8.1.x, to avoid the javax.naming.NoPermissionException occured during the WebLogic integration.