You can view the status and settings for all connectors installed on the system using the CA Spectrum SA Administration interface. To determine if the CA Clarity PPM connector has started correctly after you have installed it, open the connector configuration page and examine the Status property.
If the connector configuration is "Offline" and no CA Clarity PPM-specific log files are present after you have attempted to start the CA Clarity PPM connector, then the CA Clarity PPM connector is failing to initialize. This failure is due to a framework-level issue, indicating that it is not a host configuration issue.
Usually the failure to initialize applies to all CA Clarity PPM connector configurations. In this case, check the framework logs for error conditions related to CA Clarity PPM connector initialization problems. The following are common issues:
Example: security restrictions and invalid XML.
If the CA Clarity PPM connector-specific logs are created, then the issue is likely related to the host settings. The INFO log indicates whether the CA Clarity PPM connector attempted to log in to CA Clarity PPM or not, and the result. If no login attempt is evident, check for configuration warnings or errors, including a failure to load one or more mapping templates. If multiple warnings appear, then verify the TemplateFolder configuration property.
A successful startup with INFO logging enabled produces a few lines of information, including the CA Clarity PPM connection information and version, and the initial data retrieval results. After startup, INFO log entries will only be created when conditions change (for example, connection to CA Clarity PPM is lost or a CI change is detected).
Log entries contain certain context information with the message to help identify the origin and significance of the entry. The following sample entry identifies the various context fields:
2010-01-01 01:01:01,000 INFO [Clarity Change Monitor [interval=60, host: mytenant\myuser@myhost:80]] connector.ClarityChangeMonitor - Changes: [added=0, removed=0, modified=1, alerts pending=0]
Identifies the local date/time (down to the millisecond) that the event took place.
Identifies the severity level of the entry.
The name of the program thread that produced the message. The name can include the host information related to the event.
The event details. Often the event details include summary information or a comma-delimited list of properties related to the current operation.
If you encounter a server-side error while using the CA Clarity PPM connector, the error details are returned to the CA Clarity PPM connector and recorded in the CA Clarity PPM connector log files. If, however, the local log files do not provide sufficient information to diagnose and resolve an issue, consult the standard CA Clarity PPM log files. CA Clarity PPM connector actions appear as XOG requests on the server. Follow the installation prerequisites to identify XOG request errors originating from the CA Clarity PPM connector through the unique login ID.
For more information, see the Administration Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|