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.
Use the steps in this section to manually configure a WebLogic® Server or a WebLogic Express Startup for integration with the Java EE agent.
2 |
Complete the 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. |
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: 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, Admin agents, Node agents, and WebSphere Deployment Managers; or modify the startup scripts.
Using Foglight for Java EE Technologies with your WebSphere servers requires three steps:
WebSphere® 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.
Review the following exceptions before you configure your server.
Complete the following steps to configure a WebSphere® environment.
2 |
Create a Generic Installation Only integration on the host. For more information, see Creating a Generic Installation for Manual Java EE Agent Integration. |
3 |
Open the global setupCmdLine script in a text editor and make the following modifications: |
• |
• |
UNIX® — Add the following code to the end of the script: |
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. |
7 |
Save the changes to your profile-specific setupCmdLine script. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center