Вы находитесь на странице: 1из 54
E NTERPRISE P ORTAL 6.0 P UBLIC ASAP “How to…” Paper Applicable Releases: EP 6.0

ENTERPRISE PORTAL 6.0

PUBLIC

ASAP “How to…” Paper

E NTERPRISE P ORTAL 6.0 P UBLIC ASAP “How to…” Paper Applicable Releases: EP 6.0 SP2

Applicable Releases: EP 6.0 SP2 May 2004

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

3.1

Basic Concepts

4

3.1.1 Understanding Roles in SAP Applications and SAP Business Packages

4

3.1.2 Content of a Business Package

5

3.1.3 Semantics and Business Packages

5

3.1.4 Delegated Administration

5

3.1.5 The Delta Link Concept

5

3.2

Business Package Release Names and Numbers

6

3.2.1 Business Package Names

6

3.2.2 Business Package Release Numbers

6

3.3

Support Packages and Upgrades for Business Packages

6

3.3.1 Support Packages for Business Packages

6

3.3.2 Upgrading Business Packages

6

3.4 Object Naming Conventions

7

3.5 Storage Structures for Business Packages in the Portal Catalog

7

3.5.1 Storage Structure for Native EP 6.0 Business Packages

7

3.5.2 Example: Storage of SAP EP 5.0 Business Packages in SAP EP 6.0

8

3.6

Shared Objects

9

3.7

Overview: Business Package for SAP CRM 4.0 for EP 6.0

9

4.1

iViewStudio Structure

10

4.1.1 Searching For a Business Package

11

4.1.2 Displaying Details for a Business Package

12

4.1.3 Downloading a Business Package

14

5.1

Preparing To Install Business Packages

15

5.1.1 Checking the SAP EP 6.0 Release

15

5.1.2 Downloading the Business Package From iViewStudio

16

5.1.3 Preparing the SAP CRM System

19

5.2

Installing Business Packages

20

5.2.1 Notes on the Installation

20

5.2.2 Installing the Import Filter

20

5.2.3 KM Compatibility Package

23

5.2.4 Example: Installing the Business Package for SAP CRM 4.0, Release 60.2.0

26

5.3

Using Business Packages

29

5.3.1 Navigation Compatibility of People-Centric SAP CRM 4.0 with SAP EP 6.0

29

5.3.2 Working With Business Packages

34

5.3.3 Modifications in SAP EP 6.0

34

 

5.3.3.1 Creating a System Landscape Objects to Connect SAP CRM 4.0

34

5.3.3.2 User Mapping to the Target System

40

5.3.3.3 Function Test for the Business Package for CRM 4.0 60.2

41

5.3.4 Working with Delta Links

45

5.3.5 Transporting Business Packages (Staging)

46

5.4

Uninstalling Business Packages

47

6.1

SAP Notes – A Compilation for Business Packages

51

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

6.2 User Registration for iViewStudio at www.iviewstudio. com

52

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

1 Scenario

A customer is using SAP CRM 4.0. The customer is using this system as People -Centric CRM for intuitive,

role-based, and personalized access for customers, employees, and partners.

Through the integrated por

originating in various sources and applications.

The customer implements access to SAP CRM 4.0 from/to SAP Enterprise Portal using predefined, prestructured content modules that are made available in the Business Package for SAP CRM 4.0.

The objective is to implement the Business Package for CRM 4.0 through all phases of the life -cycle, from providing, installing, and working with the business package, and uninstalling it.

tal solution, SAP Enterprise Portal 6.0, users are able to access content

2 Result

In this document, you can find practical information that allows you to implement the scenario described.

It documents the use of business packages with SAP Enterprise Portal 6.0 through all phases of the business package life-cycle.

After the basics, which provide a short overview for people new to this topic, all phases of using a business package are described, based on an example of using the Business Package for SAP CRM 4.0:

Preparing to install business packages

Installing business packages

Using business packages

Uninstalling business packages

At this point, we want to emphasize that the use of the Business Package for SAP CRM 4.0 represents an example. In comparison to other business packages, the business package implemented here, which contains more than 1100 objects, is very large.

At the moment, most of the business packages that are released for SAP Enterprise Portal 6.0 were developed on the basis of SAP Enterprise Portal 5.0. This results in migration processes that you must follow during installation. These steps are not required for business packages that were developed on the basis of SAP Enterprise Portal 6.0.

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

3 Business Packages – Overview

For SAP Enterprise Portal 6.0 SP2, SAP develops predefined, preconfigured content objects and makes them available. These content objects are bundled by subject area and are made available in business packages. Business packages provide the means to support the infrastructure to be integrated and to support application-specific processes and roles.

Business packages provide numerous benefits:

Business packages are shipped independent of the

SAP Enterprise Portal

platform. They are

offered for download on iViewStudio (www.iviewstudio.com).

Business packages can relate to SAP software or software from other providers.

Business packages can be limited to a single business area or implemented for all users of a portal.

Business packages have a modular structure. Depending on the application in question, you can modify and combine one or more packages according to role and task requirements.

Business packages are made available in industry application-specific forms.

-specific, user -specific, role -specific, and

3.1 Basic Concepts

3.1.1 Understanding Roles in SAP Applications and SAP Business Packages

The SAP applications have different interpretations of roles. Common to all are the following factors:

Roles can be assigned to different users and contain authorization information

Roles are made available by the application system, can be changed by the administrator, or can be defined from scratch.

Below you can find the role concept for the most important SAP solutions:

mySAP Business Suite (for example: SAP ERP, SAP CRM 4.0):

Roles from ABAP-based systems define a number of transactions for a user or a user group, which are provided in a menu structure.

SAP Business Warehouse:

Roles contain directories containing the reports and analyses that the user uses.

SAP Enterprise Portal 6.0 (SAP EP 6.0)/business packages:

o

Portal roles are used to assign portal content to users.

o

Portal roles are used to control permissions for portal content objects.

These different role concepts exist for historic and application

restriction that you cannot directly use portal roles to define authorizations in R/3

Application Server backend systems.

For more information about the SAP role concepts, see the how-to guide Role Concept in EP 5.0 and 6.0.

You can find this at the Internet address service.sap.com/nw-ep

People Integration How-To Guides

-specific reasons. This results in the

systems or Web

SAP NetWeaver in Detail EP 6.0 (SP2 and before)

Portal

Media Library

Documentation & More

Current How-To Guides.

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

3.1.2 Content of a Business Package

A business package contains the following content objects:

iView: An iView is a small application and

appears in a particular area on a page. An

iView receives and processes data from various sources in the enterprise or from the Internet and displays this in the Portal Content area.

Page: A portal page provides a display area as a container for iViews an d its structure is described in a layout that you use to determine the arrangement of objects on the page.

Workset: A workset logically bundles related pages and forms the basis for the

navigation. A workset allows access to tools, applications, and inform responsible for a particular area.

Role: As described in the previous section.

ation for users

3.1.3 Semantics and Business Packages

We can also describe content objects from the semantic perspective: An iView represents a

a user wants to have acces s to tools, applications, or information that he or she needs for a particular workstep. These worksteps are part of a business process.

The content of a page provides the tools to process or resolve this

various steps. Related iViews that support these steps are grouped together on a portal page.

Portal pages, in turn, are grouped together as simple worksets (

level. A simple workset therefore described the tasks that a portal user business process.

Some business processes require one or more simple worksets to be grouped into complex worksets. These are used to cover more extensive areas of responsibility.

workstep, if

task. The portal user works through

collection of tasks ), the next structure

requires to handle a specific

3.1.4 Delegated Administration

The concept of deleg ated administration allows distribution of administrative tasks (for example, user administration) and distributed access to content objects. Therefore, delegated administration is a process

for hierarchical distribution of administrative tasks between one administrators.

One use case is distributed and very large portal implementations.

or more administrators or groups of

3.1.5 The Delta Link Concept

The delta link concept implemented in SAP EP 6.0 allows you to use portal content objects from business packages more than once.

You can change objects generated by means of delta links without changing the original objects that the delta link objects reference. This is beneficial for maintenance (delivered portal content, for example, from SAP, content from other departments, and so on), object protection, and reuse.

Objects generated by means of delta links can have different properties. If you delete the delta link object, the original object is retained.

From delta link objects, you can generate further delta li interlinked objects.

When working with content objects for business packages, SAP principally recommends working with

delta links, because otherwise the objects are not updated automatically when you import packages and new minor releases.

nk objects. This allows you to create a chain of

support

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

For more information about the delta link concept, see the administration guide for SAP Enterprise Portal

6.0 SP2. You can find this on the

Administration Guide

SAP Help Portal at the Internet address

Content Administration

help.sap.com/ep. Choose

Portal Platform

Content Object Model.

3.2 Business Package Release Names and Numbers

