In the Endpoint Task frame, you can configure endpoint-specific logging. Endpoint logs track messages that a connector generates when it processes requests for objects residing in that endpoint. Each endpoint can be configured separately so you can turn logging on or off for just the endpoints where you need to learn additional information to diagnose problems.
You can also specify the severity (success, information, warning, fatal, and error) of the messages that get logged.
To turn logging on or off and to set the logging destinations and the severity levels of the messages logged for each endpoint, use the Logging tab of the endpoint's property sheet in the Provisioning Manager. For detailed instructions, see Setting Endpoint Logging in the Provisioning Manager help.
Endpoint logging is sent to a log file for the connector server in which the connector for the endpoint runs. For C++ connectors, the default log file name is PSHOME\Logs\saYYYYMMDD.log. The C++ connector server also adds some additional messages to this log. You control the log file name in the im_ccs.conf using the BaseLogFileName parameter. And you control which severities of these other messages are logged in the same conf file using the LogSeverities parameter.
Endpoint logging from connectors which run directly within the provisioning server (for example, the CA ACF2 connector) log to the provisioning server’s event log which has the default name of PSHOME\Logs\etaYYYYMMDD.log.
|
Copyright © 2013 CA.
All rights reserved.
|
|