Configuring the Management Pack for Microsoft Service Bus
Applies To: Service Bus for Windows Server 1.0
This section provides guidance on configuring and tuning this management pack.
Best Practice: Create a Management Pack for Customizations
Security Configuration
Optional Configuration
Best Practice: Create a Management Pack for Customizations
By default, Operations Manager saves all customizations such as overrides to the Default Management Pack. As a best practice, you should instead create a separate management pack for each sealed management pack you want to customize. When you create a management pack for the purpose of storing customized settings for a sealed management pack, it is helpful to base the name of the new management pack on the name of the management pack that it is customizing, such as “Microsoft Service Bus Customizations”.Creating a new management pack for storing customizations of each sealed management pack makes it easier to export the customizations from a test environment to a production environment. It also makes it easier to delete a management pack, because you must delete any dependencies before you can delete a management pack. If customizations for all management packs are saved in the Default Management Pack and you need to delete a single management pack, you must first delete the Default Management Pack, which also deletes customizations to other management packs.
Security Configuration
Run As Profiles
When the Management Pack is the first imported, it creates Run As profile:
- Service Bus Discovery and Monitoring Profile
This profile is associated with all discoveries and all tasks.
By default, all discoveries, monitors, and tasks defined in the management pack default to using the accounts defined in the “Default Action Account” Run As profile. If the default action account for a given system does not have the necessary permissions to discover or monitor the instance of Service Bus, then those systems can be bound to more specific credentials in the Service Bus Discovery and Monitoring Profile, which do have access.The following steps help you configure Run As profiles for Service Bus:
To configure Run As profile
Identify the names of the target computers where the default action account has insufficient rights to monitor Service Bus.
For each system, create or use an existing set of credentials that have at least privileges.
For each set of credentials identified in step 2, make sure a corresponding Run As account exists in the management group. Create the Run As account if necessary.
Set up the mappings between the targets and the Run As accounts on the Run As Accounts tab of each of the Run As profiles. Use the following table to identify mappings.
Run As Profile
Targets
Service Bus Discovery and Monitoring Profile
Classes:
Service Bus Farm
Service Bus Host
Service Bus Gateway role
Service Bus Message Broker role
Service Bus Fabric role
Groups:
Service Bus Hosts Group
Service Bus Containers DBs Group
For more information, see Run As Profiles and Run As Accounts in Operations Manager 2007.
Optional Configuration
By default SQL Server monitor for Service Bus databases is disabled. If you would like to enable it, you should download and install System Center Management pack for SQL Server before (https://www.microsoft.com/download/details.aspx?id=10631).