ENTERPRISE PORTAL 6.

0

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

2

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

3

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

4

This is beneficial for maintenance (delivered portal content. or information that he or she needs for a particular workstep. Portal pages. An iView receives and processes data from various sources in the enterprise or from the Internet and displays this in the Portal Content area. A simple workset therefore described the tasks that a portal user requires to handle a specific business process. applications. SAP principally recommends working with delta links. if a user wants to have acces s to tools.3 Semantics and Business Packages We can also describe content objects from the semantic perspective: An iView represents a workstep. the next structure level. are grouped together as simple worksets ( collection of tasks ). 3. Therefore. Related iViews that support these steps are grouped together on a portal page.1.0 allows you to use portal content objects from business packages more than once. in turn. and inform ation for users responsible for a particular area. Workset: A workset logically bundles related pages and forms the basis for the navigation. for example. The portal user works through various steps.5 The Delta Link Concept The delta link concept implemented in SAP EP 6.0 3.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. and reuse. Role: As described in the previous section. content from other departments. One use case is distributed and very large portal implementations. 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. A workset allows access to tools.1. This allows you to create a chain of interlinked objects. Objects generated by means of delta links can have different properties. ©2004 SAP AG 5 . When working with content objects for business packages. Some business processes require one or more simple worksets to be grouped into complex worksets. the original object is retained. These are used to cover more extensive areas of responsibility. 3. object protection. applications. If you delete the delta link object. you can generate further delta li nk objects. From delta link objects. user administration) and distributed access to content objects. and so on). These worksteps are part of a business process. because otherwise the objects are not updated automatically when you import support packages and new minor releases. You can change objects generated by means of delta links without changing the original objects that the delta link objects reference. The content of a page provides the tools to process or resolve this task.4 Delegated Administration The concept of deleg ated administration allows distribution of administrative tasks (for example. from SAP. • • • 3.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. delegated administration is a process for hierarchical distribution of administrative tasks between one or more administrators or groups of administrators.1.1.

2.3 Support Packages and Upgrades for Business Packages 3.com/ep. has been developed solely for use with SAP CRM Release 4. you can display more information about the package ( Package Information tab page) and the support package (Support Package tab page). You must follow this information. it is not released for earlier portal platform releases or support packages.2.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. worksets. Choose Administration Guide → Portal Platform → Content Administration → Content Object Model.2. A business package upgrade can contain the following content: • • New languages New iViews.2 Business Package Release Numbers The release numbering of a business package is composed as follows: <SAP Enterprise Portal Release> . They are created at regular intervals and shipped through the iViewStudio.1. the business package has support package level zero with the release number 60. as in the case of the SAP BW business packages. others are release-independent.0 PUBLIC For more information about the delta link concept.iviewstudio. you can find the information Support Package Available on the iViewStudio in the Content Catalog. <Support Package Level> In our cases.3. By choosing More Information.2 Upgrading Business Packages example.3. or roles.0. for 60. the business package is either suitable for several back -end system releases. that is. 3.sap. you cannot use it with SAP CRM Release 3. that is.0 SP2.2. You can find this on the SAP Help Portal at the Internet address help. release 60. in the entry for the business package concerned. the business package release (minor release) changes. support package 3 contains all changes included in support packages 1 and 2. Some business packages are released for a certain release of an application system. In the detailed information on the business package in the iViewStud io (www. Significant is also the portal platform release of SAP Enterprise Portal 6.1 Support Packages for Business Packages Support packages are used to correct errors in the software. Support packages are cumulative. or iViews with changed features ©2004 SAP AG 6 .2. 3. 3.1 to During an upgrade.0 SP2.0. see the administration guide for SAP Enterprise Portal 6. from 60. 3.0. as in the case of the Business Package for Manager Self-Service. Therefore.1 Business Package Names The Business Package for CRM 4. you can read that the business package used in our scenario is released for SAP EP 6.com). only the latest support package is availabl e for download from the iViewStudio. If a support package is available for a business package. 3. Support packages contain o nly corrections to iViews. <Business Package Release> . that is. or it is plug -inbased. they do not contain any new pages. If no back -end release is specified in the business package name.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.

Knowledge of the storage structures is significant for migrating portal content.<project>. Every on the iViewStudio (path: Content Provided by SAP User). You should not change the SAP objects. A business package upgrade is frequently connected with an upgrade in the back-end system or a plug-in. This ensures simple orientation and recognition. The storage of business packages differs according to whether the business package is question is a native SAP EP 6. You must note that a portal content object can be assigned to more than one other portal content object.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. Bear this in mind when planning your upgrade. For example. worksets. pages. 3.0 that is migrated during import. Related Lin ks 3. Specialists.0 • • • • New or changed pages New or changed worksets New or changed roles New or changed dependencies to back-end systems. For more information about upgrading business packages. 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. This is described in the SAP Collaboration Room documentation. 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.0 business package or an SAP EP 5.sap. Only two minor releases of a business package are available on the iViewStudio. An exception to this rule is SAP Collaboration Room – in this case you must copy the objects to your namespace for production use. in order to be able to use all features. see the iViewStudio in the column in the Portal Content News section.pct. the native SAP EP 6.0 business packages are   stored in the portal catalog in the same way as Content for Line Managers . and iViews. the SAP namespace starts with: com. In principle.1 Storage Structure for Native EP 6.4 Object Naming Conventions The objects in business packages are also subject to naming conventions.0 Business Packages The following storage structure in the portal catalog describes the storage of portal content objects from native SAP EP 6. For all o bjects in the portal.0 business package released for SAP EP 6. because the objects in the SAP namespace may be changed during subsequent upgrades of the portal or support package imports. ©2004 SAP AG 7 . such as roles. 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.5.0 business packages.5 Storage Structures for Business Packages in the Portal Catalog This section described how the imported business packages appear in the p ortal catalog. 3.

0 3.0 are located in the Migrated Content folder. portal content objects that are migrated from SAP EP 5.2 Example: Storage of SAP EP 5.0 are stored in a predefined folder.0 to SAP EP 6. The graphic below shows the storage structure for the Business Package for SAP CRM 4.0.0 PUBLIC Generally.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. subfolder EP 5.0 Business Packages in SAP EP 6.0: ©2004 SAP AG 8 . In the case of a migrated business package.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. The objects migrated from SAP EP 5. a folder is created in the EP 5.

and so on). However. Account Manager. 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. ©2004 SAP AG 9 . and Partner Employee E-Commerce: Customer and Customer Administrator Administration: CRM Portal User. Sales Assistant.0 PUBLIC 3. It contains the following roles: • • • • • • • Sales: Sales Manager. Partner Manager. and Billing Clerk Marketing: Campaign Manager. Lead Manager. You can combine and personalize the por content objects contained in the business package as required.3 Using Business Packages when referencing objects. and KM Author The content of this business package supports employees when they face decisions and operational issues in their daily work. and newer versions of business packages.0 The Business Package for SAP CRM 4. and Brand Manager Service: Service Manager and Service Representative Interaction Center: Interaction Center Manager and Interaction Center Agent Channel Management: Channel Manager. BSPs. 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. iViews (including external services.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. Partner Manager – Channel Commerce. and Customer Services. who require central access to all relevant data information on customers and markets.0 is targeted at employees in Sales. You can access structured and unstructured CRM content and tailor it depending on how it is used.0 for SAP EP 6. Marketing. The benefit of using shared objects is the possibility of extending a business package to include functions from another business pack age. and worksets can be shared objects. 3. pages. 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.6 Shared Objects Some business packages reuse components located in other business packages. support packages.7 Overview: Business Package for SAP CRM 4.0 for EP 6. Lead Qualifier. roles. SAP recommends following the procedure documented in section 5. CRM Portal Administrator. 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. Each original shared object is assigned to only one business package. Sales Representative. Trade Marketing Manager. cross -package usage results in dependencies with regard to upgrades.

©2004 SAP AG 10 . If you have a user for iViewStudio.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. The prerequisite for this is that you have registered as a licensed user of iViewStudio.iviewstudio.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. The procedure for doing this is described in the appendix to this document. iViewStudio provides the following functions: • • • Searching for business packages Displaying details for a business package Downloading business packages. and additional information about business packages. 4. log on to iViewStudio and accept the conditions of use for business packages. The prerequisite for extended access to iViewStudio is having a registered user.1 iViewStudio Structure You can find iViewStudio on the Internet at www.com . documentation.

The technical information on the business package is available in the Online Documentation area. there are numerous business packages for SAP EP 6. start The Software-Centric Search allows you to search for business packages for a specific backend system.2: ©2004 SAP AG 11 .0. Example: Results of the search for the Business Package for SAP CRM 4.0 4.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.1 Searching For a Business Package PUBLIC In the iViewStudio Content Catalog. To do this. the system displays the business packages found. There you can also find information about configuring the backend system and specific installation instructions. If you require more information about a business package. choose More Information.1.0 60. When the search is complete. you select the category required from a dropdown list in the Software-Centric Search area. You searching for business packages by choosing Content Catalog on the entry navigation bar.

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. short description. you can first see an overview of the business package functions.1.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. business area. More Information.2. and adding the package to the download basket. iView runtime technology.2.0 60. If you choose More Information. Example: Business Package for SAP CRM 4. Package Information – Business Context: ©2004 SAP AG 12 . delivered roles o License Information: License model. you add the business package to your basket for subsequent download. languages supported o System Requirements: Data sources for connection. other prerequisites o Business Context: Industry.2 Displaying Details for a Business Package In the section about each business package. target group. Below this. status. portal releases.0 PUBLIC 4. there are buttons for more information. Package Information – General Information: Example: Business Package for SAP CRM 4. Add To Basket. information appears about the following: • Package information: o General Information: Name. release.0 60.

Package Information – System Requirements: System Particularly important is that you heed the portal release specified in the Package Information Requirements section.0 60.2. The corresponding business package can be implemented on the portal release specified here. Package Information – License Information: Example: Business Package for SAP CRM 4.0 PUBLIC Example: Business Package for SAP CRM 4.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 60.2.   ©2004 SAP AG 13 .

In some cases. For example. a business package may be listed in the iViewStudio catalog. a local back-up copy is required in the following case: A business package. or an upgrade is installed on a test or QA portal for test purposes.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. You should also save support packages or upgrade files from iViewStu dio locally. choose More Information → Documentation. ©2004 SAP AG 14 . Provided that you possess the license required.1. so that you can access them again at a later time. If you are interested in one of these business packages. You must also note the release number of the installed package.3 Downloading a Business Package You require a user ID to download business packages. either contact the corresponding ramp-up owner or wait until the business package is generally available. you require a local back-up copy. you can start downloading business packages immediately. you can also fi nd support packages for individual business packages here. Please note: SAP strongly recommends saving and archiving the downloaded . SAP is continuously extending and improving its business packages and therefore the file that you download is available for a limited period only.zip file. When you want to install the tested version on the production portal. These business packages are in restricted shipment and are only available to a limited number of customers at the moment. because SAP Enterprise Portal currently cannot display the release number of an installed package. In addition. you can find the documentation for the respective business packages. For more information about individual business packages. This user ID allows you to access all business packages available. support package. the file on iViewStudio is replaced by a new version. In the content catalog on iViewStudio. but not be publicly ava ilable for download. During this period.0 PUBLIC 4.

0. The business package that you want to install must be released for this portal release.1 Checking the SAP EP 6. each phase is described in detail. 5.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. The procedure is as follows. 5. navigate to: System Administration   Support   Support Desk.0: In SAP EP 6. you should update your software. “ using business packages”.0 Release You must first establish the exact release of your portal implementation. “installation”. If necessary. and “deinstallation” together make up the business package life-cycle.1.0 PUBLIC 5 Business Package Life-Cycle The phases “preparing for installation”. ©2004 SAP AG 15 . which vary Before the actual installation of a business package. Example: Establishing the portal release for the Business Package for SAP CRM 4. you must comp depending on the business package concerned.1 Preparing To Install Business Packages lete the preparations. In this section.

0 PUBLIC Choose Version to display the portal release of your SAP Enterprise Portal: 5. As an example.0 60.2 is documented here: ¡£¢ ¤ ¥¨§©¥£ .HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.1.2 Downloading the Business Package From iViewStudio The next step is to download the business package from iViewStudio. the detailed procedure for downloading the Business Package for SAP CRM 4.

¥     ¥ ¦ ¢ ¢%$   ! "# .

¥£<= . ¥ ¥'& (£")( * +§. "-  * + "# */. 0 * ¥  21¥ * & (3  ¥£ (546¥¨ 7 98:.

& & * 4 ¥£ "# * "#+  >  2§?82! "#  2§ @   .

RJSUT VPWYX $ ¡3¢Z¡£¢\[ ¢ T   ¥£ ¥3 ] ( * ¦" ©2004 SAP AG 16 .¦ ¥¨A5 "- CB)DFEHGJIDLKNMPOHQ.

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 PUBLIC ^ ¢ d $ _`"#  :§© 98:.aP+bc ¥ *  "#+( * 8:A£ : .

 * $ Bfe .

(£. i $ ¢ ( a.h1¥ * j q ¢ $ kml)n +( * 8 * r"#s " .¥"#+( * 8 1¥ * 9 8:hg"#  :+"#" i $ i km) l n []¢%oNp£o¨¢ ^ ( a.(£§. § h "t1¥¨P : g¦"- Z :+"#" [u¢ vw "x<=s(3bY H8:h+ .

(£ s+  :1y¥ * & (3  ¥£ $ ¢ (z 46¥¨ 8: 46  "2 <| ( ‡.

 }~h  = 7 €r H = ‚#{ ƒ/„ €+ €"# …  : ƒ/+ †£"# …: ‡€! …2 ©2004 SAP AG 17 .ˆ aP(£§.

¦‚-‘Z…:€+‚#‚)’Œ£ƒ/“PŒ£”.€h•†¨ ’ kms l—n ˜ Š oNp£o Š%™ j ‡.0 PUBLIC ‰¨Š v – †£‹… †¨Œ£ H ‡ Ž2€.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.

¦‚-‘Z…:€+‚#‚)’Œ£ƒ/“PŒ£”.€h•†¨ ’ kms l—n ˜ Š oNp£o Š%™ j ‡.€ †£…:€+ˆ }‚# p Š v – †£‹… †¨Œ£ H ‡ Ž2€.

•y†¨ ’ kms l—n ˜ Š oNp£o Š%™ j }‚#‡.€ ‡9‹ †¨ˆ }‚# š¨Š v – †£‹… †¨Œ£ ‡HŽ›€h‚#‘…2€r‚#‚t’Œ£ƒ/“PŒ3”P€.

€ ‡9Ž:„€+€rˆ œ.žyŸN Ÿ£¡LŸ3¢ £ …:‚#‡.

Œ Œ£‡.

‘†£……:†¨‡.

€+‚#¤ ‘“.€h‡HŽ:†¨‚#€ ‘‚#‡.

Œ£L¦€+ s  Œ3‚ ‚#‡€! ‡HsŽ: s ”P€…:€+LŒ ‘…:•y†¨L§ Œ£‡.€+ ‘… s „€+€+¤3‚xŽ:†¨ ¦s¥6€.„€+”.

‘ †3… Š5¨ †' § ‚#‡©…2†'‡€ ‡9Ž:€h‚ª=€+s ƒ/‘•y‘ƒ«‘…:‚#‡.

Œ Œ3‡‘†£… ‘…:‚#‡.

„ƒJ‡.

‘†£…:‚ s s ‘…:”¥6‚#‘…:€+‚#‚ •y†¨|‡9Ž:€.ƒJ†¨L„€+‚x=†3…2 =Œ£ƒ/“PŒ3”P€ Š } – €+€ – ’ ¬­†¨‡€r‚#ˆ j ®¨Š € ‚t‘… Œz… Œ3„ƒ°Ž:‘¯€h•† ¦€r Š – Œz¯€h‡HŽ:€h•‘ r s s ± Œ3„ƒ°Ž:‘¯€ ±P™ o£o5˜£²'o ™ ²¨o ™ ²'kml)n ² ’ ²'p£o5² ™ ²¨o ©2004 SAP AG 18 .

1. a user must have a user ID in SAP CRM 4.0 PUBLIC 5. a minimal SAP CRM 4. you must prepare your SAP CRM 4. If you are setting up an SAP CRM 4.0 system forms the basis for the activities performed. For more precise information about installing and setting up a SAP CRM 4. you may require further main components that allow operations. you can install optional dialog instances on different servers. once the central instance and database instance have bee n installed. so that they can return meaningful results. you must install an SAP CRM 4.0 with regard to data and user IDs. ©2004 SAP AG 19 . Furthermore. For subsequent access through SAP EP 6. see the corresponding documentation (installation guides.3 Preparing the SAP CRM System As described in the scenario. and so on). As a test environment.0 system.0 system.0.0. Once installation is completed.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 system. This consists of a central instance and a database instance. The reports require data.

The import f ilter is available for various different portal releases. Other possible modifications are mentioned in the post-installation phase. Rename the text file to cms_mapping. Restart the portal. Depending on the busines s package concerned. In SAP EP 6.2) cannot be displayed in SAP EP 6.0.2 Installing the Import Filter Some SAP Enterprise Portal 5.0. other portal content objects are reassigned. with regard to the effects on functions and the technical naming.0 60. 5. 6. depending on the business package concerned.2 Installing Business Packages The installation of a business package refers to the import of the business packages to SAP EP 6. navigate to: System Administration ³ Support ³ Portal Content Directory ³ PCD Configuration ³ Parameters for Portal Content Migration ³ Pcd. The installation process for the import filter is as follows: 1. Note the path as it is displayed.0 are based on busi ness packages for SAP EP 5. for example. but also a migration at the same time. Therefore. Change the user and group assignment to cms_mapping.Mapfile.Migration. Change the access rights to cms_mapping. you may have to modify the navigation. navigate to the folder path you noted in step two.0. 5. You must install the import filter before installing a business package containing SAP EP 5.0 PUBLIC 5.properties to cms_mapping. As an attachment to SAP Note 642999 Import Filter is a version each for SAP EP 6.0. In SAP EP 6.Path. certain portal content objects in the Business Package for SAP CRM 4. 2.1 Notes on the Installation Most of the business packages currently released for SAP EP 6.properties. SAP provides an import filter and a KM compatibility package. the detailed procedure for installing the import filter on EP 6. 5.0 SP1 and SP2 respectively.2. you must install these before installing the business package.0 is not only an installation. 4.0. 8. On the following pages. The import filter checks these objects: Certain portal content objects are excluded from the import.0. Rename the file cms_mapping.0 content that is released for SAP EP 6.0 objects (for example.0 server.properties for read-write permission.2. On your EP 6.0. Copy the text file from your temporary folder to this folder. Download the text file (depending on your portal release) from SAP Note 642999 to a temporary folder.properties for the J2EEAdminUser and the group sapsys . there are improvements in working with portal content objects. the installation of non -native business packages for SAP EP 6.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 is shown: ©2004 SAP AG 20 . These business packages are therefore not developed natively on SAP EP 6. For example: /usr/sap/ep01/global/config/pcd/Migration/mapping/ 3. 7. For the migration.properties_old. After completion of the installation.

‡.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 PUBLIC ´ Š †£‹… †¨Œ£ ‡HŽ2€.

Œ£‡.€+µ¶‡7•‘ €.

‡Œ3ƒ°Ž:€+ ‡.

¸ ˜ ™£¹3¹£¹ }€=€!…2‘…:”Y†£… ‡HŽ:€ – · ’ º’ ¸ Š¼» L€ €+Œ£‚#€.‘§ €+§ €…:‡.† s s –· ’ ¬­†¨‡€.

€+¦ˆ½‡.

†  s Œ ‡.

’†¨„‡.€+§=†¨LŒ£„¿©•ys† €+ Š ¾ s v ™¨Š £ … ºC…:‡€+À=„‘‚#€.

‡†]Á ÂÄÃ'ÅLÆyÇFÈ ÉÊ3È`ËÍÌPËHÅFÆyÎLÏ/ÆyËHs Ð/Ì Ñ ÂPÒcÓ£Ó¨Ð/ÎLÆ2Ñ Ô Ð/ÎLÆyÏ/թ֗ÐJÌ.ÆyÇFÌPÆ×`ËÍÎLÇLØÙÆÐJÎÚÃ Ñ Ô Ö—× Ö)Ð/ÌxÛzËÝܨÒPÎFÏJÆËHÐJÌ Ñ Ô Ï/ÎLÏ/È`ÇFÆyÇLÎFÅÞÛzÐ/Î Ô ÐJÎFÆyÏ/Õ Ö)Ð/ÌPÆyÇFÌPÆàß ËáܨÎFÏJÆËHÐJÌ Ñ Ô ØÙÊ'âãß ËáÜ'ÎLÏJÆËHÐ/Ìâ Ô ÏJÆä¨âãß Ï„ÓåÛzËÍÕHÇ Š ¬†¨‡.Œ ¸ Š%» ¤5…:Œz¯‘”PŒ3‡€.

€h‡HŽ:€{=Œ3‡9Ž Œ3‚t‘‡7Œz6=€+Œ3„‚t‡HŽ:€+„€ Š ©2004 SAP AG 21 .

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 PUBLIC ™¨Š }ƒJ†3…2‡.

‘…:€+ˆ6¬†¨‡.

€h‡HŽ:€{|Œ£‡HŽ Š q¨Š … ‡HŽ2€.‡.º¦’ ¸ Š%» ‚#€+ç¯€+L¤z…:Œz¯‘”PŒ3‡€.

†‡HŽ2€ æ•y†   €+=¿.†¨Y…:†¨‡.

€+ ‘… ‚#‡.

€ ‡H‹ † Š s è †£=¿©‡HŽ2€.•y„†¨§ ‡9Ž:€ ‡€+§|†¨„Œ3„¿©•y†¨é€+=‡.‡€rµ¶‡7•y‘é€.

‡€+µÄ‡7•y‘é€ ì ØÙÈ`ÅÚí¨ÈwÏÙÓ£Ó'ËHÌÄÜ]âãÓ¨ÎFаÓ'ÇLÎLÆËHÇLÅ ‡. † |€+µÄŒ£§=é€Á ´ ê ¨ ± ‚# ± ‚#Œz ± €! » ± ”.†‡HŽ:‘‚t•y†'é €+ .醣¥6Œ£é ± ƒJ†£…:•y‘” ± |ƒJ ±Cë ‘”P„Œ3‡‘† … ± § Œz6=‘…:” ± ˜ Š €…:Œ£§ €.‡9Ž:€.

‡9Ž:€.† ØÙÈ`ÅÚí¨ÈwÏ°Ó3Ó¨ËÍÌÄÜuâ\Ó¨ÎLЄӨÇFÎLÆyËÍÇLÅÀí'ÐJÕHÊ Š €…:Œ£§ €.‡€+µÄ‡7•y‘é€h‡.

Œ£ƒ/ƒJ€+‚#‚)„‘”ÄŽ:‡.† ì ØÙÈ`ÅÚí¨ÈwÏ°Ó3Ó¨ËÍÌÄÜuâ\Ó¨ÎLЄӨÇFÎLÆyËÍÇLÅ Š · ‚#‚#‘”c… ‡9Ž:€.

Œ£ƒ/ƒJ€+‚#‚)„‘”ÄŽ:‡.properties cms_mapping.properties Ž Œ5…:”P€.properties.‚ Š mv cms_mapping.properties_old ‰¨Š ¸ Š mv cms_mapping.txt cms_mapping.

†£‹…:€+L‚xŽ:‘Z „‘”cŽ2‡.‚t•y†¨ è 2 ƒJ§ ‚ ² § Œ5|‘Z…:” Š =L†£=€+L‡‘€+‚)‡†uÁ š¨Š · ‚#‚#‘”c… ‡9Ž:€.

‚ Š chmod 755 cms_mapping.†£‹…:€+L‚xŽ:‘Z †¨•½‚#€+|Œz…: ”P„†'P •†¨ è 2 ƒJ§ ‚ ² § Œ5|‘Z…:” Š =L†£=€+L‡‘€+‚)‡†uÁ ®¨Š ì €+‚#‡.properties Ž Œ5…:”P€.

Œ£L‡7‡9Ž:€{|†¨„‡.

Œ£é Š chown j2eeadm:sapsys cms_mapping.properties ©2004 SAP AG 22 .

A log file is generated during the import. the detailed procedure for installing the KM compatibility package on EP 6.3 KM Compatibility Package PUBLIC The ne xt step is to install the KM compatibility package.0 SP1. Between SAP EP 5. 2.0.0. Unpack the *.0 5. create a folder for the KM compatibility package with the path: cd /usr/sap/<MyPortalInstance>/global/config/pcd/Import mkdir KMCompatibilityPackage 3.0 KM objects.0 is shown: ©2004 SAP AG 23 .sap. Download the *. 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. You install the KM compatibility package as follows: 1. 4. 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.2. Therefore.0 and SAP EP 6.migrated ³ ep_5.0. The KM compatibility package contains PCD KM objects with the names previously used that the migrated EP 5. These references then do not point to non-existent objects. You can check this at: /usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file> 8. In Enterprise Portal 6. You can find notes on this in SAP Note 642775 Composite SAP Note for Business Packages as of EP 6.portal. After the import. import the package as usual using System Administration ³ Import.0 format.zip file in SAP Note 640634 KM compatibility package to a temporary folder. references to such objects can no longer find their targets. The iViews therefore appear in the more up-to-date SAP EP 6. 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 the PCD import folder. the naming conventions for KM content objects have changed.0 to SAP EP 6. On the following pages.0 KM platform. The KM compatibility package solves t his problem for portal content objects that have been migrated from SAP EP 5.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 content can reference. 7.zip file to this import folder. 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. the imported portal content appears in com.0. Transport ³ The imported PCD objects reference the same program code as the corresponding SAP EP 6.

0 PUBLIC î£ï ï%û3üý  þü ðwñ£òó:ôñ¨õ£ö ÷Hø2ù.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.ú ô ùwÿõ¡ tõ3÷÷.

õ£¢„ø:ù+ö  ¤ ü ý ÷ñ ñ¨÷.

ù¦¥¨§ ©¡¥£ .

§ ó õN÷.

ù ñ Lõ£ þ ï ñ¨ôöù  ï ü ý þ þ „ù+õ3÷ù.õ£.ú ô ùh÷.ù ó ÷H2 ø ù!mð ü ý þ  ñ „÷ ñ'ôö¦ù#" ï ý ï%û3üý  þü ü ü ý $ ó õ¡¢©÷Hø2ù.÷9ø:ù  ñ „÷ ñ'ô öù ñ |÷9ø:ù ý ü6ü ü ý ü ¢Jñ  õ3÷ ô ÷ ¡ õ ¢.

©÷.ñ÷Hø    ñ „÷  þ ï ñ¨ôöù ï ü þ —ø2õ5ó%Pù.÷9ø:ùhõ¡ &  Äó% ùó:÷ „ñ '! #ù ý ü+* õzó:ö („ñ' „ù)¢'!  ù+ô.

>?@4ACB)4EDF þ ñ¨ôöù|õzó:ö þyü þ ü ÷ñ ÷9ø:ù ôù tõ5ó2ö ñ¨ôö¦ù) t÷Hø2õ3÷7÷9ø   ü ï ¢Jñ£ó:÷. /102¦3 46587:9.ñ÷Hø2ù -%.7=<:7:5.

>?@4ACB64EDF{þ ÷ñ ÷9ø:ù ñ¨ôöù þyü þ ü õzó:ö ÷ñ ÷9ø:ù ôù tõ5ó2ö ñ¨ôö¦ù) t÷Hø:õ£÷7÷9ø   ü ï ¢Jñ£ó:÷. /102¦3 46587:9.÷9ø:ù ù  &  ñ£ó% HLù¢'!I  ùrôJ -%.7=<:7:5.õ ó%  ý ü ü ü* —ø2õ5ó%Pù.

õ ó%  ý ü ï ü ý K ó LCó:÷ù   #ùñ „÷.

õ£ô¥ ©£M  ñ „÷7÷Hø:ù ý  ü >QI58FR2 Põ¡Pù N¢„ø:ñ¨ñ   ó%PO SUõ£ T ¢6 2V7=W(7:QR58XI46587:06W Y Z[XR4W(Q 06XI5]Y ^82¦3 06XI5„ï ï cd /usr/sap/<MyPortalInstance>/glo bal/config/pcd/Import mkdir KMCompatibilityPackage § chown –R <J2EEAdminUser>:sapsys KMCompatibilityPackage G ï 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 .

import the package as usual using System Administration c Import.0 from iViewStudio to a temporary folder.portal. 7. After the import. 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 Transport c On the following pages. the imported portal content appears in com. the imported portal content appears in com. The screenshot shows the portal catalog with the imported business package: ep_5.4 Example: Installing the Business Package for SAP CRM 4.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.2.0 c chown –R <J2EEAdminUser>:sapsys BPForSAP_CRM_60_2_0 5.0 As described in the section above. Unpack the *. the detailed procedure for installing the Business Package for SAP CRM 4.0. A log file is generated during the import.sap.0.0 is shown: ©2004 SAP AG 26 . After the import.sap.0.2. 3.0 PUBLIC 5.0 with the path: cd /usr/sap/<MyPortalInstance>/global/config/pcd/Import mkdir BPForSAP_CRM_60_2_0 2. You can check this at: /usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file> 8. In Enterprise Portal 6. release 60.migrated c <business package name>. In the PCD import folder.2. 4.zip file to this import folder. you must work through the following steps: 1.0.0 on EP 6. release 60.0. you have already downloaded the Business Package for SAP CRM 4. Release 60. release 60.2.0. 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.portal. To install the Business Package for SAP CRM 4. create a folder for the Business Package for SAP CRM 4.2. The prerequisite for this is that the import fi lter and KM compatibility package are installed.migrated c <business package name>.

ú ôù ñ=÷Hø2ù d ü þ ï '!  ó:ù & bõ¡¢.÷9ø:ù ñ¨ôöù ñ =÷Hø:ù '!  ó:ù &  þ ï ü õ¡¢.õ£.õ£.÷9ø:ùhõ¡ &  Äó% ùó:÷ „ñ '! #ù ý ü+* õzó:ö („ñ' „ù)¢'!  ù+ô.ù ñfehgi jb § © þ ü+kü ü ý „ñ ùò e÷l'ö ñ ÿ9÷ñ õN÷ù ñm„õ£I þ ï ñ¨ôöù  ï ï § ï G ï ¥ ï þ þ d ü „ù+õ3÷ù.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 PUBLIC î£ï ï%û3üý þü þ ðwñ£òó:ôñ¨õ£ö ÷Hø2ù.©÷.ù ñ fehgi jb § © ó ÷Hø:ù ü ý þ @ ð  ñ L÷ ñ¨ôöù6" ý ï%û3üý þü þ $ ó õ¡¢©÷Hø2ù.ú ôù Lñ  ÷Hø2ù ý þ ü ü ý ÷ù ñ „õ¡ ñ©ôö¦ù|÷ñ ÷Hø    ñ „÷ þ ï ñ¨ôöù ü þ —ø2õ5ó%Pù.

rut.ñ÷Hø2ù no?qp!06X S ?qr /1s%.

v¨r w¨r v þ O ñ¨ôöù|õzó:ö þyü þ ü ÷ñ ÷9ø:ù ôù tõ5ó2ö ñ¨ôö¦ù) t÷Hø2õ3÷7÷9ø   ü ï ¢Jñ£ó:÷.

rut.õ ó%  ý ü ü ü* —ø2õ5ó%Pù.÷9ø:ù ù  &  ñ£ó% HLù¢'!I  ùrôJ S no?qp!06X ?qr /1s%.

v¨r w¨r v ÷.

ñ÷Hø2ù O þ þü þ ñ¨ôöù=õ5ó:ö ÷.

ñ ÷9ø:ù ô ù) tõzó:ö ñ'ôö¦ùI  ü ü ï ÷9ø:õ3÷½÷Hø  H¢Jñ3ó2÷.

õ ó%  ý ý K\ ñ „÷7÷9ø:ù õ¡¢Põ¡Pù.÷ñxehgV ý ü ï  ü L ó:÷.

ù  Sy  #T ù¦ñ „÷.

õ3ô¥ © P¢°ø:ñ¨ñ   ó%!" >QI58FR2 2V7=W(7:QR58XI46587:06W Y Z[XR4W(Q 06XI5]Y O ^82¦3 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 .

¢/ñ£ó:÷ % ó 'ù+ö@ uK8 ñ„÷ _ ï g þyü ü ü ôñ  ôù  H.0 PUBLIC ¥ ï ü ý ï ÿ.ùó:ù„õ3÷ùrö ö@'! ó%©÷9ø:ù ý ï.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.

† ‹‹# ‘ ‹’”“ ‡ ˆ ‹Œ ü ˜ ™ —„ ƒf„:› • ‚ ƒ„lœ¡„› • ‚ ƒ„  š ‹ ƒ ’” ‹ž ‚ ƒI‹ „…¡† ‚ ‹ „’”“ „Ÿ… …¡ •“ “ Š ‡ ‹#‡ “!“ ‹ ˆ ‡ ¡C¢£¥¤§¦I¨©ª¤«© ¢6¬I­8¨6®l¤§£i¯±°¬I¨­²I³µ´ ¶ ² ©£·¸ ¤º¹ ™ » ™ › • „…¡†.…£„l•.‚ ‚ —½„› • ¼€@… ‹ £ ˆ ‡%‹ˆ&ˆ … ‡%– ˆ —‚ ƒfÁ ‡ € ÂÃb~ ‹¾o Ä ¿! ™ œ¡Ã † … ŠÀ ‹ š† „  ‹ ‹ ˆ&‹ Å ™Ž ™ • ‚ ™   ˆHŠ ’”“ ‹ ‹ ©2004 SAP AG 28 .–(ƒI…£ „l•.†.z ü ñ ' }(~ ¢/õz ó €!¢„ ø: ¢† ©÷Hø „…  tõ3÷{" |)lŽ |  ñ | „÷ ý |@ ‚ ƒù „l…£ ! ' &    #   õ K.ˆ ‚ ‡‰ |qŠ6 †.‡‰ ‹– Œ |@}( ‹ |)lŽ |(„ |(~ •.‚ —8‹ •.

par).sap. The main points are the following: • • • • E-mail and calendar integration in SAP EP 6.0 and EP 6.zar to com.sap.zip file to this folder.crm.crmcontext.pct.0. for example. the following section describes activities for implementing the navigation compatibility. you download the attached *.0 60.0 does not support references to generic services (for example.0 with SAP EP 6.crm. you have to work through some post-processing steps.UrlDispatcher. with SAP CRM 4. Copy both PAR files to the J2EE Servlet path.pct.3. This affects the navigation and its compatibility. ValueHelp or URLDispatcher).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. there is a list of related SAP Notes for the topics listed above.zip file to a temporary folder. 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. for example.0. the URL Dispatcher (com.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. In the PCD import folder.pct. Restart the J2EE Engine.sap. 1.crmcontext.1 Navigation Compatibility of People-Centric SAP CRM 4.0) In the appendix.2. 3. 6.par. the path: /usr/sap/ep01/j2ee/j2ee_01/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB INF/deployment/pcd 5.sap. 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. create a new folder. called Navigation_40_60_2. ©2004 SAP AG 29 .crm.0 PUBLIC 5.pct.crmcontext.crm. depending on the business package concerned.zar). Unpack the *.3 Using Business Packages After completion of the installation.0 SAP EP 6. 2. Unpack the file to a temporary folder. 5. Based on the Business Package for SAP CRM 4. 4. Rename the file com. SAP provides the corrected version of the CRM Conte xt Service (com.0. As described in SAP Note 659881 Compatibility of navigation of People-Centric CRM with EP 6. and a package for navigation compatibility between SAP CRM 4.

0 is shown: ‘ ™ Á ţϡ»£˜¡˜ œ É’ šVÊ ËÌÉ ÍÎ ‘ ÐÇ(È ¢#£Ñ©¨­¯:Ò.0 and EP 6. 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.crm_default_services is available.Ú Ð ²RÖ(­8¬R¯:¡ Ð1Û%Ü Ý ¯:­Þàß@٠ᣤº¹ œ ž@É£âµã‰ä.Óx¢ÕÔ×Ö(¨Ø¡¯±°¨­8¯=¢ÖP¢ÕÔ×Ùo²R¢E©®:². 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.Î è Ç(É È Îéêå£ë”ìfä. 11.É å¡ž › › ™§è • —• ™ Í Î¦å¡ÍlÍå¡æ Ξ ç “ ä.Îhí¨î8ï. import the package as usual using System Administration Æ Import. Transport Æ On the following pages.¯:®:¯=­. You must assign this to the predefined group Everyone.pct. You can check this at: /usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file> 12.0 PUBLIC 8.éñð ò@Ê!ó£ô£õ¨ð ö÷1ø ùô ú ïì è É Èfîï. the role com. the detailed procedure for installing the navigation compatibility between SAP CRM 4. After the import.sap. In Enterprise Portal 6.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.é)ðòoÊ!ó¡ô û£ûCð ö÷1ø ùô ú ïì õ ú  üÑý½ìfþ¡ÿ¡ £¢¥¤§¦î8難©¦ ¢. A log file is generated during the import.0.

xþ ¢.

=+¡2 ¢..'/.¦ë”ì þ î ¨©¦6ú ÷# ¦ ý%þ ¦ ¢!¤" ¦ î8難©¦ #%$¡&('*)+-.#%01'*#%2&('*#%23&4#%$657098:01'<.

#%$¡&('*)+-.#%01'*#%2&('*#%23&4#%$657098:01'<..+¡2 ú öC £ì£¢¥¤§¦ DFEV÷ î8難©¦¢9 G¢!¤"¦IH õJJ K ¦L>¨©¦¢mìfþM¢!¤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 S¦L@ > ï.ÿ¡¦ S¦V>¨¦ ¢ð  ì -   ìY X ¦”ì ï© -  ¢ \[  N  J òF]^`_ o # ¦ ìO¨ 7 # ¦ ý"¢ ìfÿ6 ùªú a ú ÷¦S¢lþ¢b¢!¤"¦IH õJJ ¦L>¦ ©2004 SAP AG 30 .

0 PUBLIC ó ú { W öC-¦þM¢9¦þý"¦ î9 ¨©Y¦-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ô û tx¨© u þ¨ ÿ¡ £ý%î8ï©t r ÿ¡ ^?r ¢ S   7@ïO_µþo>oï©tþ¢lï© £ý½ð£ùô.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.

ð ó¡ô.

ðõ ú € üÑýsrfþ£ÿ6 |¢¥¤"¦ }#ú~B£ïvr î8難©¦ ¢.

¢¥¤%ï©Hî ¨©¦6ú ú ö¤‰þ¨ý"t7¦ Q ! ¢ ¤"¦¦þMS&ï©têý" ¦#ý"¢Ÿî-  S¦ Q þ.

" ý  t7- r -¦)ÿ - ï‚>¦¨©£¢.

¢¥¤§¦ c +6degf+¡09e¥$¡5ihjMklhnmlkohp î ¨©¦ þ.

ý" ¢9 G¢!¤"¦  î8© ï ¨©¦Hþ¨" ý  9 î ¨©Y¦-ƒ¢¥¤% þ ¢b¢!¤%© ï H6 ÿ £" ý ¢lþ£ïý"ñú Q chown –R <J2EEAdminUser>:sapsys Navigation_40_60_2 Q 9. ö¤‰þ¨ý"t7¦ ¢!¤"¦IrO¦- „©SS„© £ý"ƒ¦ÿ S„v>Y¦¨© c +6degf+¡09e¥$¡5ihjMklhnmlkohp†… ¢9 G¢!¤"¦ ¨©¦ þ.

^`?rO -¢b¢!¤"¦yf J ý"¢.ý" … … ¢9 G¢!¤"¦ „©¨©¦Hþ¨ý§ ¨©Y¦-ƒ¢¥¤‰þM¢b¢!¤"„© ÿ¡£ ý"l ¢ þ „ ý"ñ  ú K r þ¡ÿ¡(   þMt7¦ ¢9 E4D 10.

$620”‘ • & .¦Lr„©S¦ DF -l [ ¢ þM¨ ‡ ú§ôˆu‰P  ÿŠ¤"  S „ ý"t ‹AŒ )083& ŽM&4e57e¥)302+60e¥$65 ‘ ’“23+¡57)`.$620 chmod –R 755 Navigation_40_60_2 ú û.

ÿ6 £ý"¢9„ý Q ¦—n^?r -¢ ú ©2004 SAP AG 31 .ô úM–.

0 PUBLIC û.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.

ô úM–.ÿ6 £ý"¢9„ý Q ¦—n^?r -¢ ú û£û¡ú E Q … ¨ t „©¨¦ „©ƒtx¦#ý"¦þ¢.

¦  -„ý"t|¢¥¤"¦ Q „© rO -¢{úl˜ ÿ6þ.

ý§›¢þ¨ý‰ÿ6¦œ õM¦¦ T    š … õM¦¦ž  ô û ¢.ý ÿ-¤"¦ÿ¡ £¢¥¤§„©HþM¢Z™ T RQ  š S &  þlr ø xDF -¢lþ¨©^.

¦?r ø „©t7I  þ¢.

„©£ ý ¨© tx „©¨ ¦œ ú JY@êþ?rO¨¦™ û.

.'/.#%01'*#%2& hŽM8 Ÿl+6¡7¢0©h)382dMe¥#%8) ¢.õú E … ¢9¦¢¥¤§¦ „©?r -¢Z™oE4SS„©t ý ¢!¤"¦  ¨©¦ #%$¡&('*)+-.

¢¥¤§¦ Q … dM82 Œ $¡5x8 r-¦Y¦  „ ý§¦ tx- r £ ú ©2004 SAP AG 32 .

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 PUBLIC û.

ÿ6 £ý"¢9„ý Q ¦—u÷ ¨©¦¦þMSS„©têý" ¦#ý"¢ ú ©2004 SAP AG 33 .õ úM–.

0.0 is installed.0 60. In our scenario. you can find an example of the value assignments for an implementation of the Business Package for SAP CRM 4.3 As CRM system.2: ©2004 SAP AG 34 .3. (To use the analysis features.0 system.0. you can find the entries in the object properties. For other SAP systems. 5. The creation and management of system landscape objects tasks are part of the system administration for SAP EP 6.3.0 SP2. As the portal.0 PUBLIC 5.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. The most important steps are described below: 1.3.) Users are available in this SAP CRM 4. 2. For example: Access to SAP CRM 4. release 60. Modifications in SAP EP 6.2.1 Creating a System Landscape Objects to Connect SAP CRM 4.0. you now have to prepare the access to the participating backend systems. Release 60.0.0 SP2 using the Business Package for SAP CRM 4. Configure the parameters of the system landscape object for use: a. you can work with the portal content objects.0 SP2 is used. The Business Package for SAP CRM 4. b. The object property is System and the values specified there must match the system alias. an SAP CRM 4.3. Create a folder for the system landscape objects.2.2 Working With Business Packages Once you have completed the postprocessing steps. SAP EP 6. 3.0 system is implemented. Assign the system alias for the SAP CRM 4. Data is available in SAP CRM 4.0 Prerequisites • • • • • • 5.0 A system landscape object creates the connection bet ween portal content objects and backend systems.0 through SAP EP 6. Users are available in EP 6. The activities that occur most frequently are documented below. Launch the System Landscape Wizard to create a system landscape object. you also require an SAP BW system.0 You need to modify SAP Enterprise Portal to use a business package. Assign properties for various categories: On the next page.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.

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 ¤.¸y¶¡¹V´UÕMÊo­®Ë Value ¸y¶¡¹`´»º<¼§¶6½¾³%°±· ¶ Èo°±²ª³%¯gÍ%´µÎÅÆËËÐÏ¥²ªÎ³%Å.¥o¦M¦M§%¨ª©¥o« Property ¬”­®­=¯±°g²ª³%´µ°g¶¡·ƒ¸y¶¡¹V´ Ç ¶6Èo°±²ª³%¯6ÉSÊl¹`´µË½ Ì ³%½¾Ë Ò Ë½¾¶6´µË.

Ô Ýs¯g°±Ë·´ Ì ³%½¾Ë Éz¬ Ô ÉzÊo¹V´µË½ Ì ³%½¾Ë Éz¬ É Êo¹VÔ ´µË½ Ì Ø®½ƒàMË3Å z ÉzËÅ.³%²ª´ÑËÅ Ç 6 ¹VÊo¹V´µË½ ·³%½¾Ë ÕÊo­®Ë.Ü Ýs¯g°±Ë·´U¹VÊo¹V´Ñ˽ ·³%½¾Ë Éz¬ Éz¬ Ô Ô ¹VÊo¹V´µË½ ¹VÊo¹V´µË½ ·³%½¾Ë ·Ø®½ƒàMËÅ Ã Example: Business Package for SAP CRM 4.0 60.2 °±¿yÀMÁµÂ%Â%Ã%Ãoº<¿yÀMÁ»º<¹V³%­Äº/²ª¶¡ÅÆ­ ÒÓ.¶¡Á´µ³%ÅÆÈoË´U¹VÊl¹`´µËн¾Í%Á¶¡Å ËÖS³%½¾­=¯±ËÍ%×l³%¯±Ø®Ë”ÙªÃoړÁµ¶¡ÅÛ´µÎË ÃY¹VÊo¹V´Ñ˽ Ò.

×lËÅ Ô ÉzÊo¹V´µË½ Ì ³%½¾Ë ÉzÊo¹V´µË½ ¶¡Å.

´ ÕË3½¾­®¯±³%´ÑË ÕÊo­=Ë Þ%ß%ß ÒÓ.Ô ß%ß Ã%á%ß%ß Éz¬ Ô Éz¬ Ï¥Ý ¶6Å.

´U·Ø®½ƒàMËÅÛ¶6Á´ÑÎˉ´Ñ³%Å.

ÈoË´ Ô Êo¹V´µË½ ¹V ÉzÊo¹V´µË½ ´µË½â­®¯±³%´Ñˉ·³%½¾Ë Òã à ÉzÊo¹V´µË½ ´µÊo­®Ë.¶¡Á´ÑÎˉ´Ñ³%Å.

ÈoË´ ¹VÊo¹V´µË½¾Í%Áµ¶¡ÅÛËÖS³%½â­®¯±ËÍ Ã ä ¹V˯g˲ª´µ°g¶¡·ƒ¯±°g¹V´µå ÒnÜ ËVàˆ¬§­®­®¯g°±²õ³%´µ°g¶¡·yÉSËÅ.

×lËÅ ó Ë3ôV²ªÅ.

°g­®´µ°g¶¡· À ¸y¶¡ô`´»º<¼§¶6½¾³%°±·\ö ¡ ¶ Å.

´ Ô ËVàˆ¬§­®­®¯g°±²õ³%´µ°g¶¡·yÉSËÅ.

¶¡Á¯±¶6Èo¶¡· ä ôV˯±Ë3²ª´µ°g¶¡·y¯g°±ô`´µåÍ Á¶¡ÅÛË֛³%½¾­®¯gËÍ%¿y°g´µÎyØ®ô`ËÅøÿ¼ ³%·Àˆ­®³%ôVôV¿ƒ¶¡Å.×lËÅø­=³%´µÎ ó Åƶ¡´µ¶6²ª¶¡¯6ôV˯g˲ª´Ñ°±¶¡· ä ôV˯g˲ª´Ñ°±¶¡· Ô °gôV´µå ¯± ÕÊo­®Ë.

À ËÁµËÅ.

Ë·²ªË.ôVÊoôV´µË½ ä ôV˯‚˲ª´µ°g¶¡· Ò °gôV´µåÁ¶6ÅÛËÖS³%½¾­=¯±ËÍ¢¡£¡¤¡£¡ ¯± ß ÕÊo­®Ë.¶¡ÁØ®ôVËÅÛ½¾³%­®­=°±·È Ô®æ%Ò § èˆé”êMêMëìµ¨ªí%©ìµ¥l¦ïîM§%«Æðo§%« ç % ñ ç é”îMò ó ó ó ó ù”ú §%«\ûüí%¦Mí%ýo§%þ §%¦M© ¬”ɧ¼§ËôV²ªÅÆ°±­®´Ñ°±¶6· ¬”ɧ¸y¶6ôV´ Ì ³%½¾Ë ¬”É ¬”É Ô ã Ç ¶6Èo¶¡· Ô ³%´µÎ Å.

¶¡´Ñ¶¡²ª¶6¯ Ë´µÎ¶6À ÒÓ.Ô °±¿yÀMÁµÂ%Â%Ã%Ãoº<¿yÀMÁ»º<ôV³%­Äº/²ª¶¡ÅÆ­Äö*÷ªß%Þ%ß °±¿yÀMÁµÂ%Â%Ã%Ãoº<¿yÀMÁ»º<ôV³%­Äº/²ª¶¡ÅÆ­Äö*÷ªß%Þ%ß Î´µ´µ­   ÿ¼ Ô ó ¼ Ò Ý Ýs¶6·´µË·´¦¥ ËÁµËÅ.

WFM CS. In ternet Transaction Server (ITS) . and Shop Administration On the following pages. the detailed procedure for creating a system landscape object in EP 6. ISA B2B.Ë·²ªËÉSÊlô`´µË½   ôVËÅ Òã ³%­=­®°±·UÈlÕMÊo­®Ë ã §ÆÉ©¨MÉSÉzÿ Ì ¥ ¬”ÀM½¾°±·Í%Ø®ô`ËÅ You do not need to enter values for any other category.0 is shown: ©2004 SAP AG 35 . WFM. ICSS. CVIEWS.0 SP2 to connect SAP CRM 4. ISA HOM. CRM Content. ISA B2R. The affected categories are: Drag&Relate Serv er (DRS). Do not change the default values for these. Shared Catalog.

HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 PUBLIC .

=<£>@?#ACB OPM0IRQ.-& '*/0. ¤ !"#£"%$&('*)+'*.=<£>@?#ACB .12(3546!/78:9 . .=<£>@?#ACB DFEBHG IJG%>C?#K@L0?#G%M0I N .GTS£UJKCL7?#G M7I N .

-& '*/0. V /0-&WX-&YZ\[]@6(^#£  _ `H'*a$&cb Wd 6e/0$f'*)J'*6.12(3546!/7:9 g YJ-f/$ %$fcb Wd@ ©2004 SAP AG 36 . .

. . .m1" 6e/7@6 _ V /7-f6WX-&YZ\[n`h'*(%$fcb Wod@ a$&('j)J'*6.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.-&

Related Interests

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

Related Interests

*/7k1"3546/7:9 l YZ. ) 6e/06 ©2004 SAP AG 37 .

!' 7 #¤2a$&'*)J'*6.HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6.0 r PUBLIC -&#WsJYZ@(%$fc1". k-f

Related Interests

*/7k1"3546/08#¤2YZ'*u9 '*'*Ws5. oWw' . oW' r V / -f6WX-&YZ\[n-&#Ws+YZ(%$&i12. oW' V /0-&6W”-&YZ\[ ©2004 SAP AG 38 .-&

Related Interests

*/7k1"3546/0˜¤"Yn'*u9 v '*'*Ws5a$&'*)J'*6. !' #¤2a$&'*)J'*6. !@'t#£"%$f '*)J'*6. . .=DFy{z£O}|~ u9k`H'j '}a$&(\YZ € YZ(¤"%$&(\YZ'*WX-&'*'t‚Z/0ƒJsJ#¤ ˆ‡ „}… † x ‰ Š‹Œ \Ž# .=DFy{z£‘“’ v #¤2/7-]-&/06W”-&s•3nYZ'*WX-&'*' l v 1"/0ƒJsJ3546/0'} ‚ —– '*)+'*!. ' r V /7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12.a$&'*)J'*6.-&

Related Interests

*/7k1"3546/78#¤2YZ'*u9 v '*'*Ws5a$&'*)J'*6.

-&. 6)=1"  /0-&WX-&YZ\[R9 • • • l l )J'*6. -&.m3Z! • r V /7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12.  l v ‚ '*)+'*6.  g „}.-&

Related Interests

*/7k1"3546/0˜¤"Yn'*u9 v '*'*Ws5-™1"1"6W' 6sJ£) l O}M0IJI+A@š¢?#M0K V  € œ1"¤@ 6.m1"6c-f. !' #¤2a$&'*)J'*6. ¤6i$&¤'*86)=12 Wo©-f›-&. ©2004 SAP AG 39 .HOW TO USE BUSINESS PACKAGES IN SAP ENTERPRISE PORTAL 6. )J'*6. /0-&WX-&YZ\[R9 -&YZ. . !' #¤2a$&'*)J'*6.  r V /7-f6WX-&YZ\[n-&#Ws+YZ(%$&i12. !' #¤2a$&'*)J'*6. .-&

Related Interests

*/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.-&

Related Interests