As mentioned in my previous article, I’m “celebrating” the release of SAP DS 4.2! There are so many of our customers stuck with SAP BI 4.0 + SAP DS 4.1 (some also with SAP IS 4.1) and can’t wait to go to SAP BI 4.1 and start benefiting from the new features.
Problem is SAP DS 4.1 and SAP IS 4.1 are of course incompatible with SAP BI 4.1… See SAP Note 1740516
For reference: SAP Data Services 4.2 and Information Steward 4.2 now “Release to Customer”: http://scn.sap.com/docs/DOC-50190
This article is Part 1: Installing SAP Data Services 4.2
Next, Part 2 will cover Post-Installation Configuration
Finally, I will cover the installation of SAP Data Services 4.2 SP01
Refer to the Product Availability Matrix (PAM): https://service.sap.com/sap/support/pam?hash=pvnr%3D67838200100900005703%26pt%3Dg%257Cd before starting the installation.
As always, it is useful to refer to:
- Installation Guide: http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_install_win_en.pdf
This tutorial has been written with the following environment:
- OS: Microsoft Windows Server 2012
- SAP BI: SAP BusinessObjects BI Platform 4.1 SP02
- Database: Sybase SQL Anywhere 12.0.1
Note: I could have of course use Microsoft SQL Server 2012 or others but I wanted to experiment with Sybase SQL Anywhere. And it takes very little RAM which is great for my VM on my poor laptop!
Step by Step Installation
Install SAP Data Services 4.2 SP01
Download the software at: http://service.sap.com/support > Software Downloads > Installations and Upgrades > A – Z Index > D > SAP Data Services > SAP Data Services 4.2
Extract 51047280_2.zip to a temporary directory E.g.: C:\Temp
Click: Yes or No
This is a new screen and I really like it. Looks like SAP is raising it’s hand here and accept they have created a problem which shouldn’t have occurred in the first place.
As mentioned above and elsewhere, this incompatibility issue is a real nightmare. I’m glad there is a better way. I’ll be investigating it and hopefully document this at a later time.
I accept the License Agreement: selected
Enter: license key
Enter the System name (aka CMS host name)
Enter the Administrator account password
I personally prefer to select Install without configuration. This allows the installation to run without trying to do too much and perhaps fail. We’ll deal with the creation of a Repository and the configuration of the Job Server after the installation.
Skip configuration: selected
It is recommended to run Data Service as a service account so the Job Server can read/write to network file locations fir instance. This is something that can be done later.
Select Use system account or Enter the credentials of your service account.
Click: Yes (when possible)
Screenshots Post Installation
Here are some post-installation screenshots.
Central Management Console (CMC) – Where you create and manage the repositories
Hope this was helpful.