How to Connect an Operations Manager SDK Client to the System Center Data Access Service
Applies To: System Center 2012 - Operations Manager
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
To programmatically access Operations Manager data and functionality, an Operations Manager software development kit (SDK) client application must connect to the System Center Data Access service. The System Center Data Access service runs on all management servers. Connecting the SDK client to the System Center Data Access service returns a ManagementGroup object, which you can use to access other useful objects, such as alerts, events, tasks, and management packs.
When it connects to the System Center Data Access service, an Operations Manager SDK client can authenticate as the current user or as a different user with specified credentials. In either case, the account that is used for authentication must be included in an Operations Manager user-role profile. All methods that are exposed by the Operations Manager SDK have a security profile that determines which user roles can access the method. In addition, some methods provide security filtering that produces different results for user profiles with limited privileges than for user profiles with unrestricted access.
If an SDK client attempts to access a method that is not allowed by the current user's profile, an UnauthorizedAccessMonitoringException is thrown. The SDK client can handle this exception to notify users that they do not have the appropriate privileges for the requested operation.
SDK clients can connect to the System Center Data Access service on the management server or remotely on a different computer. In either case, SDK clients use the local computer's copy of the Operations Manager class libraries. When an SDK client is running on a remote computer, the System Center Data Access service automatically handles all necessary remote calls and communication channels.
Note
To improve client performance, the System Center Data Access service automatically distributes a type space cache to remote client computers. This cache is initialized once per language, per service connection. The cache improves client performance by providing local access to frequently used types. By default, the System Center Data Access service automatically maintains and updates the cache when necessary.
In This Section
- How to Connect to a System Center Data Access Service by Using the Current Credentials
Demonstrates how to authenticate as the current user when connecting to the System Center Data Access service.
- How to Connect to a System Center Data Access Service by Using Specified User Credentials
Demonstrates how to authenticate as a different user when connecting to the System Center Data Access service.
See Also
Concepts
Getting Started with the System Center 2012 - Operations Manager SDK
Getting Started Developing an SDK Client Application
System Center 2012 - Operations Manager SDK Architecture Overview