Chat now with support
Chat with Support

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

Integrating with Spring Boot for Embedded Tomcat

You can use the Java EE Integration Agent to prepare the artifacts for the embedded Tomcat, to integrate the Java EE agent with Spring Boot startup scripts on Windows and Linux.

New Integration - Type: Select Generic installation only on Solaris, Linux, HP-UX, or AIX for Linux, or select Generic installation only on Windows for Windows.
New Integration - Details: Type the same Java installation directory to run your Spring Boot application in the Java Home field.
Consider for example you are using the java -jar example-application.jar command to launch your Spring Boot application. Update the original command to the following:
IMPORTANT: During the integration, change the variables inside “<>” to the actual values used in your environment.
NOTE: The value of <Integration ID> is generated during the agent setup. In other words, the <Integration ID> is the value of the QUEST_INTEGRATIONID property in the integration file (either .sh or .cmd file) that is generated after the generic installation and located under the <FGLAM_HOME>\agents\JavaEE\ folder.
Linux: Assume the Java EE agent directory is “/opt/quest/foglightagentmanager/agents/JavaEE/5.9.11-20170410-1146”, the “QUEST_INTEGRATIONID” value is “8tKWIAFGo9xd82p”, and the target Spring Boot application jar is “example-application.jar”. Then update the original command to the following:
Windows: Assume the Java EE agent directory is “C:\Quest\foglightagentmanager\agents\JavaEE\5.9.11-20170410-1146”, the “QUEST_INTEGRATIONID” value is “8tKWIAFGo9xd82p”, and the target Spring Boot application jar is “example-application.jar”. Then update the original command to the following:

 

Creating a Generic Installation for Manual Java EE Agent Integration

Use this Generic installation only option in the Java agent setup wizard to create and deploy a Java EE Integration Agent to a host without a Java EE agent integration. This option is useful in situations where you need to create an installation directory and configure pre-instrumentation in preparation for manually integrating an agent.

Part of an application server’s integration with the Java EE agent includes a step known as pre-instrumentation. Pre-instrumentation prepares a special bootstrap jar file required for the operation of the Java EE agent. Many application server startup routines include the pre-instrumentation step as part of the integration with the Java EE agent, but some startup routines do not. In these cases (such as, WebLogic® Windows® Services, and Oracle® Application Server), pre-instrumentation must be run as a separate step from application server startup. Create a Generic installation only that includes a value for the JAVA_HOME option for each JDK used in your application server environment. This task creates the initial bootstrap jar, which may be referenced in your integrations, and it can also be used to update the bootstrap jar from time to time, as needed. The Java EE Integration Agent can be configured to complete this extra step as part of its activation routine.

1
On the navigation panel, under Dashboards, click Application Servers > Administration.
Click Next.
5
On the New Integration — Type page, select either Generic installation only on Windows or Generic installation only on Solaris, Linux, HP-UX, or AIX.
Click Next.
6
For Oracle AS only: On the New Integration — Details page, specify any agent or pre-instrumentor options that are required for integration.
a
Click the arrow beside Command Line Options to show the pre-instrumentor Options box.
b
Click the down arrow beside Other Options to show the Java Home box.
If you specify a value for Java Home, the Java EE Integration Agent instruments Java Home and creates a bootstrap jar file. If you leave the Java Home box blank, the instrumentation script is created but the bootstrap jar is not. You can use the generated instrumentation script at any time to create or recreate the bootstrap jar.
c
Click Next.
Click Next.
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.
Click Next.
a
By default, the instrumentation script is assigned a name based on the integration type. For example: Generic installation only on Windows: Install Configs and pre-instrument.
b
Click Finish.

The Application Servers Administration dashboard refreshes, and the installation task appears in the Task History list, where you can monitor its progress. Wait for the Result column status to change to Success.

 

Managing Java EE Agent Installations, Integrations, and Configurations

The Java Administration dashboard provides a centralized location for managing agent integrations, configurations, and installations. This dashboard is sub-divided into three tabs, each of which focuses on one aspect of agent management.

1
On the navigation panel, under Dashboards, click Application Servers > Administration.

Next steps:

Managing agent integrations

The Java EE Integration Agent creates and manages the integration between the Java EE agent and the monitored application server. The integration agent uses an integration configuration that consists of several key pieces of information: the startup method, pre-instrumentation options, the instrumentation settings for recording data, and the Agent Manager host. You can create or edit Nexus connections and logging configurations for a particular integration, or review the integration information. All these tasks are performed through the Java Administration dashboard, Integration Configurations tab.

1
On the navigation panel, under Dashboards, click Application Servers > Administration.
3
Click the Integration Configurations tab.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating