Chat now with support
Chat with Support

Foglight for Java EE Technologies 5.9.10 - 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 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

Prerequisites:
Before installing the Java EE agent, make sure that the following components are installed and running:
1
An Agent Manager installed and running on the target host.
2
The Nexus is installed and the Nexus agent is running.
To install an agent:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
The Application Servers Administration dashboard opens.
2
On the Monitoring Agents view, click Setup agents and select Java.
The Java — Setup New Application Server Integration wizard opens.
3
Select whether you want to set up a new application server integration configuration, or reuse an existing one, and click Next.
For information about reusing an integration configuration, see Reusing an integration configuration .
For new integrations, continue with the next step.
4
Select the type of integration you want to perform and click Next.
Follow the on-screen instructions to configure the integration and create the agent.
Integrating with application servers
For detailed instructions, see the section applicable to the type of integration you are creating:
•
Integrating with JBoss
•
Integrating with Apache Tomcat
•
Integrating with WebLogic Domain Startup Scripts
•
Integrating with WebSphere
•
Integrating with Oracle AS
•
Creating a Generic Installation for Manual Java EE Agent Integration
•
Reusing an integration configuration
 
* 
NOTE: Some older versions of Java EE agents can still connect to this version of Foglight for Java EE Technologies. See the Foglight for Java EE Technologies Release Notes for details.

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.
 
* 
NOTE: You can specify a custom location during installation. If you do not specify a fully qualified path, it is relative to the <FglAM_HOME>\agents directory.
 
* 
IMPORTANT: Do not use the JavaEE Installation directory anywhere in your application server startup scripts. This directory is used by the Java EE Integration Agent to maintain a copy of the original agent files/libraries.
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. .
Configuration migration during upgrades
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.
 
* 
IMPORTANT: No automatic migration occurs during an upgrade to the next major version (for example, from 5.8.x to 5.9.x), however the migration from 5.9.x to 5.10.0 is supported.
 
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating