There are several ways to monitor a run-time adapter:
At run-time, TIBCO Administrator Enterprise Edition allows you to remotely access all deployments in your administration domain. Depending on your security privileges, you may be able to perform one or more of the following tasks.
These aspects of monitoring and management are supported by TIBCO Administrator Enterprise Edition, which includes the TIBCO Administration Server and the TIBCO Administrator GUI.
TIBCO Hawk allows monitoring, management, and fault detection. It can be customized according to the user’s requirements and be used to monitor any TIBCO product on the network. TIBCO Hawk is especially suited for very large distributed systems where customization is required.
If TIBCO Hawk is installed at a site, Hawk microagents can be used to supplement the monitoring information provided by the standard logging capability. Examples of supplemental information that you can obtain with microagents are:
In a TIBCO Hawk environment, agents on each local computer can perform the monitoring work. A TIBCO Hawk Agent is an autonomous process that uses microagents to monitor local applications and systems activity. Microagents represent managed objects such as operating system subsystems, agent components, log files, event logs, and applications. Each microagent exposes a set of methods to the agent for collecting information and taking actions. This design allows for separation between management data and management rules or policies.
See your adapter user’s guide for a list of supported microagents.
By default all error, warning and information messages are printed in the console window in which the adapter instance starts and to a default log file. The log file can be located anywhere on the file system.
When a log file name is specified in the Logging tab, the adapter:
Information can also be written to the log file in the overwrite mode, rather than the default append mode. In overwrite mode, the adapter instance overwrites the existing log file when it is next started. In append mode, trace information is appended to existing entries in the log file.
Trace messages provide information about adapter activities. The messages are logged to the console where the runtime adapter was started and to a log file. Trace messages can also be redirected to the TIBCO Hawk Display application, or sent to other applications using the TIBCO Rendezvous transport.
Each trace message can include the following fields:
The above fields are explained your adapter user’s guide. The following diagram shows an example trace message and calls out the fields.
An adapter includes a status code in a tracing message. A status code provides information such as connection errors, startup errors and certain adapter service errors. These messages provide details about the error, are contextual and are applied uniformly across adapters.
Low-level exception messages like System and TIBCO Rendezvous messages have appropriate adapter-level information. Status code descriptions and resolutions are available in the respective adapter user’s guide.
A tracking identifier is "stamped" on each significant trace message by the originating adapter. This allows you to track the progress of a message as it travels among TIBCO applications.
TIBCO Adapter™ Concepts April 2005 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |