How to Use Business Packages in SAP Enterprise Portal 6.0

7/31/2019 How to Use Business Packages in SAP Enterprise Portal 6.0

http://slidepdf.com/reader/full/how-to-use-business-packages-in-sap-enterprise-portal-60 1/54

How t o …

Use Busin ess Pack ag es inSAP En t er pr ise Por t a l 6 .0

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

1 SCENARIO .......................................................................................................................................... 3

2 RESULT...............................................................................................................................................3

3 BUSINESS PACKAGES – OVERVIEW..............................................................................................4

3.1 Basic Concepts.........................................................................................................................................4 3.1.1 Understanding Roles in SAP Applications and SAP Business Packages ......... ........... ........... .......... ........4 3.1.2 Content of a Business Package .................................................................................................................5 3.1.3 Semantics and Business Packages ............................................................................................................5 3.1.4 Delegated Administration.........................................................................................................................5 3.1.5 The Delta Link Concept............................................................................................................................5

3.2 Business Package Release Names and Numbers ..................................................................................6 3.2.1 Business Package Names ..........................................................................................................................6 3.2.2 Business Package Release Numbers .........................................................................................................6

3.3 Support Packages and Upgrades for Business Packages ....................................................................6 3.3.1 Support Packages for Business Packages .................................................................................................6 3.3.2 Upgrading Business Packages ..................................................................................................................6

3.4 Object Naming Conventions ..................................................................................................................7

3.5 Storage Structures for Business Packages in the Portal Catalog .......................................................7 3.5.1 Storage Structure for Native EP 6.0 Business Packages...........................................................................7 3.5.2 Example: Storage of SAP EP 5.0 Business Packages in SAP EP 6.0.......................................................8

3.6 Shared Objects ........................................................................................................................................9

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

4 THE PORTAL FOR BUSINESS PACKAGES – IVIEWSTUDIO....................................................... 10

4.1 iViewStudio Structure ..........................................................................................................................10 4.1.1 Searching For a Business Package..........................................................................................................11 4.1.2 Displaying Details for a Business Package.............................................................................................12 4.1.3 Downloading a Business Package ..........................................................................................................14

5 BUSINESS PACKAGE LIFE-CYCLE................................................................................................ 15

5.1 Preparing To Install Business Packages .............................................................................................15 5.1.1 Checking the SAP EP 6.0 Release ..........................................................................................................15 5.1.2 Downloading the Business Package From iViewStudio.........................................................................16 5.1.3 Preparing the SAP CRM System ............................................................................................................19

5.2 Installing Business Packages................................................................................................................20 5.2.1 Notes on the Installation .........................................................................................................................20 5.2.2 Installing the Import Filter ......................................................................................................................20 5.2.3 KM Compatibility Package.....................................................................................................................23 5.2.4 Example: Installing the Business Package for SAP CRM 4.0, Release 60.2.0.......................................26

2004 SAP AG 1




5.3 Using Business Packages ......................................................................................................................29 5.3.1 Navigation Compatibility of People-Centric SAP CRM 4.0 with SAP EP 6.0 ......... ........... .......... ........29 5.3.2 Working With Business Packages ..........................................................................................................34 5.3.3 Modifications in SAP EP 6.0..................................................................................................................34

5.3.3.1 Creating a System Landscape Objects to Connect SAP CRM 4.0.....................................................34 5.3.3.2 User Mapping to the Target System...................................................................................................40 5.3.3.3

Function Test for the Business Package for CRM 4.0 60.2 .......... .......... ........... .......... ........... .......... .41

5.3.4 Working with Delta Links ......................................................................................................................45 5.3.5 Transporting Business Packages (Staging).............................................................................................46

5.4 Uninstalling Business Packages ...........................................................................................................47

6 APPENDIX.........................................................................................................................................51

6.1 SAP Notes – A Compilation for Business Packages ...........................................................................51

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

2004 SAP AG 2




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 portal solution, SAP Enterprise Portal 6.0, users are able to access contentoriginating 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, fromproviding, 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 thebusiness package life-cycle.

After the basics, which provide a short overview for people new to this topic, all phases of using abusiness 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 anexample. In comparison to other business packages, the business package implemented here, whichcontains more than 1100 objects, is very large.

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

2004 SAP AG 3




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 businesspackages. Business packages provide the means to support the infrastructure to be integrated and tosupport application-specific processes and roles.

Business packages provide numerous benefits:

• Business packages are shipped independent of the SAP Enterprise Portal platform. They areoffered 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 aportal.

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

• Business packages are made available in industry-specific, user-specific, role-specific, andapplication-specific forms.

3.1 Basic Concepts

3.1.1 Understanding Roles in SAP Applications and SAP Business Packages

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

• Roles can be assigned to different users and contain authorization information

• Roles are made available by the application system, can be changed by the administrator, or can

be defined from scratch.Below you can find the role concept for the most important SAP solutions:

• mySAP Business Suite (for example: SAP ERP, SAP CRM 4.0):Roles from ABAP-based systems define a number of transactions for a user or a user group,which are provided in a menu structure.

• SAP Business Warehouse:Roles contain directories containing the reports and analyses that the user uses.

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

o Portal roles are used to assign portal content to users.

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

These different role concepts exist for historic and application-specific reasons. This results in therestriction that you cannot directly use portal roles to define authorizations in R/3 systems or WebApplication 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




3.1.2 Content of a Business Package

A business package contains the following content objects:

• iView: An iView is a small application and appears in a particular area on a page. AniView receives and processes data from various sources in the enterprise or from theInternet and displays this in the Portal Content area.

• Page: A portal page provides a display area as a container for iViews and its structure isdescribed 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 thenavigation. A workset allows access to tools, applications, and information for usersresponsible 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, ifa user wants to have access to tools, applications, or information that he or she needs for a particularworkstep. 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 throughvarious 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 structurelevel. A simple workset therefore described the tasks that a portal user requires to handle a specificbusiness 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 delegated administration allows distribution of administrative tasks (for example, useradministration) and distributed access to content objects. Therefore, delegated administration is aprocess for hierarchical distribution of administrative tasks between one or more administrators or groupsof 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 businesspackages more than once.

You can change objects generated by means of delta links without changing the original objects that thedelta link objects reference. This is beneficial for maintenance (delivered portal content, for example, fromSAP, 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 link objects. This allows you to create a chain ofinterlinked objects.

When working with content objects for business packages, SAP principally recommends working withdelta links, because otherwise the objects are not updated automatically when you import supportpackages and new minor releases.

2004 SAP AG 5




For more information about the delta link concept, see the administration guide for SAP Enterprise Portal6.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 portalrelease required and what application system it is associated with. Some business packages are releasedfor 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 CRMRelease 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 iViewStudio (www.iviewstudio.com), you canread that the business package used in our scenario is released for SAP EP 6.0 SP2, that is, it is notreleased 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 suitablefor several back-end system releases, as in the case of the SAP BW business packages, or it is plug-in-based, 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 andshipped through the iViewStudio. Support packages contain only corrections to iViews; they do notcontain any new pages, worksets, or roles.

Support packages are cumulative, that is, support package 3 contains all changes included in supportpackages 1 and 2. Therefore, only the latest support package is available for download from theiViewStudio.

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

During an upgrade, the business package release (minor release) changes, for example, from 60.1 to60.2. A business package upgrade can contain the following content:

• New languages

• New iViews, or iViews with changed features

2004 SAP AG 6




• New or changed pages

• New or changed worksets

• New or changed roles

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

o New plug-in version (in the case of plug-in-based business packages)o New support packages for the back-end system

o New back-end system release

Because of the dependencies to a back-end system in particular, it is important that you read theTechnical Description section of the documentation for the respective business package carefully andbear in mind the dependencies documented. A business package upgrade is frequently connected withan upgrade in the back-end system or a plug-in, in order to be able to use all features. Bear this in mindwhen 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 Related Links column in the Portal Content News section.

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 changedduring 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 yournamespace for production use. This is described in the SAP Collaboration Room documentation.

For all objects 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 portal catalog. The storage ofbusiness packages differs according to whether the business package is question is a native SAP EP 6.0business package or an SAP EP 5.0 business package released for SAP EP 6.0 that is migrated duringimport.

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 fromnative 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 ason the iViewStudio (path: Content Provided by SAP Content for Line Managers , Specialists, Every User ). This ensures simple orientation and recognition.

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

2004 SAP AG 7




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

Generally, portal content objects that are migrated from SAP EP 5.0 to SAP EP 6.0 are stored in apredefined 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 appropriatefolders according to the object type.

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

2004 SAP AG 8




3.6 Shared Objects

Some business packages reuse components located in other business packages. These reusedcomponents are known as shared objects. These are portal content objects that originate in a particularbusiness 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 objectis not imported with several business packages in more than one version into the portal and it does notimpair the function of other business packages.

Objects are shared by means of delta links to other portal content objects that originate in a particularbusiness package and are used in another business package.

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

SAP recommends following the procedure documented in section 5.3 Using Business Packages whenreferencing 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 andmarkets.

It contains the following roles:

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

• Marketing: Campaign Manager, Lead Manager, Lead Qualifier, Account Manager, TradeMarketing 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 – ChannelCommerce, 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 operationalissues in their daily work. The added value consists of:

• Bringing together information that was previously distributed among different sources

• Allowing access to this information

• Structuring this information at the time it is requested

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

2004 SAP AG 9




4 The Portal for Business Packages – iViewStudio

About 95 business packages from SAP and about 30 business packages from certified and non-certifiedthird-party vendors are currently available on iViewStudio. This means that more than 3000 iViews andmore 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 businesspackages.

The prerequisite for extended access to iViewStudio is having a registered user. The prerequisite for thisis 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 businesspackages.

2004 SAP AG 10




4.1.1 Searching For a Business Package

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

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

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

The technical information on the business package is available in the Online Documentation area. Thereyou 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




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 packagefunctions. Below this, there are buttons for more information, More Information , and adding the packageto 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 packageo

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:

2004 SAP AG 12




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

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:

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

2004 SAP AG 13




4.1.3 Downloading a Business Package

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

In the content catalog on iViewStudio, you can find the documentation for the respective businesspackages. In addition, you can also find 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 availablefor download. These business packages are in restricted shipment and are only available to a limitednumber of customers at the moment. If you are interested in one of these business packages, eithercontact 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 iscontinuously extending and improving its business packages and therefore the file that you download isavailable for a limited period only.

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

You should also save support packages or upgrade files from iViewStudio locally, so that you can accessthem 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 thetested version on the production portal, you require a local back-up copy.

2004 SAP AG 14




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 PackagesBefore the actual installation of a business package, you must complete the preparations, which varydepending 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 youwant 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




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 detailedprocedure for downloading the Business Package for SAP CRM 4.0 60.2 is documented here:

1. Log on to iViewStudiowww.iviewstudio.com as a

registered user:For information about the optimumbrowser setting when usingiViewStudio, visit Related Links FAQ Section 1.1.4 onwards.

2004 SAP AG 16

http://www.iviewstudio.com/





2. Using the keyword search, enterCRM to search for the BusinessPackage for SAP CRM 4.0 60.2

3. Search results: CRM BusinessPackage is found.

4. Display the detailed information

about the business package.(Upper screen content)

2004 SAP AG 17




5. Download the Business Package forSAP CRM 4.0 60.2(step one)

6. Download the Business Package forSAP CRM 4.0 60.2(step two)

7. Download the Business Package for

SAP CRM 4.0 60.2(step three)

Note here: Installation notes, like those listed instep three, should be regarded asgeneral information. You must notethe specific installation instructionsfor the corresponding businesspackage.(See SAP Notes)

8. Save the files in an archive folder. /archive/2004_02_02_CRM_BP_60_2_0

2004 SAP AG 18




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 minimalSAP 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 dialoginstances on different servers, once the central instance and database instance have been installed. Ifyou are setting up an SAP CRM 4.0 system, you may require further main components that allowoperations.

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 reportsrequire data, so that they can return meaningful results.

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

2004 SAP AG 19




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 business packages forSAP 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 tothe 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, butalso a migration at the same time. For the migration, SAP provides an import filter and a KM compatibilitypackage. Depending on the business package concerned, you must install these before installing thebusiness package.

After completion of the installation, you may have to modify the navigation, depending on the businesspackage 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 BusinessPackage for SAP CRM 4.0 60.2) cannot be displayed in SAP EP 6.0. The import filter checks theseobjects: Certain portal content objects are excluded from the import; other portal content objects arereassigned.You must install the import filter before installing a business package containing SAP EP 5.0 content thatis released for SAP EP 6.0.

The import filter is available for various different portal releases. As an attachment to SAP Note 642999Import 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 6432999 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 thepath 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 fromyour 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 andthe 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




1. Download the text file attached toSAP Note 642999 (depending on theSAP EP 6.0 release implemented) toa temporary folder.

2. In Enterprise Portal 6.0, navigate to:System Administration Support

Portal Content Directory PCDConfiguration Parameters for PortalContent Migration Pcd.Migration.Path.Mapfile.Note the path as it appears there.

2004 SAP AG 21




2. (continued) Note the path.

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

For example:/usr/sap/ep01/global/config/pcd/Migration/mapping/

4. Rename the text filecms_mapping.properties tocms_mapping.properties_old.

mv cms_mapping.propertiescms_mapping.properties_old

5. Rename the text file tocms_mapping.properties.

mv cms_mapping.properties.txtcms_mapping.properties

6. Assign the access rights. Change access rights forcms_mapping.properties to:chmod 755cms_mapping.properties

7. Assign the ownership rights. Change ownership of user and group forcms_mapping.properties to:chown j2eeadm:sapsyscms_mapping.properties

8. Restart the portal.

2004 SAP AG 22




5.2.3 KM Compatibility Package

The next step is to install the KM compatibility package. Between SAP EP 5.0 and SAP EP 6.0, thenaming conventions for KM content objects have changed. Therefore, references to such objects can nolonger find their targets. The KM compatibility package solves this problem for portal content objects thathave 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 themigrated 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/Importmkdir 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 folderand 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 Transport 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 .

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

The KM compatibility package is also relevant for other business packages that reference parts of theBusiness 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 onebusiness package that reference parts of the Business Package for Communication or the BusinessPackage for Portal Users for the KM platform.

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

2004 SAP AG 23




1. Download the *.zip file (as attachedto Note 640634) in a temporaryfolder.

2. Create the import folder for the KMcompatibility package in the PCDimport folder:

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

mkdir KMCompatibilityPackage

3. Unpack the *.zip file to this importfolder.

4. Change the assignment from userand group recursively to theKMCompatibilityPackage folder andto the files and folders that thiscontains.

chown –R <J2EEAdminUser>:sapsysKMCompatibilityPackage

5. Change the permissions recursively

to the KMCompatibilityPackage folderand to the files and folders that thiscontains.

chmod –R 755KMCompatibilityPackage

6. In Enterprise Portal 6.0, import thepackage by choosing System Administration Transport Import.

2004 SAP AG 24




7. Check the log file.

8. The import is complete.

2004 SAP AG 25




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 CRM4.0, release 60.2.0 from iViewStudio to a temporary folder.

The prerequisite for this is that the import filter 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/Importmkdir BPForSAP_CRM_60_2_0

2. After the import, the imported portal content appears in com.sap.portal.migrated ep_5.0 <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 folderand to the files and folders that this contains: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 folderand to the files and folders that this contains:chmod –R 755 BPForSAP_CRM_60_2_0



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

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

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




1. Download the *.zip file for theBusiness Package for SAP CRM 4.0from iViewStudio (to a temporaryfolder).

2. Create the folder for the BusinessPackage for SAP CRM 4.0 in the

PCD import folder:

cd /usr/sap/<MyPortalInstance>/global/config/pcd/Importmkdir BPForSAP_CRM_60_2_0

3. Unpack the *.zip file from thetemporary folder to this importfolder.

4. Change the assignment from userand group recursively to theBPForSAP_CRM_60_2_0 folder andto the files and folders that thiscontains.

chown –R <J2EEAdminUser>:sapsysBPForSAP_CRM_60_2_0

5. Change the permissions recursively

to the BPForSAP_CRM_60_2_0 folder and to the files and foldersthat this contains.

chmod –R 755

BPForSAP_CRM_60_2_0

6. Import the package to SAPEnterprise Portal 6.0 by choosing:System Administration Transport Import.

2004 SAP AG 27




6. (continued) 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 importedportal content appears incom.sap.portal.migrated ep_5.0.

9. The installation of the BusinessPackage for SAP CRM 4.0, Release60.2.0 is complete.

2004 SAP AG 28




5.3 Using Business Packages

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

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

Package for Communication)

• Configuration of additional properties for system landscape objects

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

• Correction of various errors:

o Workforce Management iViews

o Value help

o Bookmarking

o KM Extensions

o Translation of the Administration Workset

• Navigation compatibilities (People-Centric CRM with EP 6.0)

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

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 Context Service (com.sap.pct.crm.crmcontext.zar), the

URL Dispatcher (com.sap.pct.crm.UrlDispatcher.par), and a package for navigation compatibility betweenSAP 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 thenavigation compatibility package with the path:cd /usr/sap/ep01/global/config/pcd/Importmkdir Navigation_40_60_2

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

2004 SAP AG 29




8. Change the assignment from user and group recursively to the Navigation_40_60_2 folder and tothe 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 tothe files and folders that this contains:chmod –R 755 Navigation_40_60_2



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

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

1. From SAP Note 659881, Compatibilityof navigation of People-Centric CRM with EP 6.0, download the attached*.zip file.For example: fix_BP602_CRM40.zipor fix_BP6011_CRM40.zip

2. Unpack the file to a temporaryfolder.

/tempfiles

3. Rename the filecom.sap.pct.crm.crmcontext.zar tocom.sap.pct.crm.crmcontext.par .

mv com.sap.pct.crm.crmcontext.zarcom.sap.pct.crm.crmcontext.par

4. Copy the PAR files to the J2EE

Servlet path.

For example, this path is:

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

5. Restart the J2EE Server

2004 SAP AG 30




6. Create a new folder,Navigation_40_60_2, in the PCDimport folder for the import of thenavigation compatibility packagewith the path:

cd/usr/sap/ep01/global/config/pcd/Importmkdir Navigation_40_60_2

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

8. Change the assignment from userand group recursively to theNavigation_40_60_2 folder and to thefiles and folders that this contains.

chown –R <J2EEAdminUser>:sapsysNavigation_40_60_2

9. Change the permissions recursivelyto the Navigation_40_60_2 folder andto the files and folders that thiscontains.

chmod –R 755 Navigation_40_60_2

10. Import the package to SAPEnterprise Portal 6.0 by choosingSystem Administration Transport Import.


2004 SAP AG 31





11. A log file is generated during theimport. You can check this at:/usr/sap/<MyPortalInstance>/j2ee/j2ee_01/temp/Migration/logs/<file>.

Example:

12. After the import: Assign the rolecom.sap.pct.crm_default_services to thepredefined group Everyone.

2004 SAP AG 32




12. (continued) Role assignment.

2004 SAP AG 33




5.3.2 Working With Business Packages

Once you have completed the postprocessing steps, you can work with the portal content objects. In ourscenario, 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.0Prerequisites

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

• Users are available in this SAP CRM 4.0 system.

• Data is available in SAP CRM 4.0.

• As the portal, SAP EP 6.0 SP2 is used.

• Users are available in EP 6.0 SP2.

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

5.3.3 Modifications in SAP EP 6.0

You need to modify SAP Enterprise Portal to use a business package. The activities that occur mostfrequently 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 between portal content objects and backend systems.The creation and management of system landscape objects tasks are part of the system administrationfor 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 portalcontent 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 objectproperty 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 animplementation of the Business Package for SAP CRM 4.0 60.2:

2004 SAP AG 34




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

Category Property Value Example:Business Package forSAP CRM 4.0 60.2

Connector Application Host Host.Domain iwdf9933.wdf.sap.corp

Logical SystemName

Logical, three-charactersystem name

RKP

