2_contentmigration

7/31/2019 2_ContentMigration

http://slidepdf.com/reader/full/2contentmigration 1/11

Migration of BusinessPackages



SAP Online Help 02.08.2004

Copyright

© Copyright 2004 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 bechanged without prior notice.

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

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks 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 productspecifications 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, withoutrepresentation 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 andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.

Migration of Business Packages 646 2




Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help → General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library .

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,

and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.





Migration of Business Packages ............................................................................................... 5 Preparing For Business Package Migration .......................................................................... 6 Migrating Business Packages................................................................................................ 6

Import Filter for Content Objects ........................................................................................ 7 Copying the Import Filter File to the Portal Content Directory........................................ 9

Compatibility Package for Knowledge Management ......................................................... 9 Modifications to the Business Package for Communication ............................................ 10 Modifications to the Business Package for Portal Users ................................................. 10





Migration of Business Packages

PurposeWhen you upgrade your portal installation from SAP Enterprise Portal 5.0 to SAP NetWeaver ’04, you can migrate your existing content without losing your personalization settings.

This documentation explains which special points you must follow during the migration of business packages.

Prerequisites

• In addition to your SAP Enterprise Portal 5.0, you have installed a SAP NetWeaver ‘04.

• You have installed the SAP Java Connector (JCo) Proxy Runtime, Release 2.0.8 or higher. For more information about the SAP JCo Proxy Runtime, see SAP Note595987.

To be able to complete the migration, you must check the release status of each businesspackage. Some business packages are not released for migration. If you are planning tomigrate business packages, you must bear in mind that often only one release of a 5.0business package is released for SAP NetWeaver ‘04. Usually, this is the latest release of abusiness package.

A business package has one of the following statuses:

• 5.0 business packages that are released for SAP NetWeaver ‘04.

• 5.0 business packages that are released for SAP NetWeaver ’04 with additionallanguages.

• 5.0 business packages that are not released for SAP NetWeaver ‘04.

For the migration you require the release of the business package that isreleased for migration. If you have not installed this particular release of the business package, you must update the business package beforemigrating it.

The Business Package for Projects is available in the releases 50.1,50.2, and 50.3. Only release 50.3 is released for SAP NetWeaver ’04;you can use only release 50.3 for the migration.

For current information about the release status of business packages,see SAP collective note 642775.

Process Flow

You must work through the following steps to migrate business packages:...

1. If necessary, prepare for business package migration.

2. Migrate the actual business packages.

3. If necessary, update the business packages (in the case of business packages withadditional languages).





Preparing For Business Package Migration

Process FlowIn the migration of 5.0 business packages, we distinguish between the following types of business packages:

• Business packages without additional languages

• Business packages with additional languages

There are different processes for each type.

Preparations for Business Packages Without Additional Languages

In this case, the preparation consists of upgrading and installing the correct SAP Enterprise

Portal and business package releases. See the prerequisites in migration of businesspackages [Page 1].

Preparations for Business Packages with Additional Languages

If you are planning to migrate 5.0 business packages with additional languages to SAPNetWeaver ‘04, you must work through the following steps:

1. Upgrade your SAP Enterprise Portal 5.0 installation to the release of the businesspackage that is released for SAP NetWeaver ‘04.

2. Migrate the business package to SAP NetWeaver ‘04.

3. Import the business package with additional languages to SAP NetWeaver ‘04.If you use this procedure, the personalization information and customizing is saved during themigration.

Migrating Business Packages

Prerequisites

You must have completed the preparations [] for migrating business packages.

Process Flow

You must heed the following points during the migration:

• Using the Import Filter [Page 7] for content objects

• Modifications to Knowledge Management using the Compatibility Package for Knowledge Management

• Modifications to the Business Package for Communication

• Modifications to the Business Package for Portal Users

• Effects on the system landscape





The system landscape connects portal content to the back-end systems.

For more information about the system landscape, see the SAP Help Portal at

help.sap.com → SAP NetWeaver → SAP Enterprise Portal → Enterprise Portal 6.0

SP2 → English→ Administration Guide→ Portal Platform → System Administration → System Landscape.The systems.xml and jcodestination.xml files are converted to system objects.

At the moment, you must create data sources manually.

• In SAP Enterprise Portal 6.0, the channels from SAP Enterprise Portal 5.0 are

converted to folders and placed in the Portal Content → com.sap.portal.migrated → ep_5.0 directory.

If you have heeded the points listed above, you can migrate 5.0 business packages to SAPEnterprise Portal 6.0 . Proceed as for importing content objects to SAP Enterprise Portal 6.0.

For more information about importing content objects, see the SAP Help Portal at

help.sap.com → SAP NetWeaver → SAP Enterprise Portal → Enterprise Portal 6.0 SP3 →

English→ Administration Guide→ Portal Platform → System Administration → Transport of

Content Objects → Transport Scenarios.

Result

The 5.0 business packages are available in SAP NetWeaver ’04.

Import Filter for Content ObjectsUse

When you import portal content from SAP Enterprise Portal 5.0 to SAP NetWeaver ’04, for example, iViews, pages, worksets, and roles, the Import Filter for Content Objects checks thecontent objects.

The Import Filter is shipped as an attachment to SAP Note 642999. For more information, seeSAP Note 642999.

Features

