Foglight for Java EE Technologies 5.9.7.5

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

Configuring Java Homes pre-instrumentation

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. You must 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 is used to create 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 perform this extra step as part of its activation routine.

To create a generic installation and pre-instrument:

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

On the Application Servers Administration dashboard, in the Monitoring Agents section, click Setup agents.

In the menu that opens, select Java.

On the Setup Options page of the Java - Setup New Application Server Integration wizard, select Setup a new application server integration.

Click Next.

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.

For Oracle AS only: On the New Integration - Details page, specify any agent or pre-instrumentor options that are required for integration.


	IMPORTANT: These settings are not applied to any integrations except Oracle AS. Any values input here are ignored by the manual integration process for other application servers.

Click the arrow beside Command Line Options to show 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.

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.

For more information about pre-instrumentation, see Configuring Java Homes pre-instrumentation .

Click Next.

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.

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.

On the Integration Hosts page, select the host that you want to integrate with. 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.

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.

On the Installation Directory page, define the location for the directory that contains all installation components and log files. To accept the default directory, leave the Directory name box empty.