Prerequisite patches and libraries for IBM InfoSphere Information Server Pack for SAP Applications 8.0

Content

Automatic prerequisite checking

The IBM Support Assistant Lite (ISALite) for InfoSphere Information Server tool can be used to automatically check for most prerequisites. It is recommended to run the tool before installation. It can be downloaded here.

Microsoft Windows prerequisites

Install the Microsoft security patch for Microsoft Visual C++ 2005 Service Pack 1 on all supported Windows operating systems before installing the Pack. If you do not install the security patch, an error is reported when you install the Pack.

The patch resolves a conflict between the SAP RFC SDK libraries that are built with Microsoft Visual C++ 2005 and the Microsoft Visual C++ 2005 redistributable. The patch works independently from any existing Microsoft Visual Studio installations on the same machine.

For more information about the security patch, see the details page in Microsoft Download Center or use this direct link.

Post-installation patches

Apply this patch after installing the Pack:

• Patch for APAR JR55426 (Engine tier)
  Resolves an issue with ABAP stage aborting when selecting columns of VARCHAR type with some rows containing no data (ref. APAR JR55426).
  The patch is available here. For more information, see the Support Flash.

Required SAP SDK libraries

You must download and install the following SAP SDKs from the SAP Support Portal:

• SAP NetWeaver RFC SDK 7.20, also referred to as NW RFC SDK
• SAP RFC SDK 7.20, also referred to as Classic RFC SDK (non-Unicode version, patch level 2 is required)
• SAP Java Connector 3.0, also referred to as SAP JCo
  (including the platform-independent IDoc class library)

On Server tier computers, install all three SDKs. On Client tier computers, only the SAP NetWeaver RFC SDK is required.

The following tables list the required library files for each supported operating system.

SAP NetWeaver RFC SDK 7.20

Operating system	Files
Windows	icudt34.dll icuin34.dll icuuc34.dll libicudecnumber.dll libsapucum.dll sapnwrfc.dll
AIX	libicudata34.a libicui18n34.a libicuuc34.a libicudecnumber.so libsapnwrfc.so libsapucum.so
Linux, Solaris	libicudata.so.34 libicui18n.so.34 libicuuc.so.34 libicudecnumber.so libsapnwrfc.so libsapucum.so

For information about downloading and installing the SAP NetWeaver RFC SDK, see SAP Note 1025361: Support and Availability of the SAP NetWeaver RFC Library.

SAP Classic (non-Unicode) RFC SDK 7.20

Operating system	Files
Windows	librfc32.dll
AIX	librfc.a librfccm.o librfccm.so libsapu16_mt.so
Linux, Solaris	librfc.a librfccm.so libsapu16_mt.so

For information about downloading and installing the SAP Classic RFC SDK, see SAP Note 27517: Installing RFC SDK.
Important note: This SDK may not be available in the SAP download catalog. Please use the SAP note mentioned to download - it provides direct download links.

SAP Java Connector (JCo) 3.0

Operating system	Files
Windows	sapidoc3.jar(1) sapjco3.dll sapjco3.jar
AIX, Linux, Solaris	libsapjco3.so sapidoc3.jar sapjco3.jar

For information about downloading and installing SAP JCo, see SAP Note 1672418: Downloading the SAP JCo.
Note (1): this file is a new requirement as compared to previous Pack version (7.1) and it's needed for the new Delta Extract stage.

File locations

• On client computers, copy the SAP NetWeaver RFC SDK files to
  <ISHome>/Clients/Classic
• On server computers, copy the SAP NetWeaver RFC SDK, SAP Classic RFC SDK and SAP JCo SDK files to <ISHome>/Server/DSComponents/bin

<ISHome> denotes the installation directory of InfoSphere Information Server.

Notes

• Always use the latest SAP libraries (patch levels). The patch level of the IDoc Class library (sapidoc3.jar) has to be equal or less than the patch level of SAP Java Connector (sapjco3.jar)
  Note : The patch level can be determined by using the command: “java -jar <jar-file>”
  (For running this command, it is important that JAVA should be installed on the machine with JAVA_HOME path set to an appropriate JDK installation directory). The patch level is mentioned under the heading: “Specification-Version” as last number e.g. Specification-Version: 3.0.12, specifies the SAP JCo used is of version 3.0 with Patch level = 12.
• The bitness of the SAP libraries (32-bit or 64-bit) needs to match the bitness of the Information Server installation. On Windows systems, use 32-bit libraries on all systems (including 64-bit systems) since Information Server is a 32-bit application on Windows.
  Note: if you need to determine the bitness and version of existing SAP SDK libraries, see this document for instructions.
• On UNIX or Linux computers, make sure that the operating system user that the InfoSphere Information Server user is mapped to has read and write permissions on the directories that the files are copied to. To confirm the user mapping, open the IBM InfoSphere Information Server Web Console (typically, http://<servername>:9080/ibm/iis/console) and click Administration > Domain Management > Engine Credentials.

Prerequisites for the IBM InfoSphere Data Architect components

The Pack includes optional IBM InfoSphere Data Architect components: InfoSphere Rapid Modeler for SAP Applications and InfoSphere Rapid Generator for SAP Applications. These have the following prerequisites:

• InfoSphere Data Architect Patch
  
  Patch for APAR JR45538
  This patch resolves an issue with IBM InfoSphere Data Architect 8.5 that can lead to errors when converting logical data models to physical data models. Because this functionality is necessary for Rapid Modeler, you must install this patch. The patch is available on Fix Central (Fix ID: 8500-Information_Management-IDA-Multiplatform-20151015_JR45538) or via this direct link.

• SAP Java Connector SDK (JCo) 3.0
  
  Note: The bitness of the SAP JCo library (32-bit or 64-bit) needs to match the bitness of the InfoSphere Data Architect installation.
  You can place the SAP JCo library files in any folder on the client computer. Rapid Modeler / Generator can be configured to load the libraries from any folder using the Preferences dialog.