Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for Microsoft DOT NET 5.9.13 - Installation and Configuration Guide

Installing and Configuring Foglight for Microsoft .NET Managing .NET Agent Configurations

Nexus requirements

The Nexus runs on Foglight Agent Manager version 5.6.7.2 or later.

If you are using the .NET Transaction agent, ensure that the following requirements for the Nexus are met.

* 
IMPORTANT: The Agent Manager heap requires at least 1Gb of memory for the Nexus. Depending on the monitored application, this heap requirement may increase to as much as 4Gb.

The Nexus requires Oracle® (Sun) Java SE JDK 1.6, 1.7, or 1.8.

The Nexus is supported on the following OS platforms:

 
Table 2. Supported OS platforms for the Nexus
OS version
Architecture

Oracle Solaris® 8, 9, 10

SPARC®

Oracle Solaris 10, 11

SPARC, x86-64

Windows® XP SP1+, Server 2003, Server 2008

ia32, x86-64

Windows Server® 2008 R2, Server 2012, Server 2012 R2, Server 2012 R2 Core, Server 2016

x86-64

Red Hat® AS/ES/WS 4, 5, 6, 7

ia32, x86-64

SUSE® 9, 10, 11, 12

ia32, x86-64

Final platform support notice

Support for the following platforms will be discontinued in the next major release:

•
Solaris 8 and 9
•
All 32-bit versions of Oracle Solaris® SPARC®
•
Windows® XP SP1+
•
Red Hat® AS/ES/WS 4.x
•
SUSE® 9

Adjusting the Agent Manager settings for the Nexus

If you intend to use the default Nexus running in the embedded Complete Product Name without Trademarks Agent Manager, adjust the Agent Manager disk cache settings before installing and configuring Foglight for Microsoft .NET. The default Nexus is created as part of the installation process.

The Agent Manager accumulates messages that are destined to be sent either upstream or downstream in queues between connections. This prevents messages from getting lost in the event of a disconnection.

Increasing the Agent Manager disk cache size ensures that data submissions from the Java EE agent or the .NET agent are not discarded. See the documentation in the fglam.config.xml file for detailed descriptions of the options.

 
* 
NOTE: This procedure is recommended for all installations.
To adjust the Agent Manager settings for use with the Nexus:
1
Navigate to your Agent Manager config folder. For example: C:\Quest_Software\Foglight_Agent_Manager\state\default\config.
2
Open the vm.config file in an editor.
 
* 
IMPORTANT: In Agent Manager versions 5.6.10 and later, this file is called baseline.jvmargs.config.
3
Uncomment and set the following setting to:
vmparameter.0 = "-Xmx1024m";
4
Save and close the .config file.
5
In the same config directory, open the fglam.config.xml file in an editor.
6
Edit the config:queue-sizes and max-disk-space settings as follows:
<config:queue-sizes>
    <config:upstream max-queue-size="500" max-disk-space="100000" max-batch-size="500" allow-runtime-change="false"/>
    <config:upstream-verified max-queue-size="250" max-disk-space="50000" max-batch-size="250" allow-runtime-change="false"/>
    <config:downstream max-queue-size="500" max-disk-space="1024" max-batch-size="500" allow-runtime-change="false"/>
</config:queue-sizes>
This sets the max-disk-cache size to 100MB for the upstream and upstream-verified queues (normal and verified submissions).
7
Save and close the fglam.config.xml file.
8
Restart the Agent Manager.
If the Nexus is running in a non-embedded Agent Manager, the Agent Manager service must be restarted. This is the more common case.
If the Nexus is running in the embedded Agent Manager (for example, if you are using the default Nexus), do one of the following:
•
Restart the Management Server.
Or
•
Go to <server>/jmx-console (for example, http://torrdv288:8080/jmx-console/) and click: service=EmbeddedFglAm.
Invoke the Stop() operation, and then invoke the start() operation.

If you still find warnings in the Agent Manager log about the disk cache being too small, increase the max-disk-space values for the upstream and upstream-verified queues.

Next step
•
After you have adjusted the settings and restarted the Agent Manager, continue with Installing Foglight for Microsoft .NET.

Installing Foglight for Microsoft .NET

Prerequisite
•
Adjusting the Agent Manager settings for the Nexus

Foglight for Microsoft .NET is distributed in a cartridge (.car) file, ApplicationServers‑DotNET‑<version>.car. Installing and enabling the cartridge file on the Management Server adds the capabilities for monitoring Microsoft .NET systems to your Foglight for Microsoft .NET environment.

The installation process is common to all Foglight cartridges. For details, see Installing Foglight cartridges in the Administration and Configuration Help.

Next step
•
Creating .NET Agent instances
 
* 
TIP: Unlike with previous versions, you do not need to manually deploy the agent package to the hosts. The agent creation process now manages this step.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation