Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version 4

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

Table of Contents

...

  • It is based on the “AL_RWJobLauncher.exe”. which is part of the Data Services Install.

  • The Task runs on Data Services for Windows and Linux.

  • The Universal Task provides the same error and trace information as the SAP Data Services Mgt. Console.

  • You can select different log-levels ; for example, Info and Debug.

  • You can configure all connection Parameters via the Universal Task.

  • For all Parameters an exception handling has been implemented.

  • Configurable Exit Code processing based on any information in the error.log file.

Current limitations

  • Currently,only “Enterprise Security” is supported.

...

FieldDescription

Agent

Universal Agent installed on the SAP Data Services Server.

This Agent runs the AL_RWJobLauncher.exe CLI.

Jobserver Hostname

Name of the Jobserver, which runs the Data Services Job. The Jobserver can be looked up in the SAP Data Service Management Console under: Administrator -> Batch

Job server port

Port of the Jobserver, which runs the Data Services Job. The Jobserver Port can be looked up in the SAP Data Service Management Console under: Administrator -> Batch

Path to AL_RWJobLauncher.exe

Location, where the AL_RWJobLauncher.exe is installed on the SAP Data Services Server.

Jobdir

Directory, where the Job execution files are exported to. The directory must contain the following files:

<Jobname>.txt and <jobname>.bat

Note: Those files are available only if the job Export job execution command has been performed in advance in the SAP Data Service Management Console.

In the example above, the files have the names:

  • loadinv.txt

  • loadinv.bat

To find the Location, open the data services Manager Tab: Run-time. The jobdir is the directory without pCache.

tracedir

Directory where the trace and log files are located.

The directory should contain trace/error files, which look as follows:

trace_MM_DD_YYYY_HH_MM_SS_...

error_MM_DD_YYYY_HH_MM_SS_...

Server_log_path

Path to the server log.

It should contain the file:

server_eventlog_YYYY-MM-DD.txt

loglevel

Logging settings DEBUG, INFO, WARNING, ERROR, CRITICAL

Poll interval

Interval, in seconds, for how often the Data Services Server is polled to get the current Job status.

Jobname

Name of the Data Services Job. It can be looked up in the SAP Data Service Management Console under: Administrator -> Batch

Log level (default is Inherited)

Universal Task logging settings: [Inherited | Trace | Debug | Info | Warn | Error | Severe]

Pattern Exit Code Mapping

This array field is used to decide about the exit code of the Task based on the information in the SAP BODS error.log file.

In Column Error Log Pattern , you define the search pattern.

The search pattern are evaluated, starting from the first Line up-to the last one, until the first search pattern matches. On the line where the search pattern matches, the corresponding Exit Code defined in the Column Exit Code is applied.

Example:

Image Added


SAP BODS error.log file:

Code Block
languagetext
linenumberstrue
- (14.2) 02-09-22 19:29:40 (W) (13816:14548) RUN-050802: |Data flow DF_PROJ_SB_LOADDATA|Transform File_Format_4541__AL_ReadFileMT_Process
                                                       Cannot convert data <xxxxx> into type <INTEGER>. Context: Column <Column zipcode>.

The match pattern in the table above will be applied starting from the first match pattern (*error*) until a match pattern succeeds.

In the example above, the 3rd match pattern, (W), is True, because (W) is in the error.log. Therefore, the Exit Code 1 Type “WARNING” will be applied to the Task.

Example forSAP Data Services Task

The following Task start the Data Service Job: loadinv on the server Walldorf.

SAP Data Services Processing Steps

...