Starting the monitoring system

All monitoring components are installed and configured. You can start the monitoring system and monitor the application status either on Linux via TEP or on z/OS via enhanced 3270UI.

About this task

Note: To guarantee the monitoring components work properly, start the Hub TEMS, TEPS, and TEP on the Linux server first, and then start the started tasks of the Remote TEMS, enhanced 3270UI, and OMEGAMON for JVM agent on z/OS.

Procedure

Start the TEMS, TEP, and TEPS on the Linux server.
1. On the Linux server, browse to the directory where you installed the IBM Tivoli Monitoring: ITMinstall_dir/bin.
2. Start the monitoring server.
  Run the following command to start the monitoring server:
```
./itmcmd server start tems_name
```
3. Start the portal server.
  Run the following command to start the portal server:
```
./itmcmd agent start cq
```
4. Start the portal client.
  Run the following command to start the portal client:
```
./itmcmd agent start cj
```
On z/OS, start the started tasks of the Remote TEMS, enhanced 3270UI, and OMEGAMON for JVM agent by running the following commands.
```
S IBMDS
S IBMTOM
S IBMJJ
```
In the RKLVLOG for the monitoring server address space, look for the following messages to indicate successful startup:
```
KDSMA001   Tivoli Enterprise Monitoring Server (TEMS) data collection server started.
KO4SRV032  Tivoli Enterprise Monitoring Server (TEMS) startup complete.
```
Look also for the following messages to indicate successful establishment of a communications path by the local location broker:
```
KDSNC007   Local Location Broker is active
KDSNC004   Bind of local location broker complete= protocol_name:address
```
Also look for the messages that indicate successful connection between the OMEGAMON for JVM agent and the local Remote TEMS.
From the Remote TEMS started task IBMDS:
```
Remote node <KJJ:SYSA:JVM> is ON-LINE
```
From the OMEGAMON for JVM agent started task IBMJJ:
```
Starting Enterprise situation HEARTBEAT
No action is required., Producer (IRA Constructor)
Timer for owner KPX.RNODESTS started. 
Connecting to CMS SYSA:CMS
```

Results

The monitoring system is started.

What to do next

You can access the monitoring system through TEP or enhanced 3270UI:

To log in to the TEP client, you can use the default user ID sysadmin. No password is required to log on to the portal client unless the hub monitoring server was configured to enable Security: Validate User.
To log in to the enhanced 3270UI, start a new VTAM 3270 session and run the following command at the VTAM logon panel.
```
LOGON APPLID(applid)
```
where applid is the VTAM Applid of the enhanced 3270UI address space. Then enter your user ID and password and press Enter.