Connection Profiles and the Pluggable Protocols Architecture store the information that is required to communicate with computers and other network devices using standard network monitoring protocols. The Pluggable Protocols Architecture unifies the configuration of protocols across the Symantec Management Platform. Connection Profiles is a feature of the Symantec Management Platform that is leveraged by other solutions and components in the Symantec Management Platform. It provides the ability to update and add protocols without requiring a wholesale upgrade of all dependent solutions. These protocols can include SNMP, WMI, WSMAN, as well as several others.
Credential Manager provides a secure storage location for user names and passwords. The types of credentials that are stored are defined by the installed management solutions. Access to credentials is controlled using the built-in role-based security of the Symantec Management Platform. When a credential is created, only the creator is granted access. If other users need to perform management operations requiring a credential, they must be assigned rights.
This component is part of the Symantec Management Platform 7.0 SP4. For release notes, see knowledgebase article 49811.
The following are known issues for this release. If additional information about an issue is available, click the Article ID link.
Pluggable Protocols Architecture
AMTRedirectionService not registered after upgrade of PPA
Support common Connection Profile by the SNMPTrapSenderPlugin
Altiris.PluggableProtocols.Alert object does not support serialization
WMI protocol plugin hangs when making a synchronous call to a buggy WMI provider
Impossible to connect to the client using the network protocol with custom credentials if another protocol is turned on with runtime credentials
Certificates may not load using IE8
Using Internet Explorer 8, certificates will not load if any of the following are true:
Retry and Timeout values may not be used during connection
Each protocol allows you to specify its own timeout and retry value. However, these values are typically only used during the execution of commands by the protocols, but not when attempting to connect to a target computer using these protocols. If a solution only attempts to connect to targets to determine availability, but does not execute any commands over the protocols used to connect, it should not be expected by the user that failed connection attempts would be retried, unless such attempts are controlled at the solution level.