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

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

Installing and Configuring Foglight for Java EE Technologies

Welcome to the Managing Java EE Systems: Installation Guide. This guide provides installation and configuration instructions for Foglight for Java EE Technologies and the instrumented agents for Java EE.
This guide is intended for any user who wants to install and configure Foglight for Java EE Technologies.
Foglight for Java EE Technologies contains a Java EE Integration Agent and a Java EE Agent. The Java EE Integration Agent is responsible for transferring the files needed by the Java EE Agent to the remote application server hosts in your monitored environment, integrating the Java EE Agent with application servers, and aiding in the configuration of the Java EE Agent. The Java EE Agent is responsible for collecting performance and monitoring data from the application servers.
Before installing Foglight for Java EE Technologies, ensure that you have the correct environment as outlined in the Foglight for Java EE Technologies Release Notes and the Managing Java Systems: Supported Platforms and Servers Guide. Also ensure that you have reviewed the information in Before You Begin the Installation Process.
 
* 
IMPORTANT: To install or upgrade Foglight for Java EE Technologies, you must belong to a user group that has Foglight Security role permissions. For more information about assigning user permissions, see the Foglight Administration and Configuration Guide.

Before You Begin the Installation Process

If you intend to use the default Nexus running in the embedded Foglight for Java EE Technologies Agent Manager, you must adjust the Agent Manager disk cache settings before installing and configuring Foglight for Java EE Technologies. The default Nexus is created as part of the installation process.

Adjusting the Agent Manager Settings for the Nexus

The Agent Manager accumulates messages that are destined to be sent either upstream or downstream in queues between connections. This prevents messages from getting lost in the event of a disconnection.
Increase the Agent Manager disk cache size to ensure that data submissions from the Java agent are not discarded. See the documentation in the fglam.config.xml file for detailed descriptions of the options.
 
* 
NOTE: This procedure is recommended for all installations.
To adjust the Agent Manager settings for use with the Nexus:
1
Navigate to your Agent Manager config folder. For example: C:\Quest_Software\Foglight_Agent_Manager\state\default\config.
2
Open the vm.config file in an editor.
 
* 
IMPORTANT: In Agent Managers version 5.6.10 and later, this file is named baseline.jvmargs.config.
3
Uncomment and set the following setting to:
vmparameter.0 = “-Xmx1024m”;
4
Save and close the .config file.
5
In the same config directory, open the fglam.config.xml file in an editor.
6
Edit the config:queue-sizes and max-disk-space settings as follows:
<config:queue-sizes>
    <config:upstream max-queue-size="-1" max-disk-space="100000" max-batch-size="-1"/>
    <config:upstream-verified max-queue-size="-1" max-disk-space="100000" max-batch-size="-1"/>
    <config:downstream max-queue-size="-1" max-disk-space="1024" max-batch-size="500"/>
</config:queue-sizes>
This sets the max-disk-cache size to 100 MB for the upstream and upstream-verified queues (normal and verified submissions).
7
Save and close the fglam.config.xml file.
8
Restart the Agent Manager.
If the Nexus is running in a non-embedded Agent Manager, the Agent Manager service must be restarted.
If the Nexus is running in the embedded Agent Manager (for example, if you are using the default Nexus), do one of the following:
•
Restart the Management Server.
or
•
Go to <server>/jmx-console (e.g. http://yourhost:8080/jmx-console/) and click: service=EmbeddedFglAm.
Invoke the Stop() operation, and then invoke the start() operation.
If you still find warnings in the Agent Manager log about the disk cache being too small, increase the max-disk-space values for the upstream and upstream-verified queues.
After you have adjusted the settings and restarted the Agent Manager, continue with Installing and Configuring Foglight for Java EE Technologies.

Installing Foglight for Java EE Technologies

Foglight for Java EE Technologies is distributed in a .car file, ApplicationServers-Java-<version>.car. Installing the cartridge file on the Management Server adds the capabilities for monitoring Java EE systems to your Foglight for Java EE Technologies environment.
The installation process is common to all Foglight for Java EE Technologies cartridges. For instructions for installing and enabling the cartridge, see “Installing Foglight for Java EE Technologies cartridges” in the Foglight for Java EE Technologies Administration and Configuration Help.
 
* 
NOTE: The cartridge file installation requires approximately 50 MB of additional hard drive disk space on the Foglight Management Server.
To view the Cartridge for Java EE Technologies:
•
On the navigation panel, under Dashboards, click Administration > Cartridges > Cartridge Inventory. Search for “Java”.
셀프 서비스 도구
지식 기반
공지 및 알림
제품 지원
소프트웨어 다운로드
기술 설명서
사용자 포럼
비디오 자습서
RSS 피드
문의처
라이센싱 지원가져오기
기술 지원
모두 보기
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택