When you import content objects from SAP Enterprise Portal 5.0, the Import Filter providestwo features:

• Skipping content objects

• Mapping content objects

The Import Filter is controlled using the import filter file. The import filter file contains a list of all content objects that should be skipped and that can be mapped. The system automaticallyskips and maps content objects.

You must not make any manual changes to the import filter file. SAP does notaccept liability for or support customer changes to the import filter file.





Skipping Content Objects

Certain content objects from SAP Enterprise Portal 5.0 cannot or should not appear in SAPNetWeaver ’04. The import filter file for the Import Filter lists the content objects that areskipped during import to SAP Enterprise Portal SP2.

The following objects can be affected:

• .ivu

• .par

• .pag

• .pcd

Mapping Content Objects

To map content objects, you must use the Import Filter to map paths in SAP Enterprise Portal5.0 to paths in SAP NetWeaver ’04. You can only map content objects that are listed in thePortal Content Directory.

You can only map paths from SAP Enterprise Portal 5.0 (technical names) to the paths inSAP NetWeaver ’04 (technical names).

Path mapping:

pcd#/global/services/installed/SAPApplications.BSP=portal_content/com.sap.portal.migrated/ep_5.0/templates/com.sap.portal.appintegrator.sap.bwc.BSP

Regular Updates to the Import Filter

SAP regularly changes the import filter file for the Import Filter . Therefore, beforeyou import a 5.0 business package, you must check each time that you have thelatest version of the Import Filter .





Copying the Import Filter File to the Portal ContentDirectory

UseTo be able to use the Import Filter , you must copy the import filter file to a particular directoryin the Portal Content Directory in SAP NetWeaver ’04.

Prerequisites

You have read SAP Note 642999.

You have copied the import filter file from SAP Note 642999 to your local system andrenamed it.

Procedure

Work through the following steps:...

1. Look in the Portal Content Directory and find out the name of the Import Filter directory.

The path to this directory is: System Administration → Support → Portal Content

Directory → PCD Configuration → Parameters for Portal Content Migration → Pcd.Migration.Path.Mapfile.

The directory name appears next to the Pcd.Migration.Path.Mapfileentry.

2. Copy the import filter file to this directory.

3. Restart the portal.

Compatibility Package for KnowledgeManagement

Use

If you are implementing Knowledge Management, the compatibility package is relevant

because business package objects that contain links to content objects in KnowledgeManagement (KM) and that are migrated from SAP Enterprise Portal 5.0 to SAP NetWeaver ’04 cannot find their target objects in KM after the migration because the naming conventionsfor KM content objects have changed in SAP NetWeaver ’04. Therefore, you must use theCompatibility Package for KM to map paths again.

The Compatibility Package for KM is shipped as an attachment to SAP Note 640634. For more information, see SAP Note 640634.

Prerequisites

You have installed the Import Filter in SAP NetWeaver ’04.





Activities

Import the KM Compatibility Package to SAP NetWeaver ’04.

Modifications to the Business Package for Communication

Use

Some of the business packages for SAP Enterprise Portal 5.0 that are released for SAPNetWeaver ‘04 contain groupware iViews from the Business Package for Communication. InSAP NetWeaver ‘04, the groupware applications are connected directly through the portalplatform, which is the reason why the Business Package for Communication is no longer provided separately.

If you use business packages for SAP Enterprise Portal 5.0 that use the groupware iViewsfrom the Business Package for Communication and that you want to migrate to SAPNetWeaver ‘04, you must modify them accordingly in SAP NetWeaver ‘04.

The following business packages are affected:

• Business Package for CRM 3.1 60.1

• Business Package for CRM 4.0 60.1

For more information, see SAP Note 640678.

Prerequisites

You have installed the Import Filter in SAP NetWeaver ‘04.

Features

The system skips or maps the content objects that are affected by the connection togroupware. For more information, see Import Filter [Page 7].

Activities

If you are using one of the business packages affected, you must perform the activitiesdetailed in SAP Note 640678.

Modifications to the Business Package for PortalUsers

Use

You cannot migrate the portal user role from SAP Enterprise Portal 5.0 to SAP NetWeaver ‘04. Instead, SAP NetWeaver ‘04 contains the standard user role, which replaces the portal

user role in SAP Enterprise Portal 5.0.






In SAP NetWeaver ‘04, various iViews that were part of the Business Package for PortalUsers are delivered as standard content together with the portal platform.

There is a backwards compatibility package to allow migration of selected content in theBusiness Package for Portal Users, for example, the Universal Worklist. For moreinformation, see SAP Note 642827 and the documentation for the Business Package for

Portal Users on iViewStudio at www.iviewstudio.com → Content Catalog → Every User →

General → Business Package for Portal Users (Release 50.5.1) → More Information → Documentation.

Prerequisites

You have installed the Import Filter in SAP NetWeaver ‘04.

Features

The system skips or maps the content objects that are available in SAP NetWeaver ‘04. For

more information, see Import Filter [Page 7].

Activities

You cannot migrate the Universal Worklist iView in the Business Package for Portal Usersfrom SAP Enterprise Portal 5.0 to SAP NetWeaver ‘04. In SAP NetWeaver ‘04, you mustconfigure this iView again as described in the documentation for the Universal Worklist iViewin the Business Package for Portal Users 50.5.

2_contentmigration

Documents