Steps to configure ITM and TADDM integration
WaleShoyinka 11000054C1 Visits (8868)
TADDM ITM integration using the OSLC
Introduction on why you will want to integrate ITM to TADDAM.
In this blog I will explain and provide screenshorts of what happenes at each stage of setting up the integration. I will also provide the XML files generated during the TADDM scripts executions.
Before you start you will need the following prereqs.
If you are using Windows 7 and above you will need
1. PowerShell version 2+
2. TEMS Soap URL
3. Check that you can connect to both TEMS and TEPS
The TADDM and ITM integration using the OSLC is done in two stages
Check and configure both TEMS and TEPS and during this process you enable the Dashboard data provider for ITM.
This is where you will setup and execute the TADDM scripts so that you can connect or integrare links to the ITM TEMS and TEPS.
TEMS and TEPS configuration
Stage 1 - Reconfiguring TEMS and TEPS
The TEMS and TEPS configuration is best done using the Manage Tivoli Enterprise Monitoring Services (MTEMS) GUI.
For the Windows OS, start the ITM kinconfig .exe process to bring up he Manage Tivoli Enterprise Monitoring Services (MTEMS) GUI.
For Unix/Linux you can start the MTEMS GUI using the CLI command "./itmcmd manage"
a. Highlight the component ie TEMS
Finally accept and OK the configuration.
TEPS: - Reconfiguration using the MTEMS.
Stage 2 - Executing TADDAM Scripts and Configuration
This is the execution of two main TADDAM scripts to help setup the integration of TADDAM to ITM.
These two scripts are deals with
1. Configure the provider.properties file.
On ITM TEMS host -Enable KT1 commands (tacmd get/put/execute) by running one of the
- Linux operating system:
When completed you should see the following lines at the end of the script execution.
INFO: Stopping ITM TEPS...
2. Run the automation_provider script from ITM TEPS host
You execute the automation _provider script on your server as thus
- Unix/Linux operating system:
- Windows operating system:
An important point to note here is that even if a provider.properties file is created prior to running the automation_provider script as per the documentation, this is ignored and a 'default' provider.properties is created in the ITM TEPS config path
You will have to locate this file, manually make the changes to the parameters and then restart the TEPS for the file to be effective.
You should also consider the following changes to the TADDM online documentation:
Configuring the provider.properties file
You can optionally configure the provider.properties file by setting the following parameters:
If you intend to run a discovery on the RTEMS then ensure that you have the parameter "KT1