Deploying a System Monitoring shared service in external mode

You can deploy a System Monitoring shared service so it runs in an external mode.

1. Click Patterns > Shared Services. If you are on 2.3.3.3, click Patterns > Provision > Shared Services.
2. Expand the Monitoring Services section.
3. 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.
4. Configure the specific properties for the shared service.

   ITMSS Version

   Select Version 6.3 only when connecting to an external ITM server if using Version 6.3 or later. Selecting Version 6.3 causes Version 6.3 OS agents to be deployed, while selecting Version 6.2.3 causes Version 6.2.3.5 OS agents to be deployed.

   Hub TEMS Address

   Type the host name or IP address of the hub monitoring server to which the remote monitoring server connects.

   Network Protocol

   Select the type of protocol to use for communication with the hub monitoring server. The protocol must match the protocol configured at the hub monitoring server for receiving incoming connections. Choose from the following options:

   ip.pipe

   TCP connection with no encryption.

   ip.spipe

   Encrypted TCP connection using SSL.

   Hub TEMS Port

   Type the port number that is configured at the hub monitoring server for accepting incoming connections. The port number is usually 1918 or 3660.

   TEPS Address

   Type the host name or IP address of the portal server.

   TEPS Port

   Type the port number that is configured at the portal server for accepting incoming connections. The port number is usually 1920 or 3661.

   User ID of Hub TEMS

   Type the administrator user ID that is used to connect to the hub monitoring server. The default is sysadmin.

   Password for the user of Hub TEMS

   Type the password that is associated with the user ID of the hub monitoring server. The password must be 15 characters or less.

   Password for the Data Warehouse User

   Type the password that is associated with the Data Warehouse User. The Data Warehouse User is usually itmuser.

   JDBC JARs

   This field is only used when the Data Warehouse database is a third party database (for example, a database other than DB2®). Packaged client JDBC JAR files are used to connect to the external data warehouse . You must first compress the client JDBC JAR files into a .zip, .tgz, or .tar.gz package.

   Use the following steps to upload the packaged client JDBC JAR file:

   1. Click Browse to specify a packaged client JDBC JAR file.
   2. Use the Local tab to specify the packaged JDBC JAR file located on the local system.
   3. Use the HTTP tab to specify a packaged JDBC JAR file that is accessible through an HTTP server.
   4. Click OK to upload the package file. Wait until you see the file listed in the JDBC JARs field, indicating that the specified file uploaded successfully. Do not initiate the deployment before the upload operation is completed.

   Shared Service Sizing

   Select the expected size of the external System Monitoring shared service. Decide which size to use based on the number of monitoring agents you plan to connect to the remote 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 external 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 1. 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

5. Continue deploying the shared service. For detailed steps, see Deploying shared services.