Sie sind auf Seite 1von 10

SAP BusinessObjects Data Services 3.

2 March 2011 English

Upgrade Guide for SAP


Best Practices Migration for Data

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

Copyright
Copyright 2011 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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, xApps, xApp, 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 in several other countries all over the world. 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.

SAP AG

Page 2 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

Icons
Icon Meaning Caution Example Note Recommendation Syntax

Typographic Conventions
Type Style Example text Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Example text EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Example text

EXAMPLE TEXT Example text <Example text>

SAP AG

Page 3 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

Contents
Upgrade Guide for SAP Best Practices for Data Migration..........................................................5 1 Purpose......................................................................................................................................5 2 Getting Started...........................................................................................................................5 2.1 Prerequisites........................................................................................................................5 3 Manual Upgrade ........................................................................................................................6 3.1 Take a Backup of existing content.......................................................................................6 3.2 Create the Temp Repository................................................................................................6 3.3 Import the Backup atl File....................................................................................................6 3.4 Re-create the Original Repository........................................................................................6 3.5 Import Data Services ATL Code Files..................................................................................7 3.6 Reconcile Objects................................................................................................................8 3.7 Lookup Files......................................................................................................................10 3.8 Upgrade Migration Services Tool.......................................................................................10 4 Other Upgrade Activities..........................................................................................................10 5 Appendix 1 Upgrade Script....................................................................................................10

SAP AG

Page 4 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

Upgrade Guide for SAP Best Practices for Data Migration 1 Purpose
This guide provides you step-by-step information on upgrading your BPDM content to the latest version. It covers both all variants of the BPDM content (currently CRM and ERP) and is applicable to upgrades from any version to any version. Due to the nature of the BPDM content it is not possible to provide a fully automated update tool, this is primarily due to the fact that after installing the BPDM content all users will then amend the Dataflows and other objects. As the names and amendments made by each specific user is not known it is not possible to be 100% certain of identifying all these changes automatically. The basic principle of the upgrade process is as follow; 1. Take a backup this is a vital step and will allow you to roll-back changes if you encounter issues during the upgrade process 2. Load the latest version of the content 3. Reconcile new and old objects 4. Apply your changes to the new content The following sections will step through the process in detail. For the purposes of this guide we will use an example of upgrading the ERP content but the process for other content types is basically the same. SAP recommend that this process is performed first in a development environment and that once it is complete the client undertakes full regression testing before releasing into a production environment.

2 Getting Started
2.1 Prerequisites
A fully deployed and working BPDM environment A good working knowledge of Data Services it is strongly recommended that you do not attempt this process without knowledge of the Data Services toolset A new and empty database in your selected target (for this example we will use AIO_REPO_IDOC_TEMP) Assuming you used the folder C:\Migration to load the content originally, please rename this to C:\Migration_Old. Follow the instructions in SAP Note 1527151 to download the latest BPDM content e.g. AIO_BPDM_ERP.zip file. Extract the zip file into C:\Migration folder. This zip file contains the following content for automatic installation and manual installation: o Data Services ATL files

SAP AG

Page 5 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

o o o o o o

IDoc Mapping templates Data Migration Installation Wizard (for automatic installation) Migration Services Reporting Lookup files ERP test data

3 Manual Upgrade
This section provides the manual upgrade steps. The upgrade content does come with a script which will perform this process for you however this is recommended for advanced users only as it requires editing the script and any errors could cause data loss.

3.1 Take a Backup of existing content


It is very important to take a backup of your existing content. Typically your repository database would be backed up as part of the standard database backup process. However recovery from this can be time consuming so we will use a Data Services feature to take a snapshot of the code. 1. Open Data Services Designer and go into your content repository 2. In the local object library (bottom left panel) right click on white space and select Repository Export to File, then pick a location and select Save 3. Make sure you select a drive which is backed up so you have a permanent copy.

Select a filename which will help you remember when and why you created the file, e.g. AIO_REPO_IDOC_Full_Export_20110101_Start_Of_Upgrade.atl. If you encounter an error during the upgrade process then you can use this file to restore the content to your present state.

3.2 Create the Temp Repository


Use the Data Services Repository Manager to create the repository tables in your new temp repository (AIO_REPO_IDOC_TEMP). Ideally you should also associate this repository with the Data Services Job Server.

3.3 Import the Backup atl File


Open Data Services Designer and go into the temp repository, then select Tools Import from File and then select the file you created in step 3.1. This will import all of your customized content into the Temporary repository. As an additional check you could perform a validate on all the jobs to ensure they have been transferred properly.

3.4 Re-create the Original Repository


Use the Data Services Repository Manager to re-create the repository tables in your original repository (AIO_REPO_IDOC). Please note that this is a destructive process and it will

SAP AG

Page 6 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

overwrite all content in the repository so if you have not performed the above steps then extreme care is recommended

3.5 Import Data Services ATL Code Files


Use
All the code developed for the SAP Best Practices for Data Migration is delivered in ATL files (the native export file format produced by SAP BusinessObjects Data Services). These files need to be imported into their respective repositories so that the Data Migration content can be used within the toolset.

Prerequisites
In the C:\Migration\DataServicesATL folder, you have the following files: Filename AIO_REPO_IDOC_A_To_M_Without_Datastores.atl AIO_REPO_IDOC_N_To_Z_Without_Datastores.atl AIO_REPO_IDOC_IDocStatus_and_Recon.atl AIO_REPO_IDOC_Project.atl Description All IDoc Jobs for objects named A through M. All IDoc Jobs for objects named N through Z. IDoc status and Reconciliation code. Project file to create the project association or all of the jobs created in the first two files together. The lookup Job code required for both ERP and CRM lookup generation. The datastores file containing the DS_SAP, DS_AIO_REPO_IDOC, DS_STAGE and DS_STAGE_INIT datastores.

AIO_REPO_Lookup_Jobs.atl DataStores_MSSQL_and_Oracle.atl

Procedure
1. From the Windows menu, choose Start All Programs SAP BusinessObjects XI 3.2 SAP BusinessObjects Data Services Data Services Designer. The Designer prompts you for logon information associated with your repository database. 2. In the BusinessObjects Data Services Repository Login dialog box, enter the following: In Database type, choose Microsoft SQL Server In Database server name, enter <the computer name>\SAPAIOBPFDM or existing server holding repository database. In Database name, enter AIO_REPO_IDOC. Select Windows authentication.

3. Choose OK and your BusinessObjects Data Service Designer screen appears. 4. The following ATL files are to be imported for this repository. Follow the steps below for importing each ATL file in the order as shown below: a. DataStores_MSSQL_and_Oracle.atl

SAP AG

Page 7 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

b. AIO_REPO_Lookup_Jobs.atl c. AIO_REPO_IDOC_A_To_M_Without_Datastores.atl d. AIO_REPO_IDOC_N_To_Z_Without_Datastores.atl e. AIO_REPO_IDOC_IDocStatus_and_Recon.atl f. AIO_REPO_IDOC_Project.atl

5. From the Tools menu, choose Import from File. 6. In the Open Import File dialog box, browse to the location that you have saved the ATL files, select the ATL file and choose Open. It would only import the file if the imported version is the same as the Data Services version that you are running on your machine, or earlier. If the imported file does not match the Data Services version that you are running, you get a warning message, which you can ignore. If the Data Services version is older than the ATL file then you get an error message and would not be able to import the file. 7. Repeat steps 5 and 6 for all ATL files listed above in the order specified.

Importing the ATL file would take few minutes. After importing each ATL, we recommend to exit out of Designer and open it again (log back in) to start importing the next ATL file. 8. If the import is successful, the following projects must now be visible in the Project tab in the Local Object Library (bottom-left section) of the Designer screen. AIO_BPFDM_IDOC AIO_BPFDM_Lookups AIO_BPFDM_Reconciliation 9. In the Local Object Library section (bottom-left) of the screen, choose the Datastores . tab. You must see the Datastores listed in the Local Object Library (bottom-left section) of the Designer screen.

3.6 Reconcile Objects


At this point you will now have all of your original content in the repository AIO_REPO_IDOC_TEMP and the latest BPDM content in the repository AIO_REPO_IDOC.

This is a good point to take another backup export of the atl file. The next step is to apply your changed content to the latest version and to do this we will use a standard fetaure of Data Services. For this example we will work with an example which includes the following changes made to the standard content; Job_AIO_CustomerMaster_IDOC replicated to Job_XYZ_CustomerMaster_IDOC Dataflow DF_AIO_CustomerMasterBasicData_Map replicated to DF_XYZ_CustomerMasterBasicData_Map and mapped to flatfile CustMastBasicData.txt

SAP AG

Page 8 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

Whilst this is clearly a simple example it is sufficient to explain the process. In your environment you will need to identify the changes you have made and be ready to apply each in turn. 1. Open the temp repository (AIO_REPO_IDOC_TEMP) in Data Services Designer. 2. In the local object library panel, go to the job Job_XYZ_CustomerMaster_IDOC and right click and select Export. 3. Once all the objects have been transferred to the export panel you need to exclude the following objects; a. All User Functions b. All Pre-Supplied Formats, e.g. the pre-supplied Excel Workbooks such as IDoc_CUSTMASTBASIC c. Do not exclude any of your data sources here, so in our example we would keep flatfile CustMastBasicData.txt

d. All Tables but not the Datastores themselves, use Exclude Tree to exclude the Datastore and all Tables and then Include on the Datastore itself. e. This will restore your specific database settings but ensure any new table definitions are retained. f. Within the job tree itself, exclude any objects you have not modified, so in our example this sould be all Dataflows except DF_XYZ_CustomerMasterBasicData_Map.

4. This is an important step so please ensure all relevant objects have been excluded, otherwise you will overwrite the new content. 5. Once you are ready and have checked all settings, right click and select Export. 6. You will be asked to provide details for the target repository, in this case it is your original repository (AIO_REPO_IDOC) and then select Next. 7. At this point Data Services will compare the code you are trying to send to the code in the target repository and report the differences. In fact it will state whether each object will be created (i.e. it is new) or overwritten (i.e. it exists there already). 8. Please review each object in turn and ensure you are happy with the results, then select Next. 9. Once this process is completed repeat for all other changed objects. 10. When all objects have been transferred then please go into your original repository and validate each object.

Note that a validation error may occur where we have updated content you will need to review the error and take appropriate action. Again, it is recommended that a full backup is taken at this point.

SAP AG

Page 9 of 10

SAP Best Practices

Upgrade Guide for SAP Best Practices for Data Migration

3.7 Lookup Files


Ensure that the LKP_*.txt files, DEFAULT_NUMBER_RANGES.txt and all csv files are in the C:\Migration folder.

3.8 Upgrade Migration Services Tool


The latest BPDM content will probably contain an updated version of the Migration Services application, to upgrade this please follow these steps; 1. You may want to take a backup of your old version, to do this first stop Tomcat and then rename the folder C:\Program Files\Business Objects\Tomcat55\webapps/MigrationServices to C:\Program Files\Business Objects\Tomcat55\webapps/MigrationServices_Old 2. From C:\Migration, copy the MigrationServices folder into C:\Program Files\Business Objects\Tomcat55\webapps (or to the location of your Tomcat installation if it varies from the default settings). This would create a folder called /MigrationServices under the /webapps folder if successfully deployed. 3. Restart Tomcat. 4. This process will retain your current configuration settings.

4 Other Upgrade Activities


It is possible that any upgrade may contain additional or changed content, e.g. new lookup tables, new columns on tables, report updates, etc. In order to ensure your content is up to date please perform the following steps; 1. Re-run the Lookup jobs. 2. Re-run your object jobs. 3. Re-load the reporting content. For more detail on how to perform these steps please refer to the standard Quick Guide.

5 Appendix 1 Upgrade Script


Please note that use of this script is recommended only for advanced Data Services users, improper use could result in loss of data. This script is provided configured for a standard install on SQL Server using Windows Authentication, use on any other environment or configuration requires changes to be made. If you have a standard install (that is you deployed the original content using the Data Migration Installation Wizard) then you will just need to update the sever name in the script.

SAP AG

Page 10 of 10