Deploying the System Monitoring for WebSphere Message Broker service in a multisystem environment

Extend the capabilities of the base System Monitoring shared service by deploying the System Monitoring for WebSphere® Message Broker service.

Before you begin

You must be assigned the following roles to perform this procedure:
  • Allow delegation when Full permission is selected
  • Workload resources administration role with permission to Manage workload resources (Full permission)
  • System level, Cloud group administration role with permission to View all cloud resources (Read-only)
  • System level, Hardware administration role with permission to View all hardware resources (Read-only)
  • Security administration role with permission to View users/groups (Read-only)

About this task

These steps are specific to shared services deployed in a multisystem environment. You can use the console or the command line interface to complete this task. For the command line information, see the Related information section.

Either a deployed instance or a reference to the System Monitoring shared service should be present in the multi-cloud environment profile the shared service is deployed to.

Procedure

  1. Click Patterns > Shared Services. If you are on 2.3.3.3 or later, click Patterns > Provision > Shared Services.
  2. Select the shared service to deploy.
    Continue deploying the shared service. For detailed steps, see Deploying shared services in a multisystem environment.
  3. Configure the specific properties for the shared service:
    Auto-start monitoring agent when deployed
    Enable this option to start the monitoring agent for WebSphere Message Broker automatically when the message brokers are started.

    When you deploy the System Monitoring for WebSphere Message Broker service and then deploy a pattern with message brokers, a monitoring agent is installed with each message broker in the pattern. If you enable this option, the monitoring agent is also started.

    When you deploy a pattern with message brokers and then deploy the System Monitoring for WebSphere Message Broker service, message brokers in the pattern discover the shared service and a monitoring agent is installed. If you enable this option, and if the Start monitoring agent when existing deployments discover Shared Service for the first time option is enabled, the monitoring agent is also started.

    If you enable this option, and if the Auto-start monitoring agent on all deployments option is enabled, when you delete and then redeploy the System Monitoring for WebSphere Message Broker service, any monitoring agents that are stopped when you redeploy are started.

    If you disable this option when you deploy the System Monitoring for WebSphere Message Broker service, you can start the monitoring agent later.

    Auto-start monitoring agent on all deployments
    Enable this option to start all monitoring agents that are currently stopped.

    If you enable this option, and if the Auto-start monitoring agent when deployed option is enabled, the monitoring agent is started on all deployments in which it is currently stopped. Use this combined setting to start all monitoring agents in a cloud group regardless of whether they were stopped by you or stopped automatically.

    If you enable this option, and if the Auto-start monitoring agent when deployed option is disabled, only those monitoring agents that are currently stopped automatically are started. Any monitoring agents that are currently stopped by you are not started at this time, but are made ready to start again automatically if you redeploy the System Monitoring for WebSphere Message Broker service later with the Auto-start monitoring agent when deployed option enabled.

    Start monitoring agent when existing deployments discover Shared Service for the first time
    Enable this option to install and start the monitoring agent on existing deployments that were not configured to monitor WebSphere Message Broker when they were deployed. This setting has no effect unless the Auto-start monitoring agent when deployed option is also enabled.

    If you disable this option, the monitoring agent is installed on existing deployments, but you must start the agent manually.

  4. Click Prepare to Deploy/Quick Deploy.

Results

An instance of the shared service is created in the selected cloud group. At this point, the shared service does not have any middleware or virtual machines associated with it.

What to do next

The shared service can be deployed once in a multi-cloud environment profile and then be made available for use as a reference to other multi-cloud environment profiles where the shared service is not deployed. For information, see Making a deployed shared service available in other multi-cloud environment profiles.