Remote Host Type Type of target system, forexample, value ”3“ for theR/3 system

3

Client Name Client system name 800

SAP System Name SAP system name RKP

SAPSystemNumber

SAP system number 00

Server Port Port number of the targetsystem

3200

System TemplateName

System template name SAP-CRM

System Type System type of the targetsystem, for example, R/3(selection list)

SAP_R3

Web Application Server(WAS)

WAS Description Web Application Serverdescription

RKP

WAS Host Name Host.Domain:Port iwdf9933.wdf.sap.corp:1080

WAS Path Web Application Server path iwdf9933.wdf.sap.corp:1080

WAS Protocol Protocol selection (selectionlist)

http

User Management LogonMethod Type of logon (selection list),for example, with user ID andpassword

UIDPWD

ReferenceSystem Reference system (selectionlist) for example, XXXX

0

UserMappingType Type of user mapping Admin, user

CRM Content? JSESSION?

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 Server (DRS), ISA HOM, WFM, WFM CS, ISA B2B, ISA B2R,Shared Catalog, CRM Content, Internet Transaction Server (ITS), CVIEWS, ICSS, and ShopAdministration

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

2004 SAP AG 35




1. Create a folder for the systemlandscape object at:System Administration System Configuration

System.

1. (continued) Create a folder.

2. Use the wizard to create the systemlandscape object:

Launch the wizard

2004 SAP AG 36




2. (continued) Use the wizard to createthe system landscape object:

Select the template

2. (continued) Use the wizard to createthe system landscape object:

General properties

2. (continued) Use the wizard to create

the system landscape object:

Summary

2004 SAP AG 37




3. Configure the parameters for thesystem landscape object for use:

Assign the system aliasHere: Use SAP_CRM as the default

value for the Business Package forCRM 4.0

Example: SAP_BW for connecting businesspackage objects to SAP BW systems.

3. (continued) Configure the parametersfor the system landscape object for use:

Assign the system alias.

3. (continued) Configure the parametersfor the system landscape object for use:

Assign the system alias (continued).

2004 SAP AG 38




3. (continued) Configure the parametersfor the system landscape object for use:Assign properties

Category Connector :

• Application host

• Logical system name

• Remote host type

• Client name

• SAP system name


Category Connector (continued):

• SAP system number

3. (continued) Configure the parameters

for the system landscape object for use:Assign properties

Category Connector (continued):

• Server port

• System template name

• System type

2004 SAP AG 39





Category Web Application Server (WAS):

• WAS description

• WAS host name

• WAS path

• WAS protocol


Category User Management:

• Logon method

• R/3 reference system

• User mapping type

If you plan to use the analysis functions, you must configure an SAP BW system as described in thisprocess 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 fromSAP EP 6.0 SP2 to SAP CRM 4.0. The prerequisite for this is having a corresponding user in bothsystems.

The following process illustrate user mapping for the system landscape object in EP 6.0 mapped to theSAP CRM 4.0 system:

2004 SAP AG 40




1. In Enterprise Portal 6.0, navigate to: User Administration User Mapping

2. Select a portal user.

3. Assign the target system.

4. User mapping: Enter the logon data.

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




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

1. Select roles for portal users.

1. (continued) Select the Sales Manager role for users.

2004 SAP AG 42




2. Check the role assignment.

3. Log on to the portal with a user that

is assigned to at least one role.

3. (continued) Portal users assigned tothe Sales Manager role.

2004 SAP AG 43




4. Check the function using the iViewsfrom the business package.

4. (continued) Check the functions:

Access to product data

5. Result: The business package hasbeen successfully installed and thefunctions tested.

2004 SAP AG 44




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 theoriginal objects. This makes sense from the perspective of task delegation (delegated administration) andfor 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 protectedagainst changes. The established procedure involves working with a reference folder, which has thefollowing 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 withbusiness packages. For improved orientation, SAP recommends extending the folder hierarchy tomatch the folder hierarchy of the business package.

• The reference folder contains only references to the original objects, implemented using deltalinks. 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




5.3.5 Transporting Business Packages (Staging)

