SAP Data Services 4.1

7/27/2019 SAP Data Services 4.1

http://slidepdf.com/reader/full/sap-data-services-41 1/391







This slide compares the classic Data Services installer (which was the only

option in 4.0) with the new “rapid deployment” installer introduced in SAP Data

Services 4.1.

The new Rapid Deployment installer combines the Data Services and

Information Platform installer, and is intended for use in combination with

HANA. The installer is running on SUSE Linux only. For other use cases,

customers can still use the classic installer, which still exists in SAP Data

Services 4.1, for any type of install.

4



The Rapid Deployment installer is available in the same location as the other

Data Services downloads. It consists of six separate downloads, each less then

1 GB. Customers still need to download the Windows client separately, as theRapid Deployment installer is only installing the server components (on SUSE

Linux).

Note: the names will slightly change (no “CUV” prefix) when SAP Data Services

4.1 is officially released.

5



Step 1: Start the installation

Note: The final screens will look slightly different; the screenshots used arefrom a pre-RTC version.

6



Step 2: Requires no data entry; it is just a summary on which components will

get installed, which versions of these components, which repository databases

used and which port numbers used.

7



Step 3: Preview the license agreement and enter the Data Services product

license key.

8



Step 4: The only screen where user input is needed. The password for the

Administrator in the Information Platform Services CMS (Central Management

Server) needs to be set. This password is needed later to log onto the DataServices UI.

The Data Services repository will be stored in HANA, so the HANA connection

parameters are required here.

Note: We no longer need the port number for the HANA box, just the instance

number. The port number is calculated as 3<instance number>15 .

The HANA ODBC driver field is optional; the installer will bundle a HANA driver,

but we provide the option for customers to use the latest HANA revision andpoint to their local driver.

9



Step 5: Final step with the installation progress and some links at the end to get

started.

10





Important: SAP Data Services 4.1 requires Information platform services 4.0

Feature Pack 3 (or the full BI 4.0 FP3).

The upgrade from 4.0 to 4.1 should be simple. There is no need to uninstall the

previous version; the new version can be installed on top of the previous

version, which will upgrade the binaries, but keep all existing configuration.

The following slides will highlight five behavior changes that customers should

be aware of.

12



For increased security, by default the (database) repository password is not

sent to the Designer client. In order to avoid the password prompt and having

to type in the database password at each login, ask your Administrator to grantthe right to send the password (and revert to the 4.0 behavior).

Data Services 4.0 follows the secure by default principle here, but provides the

option to loosen security for better usability.

13



This is a screenshot of the password prompt popup that will appear for

users/repositories that have not been granted the right to send the password.

14



This is a screenshot from the CMC (Central Management Console), where you

can grant the right for a repository/user combination to retrieve the password to

avoid the password prompt in Designer.

15



For better alignment with Microsoft Windows guidelines, locations for the

configuration and log files have changed. There are no manual upgrade steps

required for this; the installer will take care of moving these files.

16



The CMS metadata integrator (to collect impact and lineage for universes and

reports in BI) is removed from Data Services 4.1. Existing customers can

continue to use the previous versions of the CMS integrator with SAP DataServices 4.1, but we recommend to use Metadata Management in Information

Steward for end-to-end metadata management.

Impact and lineage for Data Services objects remains available in the

Management Console.

17



JDBC drivers for Oracle and mySQL are no longer bundled with SAP Data

Services 4.1. If you are using an Oracle or mySQL repository, you will get

prompted for the JDBC driver’s location during the installation.

18



New functions used by Data Services to extract and load into SAP ERP/BW are

shipped with this release. Because we moved from the custom Z namespace to

a dedicated namespace /BODS/, installing the new functions is required andthe old functions in the Z namespace will not work.

After installing the functions, additional configuration is needed to set the

correct authorizations for these functions.

19





The monitor sample rate changed from a row-based trigger to a time-based

trigger.

21



The time-based monitor sample rate will make it easier to follow what’s

happening in the monitor log. But identifying bottlenecks (why is my load slow?)

can still be tricky. So we added some additional information to the logs (seenext slide)

22



Three new columns on CPU usage and input buffer are added to the monitor

log. The additional columns are visible only in the log files, not inside Designer.

The visualization aspect will be added in a later release; for now it’s moreimportant to just make the data available so that

support/consultants/partners/customers can get more insight into what’s

happening in the engine.

23



Here is an example of a monitor file in Excel with additional calculations on

input buffer size.

The input buffer is a mechanism to pass rows from one transform (thread) to

the next transform.

An empty buffer means that the transform is fast in processing all available

rows, and is waiting for the previous transform to get new records.

A full buffer means that either the transform is slow and cannot keep up

with processing the rows, or there is a later transform that has a full buffer

as well and the transform is just waiting before it can pass the rows to the

next transform.

The input buffer size is expressed with two values separated with a colon

[Buffer used:Buffer available], for example:

0:5 means the buffer has a size of max 5 rows and there are no rows in the

buffer.

4:5 means the buffer has a size of max 5 rows and 4 rows are in the buffer

waiting to get processed.

24



Here is an example of a graphical representation of the monitor log. In this case

the CPU used by the thread is visualized. It is clear that one transform (Query1)

is doing all the processing; the two other threads (reader & loader) are idlemost of the time.

25





Note: Dates are subject to change.

This slide lists the dependencies between Solution Manager and Data

Services. Customers need at least Solution Manager 7.1 SP3. Support for SAPData Services 4.1 is planned for Solution Manager 7.1 SP6.

27



Solution manager will get information from Data Services in three different

ways. Additional configuration is needed for all three of these.

28



This architecture diagram illustrates the different means Solution Manager uses

to get data from Data Services:

SAP Host Agent collects the host’s CPU & memory statistics. The SAPDiagnostic agent will also access log and configuration files from Data

Services.

Data Services sends runtime statistics directly to the SAP Diagnostic

Agent.

Dedicated Data Services jobs run on the DS server and write information to

log files, which are picked up by the SAP Diagnostic agent.

Solution manager is helping customers to get a unified view on all their SAP

solutions, but it also provides a powerful tool for SAP support to get diagnostic

information on the customer’s system while doing root cause analysis.

For Data Services we are still in the early changes of Solution Manager

integration; more enhancements will be mode from both sides (Data Services +

Solution Manager content) in future releases.

29



Before being able to monitor Data Services in Solution Manager, you need to

set up Data Services as a managed system.

Once configured there are two main work centers where you can see DataServices content in Solution Manager: Root Cause Analysis and System

Monitoring.

The next slides show a few screenshots about the content available in these

work centers.

30



The E2E Workload Analysis application gives an overview of the Data Services

system performances in the long run. Thanks to the Business Warehouse (BW)

functionality embedded in Solution Manager, you can get a performance trendof a complex Data Services system with graphics and KPIs.

With Solution Manager’s Change Analysis, you are able to check over an

extended period of time the amount of configuration changes, the Data

Services components impacted by those changes, as well as the trends.

CA Wily Introscope is a performance monitoring infrastructure integrated with

Solution Manager. With Introscope WorkStation or Introscope WebView, you

can monitor the average response time of Data Services components involvedin main business processes

31



There are memory consumption and CPU utilization views for each jobserver,

job, and dataflow. The available subviews can tell you which jobserver, job, or

dataflow consumes most of the hardware resources. The unit of memory isbytes.

32



Data Services KPIs are collected through the predefined job that is scheduled

in the Data Services repository and send information on objects used in the

repository, as well as operational information like number of rows read/loadedfor each dataflow.

33



Change analysis collects snapshots of the configurations in Data Services and

shows the number of changes made over time.

34



CA Wily Introscope provides a different UI with access to performance

dashboards on CPU and memory utilization.

35



The other work center in Solution Manager where Data Services content will

become available is in System Monitoring. This will be added in Solution

Manager 7.1 SP5 and further enhanced with SAP Data Services 4.1 support inSolution Manager 7.1 SP6.

Here you can monitor the system in real time and set thresholds and alerts.

36



More information is available on Service Marketplace for SAP Enterprise

Support customers.

37





Documents

SAP Data Services 4.1