2.1.1 Starting ITSLM - Manager
To start ITSLM - Manager, start the services that comprise ITSLM - Manager and set their service status to Start.
You can have the ITSLM - Manager services start automatically when the OS starts. In such a case, you must use JP1/Base's startup control to set the order in which the services are to be started. If the services start automatically when the OS starts without setting the order, logging in to ITSLM or issuing JP1 events might fail. If ITSLM - Manager and ITSLM - UR are installed on the same host and you want to start the services automatically, you must use JP1/Base's startup control to set the ITSLM - Manager services to start first when the OS starts. For details about using JP1/Base for startup control, see the Job Management Partner 1/Base User's Guide.
If you have not set up the services to start automatically or when you are restarting ITSLM - Manager, you must start ITSLM - Manager by starting the services manually.
This subsection explains how to start ITSLM - Manager manually. If you run ITSLM - Manager in a cluster system, use the cluster software to start ITSLM - Manager; for details about the services to be started by the cluster software, see (3) Supplementary information.
- Organization of this subsection
(1) Before you start
-
Verify that JP1/Base is running.
For details about how to start JP1/Base, see the Job Management Partner 1/Base User's Guide.
-
Verify that ITSLM - Manager has been set up.
For details about how to set up ITSLM - Manager, see 5.1.6 Setting up ITSLM - Manager.
-
Verify that ITSLM - UR is not running.
-
If you link your ITSLM with Performance Management, verify that the necessary linkage information has been defined in a system definition file. For details about how to define the necessary linkage information, see 5.4.1 Setting up the linkage between ITSLM and Performance Management (working with Performance Management).
-
If you link your ITSLM with Performance Management, start each monitoring agent of the linked Performance Management and PFM - Manager. It doesn't matter whether you start ITSLM - Manager first or Performance Management first.
-
If you link your ITSLM with JP1/IM, verify that the necessary linkage information has been defined in a system definition file. For details about how to define the necessary linkage information, see 5.5.1 Linking with JP1/IM.
(2) Procedure
To start ITSLM - Manager:
-
From the Windows Start menu, select Administrative Tools, and then Services.
-
Start the ITSLM - Manager service JP1/ITSLM - Manager DB Service (service name: HiRDBEmbeddedEdition_JL0).
-
Start the ITSLM - Manager service JP1/ITSLM - Manager Service (service name: JP1_ITSLM_MGR_Service).
-
Start the ITSLM - Manager service JP1/ITSLM - Manager Web Service (service name: JP1_ITSLM_MGR_Web_Service).
Once the status of all three services is set to Start and in the above order, ITSLM - Manager has started.
(3) Supplementary information
-
If you run ITSLM in a cluster system, use the cluster software to start the following services in the order shown below:
-
Start the ITSLM - Manager service JP1/ITSLM - Manager DB Service (service name: HiRDBEmbeddedEdition_JL0).
-
Start the ITSLM - Manager service JP1/ITSLM - Manager DB Cluster Service (service name: HiRDBClusterService_JL0).
-
Start the ITSLM - Manager service JP1/ITSLM - Manager Service (service name: JP1_ITSLM_MGR_Service).
-
Start the ITSLM - Manager service JP1/ITSLM - Manager Web Service (service name: JP1_ITSLM_MGR_Web_Service).
-
-
To restart ITSLM - Manager, perform (2) Procedure after ITSLM - Manager has terminated.
-
When you start ITSLM - Manager and ITSLM - UR, if you perform the following steps in this order, you might not be able to log in to ITSLM - Manager for about two minutes because it takes time for ITSLM - Manager to initialize:
-
Terminate ITSLM - Manager.
-
Terminate ITSLM - UR.
-
Start ITSLM - Manager.
-
-
If you restart ITSLM - Manager while you are logged in to ITSLM - Manager, you must log in to ITSLM - Manager again because the logged-in session becomes invalid.
For details about how to log in, see 2.2.1 Logging in to ITSLM - Manager.
-
The services that comprise ITSLM - Manager are dependent on each other. If you start JP1/ITSLM - Manager Service before starting JP1/ITSLM - Manager DB Service, JP1/ITSLM - Manager DB Service starts automatically. Similarly, if you start JP1/ITSLM - Manager Web Service before starting JP1/ITSLM - Manager Service, JP1/ITSLM - Manager Service starts automatically.
-
If you have changed the system configuration (including when you restore the system configuration after a change) while ITSLM - Manager is running, you must restart ITSLM - Manager.
-
If you link your ITSLM with Performance Management, information about the linkage with Performance Management that is defined in a system definition file takes effect when ITSLM - Manager is started. Therefore, if you want to edit the system definition file while ITSLM - Manager is running, first terminate ITSLM - Manager, edit the system definition file, and then restart ITSLM - Manager.
-
If ITSLM - Manager is terminated after service detection of monitored services has started, service detection of monitored services will remain stopped the next time ITSLM - Manager is started.
-
If ITSLM - Manager is terminated after monitoring of monitored services has started, the following processing takes place, depending on the managerStartMode value in ITSLM - Manager's system definition file (jp1itslm.properties):
-
When the managerStartMode property is omitted or normal is specified:
Monitoring of all monitored services whose monitoring had already started at the time of the previous termination processing is stopped.
-
When restart is specified for the managerStartMode property:
Monitoring of all monitored services whose monitoring had already started at the time of the previous termination processing is restarted in the normal status.
If you specify restart for the managerStartMode property and you restart monitoring of the monitored services, the monitoring of inactive ITSLM - UR's monitored services is also placed in started status, but collection of service performance information is restarted after the corresponding ITSLM - UR is started.
-