Home
Scheduling Job Integrations with HCL Workload Automation
Integration with SAP
Access method for SAP
The SAP R/3 batch access method enables communication between an external SAP R/3 system and HCL Workload Automation and provides a single point of entry for automating the launching of jobs, monitoring the status of jobs and managing exceptions and recovery.
Troubleshooting
Learn what to do if you get any problems while installing or using HCL Workload Automation access methods or plug-ins.
Troubleshooting the SAP connection

Scheduling Job Integrations with HCL Workload Automation
- Job integrations to extend workload scheduling capabilities
- Access methods
- Integration with SAP
  - Introducing HCL Workload Automation for SAP
    Improve SAP operations and enable business growth with HCL Workload Automation.
  - Access method for SAP
    The SAP R/3 batch access method enables communication between an external SAP R/3 system and HCL Workload Automation and provides a single point of entry for automating the launching of jobs, monitoring the status of jobs and managing exceptions and recovery.
    - Scheduling process for the agent workstation hosting the r3batch access method
    - Roles and responsibilities
    - Configuring user authorization (Security file)
    - Configuring the SAP environment
      You must configure the SAP environment before using the SAP access method.
    - Configuring the SAP access method
      This section provides detailed information about the SAP options file creation.
    - Defining SAP jobs
      You must define some jobs to be able to run jobs on an SAP workstation from HCL Workload Automation.
    - Managing SAP jobs
      This section describes how to manage SAP jobs.
    - Defining SAP jobs dynamically
      This section describes how to create and submit SAP jobs dynamically without creating or referencing predefined job templates.
    - Defining conditions and criteria
      HCL Workload Automation accesses the Computer Center Management System (CCMS) Background Processing components of SAP systems through the BC-XBP interface to provide additional capabilities from the Dynamic Workload Console, one of those being the Criteria Manager.
    - Using the BDC Wait option
      By using the Batch Data Collector (BDC) Wait option, you can specify that a SAP job launched by HCL Workload Automation is not to be considered complete until all of its BDC sessions have completed.
    - Job interception and parent-child features
      This section describes how the job interception and parent-child features of BC-XBP 2.0 and 3.0 are supported by HCL Workload Automation.
    - Using Business Information Warehouse
      Business Information Warehouse (BIW) is a data warehouse solution tailored to SAP.
    - Job throttling feature
      Learn how the job throttling feature helps you to improve the efficiency of your scheduling on SAP systems and reduce the batch window for your SAP jobs to a minimum.
    - Exporting SAP factory calendars
      This section describes how to export SAP factory calendars into a file format that can be processed by the HCL Workload Automation composer command line, to add the exported calendar definitions to the HCL Workload Automation database.
    - Defining internetwork dependencies and event rules based on SAP background events
      This section describes how to define internetwork dependencies and event rules for HCL Workload Automation based on SAP background events.
    - Defining event rules based on IDoc records
      You can use HCL Workload Automation to monitor Intermediate Document (IDoc) records in SAP systems and forward events to the HCL Workload Automation event integration framework.
    - Defining event rules based on CCMS Monitoring Architecture alerts
      Use CCMS functions to check the performance of the various SAP system components, diagnose potential problems, and be alerted about error and warning conditions.
    - National Language support
      The National Language support feature allows you to install SAP on a localized HCL Workload Automation workstation and use localized characters for HCL Workload Automation job names, job streams, and SAP variants.
    - Troubleshooting
      Learn what to do if you get any problems while installing or using HCL Workload Automation access methods or plug-ins.
      - Troubleshooting the SAP connection
      - Other known problems
  - Scheduling jobs on HCL Workload Automation from SAP Solution Manager
    HCL Workload Automation and SAP Solution Manager are integrated to allow the HCL Workload Automation engine to run the job scheduling tasks available from the Solution Manager user interface.

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.