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

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

Integrating with WebLogic Domain Startup Scripts

You can use the Java EE Integration Agent to integrate the Java EE agent with WebLogic domain startup scripts. You must supply a description and the domain home path for the application server with which you want to integrate. If you are integrating with WebLogic running as a Windows Service, you must specify the name of the Windows Service.
 
* 
NOTE: You must have a Windows Service defined before attempting an integration with WebLogic running as a Windows Service.
 
* 
IMPORTANT: If you are integrating with WebLogic 8.1.x, you cannot use the Integration Wizard described in this section. Instead, you must perform a manual integration, as described in “Creating a Generic Installation for Manual Java EE Agent Integration” on page 38.
To integrate with WebLogic on Solaris, Linux, HP-UX, or AIX, or on Windows:
1
On the navigation panel, under Dashboards, click Application Servers > Administration > Application Servers Administration.
2
On the Application Servers Administration dashboard, in the Monitoring Agents section, click Setup agents.
3
In the menu that opens, select Java. The Java - Setup New Application Server Integration wizard opens.
4
On the Setup Options page, select the type of integration. This example describes how to Setup a new application server integration (the default selection).
* 
TIP: For other integration methods, see Reusing a Previous Integration Configuration .
5
On the New Integration — Type page, select the type of Java application server you want to integrate with. In this case, select WebLogic on Solaris, Linux, HP-UX, or AIX, or WebLogic on Windows.
a
The wizard refreshes, providing the option to select the WebLogic application server startup method:
 
Table 1. Startup methods.
Startup Method
Description
Non-Domain startWLS Startup Script
Integrates the startWLS script within a WebLogic installation (WL_HOME/server/bin/startWLS).
Windows Service
Integrates a WebLogic Server or NodeManager Windows Service.
All Non-Domain Scripts
Combines the NodeManager, Managed Server, and startWLS Startup Script tasks into a single integration.
Managed Server Startup Script
Integrates the startManagedWebLogic.sh/.cmd scripts within a WebLogic installation (WL_HOME/common/bin/startManagedWebLogic).
NodeManager Startup Script
Integrates the startNodeNodeManager.sh/.cmd scripts within a WebLogic installation (WL_HOME/server/bin/startNodeManager).
NOTE: By default, all servers managed by the Node Manager are instrumented.
Domain Startup Script
Integrates the startWebLogic.sh/.cmd scripts within a WebLogic Domain (DOMAIN_HOME/bin/startWebLogic).
b
Select a startup method.
c
Click Next.
6
On the New Integration — Details page, provide the details required for integrating with your WebLogic server, including command-line options.
a
For most WebLogic integrations, type or select the absolute path to the WebLogic Home directory. WebLogic Home is the installation directory of a particular WebLogic version.
If you are integrating using startWebLogic as the startup method, type or select the absolute path to the Domain Home. Domain Home is the directory containing a WebLogic Domain.
If you are integrating with WebLogic as a Windows Service, type the name of the Windows service in the Service Name box.
b
Optional — If your application server uses startup scripts with customized names, click the arrow beside Other Options to open a list of script paths and names. Type the custom names in the appropriate boxes.
* 
NOTE: Always use forward slashes to separate directory names, regardless of whether the application server is running on Windows or UNIX.
c
Optional — Click the arrow beside Command Line Options to show the agent and pre-instrumentor option boxes. Use these boxes to provide command-line parameters for the agent or pre-instrumentor.
•
To add agent options, type them in the Agent Options box.
* 
NOTE: If you need to add more than one option to the Agent Options, separate them with spaces. Do not use quotes.
•
To add pre-instrumentation options, type them in the pre-instrumentor Options box.
To set pre-instrumentor options specific to the JVM you are running: type the desired VM options, separated by spaces, in the pre-instrumentor Options box.
For example, to set the memory limit for the pre-instrumentor to 256 MB, type the following: ‑Xmx256m
* 
NOTE: If you need to add more than one option to the pre-instrumentor Options, separate them with spaces. Do not use quotes.
* 
TIP: For information about pre-instrumentation, see Creating a Generic Installation for Manual Java EE Agent Integration .
d
Click Next.
7
On the Nexus Connection page, select or create the connection that the agent should use to locate and communicate with a Nexus.
* 
TIP: For more information about the Nexus, see Understanding the Nexus and Agent-Nexus Connections .
If you are using the default Nexus on the embedded Agent Manager, or if you have created a single remote Nexus, a default Nexus Connection is created and pre-selected for you.
Otherwise, you must select or define at least one Nexus connection. For more information, see Creating or Editing Agent-Nexus Connection Settings.
Click Next.
8
On the Logging page, select or create a logging configuration to control how logs are written, including retention policies and rollovers.
•
Select an existing log configuration from the list. The default log provides a basic log configuration that you can use to get started.
•
Click New log configuration. The New Log Configuration dialog box opens.
* 
TIP: If you are uncertain about how to adjust these settings, click Help for an overview of log targets and their purposes. For details, see Creating or Editing Logging Properties .
Click Next.
9
On the Integration Hosts page, select the host where WebLogic is installed. By default, only eligible hosts (that is, hosts that have an active Foglight Agent Manager of a compatible version installed and running) are listed.
Select one or more hosts and click Next.
10
On the Agent Configuration page, select the configuration that the agent will use. This agent configuration defines the requests to monitor and collect details.
* 
TIP: You can create new agent configurations or edit existing ones from the Java Administration dashboard. For more information, see Managing Java EE Agent Configurations.
Select a configuration and click Next.
11
On the Installation Directory page, define the location for the directory that contains all installation components and log files.
a
To accept the default directory, leave the Directory name box blank.
* 
NOTE: If you have previously configured the host for agent installation, the existing installation directory is used.
To specify a custom directory, type a path in the Directory name box.
b
Click Next.
12
On the Review page, verify the details of the integration.
a
By default, the instrumentation script is assigned a name based on the integration type. For example: WebLogic on Windows: startWebLogic.
If you want to customize this name, type the new value in the Name box.
b
Click Finish.
The Application Servers Administration dashboard refreshes, and the integration task appears in the Task History list, where you can monitor its progress.
13
Restart your application server.
The agent starts collecting data after the application server has restarted and the agent is successfully integrated. Use the Application Servers Monitor dashboard to view the application servers status. For more information about the Application Servers Monitor dashboard, see the Monitoring Application Servers User and Reference Guide.
 

