Chatta subito con l'assistenza
Chat con il supporto

Foglight for Java EE Technologies 5.9.9 - Installation Guide

Install and Configure Foglight for Java EE Technologies Integrate with JBoss Integrate with Apache Tomcat Integrate with WebLogic Domain Startup Scripts Integrate with WebSphere Integrate with Oracle AS Create a Generic Installation for Manual Java EE Agent Integration Manage Java EE Agent Installations, Integrations, and Configurations Managing Java EE Agent Configurations Java EE Installation Management Java EE Integration Configuration FAQ and Troubleshooting Manual Application Server Integrations AppendixB: Managing Permissions for the Java EE Integration Agent Appendix A: Java EE Application Methods

The Nexus and Agent-Nexus connections

Foglight for Java EE Technologies includes the Nexus, a central analytical engine that correlates data sent from multiple agents, restores and preserves the temporal order of events across all servers, and provides other basic analysis of the data. The Nexus is essential to the data management facilities of Foglight for Java EE Technologies.
Foglight creates a default Nexus as part of the installation process for Foglight for Java EE Technologies. The default Nexus controls all agent data correlation and submission unless you create another Nexus and assign agents to it instead.
* 
TIP: For more information about the Nexus, see the topic Understanding the default Nexus in the Foglight for Application Servers Administration and Configuration Guide or help.
The Nexus connection is the communication link between the Java EE agent and the Nexus. It defines how the agent communicates with the Nexus and controls settings such as retry intervals and timeouts.
The initial agent-Nexus connection is created as part of the agent installation process. You can also create connections, or edit existing ones, and change which agents are using a connection by switching the agent’s Nexus connection.
Related topics:
•
Managing Nexus connections

Managing Nexus connections

During the process of creating a Java EE agent, you assign it to an existing Nexus, and an agent-Nexus connection is created. You can also change the connection between an agent and a Nexus, or create a connection and assign it to different agents after they have been created.
Creating or editing Agent-Nexus connection settings
The process for creating an agent-Nexus connection and the process for editing an existing one are similar. The following procedure describes both options and any differences between them.
To change agent Nexus connection settings:
1
On the navigation panel, under Dashboards, click Application Servers Administration.
2
On the Application Servers Administration dashboard, click Java Administration.
3
On the Java Administration dashboard, click the Integration Configurations tab.
4
Click Manage Nexus Connections.
The Manage Nexus Connections page opens.
5
To edit an existing connection, click the name of the connection. In the menu that opens, click Edit.
Or
To create a connection, click New.
In either case, the Nexus Connection dialog box opens.
6
On the Locations tab, add one or more Nexuses that the agent should attempt to connect to, in the order that you want. The agent attempts to connect to each Nexus in turn until a successful connection is established.
Click Add Nexus location and select a Nexus from the list.
* 
TIP: Use the Add custom option to define a Nexus location by listen address and port.
7
Optional — Use the up and down arrows to change the order in which the agent attempts the Nexus connections.
8
Click the Advanced tab.
9
Edit the connection settings as necessary. Click the icon to view a detailed description of the setting and its effects.
a
Connection Retry Interval — If the connection between an agent and the Management Server is broken, or if the agent fails on its initial attempt to connect to the Nexus, the agent tries to reconnect at regular intervals. The default setting is 20,000 milliseconds (20 seconds). You can increase or decrease this interval. You can also turn off automatic reconnection attempts by setting the interval to zero.
b
Trace Aggregation Interval — When an agent attempts to synchronously connect to the Nexus, it waits for a response for the amount of time specified in this setting. The default setting is just over 23 seconds (23,497 ms). You can increase or decrease this interval.
c
Authentication Failure Retry Interval — If the agent fails on its initial attempt to connect to the Foglight Management Server due to an authentication failure (such as a build number mismatch or expired licensing) it continues trying to connect at regular intervals. The default setting is just over 120 seconds (two minutes). You can increase or decrease this interval. You can also turn off automatic reconnection attempts by setting the interval to zero.
d
Authentication Timeout — When an agent attempts to connect to the Foglight Management Server, by default it waits up to 30 seconds for an authentication response from the Nexus before dropping the connection. You can change the length of time that the agent waits for authentication.
10
For New Nexus Connections only — If you want to reuse this connection and assign it to other agents, type a unique name in the Save as box.
11
Click Save.
The Manage Nexus Connections page refreshes. Any changes you have made to the Nexus connection information are listed in the table, along with the modification date and time.

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 Java Administration.
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) 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

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 > Application Servers Administration.
2
On the Application Servers Administration dashboard, click Java Administration.
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
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione