in Data Management

SAP Data Services 4.x Upgrade Gotchas

With Data Services 3.2 being out of maintenance and headed for End of Life, I’ve been involved in more and more upgrades to Data Services 4.x. Depending on your requirements, both Data Services 4.1 and Data Services 4.2 are available as upgrade paths. There are some interesting differences and some gotchas that I’ve discovered through my experiences — I thought I’d try to sum them up here.

Introducing Information Platform Services

The big change in the 4.x release is that Data Services now requires either the BusinessObjects BI Platform or the new “BusinessObjects-lite” known as Information Platform Services, or IPS. That means that your system requirements, including hardware and OS, hinge not only on Data Services but also on BusinessObjects. As I covered previously, there is a complicated support table which shows which versions of Data Services work on which versions of BI.  Because of this, SAP now suggests going with the IPS and setting your Data Services deployment up as a standalone environment.

That doesn’t mean you can ignore the BI Platform requirements though. You’re going to want a machine with plenty of memory to handle the IPS installation. Also, check the Supported Platforms Guide in the PAM (4.1, 4.2), because there are some major differences. For example, Windows 2003 support was dropped for BI 4.1, but that release is the only one that supports Windows Server 2012 R2.

Prerequisites Hell

If you’re installing on a Windows Server 2003 or 2008 machine, make sure to check the Patch Level Requirements section of the Supported Platforms Guide. Depending on your OS version, you may need to install the Microsoft .NET Framework 3.5, Visual C++ 2005 Redistributable for x64, and a hotfix for Windows KB 941105 for both 32 and 64 bit.

Also, don’t forget to install both the 32 and 64 bit database drivers for all data sources that your Data Services jobs might use!

New Log Location

For some reason, the 4.x release includes a “feature” where the Data Services logs are saved to the C: drive, regardless of where Data Services is installed. This was a frustrating thing and it is not currently configurable within the application itself. Instead, I found it requires you to change the value of the DS_COMMON_DIR environment variable to move this directory. If you wish to move this directory (you probably do), stop Data Services, navigate to %DS_COMMON_DIR% in Explorer, and move the contents to the location of your choosing. Finally, update the DS_COMMON_DIR environment variable in your Windows System settings before restarting Data Services.

If you hate this as much as I do, be sure to head over to SAP Idea Place and promote the suggested change there.

For More Information

Again, for more on this, carefully read the Supported Platforms Guide for your selected Data Services release. Missing details here can cause you headaches when you go to begin your installation!

Data Services 4.1 Supported Platforms

Data Services 4.2 Supported Platforms

Free Web Intelligence Best Practices Guide

We put together a Best Practices Guide for Web Intelligence Development that includes over 20 pages of tips and techniques for developing business-ready reports. Plus we'll show you the common functions that have a negative impact on performance, how to create interactive reports, the best ways to standardize look-and-feel, and much more!


Powered by ConvertKit

Leave a Reply for Peeyush Cancel Reply

Write a Comment


  1. HI Ryan, I am trying to setup BODS client on a TS server and not sure which directory should be setup as the user level? is it DS_Common_DIR and should it be equal to DS_USER_DIR?