The activities described in the previous section make staging easier, that is, transporting objects betweenvarious 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 Packagefor CRM 4.0 60.2.

The solution is made possible using the reference folder described in the previous section. The BusinessPackage 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 businesspackage. 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




5.4 Uninstalling Business Packages

There is no application or tool support for uninstalling a business package. You must work through theprocedure manually.

Based on experiences to date, the following general procedure has proven to be practical:

1. Delete the role assignment to users

Example: Delete the assignment tothe Everyone group.

In SAP EP 6.0:a) User Administration Roles.b) Search for the Everyone group.

c) Edit the group properties.d) Select thecom.sap.km.ContentManager role.e) Choose Remove.

You must also delete any other roleassignments to the businesspackage.

2004 SAP AG 47




2. Delete the working folder.

3. Delete the iViews in the businesspackage.

Example: Delete the folders for theBusiness Package for SAP CRM 4.060.2:

In Content migrated EP 5.0 iViews delete all CRM–specificfolders and their content.

Folders:o Channel Managemento Common

o E-Sellingo Indirect Saleso Interaction Centero Marketingo Portal Administrationo Saleso Service

2004 SAP AG 48




4. Delete the roles in the Roles folder.

Example: Delete the roles in theBusiness Package for CRM 4.0.

Please note: Make sure that you donot delete the roles Content Manager and KM Administration!

5. Delete the pages in the Pages folder.

Example: Delete the pages in the

Business Package for CRM 4.0.

Please note: Make sure that you donot delete the KM-specific pagescom.sap.km.* !

6. Delete the worksets in the Worksets folder.

Example: Delete the worksets in theBusiness Package for CRM 4.0.

Please note: Make sure that you donot delete the KM-specific worksetscom.sap.km.* !

2004 SAP AG 49




7. Delete the templates in the Templates folder.

Example: Delete the templates in theBusiness Package for CRM 4.0.

Please note: Make sure that you donot delete the KM-specific templatescom.sapportals.km.* !

8. Delete the systems in the Systems folder.

Example: Delete the systems in theBusiness Package for CRM 4.0.

Navigate to System Administration System Configuration System.

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




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

No. Note No. Description

1 564198 Missing technical documentation for CRM objects in iViewStudio

2 642775 Composite SAP Note for Business Packages as of EP 6.0 SP 1

3 660774 Installation of the Business Package for SAP CRM 4.0 60.2

4 640634 KM compatibility package

5 642999 Import Filter

6 644024 Workforce Management iViews in EP 6.0

7 640678 Groupware Integration in EP 6.0

8 640330 EP6: Adding Properties to systems and system templates

9 691782 Disable Caching for Balanced View in BP for SAP CRM 4.0 60.x

10 642827 BP for Portal Users on SAP EP 6.0

11 645627 PCUI: Complex input help does not work in EP6 portal (value help problem)

12 649062 SAP CRM 4.0 50.2 Correction of object link for Internal News

13 659881 Compatibility of navigation of People-Centric CRM with EP6

14 642515 Compatibility of PC-UI navigation with EP 6

15 654959 Translation does not exist

16 660777 Extensions for KM in CRM4.0 do not work in BP60.1 and BP60.2

17 668154 Saving and Resetting Properties fails.

18 675280 Modification of pdv Factsheet iViews for EP6 Compatibility

19 683705 Search URL generation incorrect for EP 6.0 Portal

2004 SAP AG 51




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, [email protected] )

• 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, [email protected] ). Otherwise, the system issues an error message.

3. You receive the password by e-mail, usually within 24 hours.

4. You can use this user to log on to the iViewStudio.

2004 SAP AG 52






No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft ® , WINDOWS ® , NT ® , EXCEL ® , Word ® , PowerPoint ® and SQL Server ® areregistered trademarks ofMicrosoft 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 ofIBM 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 ofCitrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C ® , World WideWeb 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 fortechnology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and CommerceOne.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and otherSAP products and services mentioned herein as well as their respective logos are trademarks orregistered 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.

How to Use Business Packages in SAP Enterprise Portal 6.0

Documents

Transcript of How to Use Business Packages in SAP Enterprise Portal 6.0