Deploying a System Monitoring shared service in internal mode

You can deploy a System Monitoring shared service in internal mode in a single system or multisystem environment.

1. Click Patterns > Shared Services. If you are on 2.3.3.3 or later, click Patterns > Provision > Shared Services.
2. Do one of the following actions:
   • Single system only:
     1. Expand the Monitoring Services section.
     2. Click Deploy in the Actions column of the shared service that you want to deploy. Continue deploying the shared service. For detailed steps, see Deploying shared services. Then, continue with step 3.
   • Multisystem only: Select the shared service to deploy. Continue deploying the shared service. For detailed steps, see Deploying shared services in a multisystem environment. Then, continue with step 3.
3. Configure the specific properties for the shared service.

   Name

   Shows the name of the shared service.

   Environment Profile

   Select the environment profile used to control aspects of your deployment.

   Cloud Group

   Optional. This option is available only when deploying to a single-cloud environment profile. It is a required option if present, and used to select the cloud group associated with the shared service. If it is not present, you will be able to select the cloud group for your virtual machines on the Distribute panel.

   IP Group

   Optional. This option is available only when deploying a single-cloud environment profile. It is a required option if present, and used to select the IP group for your shared service instances. If it is not present, you will be able to select the IP group for your virtual machines on the Distribute panel.

   SSH Key

   To upload a public key so that you can connect to the deployed virtual machines using SSH, complete the SSH section and specify the SSH public key. If you do not have an existing SSH key pair, you can generate one that can be reused with other deployments. Click Generate. The SSH Key field populates with the generated public key. Select Click here to download the file containing the private key and save the private key to your local system.

   By downloading and saving the key, you can access your virtual machines even if the appliance loses connectivity or encounters problems.

   Password for the user ID sysadmin

   Type a password for the sysadmin user ID. Use this initial user ID for logging on to Cloud Pak Software Monitoring Portal, with full access and complete administrator authority. Enter the same password again in the verification field. The password must be 15 characters or less.

   Password for the user ID itmuser

   Type a password for the itmuser user ID. Use this user ID for collecting historical data. Enter the same password again in the verification field.

   Password for the user ID db2inst1

   Type a password for the db2inst1 user ID. Use this user ID for creating and maintaining the data warehouse database. Enter the same password again in the verification field.

   Allow connections from other System Monitoring shared services

   Enable this property if you want this internal mode shared service to receive connections and monitoring data from System Monitoring shared services (external mode) that are running in other cloud groups. Enabling this property opens the required port that permits external connections from System Monitoring shared services in other cloud groups.

   Enable Monitoring Agent for IBM® Cloud Pak System

   By default, the Monitoring Agent for IBM Cloud Pak System is started in each deployed System Monitoring shared service. This agent provides monitoring and eventing for hardware resources for the entire system. In systems that contain many cloud groups, it is possible to have more than one IBM Cloud Pak System agent that is running. This scenario can lead to duplication of monitoring and duplicate events being sent for configured event receivers. On systems that contain more than one cloud group, enable one System Monitoring shared service to run the Cloud Pak Software Agent. For all other cloud groups on the rack, disable the Cloud Pak Software Agent.

   In 2.3.3.3 or later: Enable monitoring for workload instance owners and read-only users in the system

   Use this option to control the view access to the monitoring portal. By default, this option is selected. If you keep this option selected, during shared service deployment, on launch of the monitoring portal, the home page displays the instance details page otherwise it displays a gray or a blank page.

   Note: This option is applicable only for read-only users and users with no permissions, but with access to pattern, environment profile, and instance. For other users, the existing function remains the same, irrespective of whether the option is selected or cleared during deployment.

   For more information, see this table.

   Table 1. User role access to the monitoring portal

   User role	Checkbox action	System Monitoring Portal
   Administrator	Selected	Home page displays the instance details.
   Administrator	Unselected	Home page displays the instance details.
   Read-only permission	Selected	Home page displays the instance details.
   Read-only permission	Unselected	Home page displays a gray or an empty page.
   No permissions (at user level)	Selected	Home page displays the instance details.
   No permissions (at user level)	Unselected	Home page displays a gray or an empty page.
   Full permission	Selected	Home page displays the instance details.
   Full permission	Unselected	Home page displays the instance details.

   Shared Service Sizing

   Select the expected size of the internal System Monitoring shared service. Decide which size to use based on the number of monitoring agents that you plan to connect to the monitoring servers in that shared service. Previously, your Cloud group administrator defined the number of monitoring agents (including workload virtual machines and the number of deployments expected) for deployment in a cloud group and determined the shared service size accordingly.

   The system adjusts for size by deploying and undeploying instances of the remote monitoring server as needed. Once a size is selected, there is no dynamic change in the runtime of the internal IBM Tivoli® Monitoring shared service. However, within the size limit itself, auto scaling is used to scale out and then in the Remote Tivoli Enterprise Monitoring Server (RTEMS).

   The following table shows:

   • The overall limit of active monitoring agents supported for each shared service size.
   • The recommended maximum number of agents is for optimal performance.
   • The absolute maximum number of agents is the limit before risking failure and loss of monitoring.
   • The storage allocations for the data warehouse.

   Table 2. Active monitoring agents per sizing

   Size	Minimum RTEMS	Maximum RTEMS	Recommended maximum agents	Absolute maximum agents	Data warehouse storage
   Tiny	1	2	200	1000	100 GB
   Small	1	3	500	1500	200 GB
   Medium	2	4	2000	4000	600 GB
   Large	2	6	5000	6000	1 TB

4. Specify the event forwarding option:
   • To forward events to Cloud Pak System Event Receiver, click Forward events to IBM Cloud Pak System Event Receiver.
   • To forward events to an external event receiver, click Forward events to external event receiver and enter the event receiver address and event receiver port.
5. Continue deploying the shared service:
   • Single system only: For detailed steps, see Deploying shared services.
   • Multisystem only: Click Prepare to Deploy to view the default placements for the different virtual machines in the available cloud groups of the public environment profile.
     Note: When you deploy a system monitoring shared service into a multisystem environment, you must place the ITM-Hub-TEMS on the local deploying system in the Distribute portion of the deployment process, otherwise you might receive an error. For example, if you are signed into local system A, and deploying from that system, you must place the ITM-Hub-TEMS on system A. Otherwise, you might receive the following error message:

     CWZKS7074E The vm-template ITM-Hub-TEMS cannot be deployed to location <location> due to the local location constraint