Integrating with WebSphere

Before you begin remote agent integration with an IBM WebSphere application server, first review the following sections:
•
Understanding What Should Be Instrumented
•
Setting the PMI Levels on WebSphere 6.x and 7.x
•
Running WebSphere with Security Enabled
Next, follow the procedure in Integrating with WebSphere Startup Scripts , as appropriate for your system.

Understanding What Should Be Instrumented

Before you begin remote agent integration with an IBM WebSphere application server, first review the following sections:
•
Understanding What Should Be Instrumented
•
Setting the PMI Levels on WebSphere 6.x and 7.x
•
Running WebSphere with Security Enabled
Next, follow the procedure in Integrating with WebSphere Startup Scripts , as appropriate for your system.

Understanding What Should Be Instrumented

The following guidelines identify the components in a WebSphere domain that require instrumentation to ensure full data collection is completed by the Nexus.
For standalone servers:
•
Each standalone server process must be integrated and running.
•
To collect WebSphere metrics on the average size of an HTTP session, you must enable Average Size (b) Current in the Show columns list and then restart your WebSphere application server using the
-Dquest.configfilter.httpsessionsize=true command. For more information about show/hide columns, see the Monitoring Application Servers User and Reference Guide.
•
WebSphere version 6.x and 7.x standalone servers must be integrated by their server startup scripts, or by individual Windows server processes.
* 
NOTE: Standalone servers started solely by an instrumented Admin agent do not need to be integrated individually. However, if a standalone server is started by other means (startup script, or Windows Service), then integrating by these methods is required.
•
WebSphere version 7.x standalone servers registered with a WebSphere 7.x Admin agent possess an additional integration option: integrating the Admin agent process instead of individual registered servers. Any standalone servers launched by an instrumented Admin agent are also instrumented. However, the Admin agent is not required for monitoring of any standalone servers it may have started, and it may be shut down once all startup activities have been completed. To manually integrate a WebSphere version 7.x Admin agent, see Manually Integrating IBM WebSphere Application Server .
For WebSphere Servers federated in a WebSphere Cell:
•
The Domain Manager of each WebSphere Cell must be integrated for complete cell monitoring, and must remain running for the duration of the monitored period. Any interruption in the service of an instrumented domain manager results in incomplete Nexus data collection, and possible false alarms.
•
Each Node agent must be integrated with the agent, and must remain running for the duration of the monitored period. Any interruption in the service of an instrumented nodeagent results in incomplete data collection, and possible false alarms. Individual application servers started by an instrumented Node agent are instrumented automatically.
•
No integration is required for individual servers. Attempts to start an individual server using a startup script fail, as WebSphere requires you to send the start command by using the server’s node 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 Java EE Integration Agent, 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.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级