Adding application support SQL files from Manage Tivoli Services on Linux or UNIX
About this task
To add application support SQL files to the hub monitoring server on z/OS®, complete this procedure.
Procedure
- Enable the GUI interface. Your Linux® or UNIX environment
might already have a GUI interface enabled. Otherwise, perform the
following tasks to enable it:
- Enable X11.
- Make sure you have access to a native X-term monitor or an X Window System emulator.
- If using an X Window System emulator, enable X11 access
to the X Window System server (command example:
xhost +
). - If using an X Window System emulator, set the display
environment variable to point to the X Window System server:
export DISPLAY=pc_ip_address:0
- Ensure that the hub monitoring server on z/OS is running.
- To start Manage Tivoli Monitoring Services,
go to the $CANDLEHOME bin directory (example:
/opt/IBM/ITM/bin
) on the system where you installed the application support data files, and run this command:./itmcmd manage &
A GUI window opens for Manage Tivoli® Monitoring Services.
- Select Actions > Install product support.
- On the Add Application Support to the TEMS window, select On a different computer and click OK.
- When you are prompted to ensure that the hub monitoring server is configured and running, click OK.
- On the Non-Resident TEMS Connection window, provide the
hub monitoring server TEMS
name (node ID), specify that it is a hub, select the communication
protocol to use in sending the application support SQL files to the
hub, and provide any values required by the selected communication
protocol. Then click OK to continue. If you made a note of the TEMS name you specified when you defined the runtime environment, find it now. Otherwise, you can find the TEMS name as the case-sensitive value of the CMS_NODEID environment variable in this location:
rhilev.rte.RKANPARU(KDSENV)
- On the next panel, select the products for which you want
to add application support. (If you want to collect historical data, be sure to select the Warehouse Proxy and Summarization and Pruning agents, in addition to any monitoring agents you have purchased.) Then specify whether you want to add the default managed system groups to situations when you process the application support files:
- All
- Add the default managed system groups to all applicable situations. Tip: Make this selection if you have never customized situations from previous releases.
- None
- Do not add the default managed system groups to any situation. Tip: Make this selection if you do not want any predefined managed system groups to be applied to your environment.
- New
- Add the default managed system groups to all situations from the application support packages
being installed for the first time. Modifications are not made to managed system groups in
previously upgraded application support packages. Tip: Make this selection if you have customized situations from previous releases and you want to protect your customized settings, but you want to apply the predefined managed system groups to new situations.
Make a selection and click OK. The SQL application support files are added to the hub monitoring server. This process might take several minutes, depending on the number of products.
Tip: Not all situations support the default managed group setting. You might have to define the distribution of some situations later from the Tivoli Enterprise Portal. For more information about managed system groups, see the IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide. - In Manage Tivoli Monitoring
Services, look for this message:
Remote seeding complete!
- Stop and restart the hub monitoring server.