ENTERPRISE PORTAL 6.

PUBLIC

ASAP How to Paper

Applicable Releases: EP 6.0 SP2 May 2004

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.2 3.2.1 3.2.2 3.3 3.3.1 3.3.2 3.4 3.5 3.5.1 3.5.2 3.6 3.7 4.1 4.1.1 4.1.2 4.1.3 5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 5.2.3 5.2.4

Basic Concepts .......................................................................................................................................... 4 Understanding Roles in SAP Applications and SAP Business Packages.................................................... 4 Content of a Business Package ................................................................................................................... 5 Semantics and Business Packages ................................................................................................ .............. 5 Delegated Administration ........................................................................................................................... 5 The Delta Link Concept.............................................................................................................................. 5 Business Package Release Names and Numbers .................................................................................... 6 Business Package Names............................................................................................................................ 6 Business Package Release Numbers ........................................................................................................... 6 Support Packages and Upgrades for Business Packages................................ ....................................... 6 Support Packages for Business Packages ................................................................................................... 6 Upgrading Business Packages .................................................................................................................... 6 Object Naming Conventions .................................................................................................................... 7 Storage Structures for Business Packages in the Portal Catalog ......................................................... 7 Storage Structure for Native EP 6.0 Business Packages ............................................................................. 7 Example: Storage of SAP EP 5.0 Business Packages in SAP EP 6.0 ......................................................... 8 Shared Objects .......................................................................................................................................... 9 Overview: Business Package for SAP CRM 4.0 for EP 6.0 .................................................................. 9 iViewStudio Structure ............................................................................................................................ 10 Searching For a Business Package................................................................................................ ............ 11 Displaying Details for a Business Package............................................................................................... 12 Downloading a Business Package............................................................................................................. 14 Preparing To Install Business Packages ............................................................................................... 15 Checking the SAP EP 6.0 Release................................................................................................ ............ 15 Downloading the Business Package From iViewStudio........................................................................... 16 Preparing the SAP CRM System ................................................................ .............................................. 19 Installing Business Packages.................................................................................................................. 20 Notes on the Installation ........................................................................................................................... 20 Installing the Import Filter........................................................................................................................ 20 KM Compatibility Package................................ ....................................................................................... 23 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 6.1 Uninstalling Business Packages ............................................................................................................. 47 SAP Notes A Compilation for Business Packages ............................................................................. 51 1

2004 SAP AG

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 6.2

PUBLIC

User Registration for iViewStudio at www.iviewstudio. com .............................................................. 52

2004 SAP AG

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 tal solution, SAP Enterprise Portal 6.0, users are able to access content 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.

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.

2004 SAP AG

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
3.1.1

Basic Concepts
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 o Portal roles are used to assign portal content to users. Portal roles are used to control permissions for portal content objects.

These different role concepts exist for historic and application -specific reasons. This results in the restriction that you cannot directly use portal roles to define authorizations in R/3 systems or Web 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 SAP NetWeaver in Detail People Integration Portal Media Library Documentation & More EP 6.0 (SP2 and before) How-To Guides Current How-To Guides.

2004 SAP AG

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 3.1.2 Content of a Business Package

PUBLIC

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 ation for users responsible for a particular area. Role: As described in the previous section.

3.1.3

Semantics and Business Packages

We can also describe content objects from the semantic perspective: An iView represents a workstep, if 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 task. The portal user works through 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 ( collection of tasks ), the next structure level. A simple workset therefore described the tasks that a portal user requires to handle a specific 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. 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 or more administrators or groups of administrators. One use case is distributed and very large portal implementations. 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 nk objects. This allows you to create a chain of 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 support packages and new minor releases.

2004 SAP AG

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 SAP Help Portal at the Internet address help.sap.com/ep. Choose Administration Guide Portal Platform Content Administration 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 SAP CRM 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 io (www.iviewstudio.com), you can 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. 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 -inbased, as in the case of the Business Package for Manager Self-Service.

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 e for download from the iViewStudio. If a support package is available for a business package, you can find the information Support Package 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). 3.3.2 Upgrading Business Packages example, from 60.1 to

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

2004 SAP AG

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 New or changed pages New or changed worksets New or changed roles New or changed dependencies to back-end systems, for example: o o o New plug-in version (in the case of plug-in-based business packages) New support packages for the back-end system New back-end system release

PUBLIC

Because of the dependencies to a back -end system in particular, it is important that you read the 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. 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 in this case you must copy the objects to your 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>.

3.5

Storage Structures for Business Packages in the Portal Catalog

This section described how the imported business packages appear in the p ortal catalog. The storage of 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. 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 Content for Line Managers , Specialists, Every on the iViewStudio (path: Content Provided by SAP 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.

2004 SAP AG

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 3.5.2 Example: Storage of SAP EP 5.0 Business Packages in SAP EP 6.0

PUBLIC

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 Migrated Content folder, subfolder EP 5.0. In the case of a migrated business package, a folder is created in the EP 5.0 folder with the name of 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:

2004 SAP AG

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 content objects that originate in a particular 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 to other portal content objects that originate in a particular 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 Using Business Packages when referencing objects.

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 tal

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.

2004 SAP AG

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.

2004 SAP AG

10

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 4.1.1 Searching For a Business Package

PUBLIC

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.

start

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 is available in the Online Documentation area. There 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:

2004 SAP AG

11

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:

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

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:

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

System Particularly important is that you heed the portal release specified in the Package Information Requirements section. The corresponding business package can be implemented on the portal release specified here.

2004 SAP AG

13

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 nd support packages for individual business packages here. For more information about individual business packages, choose More Information Documentation. 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: SAP strongly recommends saving and archiving the downloaded .zip file. SAP is 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.

2004 SAP AG

14

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5 Business Package Life-Cycle

The phases preparing for installation, installation, using business packages, and deinstallation together make up the business package life-cycle. In this section, each phase is described in detail.

5.1

Preparing To Install Business Packages

lete the preparations, which vary

Before the actual installation of a business package, you must comp depending on the business package concerned. 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.

2004 SAP AG

15

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

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

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:

     %$   ! "# '& (")( * +, "- * + "# */. 0 * 
21 * & (3 
(546798:;<= & & * 4  "# * "#+> 
2?82!
"# 
2 @   A5 "- CB)DFEHGJIDLKNMPOHQ,RJSUT VPWYX $ 3Z\[ T   
3
] ( * "

2004 SAP AG

16

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

^ d

$ _`"# 
:98:;aP+bc *  "#+( * 8:A
: * $ Bfe "#+( * 8 1 * 9  8:hg"# 
:+"#" i $ i km) l n []%oNpo ^ ( a,(,h1 * j

$ kml)n +( * 8 * r"#s" . i $ ( a,(, h "t1P

:

g"- Z
:+"#"

[u

vw "x<=s(3bYH8:h+( s+ 

:1y * & (3 
$ (z 46 8: 46  "2 <| (  aP(, }~h  =7 rH = #{ / + "# 
: /+ "# : ! 2

2004 SAP AG

17

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

 H 2;-Z:+#)/P,h kms ln oNpo % j  :+ }#

p v

 H 2;-Z:+#)/P,h kms ln oNpo % j  9 }#

 Hh#2r#t/P3P;y kms ln oNpo % j }# 9:+r

,yNL3 :# :+# ,hH:# #+  s ++3x: s6;+,L+ s 3 #! Hs: s P:+L :yL  3 5 ' #2' 9:h=+s /y:# 3 :#J: s s :6#:+# y|9:;JL+x=32 =/P3P } + r# j t z 3:h r zhH:h r s s 3: P oo5'o o 'kml)n  'po5 o

2004 SAP AG

18

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).

2004 SAP AG

19

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 ness packages for 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 s package concerned, you must install these before installing the 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. 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 Parameters for Portal Content Migration Pcd.Migration.Path.Mapfile. Note the path as it is displayed. For example: /usr/sap/ep01/global/config/pcd/Migration/mapping/ 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:

2004 SAP AG

20

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

 H2;+7 ;3:+  s s  ; 3 }=!2:Y H:  L +#; + :+  s +=Lys + s v

C:+=#; % 5:zP3;] 'LyF 3`PHFyL/yHs / Pc/L2 /Ly/J,yFP`LLJ )/xzPFJHJ /L/`FyLFz/ JFy/ )/PyFP FJHJ ' 'LJH/ J zH hH:{=39 3t7z6=+3tH:+

2004 SAP AG

21

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

}J32:+6hH:{|H

H2; % #++Lz:zP3;H2 y  +=,Y:+  # H s =H2;r7y;y 9: +|3y+=H:ty' + .

|+= # #z ! ,6 J:y |J C P3 z6=:

: ;9:;+7y `w'H]F'LLHL  `w3u\LFLyL'JH : ;9:;+7yh `w3u\LFLyL ##c 9:;/J+#):

mv cms_mapping.properties cms_mapping.properties_old

mv cms_mapping.properties.txt cms_mapping.properties
5:P;/J+#):ty 2 J 5|Z: =L=+L+)u

##c 9:;:+Lx:Z c2

chmod 755 cms_mapping.properties

5:P;:+Lx:Z #+|z: P'P  2 J 5|Z: =L=+L+)u

+#L79:{|

chown j2eeadm:sapsys cms_mapping.properties

2004 SAP AG

22

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 5.2.3 KM Compatibility Package

PUBLIC

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: /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. Transport

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 even if you are implementing more than one 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:

2004 SAP AG

23

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

%3  w: H2; wt3:+   

 N
L 

+3;9: 
 ' 
|9: 6 J
 3  ,, H2 !m 
 '#" %3  $ H2; hH 
   25%P;9:h& % :  '!# +* z: (' )'! +,H2 -%. /1023
46587:9;7=<:7:5,>?@4ACB)4EDF |z: y  9: t52 )tH2379 J: % * 25%P;9:  & %HL'!I rJ -%. /1023
46587:9;7=<:7:5,>?@4ACB64EDF{  9:  y z:  9: t52 )tH:79 J: % K LC:  #
 M 
7H:  >QI58FR2 PP N:
%PO SU T 6 2V7=W(7:QR58XI46587:06W Y Z[XR4W(Q\3
06XI5]Y ^823
06XI5

cd /usr/sap/<MyPortalInstance>/glo bal/config/pcd/Import mkdir 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

2)9:;


a :

L b J
 +

2004 SAP AG

25

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 c <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 c

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 c Import. 7. A log file is generated during the import. You can check this at: /usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file> 8. After the import, the imported portal content appears in com.sap.portal.migrated c <business package name>. The screenshot shows the portal catalog with the imported business package: ep_5.0 c Transport c

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: 2004 SAP AG

26

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

%3  w: H2;  =H2 d '! :&b,, fehgi jb +k   el' 9 N mI 

d +3;9: 
=H: '! :& ,,
fehgi jb H: @ 
L 6" %3  $ H2;  L
 H2 
 | H 
  25%P;9:h& % :  '!# +* z: (' )'! +,H2 no?qp!06X S ?qr
/1s%. rutvr
wr
v O |z: y  9: t52 )tH2379 J: % * 25%P;9:  & %HL'!I rJ S no?qp!06X ?qr
/1s%. rutvr
wr
v H2 O  =5:  9: )tz: 'I 9:3H HJ32 % K\
79: PP;xehgV  L :  Sy #T 
3 P:
%!" >QI58FR2 2V7=W(7:QR58XI46587:06W Y Z[XR4W(Q\3
06XI5]Y O ^823
06XI5

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

2004 SAP AG

27

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

,/: % '+@ uK8 

y 
  H,:3r @'! %9: z
' }(~ /z ! :  H  t3{" |)l | 
|  |@
 l ! ' &  # K,  |@}(  |)l |( |(~ ,(I l, |q6 ,
8 , #
 

 f:
l  
 I  # ! CI
6I86liII 

,,l,
@ %& % 
f b~ o !  & H

2004 SAP AG

28

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 o o o o Workforce Management iViews Value help Bookmarking KM Extensions 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 xt Service (com.sap.pct.crm.crmcontext.zar), the URL Dispatcher (com.sap.pct.crm.UrlDispatcher.par), and a package for navigation compatibility between SAP CRM 4.0 and EP 6.0.

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.

2004 SAP AG

29

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: /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. Transport

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

 V
 ( #:;::=,x(8=PoRE:; R(8R: 1% :@ @,
 l  , (
f,h8,
@!
1 

f,)o!
C
1 


f8
x  6 # % !" 8 #%$&('*)+-,.'/,#%01'*#%2&('*#%23&4#%$657098:01'<;=+2  #%$&('*)+-,.'/,#%01'*#%2&('*#%23&4#%$657098:01'<,+2 C DFEV 89G!"IH JJ K L>mfM!b
K N

f

?>  * & {6- 6- "@A *B  *   f{6- 6- "@A  O@PM!%  RQ   T UT  Q   S &   f
M #
 S  S  L>  T AW UT T  Z SL@ > , SV>  -  Y X   - \[  N  J F]^`_ o # O7 # " f6

Slb!"IH JJ

L>

2004 SAP AG

30

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

W C-M9" 9Y-P c 6 + degf+09e$5ihjMklhnmlkohp P D!Cq  rO- Y  O ?r-b

s o@ > ( t l  6?f r M vu , 9wf r tx W !"yf r b

 RQ

        &lr zrf
txu  %8t r ^?r S  7@O_o>otl


srf6|"
}#~Bvr 8
%H6 "t7 Q ! "MS&t" #"- S Q "  t7- r -) - > c +6degf+09e$5ihjMklhnmlkohp " 9G!"  8 H"  9 Y-% b!% H6 " l"
Q

chown R <J2EEAdminUser>:sapsys Navigation_40_60_2

Q 9. "t7 !"IrO- SS" Sv>Y c +6degf+09e$5ihjMklhnmlkohp 9G!" " 9G!" H Y-Mb!"  "l  "  K r ( Mt7 9 E4D 10. ^`?rO-b!"yf J "LrS
DF-l [ M
uP  "S "t A )083& M&4e57e)302+60e$65 23+57)`,$620 &
,$620

chmod R 755 Navigation_40_60_2


M,6"9

n^?r-

2004 SAP AG

31

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC


M,6"9

n^?r-

Q t  tx#"  -"t|" Q  rO-{l 6 -"HMZ T RQ   S &  lr xDF-l^,6 M T     M
?r t7I    tx 

JY@?rO

 E 9 ?r-ZoE4SSt !"



#%$&('*)+-,.'/,#%01'*#%2&
hM8l+670h)382dMe#%8)  Q dM82 $5x8 r-Y   tx- r

2004 SAP AG

32

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC


M,6"9

uMSSt" #"

2004 SAP AG

33

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 5.3.3 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. 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:

2004 SAP AG

34

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
.oMM%o

Property
=g%gyV 6o%6Sl` % 6.yVUMo

Value
y`<6% o%g%%% 6 VoV % o.%oUVl`% S%=%l%o YVoV . sgUVoV % z z VoV VoV % M

Example: Business Package for SAP CRM 4.0 60.2 yM%%%o<yM<V%/

.

sg % z zoV % z oV  M3 z zl zoV % zoV  3% o=

%% . % %%% z z

6UM6%o oV V zoV %%

zoV o.%o VoV%S% VgggV n Vg%gySl 3Vgg  y`<6%\  Vg%gySl=% 66Vg Vg gV o.6o V3gyg` %g%ygy` %%VV .VoV Vg gV6S%= o.V%=

MM%lM%o% % M %\%M%o% %M

V6 y6V % 6o % 6 6

. yM%%%o<yM<V%/*%% yM%%%o<yM<V%/*%% 

s6

Sl`
V

%=UlMo MSz

M%`

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 ternet Transaction Server (ITS) , CVIEWS, ICSS, and Shop 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:

2004 SAP AG

35

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

 !"#"%$&('*)+'*, .-& '*/0.12(3546!/78:9 ;=<>@?#ACB DFEBHGIJG%>C?#K@L0?#G%M0I N ;=<>@?#ACB OPM0IRQ.GTSUJKCL7?#GM7I N ;=<>@?#ACB

 V

/0-&WX-&YZ\[]@6(^# 

`H'*a$&cb Wd 6e/0$f'*)J'*6, .-& '*/0.12(3546!/7:9 g YJ-f/$ %$fcb Wd@

2004 SAP AG

36

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

_ V

PUBLIC

/0-&WX-&YZ\[]`h'*a$&ib Wd a$&('j)J'*6, .-&\'*/7k1"3546/7:9 l /78%$&(6,m1"

6e/7@6

_ V

/7-f6WX-&YZ\[n`h'*(%$fcb Wod@ a$&('j)J'*6, .-&\'*/7k1"(3546!/7:9 p q-&1"@1"@W'

6e/06

_ V

/7-f6WX-&YZ\[n`h'*(%$fcb Wod@ a$&('j)J'*6, .-&\'*/7k1"3546/7:9 l YZ, , )

6e/06

2004 SAP AG

37

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

r

PUBLIC

-&#WsJYZ@(%$fc1", !@'t#"%$f '*)J'*6, k-f\'*/7k1"3546/08#2YZ'*u9 '*'*Ws5- a$&'*)J'*6, oWw' ;=DFy{zO}|~ u9k`H'j '}a$&(\YZ YZ("%$&(\YZ'*WX-&'*'tZ/0JsJ# } x  \# ;=DFy{z v

#2/7-]-&/06W-&s3nYZ'*WX-&'*' l v 1"/0JsJ3546/0'} '*)+'*!, '

r V

/7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12, !' #2a$&'*)J'*6, .-&\'*/7k1"3546/78#2YZ'*u9 v '*'*Ws5a$&'*)J'*6, oW'

r V

/ -f6WX-&YZ\[n-&#Ws+YZ(%$&i12, !' 7 #2a$&'*)J'*6, .-&\'*/7k1"3546/0"Yn'*u9 v '*'*Ws5a$&'*)J'*6, oW' V /0-&6W-&YZ\[

2004 SAP AG

38

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

r V

PUBLIC

/7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12, !' #2a$&'*)J'*6, .-&\'*/7k1"3546/0"Yn'*u9 v '*'*Ws5-1"1"6W' 6sJ) v O}M0IJI+A@?#M0K 9

1n1"W/7W-$f'* s+W/7'*)J'*6, -&, 

},

6i$&'*86)=12

Wo-f-&,  l v '*)+'*6, -&, 

r V

/7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12, !' #2a$&'*)J'*6, .-&\'*/7k1"3546/08#2YZ'*u9 v '*'*Ws5-1"1"6W' 6sJ) l v O}M0IJI+A@?#M0K V '*)+'*6, /0-&WX-&YZ\[R9 -&YZ,m3Z!

r V

/7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12, !' #2a$&'*)J'*6, .-&\'*/7k1"3546/0"Yn'*u9 v '*'*Ws5-1"1"6W' 6sJ) l O}M0IJI+A@?#M0K V  1"@ 6,m1"6c-f, 6)=1"  /0-&WX-&YZ\[R9

l l

)J'*6, )J'*6,

2004 SAP AG

39

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

r V

PUBLIC

/7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12, !' #2a$&'*)J'*6, .-&\'*/7k1"3546/0"Yn'u9 v '*'*Ws5-1"1"6W' 6sJ) v l v l v l v l A@}D%G%L0?#G%M0I;JA@KCACKi# \'*/0WX1"6W$&'j-&, 12%$ 126/7  DF;+ 9

r V

/7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12, !' #2a$&'*)J'*6, .-&\'*/7k1"3546/0"Yn'*u9 v '*'*Ws5-1"1"W' >CA@K~ L7IJLSACBHACIJ? 6sJ)m 9 g s+- , %$& r !#@q-&/7('j)J'*6,

`H'*!",

.1n1"WX-&s6)51"

If you plan t o use the analysis functions, you must configure an SAP BW system as described in this process and using the same procedure.

5.3.3.2

User Mapping to the Target System

Once you have configured the parameters of your system landscape object, you must map the users from SAP EP 6.0 SP2 to SAP CRM 4.0. The prerequisite for this is having a corresponding user in both systems. The following process illustrate user mapping for the system landscape object in EP 6.0 mapped to the SAP CRM 4.0 system:

2004 SAP AG

40

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

  -&1"W'*Z6 -f WsJ6(69 v `h'* \, WX-&W'*66W`h'*" .1n1"WX-&s l /781"YZ'* oN N

PUBLIC

'*'*Ws5-

a$&sJ!'j)J'*6,

`H'*!",

.1n1"WX-&sZ9k{-&6"%$&(s+-

\6

5.3.3.3

Function Test for the Business Package for CRM 4.0 60.2

Once you have completed the user mapping and the previous tasks, you have finished implementing the business and can use it. 1. Select one or more roles for users or groups to use the business package. 2. Check the role assignment. 2004 SAP AG 41

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 3. Log on to the portal as a user with a suitable role. 4. Check the connection from SAP EP 6.0 to the SAP CRM 4.0 system: a. Check CRM functions b. Check BW functions

PUBLIC

/78@'tZ126YZ'*!'

/ -&6W-&YZ\[ 0 (2YZ'*'

 V

/78%$&

;JL0%A@>~

L7I+LSAK

2004 SAP AG

42

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

P$f!/7a$&('*'*Ws=-&,

q-&

s- 6e%$&i126b Wa$ ^YZ'*2%$f W't'*'*Ws5-& 8'j-f

r V

/0-&6W-&YZ\[Z6YZ'*!'t'*'*Ws=-& ;JL7%A@>~ L7I+LSA@K a$& 

6

2004 SAP AG

43

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

P$f!/7a$&#YJ-&/76W- YZ'*WX-&s%$&(WXFWqb #, a$&i3nYZ'*WX-&'*'&1"/7JsJ

'

V

/7-&6WX-fYZ! []P$&/7%$f#YJ-&/0W-&'9

/0/7!'*'t61"@ YZ/08 

'*YZ:9.$fc3nYZ'*WX-f!'*'f1"/7+sJc$f' } 3nq- '*YZ/0/7'*'*YZ)WX-&'*6 .-& %$f #YJ-&/76W-&'t6'*6

2004 SAP AG

44

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.3.4

Working with Delta Links

The established method of working with portal content objects in SAP EP 6.0 is to use references to the original objects. This makes sense from the perspective of tas k delegation (delegated administration) and for maintenance reasons (upgrades, patches, and so on). This section contains a proposal for working with the objects in a business package. Example: Working with references in the Business Package for CRM 4.0 60.2. A business package can equally be subject to change and the original content should be protected against changes. The established procedure involves working with a reference folder, which has the following properties: The reference folder is in the area of responsibility of a portal content administrator. The structure (hierarchy) of this reference folder corresponds to the requirements for working with business packages. For improved orientation, SAP recommends extending the folder hierarchy to match the folder hierarchy of the business package. The reference folder contains only references to the original objects, implemented using delta links. You should avoid using copies of objects.

The graphic below shows a reference folder and its detailed structure. Example: Working folder WorkBusinessPackages in SAP EP 6.0

2004 SAP AG

45

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.3.5

Transporting Business Packages (Staging)

The activities described in the previous section make staging easier, that is, transporting objects between various systems in the portal environment. Example: Scenario: Let us assume that you are using a three -level system with the areas Test, Consolidation, and Production. Your task is to create a concept for transports for the Business Package for CRM 4.0 60.2. The solution is made possible using the reference folder described in the previous section. The Business Package for CRM 4.0 60.2 is installed in each system in the portal environment. Result: You have to transport only the reference folder that contains the links to the actual business package. This results in the following procedure for the entire transport process from Test to Production: 1. Create a transport package Reference1 containing the reference folder and its content. 2. Transport the transport package Reference1 from Test to Consolidation. 3. Check the functions. 4. Create a transport package Reference2 containing the reference folder and its content. 5. Transport the transport package Reference2 from Consolidation to Production. 6. Check the functions and production use.

2004 SAP AG

46

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

5.4

Uninstalling Business Packages

There is no application or tool support for uninstalling a business package. You must work through the procedure manually. Based on experiences to date, the following general procedure has proven to be practical:
h6(%&(@(**=&  \# q&6Z*C q&86

h!a&**=& a& @7+J@J

uh \ fC@HJ%C#@0#%0 }0%@  ]u #2a&( @7+J@J 7 \8a&(+J "@"@ u0%& 7@7P7+#@+ ]f*}CH0 7+@}

Z**e\6.&%f!"o **5f q&6t6e%&  Z*X&* "JJ

2004 SAP AG

47

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

h6(%& +Xf 

PUBLIC

6(%&(F h "JJ  \#

tX

a&

Z*Xf!*

%f#\}#2a& Z Xf!*tZJJ(2h  

0J#CJhTC7#C   } t%" ! uR"0# #\tk& a&27&6q&

\ eP&.& .&J q& e  e #uXf & 08u &@0 f6   +6Xf eZ6H\ Xf*6 eu eu  0

2004 SAP AG

48

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0



%f(}0%@#\

PUBLIC

h6(%&(@tX  \#

!a&tX % h & Z*X&*}\!++(#" 

\!*cf " J*Z(%&8J \ f\6(%&(@}}0J#CJ 7+@ .& #& Fh%J@#C7#7% $

&

h6(%&i2+tX  \#

%f' C#\

%fc"JtX %& Z*X&*}\!++(#" 

\!*cf " J*Z(%&8m f\6(%&'() #R"0#""+ 7@7+ *,$

h6(%& #\  \#

+*6tX

%f.-

7@0@C#

%f/ J*!tX Z*X&*}\!++(#" 

%&

\!*cf " J*Z(%&8J \ f\6(%&'() #R"0#0 J*6 7@7+ *,$

2004 SAP AG

49

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

1
a&32{C%7@

PUBLIC

h6(%&(6m"!tX #\  \#

%f! 26tX Z*X&*}\!++(#" 

%&

!*cf "J*Z(%&8J \ \ f\6(%&'() #R"0# m26 7@7C#0%q0+*4$

h6(%&(*+*! #\  \#

tX

a&76=@#CH

%f*J*6 tX a& Z*X&*}\!++(#" 

9\  J6(6:6=@#C FHJ%C#@0#%0 6=@#C P0<;.T=JC7#7 6=@#C

Depending on the business package being implemented, deinstallation can take some time to complete. Depending on the package structure, you should allow sufficient time for this process.

2004 SAP AG

50

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

6 Appendix
6.1 SAP Notes A Compilation for Business Packages

The following list of SAP notes represents useful sources of information when working with business packages.

No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

Note No. 564198 642775 660774 640634 642999 644024 640678 640330 691782 642827 645627 649062 659881 642515 654959 660777 668154 675280 683705

Description Missing technical documentation for CRM objects in iViewStudio Composite SAP Note for Business Packages as of EP 6.0 SP 1 Installation of the Business Package for SAP CRM 4.0 60.2 KM compatibility package Import Filter Workforce Management iViews in EP 6.0 Groupware Integration in EP 6.0 EP6: Adding Properties to systems and system templates Disable Caching for Balanced View in BP for SAP CRM 4.0 60.x BP for Portal Users on SAP EP 6.0 PCUI: Complex input help does not work in EP6 portal (value help problem) SAP CRM 4.0 50.2 Correction of object link for Internal News Compatibility of navigation of People-Centric CRM with EP6 Compatibility of PC-UI navigation with EP 6 Translation does not exist Extensions for KM in CRM4.0 do not work in BP60.1 and BP60.2 Saving and Resetting Properties fails. Modification of pdv Factsheet iViews for EP6 Compatibility Search URL generation incorrect for EP 6.0 Portal

2004 SAP AG

51

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

PUBLIC

6.2

User Registration for iViewStudio at www.iviewstudio.com

If you do not have a user for the iViewStudio, work through the following steps: 1. Choose Register Now. 2. To register, enter the following information in the Licensed User section: First name Last name Company e-mail address (for example, myname@mycompany.com ) Customer number Installation number of your Enterprise Portal installation

To log on to the iViewStudio, you must use your company e-mail address (for example, myname@mycompany.com ). Otherwise, the system issues an error message. 3. 4. You receive the password by e-mail, usually within 24 hours. You can use this user to log on to the iViewStudio.

2004 SAP AG

52

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0

>

PUBLIC

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 , NT, EXCEL, Word , PowerPoint and SQL Server 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, z/OS, AFP, Intelligent Miner, WebSphere , Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA 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, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame , VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 trademarks of their respective companies.

2004 SAP AG

53