Troubleshooting the SAP connection

If you are unable to submit SAP jobs using HCL Workload Automation after the R/3 configuration, perform the following tests:
  • Ensure that you can ping the SAP system from the HCL Workload Automation system. This shows basic network connectivity.
  • Note that using the SAP routers to access the R/3 system could exceed the size of internal buffers of the RFC library used to store the hostname of the SAP system. When this occurs, the hostname gets truncated, causing the connection to the R/3 system to fail. To work around this problem, do not fully qualify the name of the SAP routers or alternatively use the IP addresses.
  • Run the following telnet command to verify connectivity: 
    telnet systemname 33xx
    where systemname is the system name or IP address of the SAP server and xx is the SAP instance.

    If the command fails to complete, this means that communication between r3batch and the SAP application server is down.

  • Log on to the SAP system as an administrator and verify that the HCL Workload Automation RFC user (created in the Creating the HCL Workload Automation RFC user) exists.
  • If the SAP gateway truncates the connection string, replace the host name with the IP address.
  • If r3batch runs on an AIX® system that does not use U.S. English, make sure that the U.S. Language Environment® is installed on both the HCL Workload Automation workstation and the SAP database workstation. Otherwise the error BAD TEXTENV (or a similar error message) might appear in the dev_rfc trace file and connections to SAP fail.