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

Foglight for Java EE Technologies 5.9.13 - Installation Guide

Installing and Configuring Foglight for Java EE Technologies Integrating with JBoss Integrating with Apache Tomcat Integrating with WebLogic Domain Startup Scripts Integrating with WebSphere Integrating with WebSphere Liberty Integrating with Oracle AS Integrating with Spring Boot for Embedded Tomcat 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 Installation Java EE Integration Configuration FAQ and Troubleshooting Manually Integrating Application Server Appendix A: Java EE Application Methods AppendixB: Managing Permissions for the Java EE Integration Agent

Installing a Java EE agent

Before installing the Java EE agent, make sure that the following components are installed and running:

1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Monitoring Agents view, click Setup agents and select Java.

For detailed instructions, see the section applicable to the type of integration you are creating:

Java EE Integration Agent user permissions

Foglight for Java EE Technologies consists of two separate agents, each of which require access to the file system and other resources.

Java EE Integration Agent - run by the same user that is running the Agent Manager process during agent activation.
Java EE Agent - run by the user running the integrated application server.

The required permissions can be supplied at any level appropriate to your organization or IT structure:

Owner/User Permissions — The Agent Manager and the Application Server must be run by the same user. Usually in this case there is no need to set permissions explicitly.
Group Permissions — The Agent Manager user and the Application Server user belong to a common group.
Others Permission — The Agent Manager user is different from the Application Server user and these two users cannot be added to a common group. Because Others permissions include all other users, it is recommended that Owner or Group permissions be used whenever possible.

For more information, see Appendix: Managing Permissions for the Java EE Integration Agent.

Java EE Integration Agent installation directory

The installation directory (DEPLOYMENT_DIRECTORY) is created during the Java EE Integration Agent activation. After the Java EE Integration Agent is activated, all future version updates of Foglight for Java EE Technologies use this directory to store sub-directories containing the latest Java agent libraries, configuration files, and log files. In addition, the installation directory contains the integrate scripts, integrate.cmd, and integrate.sh, that are used to configure your application servers.

The default value for this installation directory is JavaEE. This path is relative to the <FglAM_HOME>\agents\ directory created during the Foglight Agent Manager (FglAM) installation.

For more information about managing installations, see Managing Java EE Agent Installations, Integrations, and Configurations .

Upgrading Java EE Agents and Integration Agents

The Foglight Upgrade Guide provides full instructions for upgrading to the latest version of the cartridge and agents. Read the topic Upgrade Foglight for Java EE Technologies in the Upgrading the Application Monitoring Cartridges section for details.

Depending on the version you are upgrading from, you may also need to upgrade the Nexus. See the Foglight Upgrade Guide for details. .

If you have modified the configuration files and you perform a minor version upgrade (for example from x.y.z to x.y.z+1), your modified files are preserved. The default contents of the configuration files from the new version are overwritten with your changes.

For example, you have version 5.9.3.2 currently installed and you have modified the Nexus recording.config and the Java EE agent instrumentation.config. Upgrading to version 5.9.4 would overwrite the default contents of the 5.9.4 versions of those files with your file contents from 5.9.3.2. All other 5.9.4 configuration files are unchanged, and contain the default contents installed by the 5.9.4 cartridge.

NOTE: Configuration files managed through the Advanced dashboards (for example, nexus/aggregation.config or agent/java/collector/jboss.config) are not automatically migrated. If you have made any modifications to these files, they must be migrated manually, with the assistance of Customer Support where necessary.

In addition, the nexus/compatible-builds.config file is never automatically migrated. If you have any patch build IDs, these must be manually added to the new version’s compatible-builds.config with the assistance of Customer Support.

 

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택