サポートと今すぐチャット
サポートとのチャット

Foglight for Java EE Technologies 5.9.7.5 - Installation Guide

Installing and Configuring Foglight for Java EE Technologies Integrating with JBoss Integrating with Tomcat Integrating with WebLogic Domain Startup Scripts Integrating with WebSphere Integrating with Oracle AS 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 Installations Foglight for Java EE Integration Configuration FAQ and Troubleshooting Performing Manual Application Server Integrations Appendix: Managing Permissions for the Java EE Integration Agent Appendix: Foglight for Java EE Application Methods

Updating Configuration Properties

In some cases, 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 Java Administration.
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.

Managing Logging Properties

You can configure the following for logs produced by the Java EE agent:
•
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 a number of 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. Log messages of a level below this threshold are ignored by the target. 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.
You must create a basic log configuration as part of the agent installation process, but you can edit that configuration, or create new ones, at any other time.
Creating or Editing Logging Properties
The process for creating a new log configuration and the process for editing an existing one are very similar. The following procedure describes both options and any differences between them.
To edit or create a logging configuration:
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
Click Manage logging. The Logging page opens.
5
Click the name of the log that you want to edit. In the menu that opens, click Edit.
Click New.
In either case, the 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.
6
Set the values for each of the logging target types: Console, Text File, Serialized File, WebSphere, and Other, as necessary. If you need more information about a particular setting, click the icon.
7
New configurations only — Type a unique and recognizable name in the Save as box.
8
Click Save.
The next time that you create an agent, you can assign the saved log configuration to it. You can also update any integrations that are already using the log configuration.
To update log settings for an existing configuration:
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 list of Configuration Name and Targets, expand the configuration group by clicking the ‘+’ sign, then click the name of the target you want to update.
5
In the list that opens, click Update logging.

Reintegrating Existing Targets

To keep your application servers up to date, you can edit the properties of an integration task, and then reintegrate either a single target, or all targets using that particular configuration.
To reintegrate a target:
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 list of Configuration Name and Targets, click the name of the integration configuration task. For example: Generic installation only on Windows: Install Configs and Preinstrument.
5
In the list that opens, click Properties.
6
In the Integration Task Properties dialog box, update the Java Home or Preinstrumentor Options as necessary.
7
Click Save.
8
In the Integration dialog box, click OK if you want to reintegrate all targets that use the configuration.
or
Clear the check box if you want to reintegrate only certain targets, then click OK.
9
Optional — In the list of Configuration Name and Targets, do one of the following:
•
To reintegrate a single target, expand the configuration group by clicking the ‘+’ sign, then click the name of the target you want to reintegrate (for example, appserver.example1.com: WebLogic on Windows: startWebLogic). In the menu that opens, click Reintegrate.
•
To reintegrate all targets that are using the same integration configuration, click the configuration name (for example, WebLogic on Windows: startWebLogic). In the menu that opens, click Reintegrate targets.

Deleting and Undoing an Integration

There are two options for removing integrations from targets: Delete only, and Delete and undo integration.
Use Delete only to remove integrations on decommissioned hosts or to delete stale integrations that have been superseded. Deletion permanently removes all records of the integration target.
Use Delete and undo integration to restore the target host to its pre-integration state. This option is useful when the integration is still active on the target.
To delete an integration:
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 list of Configuration Name and Targets, expand the configuration group by clicking the ‘+’ sign, then click the name of the target you want to delete.
5
In the list that opens, select either Delete only, or Delete and undo integration, as necessary.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択