Converse agora com nosso suporte
Chat com o suporte

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

Updating the Nexus connection for a target application server

If you changed the Nexus Connection (see Managing Nexus connections for details), you can update any target application servers that are using that Nexus connection through the Integration Configurations tab of the Java Administration dashboard.

To update an application server’s Nexus connection:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, click the Java tab.
3
On the Java view, click the Integration Configurations tab.
4
In the Configuration Name and Targets list, expand the configuration group (for example, WebLogic on Windows: startWebLogic) that contains the target by clicking the ‘+’ sign.
5
Click the name of the target application server that you want to update.
6
In the menu that opens, click Update Nexus connection.
Related topics:
•
Managing Nexus connections

Switching a Nexus connection

Switching a Nexus connection

You can change the Nexus connection between an agent and a Nexus after the agent has been created. For example, you might switch the connection for performance reasons (divide up the agents) or to organize your environment (all agents monitoring a particular application use the same Nexus). Switching the Nexus connection affects all of the agents belonging to the application server integration.

To switch a Nexus connection:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, click the Java tab.
3
On the Java Administration dashboard, click the Integration Configurations tab.
4
In the Configuration Name and Targets list, expand the configuration group (for example, WebLogic on Windows: startWebLogic) by clicking the ‘+’ sign.
5
Click the name of the application server (agent target) that you want to switch the Nexus connection on.
6
In the list that opens, select Switch Nexus Connection.
A dialog box opens, listing all the available Nexus Connections for that application server integration.
7
Select the Nexus connection that you want to switch to.
8
Click Switch to save your changes.

All of the agents within the application server integration now use this Nexus connection to communicate with the Nexus.

Related topics:
•
Managing Nexus connections

Updating integration configuration properties

Sometimes, due to monitored environment changes, it may be necessary to update the integration configuration properties, such as the target integration script location, or the agent or pre-instrumentor options.

To edit the integration configuration properties:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, click the Java tab.
3
On the Java Administration dashboard, click the Integration Configurations tab.
4
In the Configuration Name and Targets list, click the name of the configuration that you want to edit (for example, WebLogic on Windows: startWebLogic).
5
In the menu that opens, click Properties.
6
In the Integration Task Properties dialog box, change the available values as necessary.
7
Click Save.
8
Restart the affected application servers.

Java EE agent logging properties

You can configure the following for logs that the Java EE agents produces:

•
Log targets, for forwarding log messages to different outputs
•
Log level (ALL, DEBUG, VERBOSE, INFO, WARN, ERROR, FATAL, and OFF) for each log target
•
The directory in which log files are created (if other than the default directory, <VERSIONED_SUBDIRECTORY>/logs)
•
A locale setting for changing the language in which log messages are written

You can also configure several log targets:

•
Console: Outputs to the application console
•
Text File: Outputs to a formatted text file
•
Serialized File: Outputs to a serialized object file
•
WebSphere: Forwards Agent messages to the WebSphere log system

Java EE agents normally have Console and Text File log targets active. The Serialized File target is active in all log-enabled applications, but its threshold is set to OFF normally. This can be overridden in release-mode by setting its threshold to something other than OFF, preferably ALL. WebSphere is active only for agents monitoring WebSphere.

Each target has a set of properties that can be set to modify its behavior. All targets have one common property: Threshold Log Level. Targets ignore log messages of a level below this threshold. Standard levels are ALL, DEBUG, VERBOSE, INFO, WARN, ERROR, FATAL and OFF, in descending order of verbosity. A threshold of OFF effectively disables a target. File-based targets do not create files when their threshold is OFF.

Create a basic log configuration as part of the agent installation process. You can edit that configuration, or create ones, at any other time.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação