ITM OSLC Execute Automation Service Provider problems

Automation plan execution fails with the message "Native integration is not available"

Problem
When you run the automation plan, it fails, and the following message is displayed:
Native integration is not available
Solution
Check whether the following files are present in the TEPS lib directory:
  • For Windows operating system:
    ksh.dll
    kt1jniwrapper.dll
    kt1cmd.dll
    kt1v3.dll
  • For Linux operating system:
    libksh.so
    libkt1jniwrapper.so
    libkt1cmd.so
    libkt1v3.so
  • For AIX operating system:
    libksh.a
    libkt1jniwrapper.a
    libkt1cmd.a
    libkt1v3.a

If these files are not present in the TEPS lib directory, contact ITM support to obtain these latest libraries for the corresponding Operating System and architecture(32 bit vs 64 bit) and copy the files here.

Discovery fails when discovered a target host via ITM OSLC method

Problem

The following error appears, in SystemOut.log on the ITM TEPS Automation Provider host:

ERROR :com.ibm.cdb.integration.actions.Execute - Native integration call returned  error code: 0xf11e0011  

Description: Sql error: no rows returned.

Solution

Contact ITM support.

Automation plan execution fails with the message Native integration call returned error code: 0x1c Description: Hub is offline

Problem
When you run the automation plan, it fails, and the following message is displayed:
Native integration call returned error code: 0x1c Description: Hub is offline
Solution

Automation plan execution fails with the message: Native integration call returned error code: 0xf11e0004 Description: Could not read a file

Problem
When you run the automation plan, it fails, and the following message is displayed:
Native integration call returned error code: 0xf11e0004 Description: Could not read a file
Solution
  • If possible, install ITM fix for APAR IV65785.
  • Otherwise, edit the provider.properties file by setting the com.ibm.automationprovider.temp.remote.keepoutputs=true property. Command outputs might be left on the discovery targets, and you might have to remove them manually.

Automation plan execution fails with other error or errors

Problem
When you run the automation plan, it fails with errors different than the ones mentioned earlier in this topic.
Solution
  • Check the TEPS logs for errors, and if the error is self-explanatory, try to fix it.
  • Check whether the KT1 protocol is enabled and operative against the target system by running manually the getfile, putfile, and executecommand commands from the TEPS command line. See the ITM documentation on how to use the getfile, putfile, and executecommand commands.

Automation Provider does not display any automation plans

Problem
No automation plans are displayed in the Automation Provider.
Solution
  • Check whether the specified CURI initial URL is correct. The default value of the com.ibm.automationprovider.itm.curi.url property is http://localhost:15210.
  • If the CURI initial URL is correct, check whether you can access REST URL (http://localhost:15210/ibm/tivoli/rest/providers) by using the same credentials that you use to fetch plans. The reply contains the data of at least one provider. Use the id of this provider to query available TEMS servers and Agents.
  • Query available TEMS servers by running the following command (replace <provider_id> with the id of your provider):
    http://localhost:15210/ibm/tivoli/rest/providers/<provider_id>/datasources/TMSAgent.%26IBM.STATIC000/datasets/msys/items?properties=ORIGINNODE,AVAILABLE,VERSION,THRUNODE,NETADDR&condition=NODETYPE=1
  • Query available agents by running the following command (replace <provider_id> with the id of your provider):
    http://localhost:15210/ibm/tivoli/rest/providers/<provider_id>/datasources/TMSAgent.%26IBM.STATIC000/datasets/msys/items?properties=ORIGINNODE,AVAILABLE,VERSION,THRUNODE,NETADDR&condition=NODETYPE=0
Query results are returned in the JSON format. Make sure that at least one TEMS and its agents are reported as online.