Extend the capabilities of the base System Monitoring shared service by
deploying the System Monitoring for WebSphere® Application server 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
- Click .
- Select the shared service to deploy. Continue
deploying the shared service. For detailed steps, see Deploying shared services in a multisystem environment.
- Configure the specific properties for the shared service:
- Auto-start monitoring agent when deployed
- Enable this option to start the monitoring agent for WebSphere Application Server automatically
when the application server instances are started.
When you deploy
the System Monitoring for WebSphere Application server service
and then deploy an application server pattern, a monitoring agent
is installed on each application server instance in the pattern. If
you enable this option, the monitoring agent is also started.
When
you deploy an application server pattern and then deploy the System Monitoring for WebSphere
Application Server service,
application server instances 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 Application server 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 Application server service,
you can start the monitoring agent later.
- Restart WAS servers automatically
- Enable this option to restart monitored application server instances.
If
you enable this option, application server instances are restarted
in the following situations:
- You deploy the virtual machine.
- You reboot the virtual machine.
- You start or restart the System Monitoring shared service in
the same cloud group as
the deployment.
- You deploy the System Monitoring for WebSphere
Application Server service
in the same cloud group as
the deployment.
- You start the monitoring agent after it has been manually stopped
previously.
When you restart application server instances, the monitoring
agent completes its configuration and makes monitoring data available
in the Cloud Pak Software Monitoring Portal.
This option is enabled by default, so you do not have to restart servers
manually every time they perform a deployment or upgrade the shared
services.
Although the default setting is recommended, you might
choose to disable this option when you are working with sensitive
systems and prefer to initiate server starts manually.
- 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 combination of settings 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 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 Application server 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 are not configured to monitor WebSphere Application Server when
they are deployed. This setting has no effect unless you also enable
the Auto-start monitoring agent when deployed option.
If
you disable this option, the monitoring agent is installed on existing
deployments, but you must manually start the agent.
- Click Prepare to Deploy, then click 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.