SAP CPI for Data Services Connector 1.0.0.0

Introduction

Prerequisites

The Redwood SAP Cloud Platform Integration for Data Services Connector (HCIDS) is packaged as a separate CAR file.

Installation

To install:

  1. Create a Partition named HCIDS.

  2. Import the HCIDS CAR file .

Contents of the CAR file

The CAR file contains the following objects:

Object Type Name
Folder HCIDS.Redwood_HCIDS
Job Definition HCIDS.HCIDS_ImportJobTemplate
Job Definition HCIDS.HCIDS_ShowTasks
Job Definition HCIDS.HCIDS_RunTask
Job Definition HCIDS.HCIDS_Template
Library HCIDS.Redwood_SAP_HCIDS

Setup

HCIDS Job Definitions need their own Job Server and Queue. The Job Server and Queue must not be in Partition GLOBAL. By default, all the HCIDS objects are in the Partition HCIDS.

The username, password, and endpoint of the SAP HCIDS system should be configured in a Credential. This Credential must be created in the same Partition as the Queue. The virtual user of the Credential must match the Job Server name.

The Job Server HCIDS_ProcessServer is used as an example to set up the connection to an HCIDS system. In order to connect to more than one HCIDS system, duplicate the HCIDS_ProcessServer Job Server and create a new Queue and a credential of type SOAP for that HCIDS system. When creating the Credential, enter the username using the following format:

<username>|<organization>|<environment>

Use the password created in HCIDS as shown above. Use environment SANDBOX or PRODUCTION.

Finding HCIDS Tasks

To retrieve the list of job templates available for scheduling, open the Redwood_HCIDS Folder and run Redwood_HCIDS > HCIDS_ShowTasks.

You can filter the list by adding a Task name filter or a Project Name filter. Be sure to select the HCIDS_Queue Queue.

Once the Job has finished, click the stderr.log file in the Detail View, and you will see output like the following:

List output

Here you can find the value later used as template name - it's the value before either TASK or PROCESS.

Scheduling an HCIDS job

In the Redwood_HCIDS Folder, run the HCIDS_RunTask Job Definition.

Submit a Run Task

Here you can choose some configuration options on the HCIDS job as well as whether you want to retrieve some of the different types of output from the task once it is finished.

The Global Variables Parameter takes parameters as a comma separated list of parameter=value pairs. The parameter names need to omit the leading $.

Importing Tasks as Job Definitions

To import a task as a Job Definition, run the HCIDS_ImportJobTemplate Job Definition.

Submit Import Template

Here the task ID or a filter on task name or project name can be used to only import a selection of tasks. Also the Overwrite flag can be set to specify that existing Job Definitions can be overwritten. Also defaults can be set for the Job Output Parameters on the generated definitions.