importing the transport files for sap integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

Importing the Transport Files for

the SAP Integrated Solutions XI 3.1

Applies to:

SAP BusinessObjects XI 3.1.

For more information, visit the Business Objects homepage.

Summary

This document explains how to apply the transport files that come with the Integrated SAP Solutions XI3.1 (aka SAP Integration Kit) using the transport management (STMS).

Author: Roland Hoeller

Company: SAP

Created on: 29 May 2010

Author Bio

Roland works at SAP as an SAP BusinessObjects Lead Support Engineer. He has experience in both SAP BW and SAP BusinessObjects XI 3.1.

http://www.sdn.sap.com/irj/boc

Importing the Transport Files for the SAP Integrated Solutions XI 3.1


© 2010 SAP AG 2

Table of Contents

Introduction ......................................................................................................................................................... 3

Transport Files for Integrated SAP Solutions XI3.1 ............................................................................................ 3

Where can the transport files for the Integrated SAP Solutions XI3.1 be found? ........................................... 3

What transport files are needed? .................................................................................................................... 4

Importing the transport Files ............................................................................................................................... 7

Related Content ................................................................................................................................................ 15

Copyright........................................................................................................................................................... 16



© 2010 SAP AG 3

Introduction

This document explains how to apply the transport files that come with the Integrated SAP Solutions XI3.1 (aka SAP Integration Kit) using the transport management (STMS).

Transport Files for Integrated SAP Solutions XI3.1

The Integrated SAP Solutions XI3.1 come with a set of a transport files which contain content like programs and function groups that allow the Business Objects system to interact with SAP systems. Most of the transport files are used for Crystal Reports connectivity but there is also one for the BusinessObjects SAP security plug-in, which enables the SAP authentication for the Central Management Console (CMC) and InfoView.

The transport files should always correspond to the version of the BusinessObjects software hence should be updated when a new BusinessObjects FixPack or Service Pack is installed.

Where can the transport files for the Integrated SAP Solutions XI3.1 be found?

The transport files for the Integrated SAP Solutions XI3.1 are delivered with the Integrated SAP Solutions XI3.1’s installation files. Additionally an updated set of transport files comes with each FixPack and Service Pack for the Integrated SAP Solutions XI3.1.

The transport files can be found in the Transports folder of the installation root for either the full install of the Integrated SAP Solutions XI3.1 or one of its FixPacks or Service Packs.

For this white paper the transport files from the Service Pack 3 for the Integrated SAP Solutions XI3.1 are used.

Locate the Transports folder in the Service Pack 3 for the Integrated SAP Solutions XI3.1’s root directory.



© 2010 SAP AG 4

What transport files are needed?

Please read the transports_yourLanguage.txt in the Transports folder to determine what version of the transport files is needed. In this case, the SAP system is running on Basis higher than 6.20 and therefore the Unicode compatible transport files have to be used.

To check the SAP Basis version, click SAP GUI > System > Status.



© 2010 SAP AG 5

The Basis version for this SAP system is SAP_Basis 7.01.

The system used in this white paper is a BW system, and the following transports are needed to enable the Crystal Reports connectivity and the SAP authentication in BusinessObjects Enterprise.

Authentication Helpers transport (K900691.r21 and R900691.r21)

Content Administration transport (K900692.r21 and R900692.r21)

Personalization transport (K900693.r21 and R900693.r21)

MDX Query Connectivity transport (K900694.r21 and R900694.r21)

ODS Connectivity transport (K900695.r21 and R900695.r21)

For more information about the transports files please consult the BusinessObjects XI Integration for SAP Solutions Installation and Administration Guide.

In the Transports folder is a folder called Unicode_compatible which contains the Unicode compatible transport files. The transports consists of two parts the cofiles and the corresponding data files which are located in the respective folder.



© 2010 SAP AG 6

Copy the content of the cofiles and data folders from the installation files to the corresponding folders on the SAP server. There is no need to unzip the files.

After copying, the transport files must not be write-protected. This can be checked by the Read-only attribute on the files’ properties (right-click Properties).



© 2010 SAP AG 7

Importing the transport Files

The transport files are imported within the SAPTransport Management System (stms). The user importing the transport files needs to have the necessary permissions to access the Transport Management System.



© 2010 SAP AG 8

1. Click the Import Overview icon.



© 2010 SAP AG 9

2. Choose the system for which you want to import the transports.



© 2010 SAP AG 10

3. Click Extras > Other Requests > Add.

4. Click F4 help to get a list of the available transport files.



© 2010 SAP AG 11

5. Choose the Authentication Helpers transport (K900691.r21 and R900691.r21).

6. Click Continue. The transport appears in the list.



© 2010 SAP AG 12

7. Click Yes.

8. Select the transport and import it through the Menu: Request > Import or the icon Import Request or by pressing CTRL + F11.



© 2010 SAP AG 13

9. Select the correct client for the system.

10. Click Yes.

Now the import queue should look as below:



© 2010 SAP AG 14

Repeat the steps (Add Request and Import Transport File) for the following transports:

Content Administration transport (K900692.r21 and R900692.r21)

Personalization transport (K900693.r21 and R900693.r21)

MDX Query Connectivity transport (K900694.r21 and R900694.r21)

ODS Connectivity transport (K900695.r21 and R900695.r21)

After completing the above, the list should appear as follows:

If there are warnings about the field length, you can safely ignore them.



© 2010 SAP AG 15

Related Content

Please have look at the following related SAP notes:

1275684 - How to remove the objects generated by the SAP Business Objects SAP Integration Kit's transport files

1420152 - How to identify the version of the transport files for the Integrated SAP Solutions XI3.1 and onwards

1475195 - How to manage the transport files for different versions of the Integrated SAP Solutions XI 3.x (aka SAP Integration Kit) connecting to one SAP server?

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3132373536383426





© 2010 SAP AG 16

Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

importing the transport files for sap integration

Documents