The information that you obtain from the name of the business package tells you the minimum portal release required and what application system it is associated with. Some business packages are released for a certain release of an application system, others are release-independent.

3.2.1 Business Package Names

The Business Package for CRM 4.0, release 60.2, has been developed solely for use with

Release 4.0, that is, you cannot use it with SAP CRM Release 3.1. You must follow this information.

Significant is also the portal platform release of SAP Enterprise Portal 6.0.

In the detailed information on the business package in the iViewStud

read that the business package used in our scenario is released for SAP EP 6.0 SP2, that is, it is not

released for earlier portal platform releases or support packages.

SAP CRM

io (www.iviewstudio.com), you can

3.2.2 Business Package Release Numbers

The release numbering of a business package is composed as follows:

<SAP Enterprise Portal Release> . <Business Package Release> . <Support Package Level>

In our cases, the business package has support package level zero with the release number 60.2.

If no back -end release is specified in the business package name, the business package is either suitable

for several back -end system releases, as in the case of the SAP BW business packages, or it is plug based, as in the case of the Business Package for Manager Self-Service.

-in-

3.3 Support Packages and Upgrades for Business Packages

3.3.1 Support Packages for Business Packages

Support packages are used to correct errors in the software. They are created at regular intervals and shipped through the iViewStudio. Support packages contain o nly corrections to iViews; they do not contain any new pages, worksets, or roles.

Support packages are cumulative, that is, support package 3 contains all changes included in support

packages 1 and 2. Therefore, only the latest support package is availabl iViewStudio.

Support Package

If a support package is available for a business package, you can find the information

Available on the iViewStudio in the Content Catalog, in the entry for the business package concerned. By choosing More Information, you can display more information about the package (Package Information tab page) and the support package (Support Package tab page).

e for download from the

3.3.2 Upgrading Business Packages

During an upgrade, the business package release (minor release) changes, for 60.2. A business package upgrade can contain the following content:

New languages

New iViews, or iViews with changed features

example, from 60.1 to

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

New or changed pages

New or changed worksets

New or changed roles

New or changed dependencies to back-end systems, for example:

o

New plug-in version (in the case of plug-in-based business packages)

o

New support packages for the back-end system

o

New back-end system release

Because of the dependencies to a back

Technical Description section of the documentation for the respective business package carefully and bear in mind the dependencies documented. A business package upgrade is frequently connected with an upgrade in the back-end system or a plug-in, in order to be able to use all features. Bear this in mind when planning your upgrade.

the

-end system in particular, it is important that you read

Only two minor releases of a business package are available on the iViewStudio.

For more information about upgrading business packages, see the iViewStudio in the column in the Portal Content News section.

Related Lin ks

3.4 Object Naming Conventions

The objects in business packages are also subject to naming conventions.

You should not change the SAP objects, because the objects in the SAP namespace may be changed during subsequent upgrades of the portal or support package imports.

An exception to this rule is SAP Collaboration Room

namespace for production use. This is described in the SAP Collaboration Room documentation.

For all o bjects in the portal, such as roles, worksets, pages, and iViews, the SAP namespace starts with:

com.sap.pct.<project>.

– in this case you must copy the objects to your

3.5 Storage Structures for Business Packages in the Portal Catalog

This section described how the imported business packages appear in the p

business packages differs according to whether the business package is question is a native SAP EP 6.0

business package or an SAP EP 5.0 business package released for SAP EP 6.0 that is migrated during import.

Knowledge of the storage structures is significant for migrating portal content.

ortal catalog. The storage of

3.5.1 Storage Structure for Native EP 6.0 Business Packages

The following storage structure in the portal catalog describes the storage of portal content objects from native SAP EP 6.0 business packages.

In principle, the native SAP EP 6.0 business packages are stored in the portal catalog in the same way as

on the iViewStudio (path:

Content Provided by SAP

Content for Line Managers , Specialists, Every

User). This ensures simple orientation and recognition.

You must note that a portal content object can be assigned to more than one other portal content object. For example, an iView in a business package can be assigned to more than one page or a page can be found in more than one workset.

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

3.5.2 Example: Storage of SAP EP 5.0 Business Packages in SAP EP 6.0

Generally, portal content objects that are migrated from SAP EP 5.0 to SAP EP 6.0 are stored in a

predefined folder. The objects migrated from SAP EP 5.0 are located in the subfolder EP 5.0.

In the case of a migrated business package, a folder is created in the

business package and this contains the objects in the business package sorted into the appropriate folders according to the object type.

The graphic below shows the storage structure for the Business Package for SAP CRM 4.0:

Migrated Content folder,

EP 5.0 folder with the name of the

for the Business Package for SAP CRM 4.0: Migrated Content folder, EP 5.0 folder with the

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

3.6 Shared Objects

Some business packages reuse components located in other business packages. These reused

components are known as shared objects. These are portal business package and are used in another business package.

iViews (including external services, BSPs, and so on), pages, roles, and worksets can be shared objects. Each original shared object is assigned to only one business package. This ensures that a shared object is not imported with several business packages in more than one version into the portal and it does not impair the function of other business packages.

Objects are shared by means of delta links

business package and are used in another business package.

The benefit of using shared objects is the possibility of extending a business package to include functions from another business pack age. However, cross -package usage results in dependencies with regard to upgrades, support packages, and newer versions of business packages.

SAP recommends following the procedure documented in section 5.3 referencing objects.

content objects that originate in a particular

to other portal content objects that originate in a particular

Using Business Packages when

3.7 Overview: Business Package for SAP CRM 4.0 for EP 6.0

The Business Package for SAP CRM 4.0 for SAP EP 6.0 is targeted at employees in Sales, Marketing, and Customer Services, who require central access to all relevant data information on customers and markets.

It contains the following roles:

Sales: Sales Manager, Sales Representative, Sales Assistant, and Billing Clerk

Marketing: Campaign Manager, Lead Manager, Lead Qualifier, Account Manager, Trade Marketing Manager, and Brand Manager

Service: Service Manager and Service Representative

Interaction Center: Interaction Center Manager and Interaction Center Agent

Channel Management: Channel Manager, Partner Manager, Partner Manager – Channel Commerce, and Partner Employee

E-Commerce: Customer and Customer Administrator

Administration: CRM Portal User, CRM Portal Administrator, and KM Author

The content of this business package supports employees when they face decisions and operational issues in their daily work. The added value consists of:

Bringing together information that was previously distributed among different sources

Allowing access to this information

Structuring this information at the time it is requested

Numerous roles and preconfigured iViews are available. You can combine and personalize the por content objects contained in the business package as required. You can access structured and unstructured CRM content and tailor it depending on how it is used.

tal

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

4 The Portal for Business Packages – iViewStudio

About 95 business packages from SAP and abou t 30 business packages from certified and non -certified third-party vendors are currently available on iViewStudio. This means that more than 3000 iViews and more than 100 content-specific roles and worksets are offered there.

4.1 iViewStudio Structure

You can find iViewStudio on the Internet at www.iviewstudio.com. iViewStudio provides the following functions:

Searching for business packages

Displaying details for a business package

Downloading business packages, documentation, and additional information about business

packages. The prerequisite for extended access to iViewStudio is having a registered user. The prerequisite for this is that you have registered as a licensed user of iViewStudio. The procedure for doing this is described in the appendix to this document.

If you have a user for iViewStudio, log on to iViewStudio and accept the conditions of use for business packages.

a user for iViewStudio, log on to iViewStudio and accept the conditions of use for business

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

4.1.1 Searching For a Business Package

In the iViewStudio Content Catalog, there are numerous business packages for SAP EP 6.0. You searching for business packages by choosing Content Catalog on the entry navigation bar.

The Software-Centric Search allows you to search for business packages for a specific backend system. To do this, you select the category required from a dropdown list in the Software-Centric Search area.

When the search is complete, the system displays the business packages found. If you require more information about a business package, choose More Information.

The technical information on the business package

you can also find information about configuring the backend system and specific installation instructions.

Example: Results of the search for the Business Package for SAP CRM 4.0 60.2:

start

is available in the Online Documentation area. There

the Business Package for SAP CRM 4.0 60.2: start is available in the Online Documentation area.

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

4.1.2 Displaying Details for a Business Package

In the section about each business package, you can first see an overview of the business package functions. Below this, there are buttons for more information, More Information, and adding the package to the download basket, Add To Basket.

If you choose More Information, information appears about the following:

Package information:

o

General Information:

Name, release, status, short description, iView runtime technology, languages supported

o

System Requirements:

Data sources for connection, portal releases, other prerequisites

o

Business Context:

Industry, business area, target group, delivered roles

o

License Information:

License model, sales information

Worksets and iViews:

o

Package Components:

iViews and worksets in the delivered business package

o

General Information:

Attributes of the iViews and worksets displayed in the tree of the left-hand side

If you choose Add To Basket, you add the business package to your basket for subsequent download.

Example: Business Package for SAP CRM 4.0 60.2, Package Information – General Information:

CRM 4.0 60.2, Package Information – General Information: Example: Business Package for SAP CRM 4.0 60.2,

Example: Business Package for SAP CRM 4.0 60.2, Package Information – Business Context:

Information: Example: Business Package for SAP CRM 4.0 60.2, Package Information – Business Context: 2004 SAP

2004 SAP AG

12

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

Example: Business Package for SAP CRM 4.0 60.2, Package Information – License Information:

CRM 4.0 60.2, Package Information – License Information: Example: Business Package for SAP CRM 4.0 60.2,

Example: Business Package for SAP CRM 4.0 60.2, Package Information – System Requirements:

CRM 4.0 60.2, Package Information – System Requirements: Particularly important is that you heed the portal

Particularly important is that you heed the portal release specified in the

Requirements section. The corresponding business package can be implemented on the portal release

specified here.

Package Information

System

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

4.1.3 Downloading a Business Package

You require a user ID to download business packages. This user ID allows you to access all business packages available. Provided that you possess the license required, you can start downloading business packages immediately.

In the content catalog on iViewStudio, you can find the documentation for the respective business

packages. In addition, you can also fi

more information about individual business packages, choose More Information

In some cases, a business package may be listed in the iViewStudio catalog, but not be publicly ava ilable

for download. These business packages are in restricted shipment and are only available to a limited

number of customers at the moment. If you are interested in one of these business packages, either contact the corresponding ramp-up owner or wait until the business package is generally available.

Please note:

continuously extending and improving its business packages and therefore the file that you download is available for a limited period only.

You must also note the release number of the installed package, because SAP Enterprise Portal currently cannot display the release number of an installed package.

You should also save support packages or upgrade files from iViewStu dio locally, so that you can access them again at a later time.

For example, a local back-up copy is required in the following case:

A business package, support package, or an upgrade is installed on a test or QA portal for test purposes.

During this period, the file on iViewStudio is replaced by a new version. When you want to install the tested

version on the production portal, you require a local back-up copy.

nd support packages for individual business packages here. For

Documentation.

SAP strongly recommends saving and archiving the downloaded .zip file. SAP is

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5 Business Package Life-Cycle

The phases “preparing for installation”, “installation”, “

together make up the business package life-cycle. In this section, each phase is described in detail.

using business packages”, and “deinstallation”

5.1 Preparing To Install Business Packages

Before the actual installation of a business package, you must comp depending on the business package concerned.

lete the preparations, which vary

5.1.1 Checking the SAP EP 6.0 Release

You must first establish the exact release of your portal implementation. The business package that you want to install must be released for this portal release. If necessary, you should update your software. The procedure is as follows.

Example: Establishing the portal release for the Business Package for SAP CRM 4.0:

In SAP EP 6.0, navigate to: System Administration

Support

Support Desk.

Package for SAP CRM 4.0: In SAP EP 6.0, navigate to: System Administration Support Support Desk

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

Choose Version to display the portal release of your SAP Enterprise Portal:

to display the portal release of your SAP Enterprise Portal: 5.1.2 Downloading the Business Package From

5.1.2 Downloading the Business Package From iViewStudio

The next step is to download the business package from iViewStudio. As an example, the detailed procedure for downloading the Business Package for SAP CRM 4.0 60.2 is documented here:

the detailed procedure for downloading the Business Package for SAP CRM 4.0 60.2 is documented here:

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.1.3 Preparing the SAP CRM System

As described in the scenario, you must install an SAP CRM 4.0 system. As a test environment, a minimal SAP CRM 4.0 system forms the basis for the activities performed.

This consists of a central instance and a database instance. Furthermore, you can install optional dialog instances on different servers, once the central instance and database instance have bee n installed. If you are setting up an SAP CRM 4.0 system, you may require further main components that allow operations.

Once installation is completed, you must prepare your SAP CRM 4.0 with regard to data and user IDs. For subsequent access through SAP EP 6.0, a user must have a user ID in SAP CRM 4.0. The reports require data, so that they can return meaningful results.

For more precise information about installing and setting up a SAP CRM 4.0 system, see the corresponding documentation (installation guides, and so on).

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.2 Installing Business Packages

The installation of a business package refers to the import of the business packages to SAP EP 6.0.

5.2.1 Notes on the Installation

Most of the business packages currently released for SAP EP 6.0 are based on busi

SAP EP 5.0. These business packages are therefore not developed natively on SAP EP 6.0.

In SAP EP 6.0, there are improvements in working with portal content objects, for example, with regard to the effects on functions and the technical naming.

Therefore, the installation of non -native business packages for SAP EP 6.0 is not only an installation, but also a migration at the same time. For the migration, SAP provides an import filter and a KM compatibility

package. Depending on the busines business package.

After completion of the installation, you may have to modify the navigation, depending on the business package concerned. Other possible modifications are mentioned in the post-installation phase.

ness packages for

s package concerned, you must install these before installing the

5.2.2 Installing the Import Filter

Some SAP Enterprise Portal 5.0 objects (for example, certain portal content objects in the Business Package for SAP CRM 4.0 60.2) cannot be displayed in SAP EP 6.0. The import filter checks these objects: Certain portal content objects are excluded from the import; other portal content objects are reassigned. You must install the import filter before installing a business package containing SAP EP 5.0 content that is released for SAP EP 6.0.

The import f ilter is available for various different portal releases. As an attachment to SAP Note 642999 Import Filter is a version each for SAP EP 6.0 SP1 and SP2 respectively.

The installation process for the import filter is as follows:

1. Download the text file (depending on your portal release) from SAP Note 642999 to a temporary folder.

2. In SAP EP 6.0, navigate to: System Administration

Support

Portal Content Directory

PCD

Configuration

path as it is displayed. For example: /usr/sap/ep01/global/config/pcd/Migration/mapping/

Parameters for Portal Content Migration

Pcd.Migration.Path.Mapfile. Note the

3. On your EP 6.0 server, navigate to the folder path you noted in step two. Copy the text file from your temporary folder to this folder.

4. Rename the file cms_mapping.properties to cms_mapping.properties_old.

5. Rename the text file to cms_mapping.properties.

6. Change the access rights to cms_mapping.properties for read-write permission.

7. Change the user and group assignment to cms_mapping.properties for the J2EEAdminUser and the group sapsys.

8. Restart the portal.

On the following pages, the detailed procedure for installing the import filter on EP 6.0 is shown:

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

.

P ACKAGES IN SAP E NTERPRISE P ORTAL 6.0 P UBLIC . mv cms_mapping.properties cms_mapping.properties_old mv

mv cms_mapping.properties

cms_mapping.properties_old

mv cms_mapping.properties.txt

cms_mapping.properties

chmod 755 cms_mapping.properties

chown j2eeadm:sapsys cms_mapping.properties

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.2.3 KM Compatibility Package

The ne xt step is to install the KM compatibility package. Between SAP EP 5.0 and SAP EP 6.0, the naming conventions for KM content objects have changed. Therefore, references to such objects can no longer find their targets. The KM compatibility package solves t his problem for portal content objects that have been migrated from SAP EP 5.0 to SAP EP 6.0.

The KM compatibility package contains PCD KM objects with the names previously used that the migrated EP 5.0 content can reference. These references then do not point to non-existent objects.

You install the KM compatibility package as follows:

1. Download the *.zip file in SAP Note 640634 KM compatibility package to a temporary folder.

2. In the PCD import folder, create a folder for the KM compatibility package with the path:

cd /usr/sap/<MyPortalInstance>/global/config/pcd/Import mkdir KMCompatibilityPackage

3. Unpack the *.zip file to this import folder.

4. Change the assignment from user and group recursively to the KMCompatibilityPackage folder and to the files and folders that this contains:

chown –R <J2EEAdminUser>:sapsys KMCompatibilityPackage

5. Change the permissions from user and group recursively to the KMCompatibilityPackage folder and to the files and folders that this contains:

chmod –R 755 KMCompatibilityPackage

6. In Enterprise Portal 6.0, import the package as usual using System Administration Import.

7. A log file is generated during the import. You can check this at:

Transport

/usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file>

8. After the import, the imported portal content appears in com.sap.portal.migrated

ep_5.0.

The imported PCD objects reference the same program code as the corresponding SAP EP 6.0 KM objects. The iViews therefore appear in the more up-to-date SAP EP 6.0 format.

The KM co mpatibility package is also relevant for other business packages that reference parts of the Business Package for Communication or Business Package for Portal Users for the EP 5.0 KM platform. You can find notes on this in SAP Note 642775 Composite SAP Note for Business Packages as of EP 6.0

SP1.

You only install the KM compatibility package once

business package that reference parts of the Business Package for Communication or the Business Package for Portal Users for the KM platform.

On the following pages, the detailed procedure for installing the KM compatibility package on EP 6.0 is shown:

– even if you are implementing more than one

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

P ACKAGES IN SAP E NTERPRISE P ORTAL 6.0 P UBLIC cd /usr/sap/<MyPortalInstance>/glo

cd

/usr/sap/<MyPortalInstance>/glo

bal/config/pcd/Import

mkdir KMCompatibilityPackage

chown –R <J2EEAdminUser>:sapsys

KMCompatibilityPackage

chmod –R 755

KMCompatibilityPackage

chown –R <J2EEAdminUser>:sapsys KMCompatibilityPackage chmod –R 755 KMCompatibilityPackage 2004 SAP AG 24

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.2.4 Example: Installing the Business Package for SAP CRM 4.0, Release 60.2.0

As described in the section above, you have already downloaded the Business Package for SAP CRM 4.0, release 60.2.0 from iViewStudio to a temporary folder.

The prerequisite for this is that the import fi lter and KM compatibility package are installed. To install the Business Package for SAP CRM 4.0, release 60.2.0, you must work through the following steps:

1. In the PCD import folder, create a folder for the Business Package for SAP CRM 4.0 with the path:

cd /usr/sap/<MyPortalInstance>/global/config/pcd/Import mkdir BPForSAP_CRM_60_2_0

2. After the import, the imported portal content appears in com.sap.portal.migrated <business package name>.

3. Unpack the *.zip file to this import folder.

4. Change the assignment from user and group recursively to the BPForSAP_CRM_60_2_0 folder and to the files and folders that this contains:

ep_5.0

chown –R <J2EEAdminUser>:sapsys BPForSAP_CRM_60_2_0

5. Change the permissions from user and group recursively to the BPForSAP_CRM_60_2_0 folder and to the files and folders that this contains:

chmod –R 755 BPForSAP_CRM_60_2_0

6. In Enterprise Portal 6.0, import the package as usual using System Administration Import.

7. A log file is generated during the import. You can check this at:

Transport

/usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file>

8. After the import, the imported portal content appears in com.sap.portal.migrated <business package name>.

ep_5.0

The screenshot shows the portal catalog with the imported business package:

shows the portal catalog with the imported business package: On the following pages, the detailed procedure

On the following pages, the detailed procedure for installing the Business Package for SAP CRM 4.0, release 60.2.0 on EP 6.0 is shown:

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

P ACKAGES IN SAP E NTERPRISE P ORTAL 6.0 P UBLIC cd /usr/sap/<MyPortalInstance>

cd /usr/sap/<MyPortalInstance> /global/config/pcd/Import mkdir BPForSAP_CRM_60_2_0

chown –R <J2EEAdminUser>:sapsys

BPForSAP_CRM_60_2_0

chmod –R 755

BPForSAP_CRM_60_2_0

chown –R <J2EEAdminUser>:sapsys BPForSAP_CRM_60_2_0 chmod –R 755 BPForSAP_CRM_60_2_0 2004 SAP AG 27

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.3 Using Business Packages

After completion of the installation, you have to work through some post-processing steps, depending on the business package concerned. The main points are the following:

E-mail and calendar integration in SAP EP 6.0 (previously modifications for the Business Package for Communication)

Configuration of additional properties for system landscape objects

Using features of the former Business Package for Portal Users in SAP EP 6.0.

Correction of various errors:

o

Workforce Management iViews

o

Value help

o

Bookmarking

o

KM Extensions

o

Translation of the Administration Workset

Navigation compatibilities (People-Centric CRM with EP 6.0)

In the appendix, there is a list of related SAP Notes for the topics listed above. Based on the Business Package for SAP CRM 4.0 60.2, the following section describes activities for implementing the navigation compatibility.

5.3.1 Navigation Compatibility of People-Centric SAP CRM 4.0 with SAP EP 6.0

SAP EP 6.0 does not support references to generic services (for example, ValueHelp or URLDispatcher). This affects the navigation and its compatibility, for example, with SAP CRM 4.0.

SAP provides the corrected version of the CRM Conte

URL Dispatcher (com.sap.pct.crm.UrlDispatcher.par), and a package for navigation compatibility between SAP CRM 4.0 and EP 6.0.

xt Service (com.sap.pct.crm.crmcontext.zar), the

1. As described in SAP Note 659881 Compatibility of navigation of People-Centric CRM with EP 6.0, you download the attached *.zip file to a temporary folder.

2. Unpack the file to a temporary folder.

3. Rename the file com.sap.pct.crm.crmcontext.zar to com.sap.pct.crm.crmcontext.par.

4. Copy both PAR files to the J2EE Servlet path, for example, the path:

/usr/sap/ep01/j2ee/j2ee_01/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB - INF/deployment/pcd

5. Restart the J2EE Engine.

6. In the PCD import folder, create a new folder, called Navigation_40_60_2, for the import of the navigation compatibility package with the path:

cd /usr/sap/ep01/global/config/pcd/Import mkdir Navigation_40_60_2

7. Unpack the *.zip file to this folder.

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

8. Change the assignment from user and group recursively to the Navigation_40_60_2 folder and to the files and folders that this contains:

chown –R <J2EEAdminUser>:sapsys Navigation_40_60_2

9. Change the permissions from user and group recursively to the Navigation_40_60_2 folder and to the files and folders that this contains:

chmod –R 755 Navigation_40_60_2

10. In Enterprise Portal 6.0, import the package as usual using System Administration Import.

11. A log file is generated during the import. You can check this at:

Transport

/usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file>

12. After the import, the role com.sap.pct.crm_default_services is available. You must assign this to the predefined group Everyone.

On the following pages, the detailed procedure for installing the navigation compatibility between SAP CRM 4.0 and EP 6.0 is shown:

detailed procedure for installing the navigation compatibility between SAP CRM 4.0 and EP 6.0 is shown:

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

 

chown –R <J2EEAdminUser>:sapsys

Navigation_40_60_2

9.

10.

chmod –R 755 Navigation_40_60_2

chown –R <J2EEAdminUser>:sapsys Navigation_40_60_2 9. 10. chmod –R 755 Navigation_40_60_2 2004 SAP AG 31
chown –R <J2EEAdminUser>:sapsys Navigation_40_60_2 9. 10. chmod –R 755 Navigation_40_60_2 2004 SAP AG 31

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL
H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.3.2 Working With Business Packages

Once you have completed the postprocessing steps, you can work with the portal content objects. In our scenario, you now have to prepare the access to the participating backend systems.

For example: Access to SAP CRM 4.0 through SAP EP 6.0 SP2 using the Business Package for SAP CRM 4.0, release 60.2.0

Prerequisites

As CRM system, an SAP CRM 4.0 system is implemented. (To use the analysis features, you also require an SAP BW system.)

Users are available in this SAP CRM 4.0 system.

Data is available in SAP CRM 4.0.

As the portal, SAP EP 6.0 SP2 is used.

Users are available in EP 6.0 SP2.

The Business Package for SAP CRM 4.0, Release 60.2.0 is installed.

5.3.3

Modifications in SAP EP 6.0

You need to modify SAP Enterprise Portal to use a business package. The activities that occur most frequently are documented below.

5.3.3.1 Creating a System Landscape Objects to Connect SAP CRM 4.0

A system landscape object creates the connection bet ween portal content objects and backend systems. The creation and management of system landscape objects tasks are part of the system administration for SAP EP 6.0. The most important steps are described below:

1. Create a folder for the system landscape objects.

2. Launch the System Landscape Wizard to create a system landscape object.

3. Configure the parameters of the system landscape object for use:

a. Assign the system alias for the SAP CRM 4.0 system:

The standard entry for the system alias for system landscape objects when using portal content objects to access a SAP CRM system is system alias SAP_CRM. For other SAP systems, you can find the entries in the object properties. The object property is System and the values specified there must match the system alias.

b. Assign properties for various categories:

On the next page, you can find an example of the value assignments for an implementation of the Business Package for SAP CRM 4.0 60.2:

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

Value Assignments of the Properties and the Assignment for the Implemented Business Package

Category

Property

Value

Example:

Business Package for SAP CRM 4.0 60.2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

   

You do not need to enter values for any other category. Do not change the default values for these.

The affected categories are: Drag&Relate Serv er (DRS), ISA HOM, WFM, WFM CS, ISA B2B, ISA B2R,

Shared Catalog, CRM Content, In Administration

On the following pages, the detailed procedure for creating a system landscape object in EP 6.0 SP2 to connect SAP CRM 4.0 is shown:

ternet Transaction Server (ITS)

, CVIEWS, ICSS,

and

Shop

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

H OW T O U SE B USINESS P ACKAGES IN SAP E NTERPRISE P ORTAL