Upgrade Master Guide SAP Netweaver 7.3

Upgrade Master GuideSAP NetWeaver® 7.3

Target Audience

n System administratorsn Technology consultants

PUBLICDocument version: 1.1 ‒ 12/06/2010Material number: 50102660

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version on SAP Service Marketplace http://service.sap.com/instguides.

The following table provides an overview on the most important document changes:

Version Date Description

1.1 12/6/2010 Correction: SAP Solution Manager 7.0 with at least Support Package Stack 23 isrequired for the upgrade.

1.0 11/29/2010 First version ‒ no changes.

2/72 PUBLIC 12/06/2010

http://service.sap.com/instguides



Table of Contents

Chapter 1 About this Document . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Introduction . . . . . . . . . . . . . . . . . . . . . . . 72.1 Key Terms for Understanding SAP NetWeaver . . . . . . . . . . . . 72.2 Mapping of Use Cases to Installable Software Units . . . . . . . . . . 8

Chapter 3 Upgrade at a Glance . . . . . . . . . . . . . . . . . . . . . 113.1 Transition from SAP NetWeaver 2004 . . . . . . . . . . . . . . . 113.2 Transition from SAP NetWeaver 7.0 . . . . . . . . . . . . . . . . 143.3 Transition from SAP NetWeaver PI 7.1 . . . . . . . . . . . . . . . 183.4 Transition from SAP NetWeaver Mobile 7.1 . . . . . . . . . . . . . 193.5 Transition from SAP NetWeaver Composition Environment 7.1 and 7.2 . . . 193.6 Upgrade Tools . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 234.1 Upgrade of Scenarios Based on SAP NetWeaver Portal . . . . . . . . . 234.1.1 Upgrade Sequence . . . . . . . . . . . . . . . . . . . . . . 244.2 Upgrade of Scenarios Based on SAP NetWeaver BW . . . . . . . . . . 254.2.1 Upgrade Sequence . . . . . . . . . . . . . . . . . . . . . . 254.3 Upgrade of Scenarios Based on SAP NetWeaver Process Integration . . . . 284.3.1 Upgrade Sequence . . . . . . . . . . . . . . . . . . . . . . 294.3.2 Upgrade of System Landscapes Including ES Repository for SAP NetWeaver CE 314.4 Upgrade of Scenarios Based on SAP NetWeaver Composition Environment . 314.4.1 Upgrade Sequence . . . . . . . . . . . . . . . . . . . . . . 324.5 Upgrade of Scenarios Based on SAP NetWeaver Mobile . . . . . . . . . 334.5.1 Upgrade Sequence . . . . . . . . . . . . . . . . . . . . . . 334.6 Upgrade of SAP Knowledge Warehouse . . . . . . . . . . . . . . 354.6.1 Upgrade Preparation for SAP Knowledge Warehouse . . . . . . . . . 354.6.1.1 Backing Up the SAP System and the SAP Content Server . . . . . . . . 364.6.1.2 Saving the SAP Content Server Configuration File . . . . . . . . . . 364.6.1.3 Saving Customer-Specific Changes to the Internet Knowledge Servlet . . . 364.6.2 Upgrade Sequence SAP Knowledge Warehouse . . . . . . . . . . . . 364.6.3 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . 384.7 Configuration of Systems . . . . . . . . . . . . . . . . . . . 38

12/06/2010 PUBLIC 3/72

Chapter 5 Description of Software Units . . . . . . . . . . . . . . . . . 395.1 Systems with Usage Types . . . . . . . . . . . . . . . . . . . 395.2 Optional Standalone Units . . . . . . . . . . . . . . . . . . . 525.3 Standalone Engines . . . . . . . . . . . . . . . . . . . . . 545.4 Clients . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 59A.1 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . 59A.2 Documentation References . . . . . . . . . . . . . . . . . . 59A.3 More Information . . . . . . . . . . . . . . . . . . . . . . 60A.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . 61A.5 Compatibility Usage Types . . . . . . . . . . . . . . . . . . . 62

Chapter B Reference . . . . . . . . . . . . . . . . . . . . . . . . . 65B.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . 65

4/72 PUBLIC 12/06/2010

1 About this Document

1 About this Document

This Upgrade Master Guide provides a central starting point for the technical upgrade to SAPNetWeaver® 7.3. It outlines the overall upgrade process, and refers you to the required detailedupgrade documentation, installation documentation, and SAP Notes.

Caution

Make sure you have the latest version of theUpgrade Master Guide by checking SAP Service Marketplaceimmediately before starting the installation. The Upgrade Master Guide is regularly updated on SAPService Marketplace at http://service.sap.com/upgradenw73.

ConstraintsThe business scenarios that are presented here serve as examples of how you can use SAP software inyour company. The business scenarios are intended only as models and do not necessarily run the waythey are described here in your customer-specific system landscape. Check your requirements andsystems to determine whether these scenarios can be used productively at your site. Furthermore, werecommend that you test these scenarios thoroughly in your test systems to ensure that they arecomplete and free of errors before going live.See AlsoThe technical implementation of this SAP solution is described in the document MasterGuide ‒ SAP NetWeaver 7.3. The Master Guide is available on SAP Service Marketplace athttp://service.sap.com/installnw73.

12/06/2010 PUBLIC 5/72

http://service.sap.com/upgradenw73

http://service.sap.com/installnw73

This page is left blank for documentsthat are printed on both sides.

2 Introduction

2 Introduction

SAP NetWeaver® is the platform that provides the shared technology foundation for SAP businessapplications. In addition, SAP NetWeaver provides optional technology components that allowcustomers:

n To extend the reach of SAP applications to more people, also via new devices and consumptionmodels

n To integrate SAP applications and processes into heterogeneous landscapesn To extend existing SAP processesn To compose new processes that span SAP and non-SAP applicationsn To securely manage and deliver informationn To holistically manage the lifecycle and infrastructure of SAP applications

Based on the principles of a service-oriented architecture (SOA), SAP NetWeaver helps organizationsoptimize the return of their investment in SAP and non-SAP applications by allowing customers toevolve their current IT landscapes into flexible business process platforms that close the gap betweeninsight and action.An open technology platform, SAP NetWeaver is based on industry standards and can be extendedwith commonly used development tools such as Java Platform, Enterprise Edition (Java EE); Microsoft.NET; and IBMWebSphere. Providing fundamental orchestration capabilities such as business processmanagement, application lifecycle management and master data management, SAP NetWeaver is akey technology that will allow customers to deploy and manage an environment of solutions thatspan SAP and non-SAP on-premise and on-demand applications, providing superior flexibility whileensuring a maximum of consistency of information and processes.

2.1 Key Terms for Understanding SAP NetWeaver

This section gives you a short overview of the technical terms used in this document:

n Usage TypeSAP systems with usage types are the main building blocks of SAP NetWeaver. They are identifiedby unique SAP system IDs (SAPSIDs) and are configured for a certain purpose, as indicated byusage types. Usage types have the following characteristics:l Usage types consist of one or several functional units.l They are a structuring element for SAP software on a technical level.l Usage types are selectable installation units.

12/06/2010 PUBLIC 7/72

2 Introduction2.2 Mapping of Use Cases to Installable Software Units

l Usage types determine the intended purpose of a system and the role it plays in a given(distributed) use case.

l They are realized by installing and configuring a collection of software components.l They allow a logical view of the SAP NetWeaver technology platform.l A usage type may require other usage types in the same system.l They can also be run in the same system together with other usage types that are not a

prerequisite.n Standalone Engine

Standalone engines of SAP NetWeaver are additional installable software units. They do not workas full-blown systems of SAP NetWeaver, but as standalone engines that provide a specific (server)function in combination with one or more SAP NetWeaver systems. Standalone engines are notpart of a usage type. They do not run on AS ABAP or AS Java.

n ClientClients are additional installable programs or tools. They reside either on local front-end PCsaccessed by users or on back-end systems where they act as client programs within an SAPNetWeaver system landscape.

n Optional Standalone UnitsOptional standalone units are additional software units that you install separately. They are basedon Application Server Java (AS Java) and provide specific (server) functions in combination withone or more SAP systems.

n Functional UnitsA configured and activated unit of SAP NetWeaver that provides a set of functions. Functionalunits are bundled into usage types as the installable unit. After the installation of a usage type, youselect those functional units that you want to use in your system landscape and configure them.

2.2 Mapping of Use Cases to Installable Software Units

To give you a quick overview of SAP NetWeaver 7.3, the table below shows the mapping between SAPNetWeaver 7.3 use cases and required SAP NetWeaver software units. For more information about theuse cases, see the Master Guide for SAP NetWeaver 7.3.For information about the software units, see section Description of Software Units [page 39].

8/72 PUBLIC 12/06/2010


Use Case Usage Types (FunctionalUnits)

StandaloneEngines

OptionalStandaloneUnits

Clients

Building CompositeApplications:Business RulesManagement andProcess Composition

n AS Javan Adobe Document

Services (optional)n Business Process

Management andBusiness RuleManagement

n Composite ApplicationFramework

n CompositionEnvironment Platform

n NW Product Descriptionn DI [optional]

DeveloperWorkplace

n DeveloperWorkplace

n SAPNetWeaverDeveloperStudio

n VisualComposer

n AdobeLiveCycleDesigner(Optional)

n Web Browser

Building CompositeApplications:Java Developmentand SOAInfrastructure

n AS Javan NW Product Descriptionn DI [optional]n Enterprise Services

Repository

n DeveloperWorkplace

n SAPNetWeaverDeveloperStudio

n Web Browser

Data Warehousing n AS ABAPn BW ABAPn AS Javan NW Product Descriptionn AS Java Extensionsn BI Javan EP Core ‒ Application

Portaln Enterprise Portal

Search andClassification(TREX)

n SAP GUIwith BWAdd-On/BIAdd-On

n SAP Busines-sObjects Ad-vanced Anal-ysis, Editionfor MicrosoftOfce* [op-tional]

n SAP Busi-nessObjectsCrystal Re-ports* [op-tional]

n SAP Busi-nessObjectsXcelsius [op-tional]

n SAP Busines-sObjects WebIntelligence*[optional]

12/06/2010 PUBLIC 9/72


Use Case Usage Types (FunctionalUnits)

StandaloneEngines

OptionalStandaloneUnits

Clients

Building IntegrationScenarios

n Application Server Javan NW Product Descriptionn AS Java Extensionsn Application Server ABAPn Process Integrationn Enterprise Services

Repositoryn Advanced Adapter

Engine

n AdapterEngine (JavaSE) [optional]

n SAPConversionAgent byInformatica[optional]

n AdvancedAdapterEngine[optional]

n AdvancedAdapterEngineExtended

n PartnerConnectivityKit [optional]

SAP GUISAP NetWeaverDeveloper Studio

Integrating and SelfServicing Contentwith SAPNetWeaverPortal:

n AS Javan NW Product Descriptionn AS Java Extensionsn EP Core ‒ Application

Portaln EPn PortalAdd-on (forBuilding

Communities with Wikis andForums only)

Mobilizing BusinessProcesses:Developing MobileApplicationsfor OccasionalConnectivity

n AS ABAPn Mobilen Application Server Javan DIn EP Core ‒ Application

Portal [optional]

n SAP GUIn SAP

NetWeaverDeveloperStudio

n Mobile Client

Mobilizing BusinessProcesses:Enabling MobileApplicationsfor OccasionalConnectivity

n AS ABAPn Mobilen Application Server Java

[optional]n EP Core ‒ Application

Portal [optional]

n SAP GUIn Mobile Client

CustomApplicationDevelopment

n Application Server ABAP n SAP GUI

*Note that SAP BusinessObjects products require separate licenses.

10/72 PUBLIC 12/06/2010

3 Upgrade at a Glance

3 Upgrade at a Glance

3.1 Transition from SAP NetWeaver 2004

Relation Between Scenarios and Use CasesSAP NetWeaver 7.3 no longer uses technical scenarios as defined with SAP NetWeaver 2004 to describethe capabilities SAP NetWeaver provides. Instead, a set of “use cases” illustrate how you can implementand use SAP NetWeaver. Use cases provide a structured access to configuration information in SAPSolution Manager and therefore ease the implementation process.From the following table you can see how SAP NetWeaver 2004 technical scenarios translate intoSAP NetWeaver 7.3 use cases.

SAP NetWeaver 2004 TechnicalScenarios

SAP NetWeaver 7.3 Use Cases More Information

SAP Business InformationWarehouse (SAP BW)

Data Warehousing Upgrade of Scenarios Based on SAPNetWeaver BW [page 25]

BI Information Broadcasting Data Warehousing Upgrade of Scenarios Based on SAPNetWeaver BW [page 25]

SAP Enterprise Portal (SAP EP) Integrating and Self ServicingContent with SAP NetWeaverPortal

Upgrade of Scenarios Based on SAPNetWeaver Portal [page 23]

SAP Mobile Infrastructure (SAPMI)

Mobilizing Business Processes Upgrade of Scenarios Based on SAPNetWeaver Mobile [page 33]

SAP Process Integration (SAP PI) Building Integration Scenarios Upgrade of Scenarios Based on SAPNetWeaver Process Integration [page 28]

SAP Knowledge Warehouse (SAPKW)

No specific use case in SAPNetWeaver 7.3; KnowledgeWarehouse is an integral part of ASABAP and AS Java

Upgrade of SAP Knowledge Warehouse[page 35]

12/06/2010 PUBLIC 11/72

3 Upgrade at a Glance3.1 Transition from SAP NetWeaver 2004

SAP NetWeaver 2004 TechnicalScenarios

SAP NetWeaver 7.3 Use Cases More Information

SAP NetWeaver DevelopmentEnvironment: Development ofABAP applications

The preferred SAP NetWeaverversion for custom applicationdevelopment in ABAP is SAPNetWeaver 7.0 as part of the SAPBusiness Suite. SAP Business Suiteis based on SAP NetWeaver 7.0 andthe features of AS ABAP includedin SAP Business Suite 7i2010 andSAP NetWeaver 7.3 have beenaligned to a great extent. AlthoughAS ABAP is fully supported asa development platform in SAPNetWeaver 7.3, we recommendusing the enhancementpackages for SAP NetWeaver7.0 for ABAP development.For information about theenhancement package availability,see SAP Service Marketplaceat http://service.sap.com/releasestrategy.

SAP NetWeaver DevelopmentEnvironment: Development ofJava applications

Not described as a separate usecase, part of the AS Java and NWDIinstallation

SAP NetWeaver DevelopmentEnvironment: Team-orienteddevelopment of Java applications


SAP NetWeaver DevelopmentEnvironment: Development withSAP NetWeaver Java DevelopmentInfrastructure


SAP NetWeaver DevelopmentEnvironment: Interactive Formsbased on Adobe software

Custom Application DevelopmentABAP (WebDynproDevelopment).Note that the preferred SAPNetWeaver version for customapplication development in ABAPis SAP NetWeaver 7.0 as part of theSAP Business Suite.

SAP NetWeaver DevelopmentEnvironment: Development ofPortal iViews Using SAP NetWeaverVisual Composer

Integrating and Self ServicingContent with SAP NetWeaverPortal


SAP NetWeaver DevelopmentEnvironment: Development ofPortal Content with PDK for .NET



12/72 PUBLIC 12/06/2010

http://service.sap.com/releasestrategy




3 Upgrade at a Glance3.1 Transition from SAP NetWeaver 2004

Installable Software UnitsWith SAP NetWeaver 7.0, usage types have been introduced. They replace the formerly knownsoftware components, such as SAP Web AS ABAP, or SAP Exchange Infrastructure. Usage typesrepresent the capabilities of a SAP NetWeaver system offered by a collection of installed and configured(technical) software components. A usage type defines the role a system plays in a given scenario. Formore information about usage types, see Key Terms for Understanding SAP NetWeaver Products [page 7].When you upgrade your SAP NetWeaver 2004 components to SAP NetWeaver 7.3, the components aremapped to the corresponding usage types and upgraded accordingly. Missing software is deployed sothat your system contains complete usage types after the upgrade.In addition to SAP systems with usage types, there are addititional SAP NetWeaver building blocks:standalone engines and clients. For a definition of these terms, see Key Terms for Understanding SAPNetWeaver Products [page 7]. For a description of these software units, see Description of Software Units[page 39].The following table provides an overview of the mapping between SAP NetWeaver 2004 componentsand SAP NetWeaver 7.3 software units.

SAP NetWeaver 2004 Components Building Blocks of SAP NetWeaver 7.30

SAP Web Application Server Components

SAP Web Application Server ABAP 6.40 Application Server ABAP (AS ABAP) [usage type]

SAP Web Application Server Java 6.40 n Application Server Java (BASIC) [usage type]n AS Java Extensions (AS) [usage type]n NW Product Description (NW-MODEL) [usage

type]

SAP NetWeaver Java Development Infrastructure Development Infrastructure (DI) [usage type]

SAP NetWeaver Developer Studio SAP NetWeaver Developer Studio [client]

Adobe Document Services Adobe Document Services [usage type]

SAP GUI SAP GUI [client]

SAP Internet Transaction Server (SAP ITS) Included in Application Server ABAP (AS ABAP)[usage type]

SAP Gateway Gateway [standalone engine]

SAP XI Components

SAP Exchange Infrastructure (SAP XI) (comprisingIntegration Server, Integration Builder, RuntimeWorkbench and XI Adapter Engine)

Process Integration (PI) [usage type]

XI Adapter Engine Advanced Adapter Engine [standalone unit]

XI Adapter Engine (J2SE) Advanced Adapter Engine (Java SE) [standaloneengine]

SAP Partner Connectivity Kit (XI PCK) Partner Connectivity Kit [standalone unit]

SAP BW Components

12/06/2010 PUBLIC 13/72

3 Upgrade at a Glance3.2 Transition from SAP NetWeaver 7.0

SAP NetWeaver 2004 Components Building Blocks of SAP NetWeaver 7.30

SAP BW Java Components consisting of:n SAP BI Universal Data Integration (BI UDI)n SAP BI Meta Model Repository (BI MMR)

Integrated into AS Java (BASIC) [usage type]

SAP BW Precalculation Service Part of Business Explorer [client]

SAP BW Business Content Add-On BI_CONT SAP NetWeaver BI Content Add-On

SAP EP Components

Portal Platform n EP Core ‒ Application Portal (EPC) [usage type]

Content Management and Collaboration 6.0_640 n Enterprise Portal (EP) [usage type]

SAP NetWeaver Visual Composer Part of Composition Environment Platform (CE-ENV)[usage type]

PDK for .Net (Portal Add-In for Visual Studio 2005,Portal Runtime for Microsoft .NET, Java-.NETInteroperability Framework).

Part of EP Core ‒ Application Portal (EPC) [usage type]

Forums Application

Search and Classification Components

Search and Classification (TREX) Search and Classification (TREX) [standalone engine]

SAP MI Components

SAP Mobile Infrastructure Client Mobile Infrastructure Client [client]

Knowledge Warehouse Components

SAP KW Internet Knowledge Servlet (KW IKS) Part of AS Java Extensions (AS) [usage type]

SAP Content Server SAP Content Server [standalone engine]

3.2 Transition from SAP NetWeaver 7.0

Relation Between IT Scenarios and Use CasesSAP NetWeaver 7.3 no longer uses IT scenarios as defined with SAP NetWeaver 7.0 to describe thecapabilities SAP NetWeaver provides. Instead, a set of use cases illustrate how you can implement anduse SAP NetWeaver. Use cases provide structured access to configuration information in SAP SolutionManager and therefore ease the implementation process.From the following table you can see how SAP NetWeaver 7.0 IT scenarios translate into SAPNetWeaver 7.3 use cases.

14/72 PUBLIC 12/06/2010


SAP NetWeaver 7.0 IT Scenarios SAP NetWeaver 7.3 Use Cases More Information

Running an Enterprise Portal Integrating and Self ServicingContent with SAP NetWeaverPortal


Accelerating Global Delivery ofApplication

Delivered as separate product —not part of the SAP NetWeaver 7.3shipment

For information about AcceleratedApplication Delivery, seeSAP Developer Network athttp://www.sdn.sap.com/

irj/sdn/nw-accad

Enterprise KnowledgeManagement:Content Integration andManagement; Content Creation,Publication, and Access



Enterprise KnowledgeManagement: Documentation,Training Materials and ManualsManagement

No specific use case in SAPNetWeaver 7.3; KnowledgeWarehouse is an integral part of ASABAP and AS Java

Upgrade of SAP Knowledge Warehouse[page 35]

Enterprise Search: EnablingEmbedded Search

No use case in SAP NetWeaver 7.3;Embedded search is provided aspart of AS ABAP

Enabling User Collaboration Integrating and Self ServicingContent with SAP NetWeaverPortal


Business Planning and AnalyticalServices


Enterprise Reporting, Query, andAnalysis


Enterprise Data Warehousing Data Warehousing Upgrade of Scenarios Based on SAPNetWeaver BW [page 25]

Enabling Application-to-Application Processes

Building Integration Scenarios Upgrade of Scenarios Based on SAPNetWeaver Process Integration [page 28]

Enabling Business-to-BusinessProcesses

Building Integration Scenarios Upgrade of Scenarios Based on SAPNetWeaver Process Integration [page 28]

Business Process Management Building Composite Applications Upgrade of Scenarios Based on SAPNetWeaver Composition Environment[page 31]

Business Task Management Building Composite Applications Upgrade of Scenarios Based on SAPNetWeaver Composition Environment[page 31]

Enabling Enterprise Services Building Integration Scenarios Upgrade of Scenarios Based on SAPNetWeaver Process Integration [page 28]

12/06/2010 PUBLIC 15/72

http://www.sdn.sap.com/irj/sdn/nw-accad






Developing, Configuring, andAdapting Applications:n Developing Java Applications

using Web Dynpron Creating Composite

Applicationsn Creating Applications Using

SAP NetWeaver VisualComposer

Building Composite Applications Upgrade of Scenarios Based on SAPNetWeaver Composition Environment[page 31]

Developing, Configuring, andAdapting Applications:n Creating Business Applications

Using ABAPn Developing ABAP Applications

Using Web Dynpro

The preferred SAP NetWeaverversion for custom applicationdevelopment in ABAP is SAPNetWeaver 7.0 as part of the SAPBusiness Suite. SAP Business Suiteis based on SAP NetWeaver 7.0 andthe features of AS ABAP includedin SAP Business Suite 7i2010 andSAP NetWeaver 7.3 have beenaligned to a great extent. AlthoughAS ABAP is fully supported asa development platform in SAPNetWeaver 7.3, we recommendusing the enhancementpackages for SAP NetWeaver7.0 for ABAP development.For information about theenhancement package availability,see SAP Service Marketplaceat http://service.sap.com/releasestrategy.

Developing, Configuring, andAdapting Applications: LeveragingJava 2 Platform, Enterprise Edition(J2EE) Standards for Porting andAdopting Applications

Not described as a separate use casein SAP NetWeaver 7.3, part of ASJava and DI installation.

Developing, Configuring, andAdapting Applications:Developing Mobile Applicationsfor Occasional Connection

Mobilizing Business Processes Upgrade of Scenarios Based on SAPNetWeaver Mobile [page 33]

Developing, Configuring, andAdapting Applications:Creating Portal Applications UsingPDK for .NET



16/72 PUBLIC 12/06/2010







SAP NetWeaver Operations The Adaptive ComputingController which was part ofthe SAP NetWeave Operations ITscenarios, is delivered as a separateproduct.

For more information about theAdaptive Computing Controller,see SAP Developer Network athttp://www.sdn.sap.com/irj/

sdn/adaptive

Software Life-Cycle Management No separate use case describedfor SAP NetWeaver 7.3; Life cyclemanagement capabilities of SAPNetWeaver are part of everyinstallation.

Mobilizing Business Processes Mobilizing Business Processes. Upgrade of Scenarios Based on SAPNetWeaver Mobile [page 33]

Authentication and Single Sign-On No separate use case defined in SAPNetWeaver 7.3For information aboutauthentication and singlesign-on, see SAP Library atSAP NetWeaver Library SAP

NetWeaver: Function-Oriented ViewSecurity User Authentication and SingleSign-On

Integrated User and AccessManagement

No separate use case defined in SAPNetWeaver 7.3For information aboutauthentication and singlesign-on, see SAP Library atSAP NetWeaver Library SAP

NetWeaver: Function-Oriented ViewSecurity Identity Management

Changes in Usage TypesCompared to SAP NetWeaver 7.0, some additional usage types are available with SAP NetWeaver 7.3.For example, SAP NetWeaver Composition Environment has been integrated into the SAP NetWeaverplatform.When you upgrade your SAP NetWeaver 7.0 systems, the source release usage types are mapped to thecorresponding target release usage types. The following table shows which usage types will be in yoursystem after an upgrade to SAP NetWeaver 7.3 depending on the source release usage types.

12/06/2010 PUBLIC 17/72

http://www.sdn.sap.com/irj/sdn/adaptive




3 Upgrade at a Glance3.3 Transition from SAP NetWeaver PI 7.1

SAP NetWeaver 7.0 Usage Types SAP NetWeaver 7.3 Usage Types

Application Server Java n Application Server Java (BASIC)n Application Server Java Extensions (AS)n NW Product Description (NW-MODEL)n Adobe Document Services (ADOBE)n Composite Application Framework (CE-APPS)

Process Integration n Process Integration (PI)n Advanced Adapter Engine (PI-AF)n Enterprise Service Repository (ESR)

Development Infrastructure n Development Infrastructure (DI)

Enterprise Portal n Enterprise Portal (EP)n Composition Environment (COMP-ENV)

Enterprise Portal Core n EP Core ‒ Application Portal (EPC)n Guided Procedures (CE-PROCESS)

BI Java n BI Java (BI)

3.3 Transition from SAP NetWeaver PI 7.1

Use Case

The SOA-Based Integration use case has been renamed to Building Integration Scenarios.

Software Units

Compared to SAP NetWeaver 7.1, some additional usage types are available with SAP NetWeaver 7.3,for example, SAP NetWeaver Composition Environment has been integrated into the SAP NetWeaverplatform. The following table shows which usage types will be in your system after the upgrade.

SAP NetWeaver Process Integration 7.1 SAP NetWeaver 7.3

Process Integration (PI) n Process Integration (PI)n Advanced Adapter Engine (PI-AF)n Enterprise Services Repository (ESR)

Application Server Java n Application Server Java (BASIC)n AS Java Extensions (AS)n Adobe Document Services (ADOBE)n Composite Application Framework (CE-APPS)n NW Product Description (NWMODEL)

For more information, see Upgrade of Scenarios Based on SAP NetWeaver Process Integration [page 28].

18/72 PUBLIC 12/06/2010

3 Upgrade at a Glance3.4 Transition from SAP NetWeaver Mobile 7.1

3.4 Transition from SAP NetWeaver Mobile 7.1

Comparing SAP NetWeaver Mobile 7.1 to SAP NetWeaver 7.3, no changes have taken place regardingthe installable software units. The functional scope of SAP NetWeaver Mobile 7.1 and SAP NetWeaverMobile 7.1 including enhancement package 1 is covered by theMobilizing Business Processes use caseof SAP NetWeaver 7.3.For more information, see Upgrade of Scenarios Based on SAP NetWeaver Mobile [page 33].

3.5 Transition from SAP NetWeaver Composition Environment7.1 and 7.2

SAP NetWeaver Composition Environment has been integrated into the SAP NetWeaver 7.3 platform.The functional scope is covered by the use case Building Composite Applications including the capabilitiesBusiness Rules Management, Process Composition, Java Development and SOA Infrastructure.Compared to SAP NetWeaver Composition Environment 7.1 and 7.1 including enhancement package1, SAP NetWeaver 7.3 includes a different set of usage types. When you upgrade system to SAPNetWeaver 7.3, the source release usage types are mapped to the target release usage types and thenthe system is upgraded accordingly.SAP NetWeaver Composition Environment 7.2 and SAP NetWeaver 7.3 have the same usage typestructure, so there will be no changes when you upgrade your system.The following tables show the mapping of usage types SAP NetWeaver Composition Environment 7.1and 7.1 including enhancement package 1, respectively to SAP NetWeaver 7.3 usage types.Source Release SAP NetWeaver Composition Environment 7.1

SAP NetWeaver Composition Environment 7.1 SAP NetWeaver 7.3

Basic (BASIC) n Application Server Java (BASIC)n Demo Applications (BASIC-RA)n CE Product Description (CE-MODEL)*

Composite Applications (CE-APPS) Composite Application Framework (CE-APPS)

Composite Views (CE-VIEWS) Composition Environment Platform (COMP-ENV)

Composite Voice (CE-VOICE) Composition Voice (CE-Voice)*

Composite Process (CE-PROCESS) Guided Procedures (CE-PROCESS)*

Adobe Print Services (CE-ADOBE) Adobe Document Services (ADOBE)

IDE Update Site (IDE-Update-Site) NWDS Update Site (IDE-Update-Site)*

Enterprise Service Repository (ESR) Enterprise Service Repository (ESR)

Source Release SAP NetWeaver Composition Environment 7.1 Including EnhancementPackage 1

12/06/2010 PUBLIC 19/72

3 Upgrade at a Glance3.6 Upgrade Tools

SAP NetWeaver Composition Environment 7.1Including Enhancement Package 1

SAP NetWeaver 7.3

Application Server Java (BASIC) n Application Server Java (BASIC)n Demo Applications (BASIC-RA)n CE Product Description (CE-MODEL)*

Composite Applications (CE-APPS) Composite Application Framework (CE-APPS)

Composite Views (CE-VIEWS) Composition Environment Platform (COMP-ENV)

Composite Voice (CE-VOICE) Composition Voice (CE-Voice)*

Guided Procedures (CE-PROCESS) Guided Procedures (CE-PROCESS)*

Adobe Document Services (CE-ADOBE) Adobe Document Services (ADOBE)

IDE Update Site (IDE-Update-Site) NWDS Update Site (IDE-Update-Site)*

Enterprise Service Repository (ESR) Enterprise Service Repository (ESR)

Business Process Management (BPEM) Business Process Management and Business RulesManagement (BPM)

BPM Portal Integration (BPEM-PP-Integration) Business Process Management and Business RulesManagement (BPM)

NW Development Infrastructure (NWDI) Development Infrastructure (DI)

* Note that CE Product Description, Guided Procedures, Composition Voice and NWDS UpdateSite are only provided for compatibility reasons. These usage types are not included in a newinstallation of SAP NetWeaver 7.3. Guided Procedures and NWDS Update Site have been replaced bynewer technologies. CE Product Description illustrates the usage of SAP NetWeaver CompositionEnvironment for previous releases, so it is not relevant for SAP NetWeaver 7.3.For more information, see Upgrade of Scenarios Based on SAP NetWeaver Composition Environment [page 31]

3.6 Upgrade Tools

SAP Solution Manager Maintenance Optimizer

To upgrade to SAP NetWeaver 7.3, you need an SAP Solution Manager 7.0 system with at least SupportPackage 23. The Solution Manager Maintenance Optimizer guides you through the selection anddownload of required software packages and creates a system-specific stack configuration file. Thisstack configuration file is requested by the upgrade tools SAPup/SAPJup and Software Update Manager.Without this stack configuration file, you cannot perform the upgrade.For more information about setting up and maintaining SAP Solution Manager for supporting theupgrade, see the documents How to Upgrade to SAP NetWeaver 7.3 (for upgrades from SAP NetWeaver 7.1and higher) or Upgrade Guide ‒ SAP NetWeaver 7.3 <Technology> (for upgrades from SAP NetWeaver 7.0or lower) available at http://service.sap.com/upgradenw73.

20/72 PUBLIC 12/06/2010


3 Upgrade at a Glance3.6 Upgrade Tools

SAPup and SAPJup for Upgrades from Source Release SAP NetWeaver 7.0 and Lower

If the source release of your system is SAP NetWeaver 2004 or SAP NetWeaver 7.0, you use the upgradeprograms SAPup (ABAP) and SAPJup (Java) to upgrade your SAP NetWeaver systems.The upgrade procedure, the System Switch Upgrade, installs an instance of the target release, theshadow system, in parallel with the current source release system in the same database. The parallelsystem contains all the software of the target release and is used to perform actions on the targetrelease while the source release is still in production operation. In the downtime, the switch is madeto the new system, and any remaining data is imported. Any parts of the source release systemthat are no longer needed are deleted.For the dual-stack upgrade, the ABAP and Java upgrade steps are merged into a common process witha common UI.For more information, see the document Upgrade Guide ‒ SAP NetWeaver 7.3 <Technology> <OperatingSystem> <Database> available at http://service.sap.com/upgradenw73

Software Update Manager for Upgrades from Start-Release SAP NetWeaver 7.1 and Higher

If the source release of your system is SAP NetWeaver Mobile 7.1, SAP NetWeaver Process Integration7.1 or SAP NetWeaver Composition Environment 7.1 or higher, you use the Software Update Manager.The upgrade to SAP NetWeaver 7.3 from SAP NetWeaver 7.1 and higher is technically an update,comparable with an enhancement package installation. The Software UpdateManager internally callsthe already known SAP Enhancement Package Installer, which also uses a system switch procedure.For more information, see the documents How to Upgrade to SAP NetWeaver 7.3 and Update Guide ‒ Updateof SAP Systems Using the Software Update Manager 1.0.

Tools for Special Purposes

n Upgrade Dependency AnalyzerWhen you plan your upgrade, you can use the Upgrade Dependency Analyzer to check theexistence of upgrade dependencies between two separately installed SAP systems in your systemlandscape.For more information, see SAP Service Marketplace at http://service.sap.com/uda.

n Unicode ConversionIf you want to upgrade a non-Unicode system to a Unicode system, you have to perform a specialprocedure named “Combined Upgrade & Unicode Conversion (CU&UC)”. For more information,see SAP Developers Network at http://sdn.sap.com/irj/sdn/i18n Unicode .

n Installation of Additional Java Usage TypesIf you want to install additional Java usage types in your upgraded system, you use the JavaSupport Package Manager. For more information, see the Installation Guide ‒ SAP Systems Based on SAPNetWeaver 7.3 Application Server Java on <Operating System>: <Database>.

12/06/2010 PUBLIC 21/72


http://service.sap.com/uda

http://sdn.sap.com/irj/sdn/i18n Unicode

4 Upgrade

4 Upgrade

4.1 Upgrade of Scenarios Based on SAP NetWeaver Portal

Below you will find information about upgrading scenarios that are based on SAP NetWeaver Portal.This section is relevant for you if you used one of the following scenarios:

n SAP NetWeaver 2004: SAP EP

n SAP NetWeaver 7.0:l Running an Enterprise Portall Enterprise Knowledge Management: Content Integration and Management; Content

Creation, Publication and Accessl Enabling User Collaborationl Developing, Configuring and Adapting Applications: Creating Portal Applications Using PDK

for .NET

In SAP NetWeaver 7.3, the functional scope is covered by use case Integrating and Self-Servicing Content withSAP NetWeaver. The following figure shows the software units which make up the use case.

Figure 1: Integrating and Self-Servicing Content with SAP NetWeaver

12/06/2010 PUBLIC 23/72

4 Upgrade4.1 Upgrade of Scenarios Based on SAP NetWeaver Portal

4.1.1 Upgrade Sequence

The following table describes the sequence in which you have to perform the upgrade or installationsteps.

Note

For information about finding the referenced documentation, see section List of Documentation [page 59].

No.Action.[Required Documentation] Remarks / Subsequent Steps

1 You upgrade SAP EP 6.0 or SAP NetWeaver 7.0Enterprise Portal.[Upgrade Guide ‒ SAP NetWeaver 7.3 Java]

As SAP NetWeaver 7.3 is only supported withSupport Package Stack (SPS) 01 or higher,include at least SPS 01 into the upgrade.

2 You upgrade the Portal Development Kit.[Installation, Upgrade, and Configuration Guide ‒ PDKfor .NET]

3 If installed as a separate system: you upgradethe system with usage types AS Java and DI.[Upgrade Guide ‒ SAP NetWeaver 7.3 Java]

4 You upgrade the standalone RTC applicationserver.If you upgrade a standalone RTC applicationsharing server that is running on usage type ASJava, and which does not have usage type EPCinstalled, then the system contains the usagetypes EP Core ‒ Application Portal and EP afterthe upgrade. The required software is calculatedby the SAP Solution Manager MaintenanceOptimizer and installed during the upgrade.[Upgrade Guide ‒ SAP NetWeaver 7.3 Java]

5 You upgrade the Forums Application.[SAP Note 1049553]

6 You upgrade SAP NetWeaver Search andClassification (TREX).[Upgrade Guide ‒ TREX 6.1 to SAP NetWeaver 7.0TREX (TREX 7.0)[Upgrade Guide ‒ TREX 7.0 to SAP NetWeaver 7.1TREX (TREX 7.1)]

7 Perform the delta configuration [page 38].

24/72 PUBLIC 12/06/2010

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1049553&_NLANG=en&_NVERS=0

4 Upgrade4.2 Upgrade of Scenarios Based on SAP NetWeaver BW

4.2 Upgrade of Scenarios Based on SAP NetWeaver BW

Below you will find information about upgrading scenarios that are based on SAP NetWeaver BusinessWarehouse. This section is relevant for you, if you used one of the following scenarios:

n SAP NetWeaver 2004: SAP Business Information Warehouse; BI Information Broadcastingn SAP NetWeaver 7.0: Business Planning and Analytical Services; Enterprise Reporting, Query,

and Analysis; Enterprise Data Warehousing

In SAP NetWeaver 7.3, the functional scope is covered by the use case Data Warehousing. The followingfigure shows the software units that make up the use case.

Figure 2: Data Warehousing



Note


12/06/2010 PUBLIC 25/72


Procedure

No.Action[Corresponding Documentation]

Remarks and Subsequent Steps[Corresponding Documentation]

1 You upgrade the SAP BW ABAP server.[Upgrade Guide ‒ SAP NetWeaver 7.3 ABAP]

NoteIf you have a dual-stack system, both the ABAPand the Java upgrade run in parallel in anintegrated procedure.

n As SAP NetWeaver 7.3 is only supported withSupport Package Stack (SPS) 01 or higher,include at least SPS 01 in the upgrade.

n The required Basis plug-in (PI_Basis) isincluded in the upgrade. It includes theEnterprise Portal plug-in.

n You must update the BI_CONT add-onduring the upgrade of the SAP BW server.The upgrade process prompts you for therequired DVD at the appropriate point intime. For more information, see SAP Note1484437.

You upgrade your Java systems.[Upgrade Guide ‒ SAP NetWeaver 7.3 Java]

n Include at least Support Package stack 01 forSAP NetWeaver 7.3 into the upgrade.

n Source Release SAP NetWeaver 2004, BIUDI and MMR: As these components havebeen integrated into Application ServerJava, you have a system with usage types ASJava, AS Java Extensions and NW ProductDescription after the upgrade. You caninstall additional usage types in this system(for example, BI Java) using the Java SupportPackage Manager. For more information,see the [Installation Guide ‒ SAP NetWeaver 7.3,section Installation of Additional Software Units orUsage Types in Existing SAP Systems]

n Source Release SAP NetWeaver 2004,BI Information Broadcasting: Theupgrade program upgrades the PortalPlatform and Content Management andCollaboration components and installs newBI components. As a result, you have theusage types, BI Java, EP Core ‒ ApplicationPortal, and EP installed in the system afterthe upgrade.

2

If no AS Java based installation exists, but youwant to use BI Java based functions, install anSAP NetWeaver 7.3 system with usage type BIJava.[Installation Guide ‒ SAP NetWeaver Application ServerJava]

n The installation of usage type BI Javaincludes the installation of usage type EPCore‒ Application Portal and EP, since BIJava depends on these usage types.

26/72 PUBLIC 12/06/2010





3 You upgrade SAP NetWeaver Search andClassification (TREX).[[Upgrade from TREX 6.1 to SAP NetWeaver TREX7.0][Upgrade Guide ‒ SAP NetWeaver TREX 7.0 to TREX7.1].

TREX enables fast and complex search for BImetadata. The metadata is directly indexedwith its attributes and it is available in the search.Therefore, search queries such as "All queriesthat contain the characteristic ’customer’ andthe key figure ’sales’ " are supported. To be ableto use all functions of the search (for example,the search query described above), you haveto use TREX. However, as a base function,you can search for objects using their text andtechnical name also without TREX. For furtherinformation see SAP Note 979444.

4 You upgrade SAP liveCache version 7.6 toversion 7.7For information about the procedure, createa customer message and assign it to thecomponent BC-DB-LCA.

n If you already use SAP liveCache version 7.7,no upgrade is required.

n You can use SAP liveCache as lock server toimprove the performance if you have a largeamount of complex data records describedwith selection tables that have to be locked.

5 Optional: You upgrade the SAP R/3 back-endplug-in to at least version 2004.1.Documentation: Composite SAP Note 704564:R/3 plug-in: PI 2004.1 installation/delta upgradeFor more information about the plug-ins, seeSAP Note 153967.

Note

n New and extended interfaces forintegrating SAP R/3, SAP R/3 Enterprise,and SAP ERP Central Component (SAPECC) will no longer be delivered with theirown add-on (SAP R/3 Plug-In). As of SAPECC 6.0, they will be contained directlyin SAP ECC. Therefore, this step is notrequired for SAP ECC 6.0 or higher.For more information about the deliverystrategy, see SAP Service Marketplace athttps://service.sap.com/r3-plug-in.

n With BI-Java, you get access to non-SAPdata sources by using the correspondingJDBC driver.

12/06/2010 PUBLIC 27/72




https://service.sap.com/r3-plug-in

4 Upgrade4.3 Upgrade of Scenarios Based on SAP NetWeaver Process Integration



6 You upgrade the SAP GUI for Windowsincluding the BW/ BI add-on (BusinessExplorer) on each host for which you want tocreate a connection to the SAP NetWeaver 7.3BW server.[Installation Guide ‒ SAP Front End ]

Up to SAP enhancement package 2 for SAPNetWeaver 7.0 you could maintain queryproperties using transaction RSRT. As of SAPNetWeaver 7.3, the maintenance of queryproperties has been partiallymoved into the BExQuery Designer. The settings Data Integrity andRead Near-Line Storage As Well are now available inBEx Query Designer (in the Query Properties) andyou can no longer maintain them in RSRT.To make these settings, you require at least BExQuery Designer 7.10 Patch 5.


4.3 Upgrade of Scenarios Based on SAP NetWeaver ProcessIntegration

Below you will find information about upgrading scenarios that are based on SAP NetWeaver ProcessIntegration. This section is relevant for you if you used one of the following scenarios:

n SAP NetWeaver 2004: SAP XI 3.0

n SAP NetWeaver 7.0: Enabling Application-to-Application Processes; Enabling Business-to-BusinessProcesses, Enabling Enterprise Services

n SAP NetWeaver Process Integration 7.1/ 7.1 including enhancement package 1: SOA-BasedIntegrationNote that the use case SOA-Based Integration has been renamed as Building Integration Scenarios.

In SAP NetWeaver 7.3, the functional scope is covered by the use case Building Integration Scenarios.The following figure shows the software units which make up the use.

28/72 PUBLIC 12/06/2010


Figure 3: System Landscape for Building Integration Scenarios with PI Standard Installation



Note

For information about finding the referenced documentation, see section List of Documentation.

No.Action[Required Documentation] Remarks / Subsequent Steps

1 You upgrade the SAP XI system or SAPNetWeaver system with usage type PI,respectively.[For upgrades from SAP XI 3.0 or SAP NetWeaver7.0: Upgrade Guide ‒ SAP NetWeaver 7.3 ABAP+Java][For upgrades from SAP NetWeaver PI 7.1: Howto Upgrade to SAP NetWeaver 7.3 and Update Guide‒ Update of SAP Systems Using the Software UpdateManager 1.0]

n As SAPNetWeaver 7.3 is only supported withSupport Package Stack (SPS) 01 or higher,include at least SPS 01 into the upgrade.

n For upgrades from source releases SAPXI 3.0 and SAP NetWeaver 7.0 (includingenhancement packages), you use theupgrade programs SAPup and SAPJup.For upgrades from source release SAPNetWeaver PI 7.1 (including enhancementpackage 1), you use the Software UpdateManager.

n If you use partner adapters, see SAP Note1407530 for information about their release.

12/06/2010 PUBLIC 29/72



No.Action[Required Documentation] Remarks / Subsequent Steps

n Modules or adapters that you havedeveloped for the SAP XI 3.0 or SAPNetWeaver 7.0 adapter framework, do notrun in the Process Integration framework ofSAP NetWeaver PI 7.3. During the upgradeof the adapter framework, you have toreplace them by appropriate versions for thePI 7.3 adapter framework.If you cannot upgrade these modules oradapters, youmay use a J2EE Adapter Engineof release SAP XI 3.0 or SAP NetWeaver 7.0as a non-central Adapter Engine in yourSAP NetWeaver 7.3 landscape. To do so, youhave to move all scenarios containing thesemodules and adapters to a non-centralAdapter Engine of release SAP XI 3.0 orSAP NetWeaver 7.0 before you upgrade thecentral PI system.

2 You upgrade the standalone Adapter Engine orPartner Connectivity Kit: As these are AS Javabased systems, the standard upgrade procedureand tools for SAP Java systems are used.[For upgrades from SAP XI 3.0 or SAP NetWeaver7.0: Upgrade Guide ‒ SAP NetWeaver 7.3 Java][For upgrades from SAP NetWeaver PI 7.1: Howto Upgrade to SAP NetWeaver 7.3 and Update Guide‒ Update of SAP Systems Using the Software UpdateManager 1.0]

SAP Partner Connectivity Kit is requiredfor small business partner and subsidiaryintegration. Note that you cannot upgrade anSAP Partner Connectivity system if there areother components installed in this system atthe same time. In this case, install a new SAPPartner Connectivity Kit system.

3 You upgrade the Adapter Engine (Java SE).SAP Library at SAP NetWeaver Library SAPNetWeaver Library: Function-Oriented View ProcessIntegration Working with the Adapter-Engine (JavaSE) Installation

The Adapter Engine (Java SE), including thecontained adapters, is only supported forcompatibility reasons. It is not developed anyfurther. It should therefore only be used incases where it is unavoidable.

4 You upgrade Search and Classification (TREX)[Upgrade Guide ‒ SAP NetWeaver TREX 7.0 to TREX7.1].

5 You upgrade your SAP GUI installations.[Installation Guide ‒ SAP Front End]

6 If required, transfer ESR content from SAPNetWeaver CE 7.1 ESR to SAP NetWeaver PI 7.3ESR.[Upgrade of System Landscapes Including ES Repository forSAP NetWeaver CE [page 31]]

7 You perform the delta configuration [page 38].

30/72 PUBLIC 12/06/2010

4 Upgrade4.4 Upgrade of Scenarios Based on SAP NetWeaver Composition Environment

4.3.2 Upgrade of System Landscapes Including ES Repositoryfor SAP NetWeaver CE

If your source release system landscape contains an Enterprise Service Repository (ESR) of SAPNetWeaver Composition Environment 7.1, you should discontinue using this ESR. Instead, use theESR included in SAP NetWeaver PI 7.3. Proceed as outlined below.

Process

1. Upgrade to SAP NetWeaver PI 7.3.2. Transport the ESR content from SAP NetWeaver Composition Environment to SAP NetWeaver PI

either using the Change Management Server (CMS) of SAP NetWeaver DI, or using the file system.For more information, see the SAP Library at SAP NetWeaver Library Function-Oriented ViewProcess Integration Enterprise Services Repository & Registry Managing Services in the Enterprise ServicesRepository Transporting Objects Transporting ESR Content and Objects of Integration Directory

3. You manually have to assign users to the user groups of the SAP NetWeaver PI ESR since thesecannot be transferred from the SAP NetWeaver CE ESR.

4.4 Upgrade of Scenarios Based on SAP NetWeaverComposition Environment

Below you will find information about upgrading scenarios that are based on SAP NetWeaverComposition Environment. This section is relevant for you if you use SAP NetWeaver CompositionEnvironment 7.1, 7.1 including enhancement package 1 or 7.2.In SAP NetWeaver 7.3, the functional scope is covered by the use case Building CompositeApplications. The following figure shows which software units make up the the use case.

12/06/2010 PUBLIC 31/72

4 Upgrade4.4 Upgrade of Scenarios Based on SAP NetWeaver Composition Environment

Figure 4: Building Composite Applications



Note


No. Action[Required Documentation]

Remarks / Subsequent Steps

1 You upgrade the SAP NetWeaverComposition Environment server orDeveloper Workplace.[How to Upgrade to SAP NetWeaver 7.3 andUpdate Guide ‒ Update of SAP Systems withSoftware Update Manager 1.0]

As SAP NetWeaver 7.3 is only supportedwith Support Package Stack 01, includeat least Support Package Stack 01 in theupgrade.

2 You upgrade the SAP NetWeaverDeveloper Studio.[Installation and Update Guide ‒ SAP NetWeaverDeveloper Studio 7.3]


32/72 PUBLIC 12/06/2010

4 Upgrade4.5 Upgrade of Scenarios Based on SAP NetWeaver Mobile

4.5 Upgrade of Scenarios Based on SAP NetWeaver Mobile

Below you will find information about upgrading scenarios that are based on SAP NetWeaver Mobile.Depending on your source release, you either have to perform a migration or an upgrade to thetarget release:

n Source release SAP NetWeaver 2004 and SAP NetWeaver 7.0: Since the system landscape andsoftware architecture changed, you need to perform a migration. For information about themigration procedure, see theMigration Guide ‒ SAP NetWeaver Mobile 7.3.

n SAP NetWeaver Mobile 7.1 and SAP NetWeaver Mobile 7.1 including enhancement package 1: Youcan upgrade directly to SAP NetWeaver 7.3. The upgrade steps are outlined below in sectionUpgrade Sequence.

In SAP NetWeaver 7.3, the functional scope is covered by the use caseMobilizing Business Processes. Thefollowing figure shows the software units that make up the use case.

Figure 5: Software Units for Mobilizing Business Processes


Note


The following table describes the sequence of upgrade steps for upgrading from SAP NetWeaverMobile 7.1 and SAP NetWeaver Mobile 7.1 including enhancement package 1 to SAP NetWeaver 7.3:

12/06/2010 PUBLIC 33/72

4 Upgrade4.5 Upgrade of Scenarios Based on SAP NetWeaver Mobile



1 You upgrade the SAP NetWeaver Mobileserver.[How to Upgrade to SAP NetWeaver 7.3]

As SAP NetWeaver 7.3 is only supported withSPS 01 or higher, include at least SPS 01 in theupgrade.

2 You generate the software component versions(SWCV).You must regenerate all the data objectsthat are part of the SAP Basis 7.10 softwarecomponent version along with otherapplication-specific software componentversions.

3 You configure the Data Orchestration Engine(DOE).SAP NetWeaver Library SAP NetWeaver

Mobile Configuring SAP NetWeaver MobileConfiguring SAP NetWeaver AS Performing DOEInitial Setup and Configuration

4 If existing in your landscape, you upgrade yourAS Java-based systems with usage type DI orEnterprise Portal.[Upgrade Guide ‒ SAP NetWeaver 7.3 Java <OperatingSystem>]

5 You upgrade your mobile clients (if SAPMobile Clients are used):

1. Download patches from SAP ServiceMarket Place and then upload them to theData Orchestration Engine.SAP NetWeaver Library SAP NetWeaver

Mobile Administering SAP NetWeaverMobile Software Logistics ApplyingPatches Uploading Patches to the DOE

2. Apply patches.You assign the patches to the clientdevices, which makes them available inthe outbound queues of the devices. Onthe next synchronization of the clientwith the DOE, the patch is downloadedto the client device. The client installerapplies the patches on the client, and thenautomatically restarts the client.SAP NetWeaver Library SAP NetWeaver

Mobile Administering SAP NetWeaverMobile Software Logistics ApplyingPatches Applying Patches on the Mobile Client

6 You upgrade your SAP GUI installations.[Installation Guide ‒ SAP Front End ]

34/72 PUBLIC 12/06/2010

4 Upgrade4.6 Upgrade of SAP Knowledge Warehouse

4.6 Upgrade of SAP Knowledge Warehouse

Below you will find information about upgrading SAP Knowledge Warehouse. This section is relevantfor you if you used one of the following scenarios:

n SAP NetWeaver 2004: SAP KW

n SAP NetWeaver 7.0: IT scenario Documentation, Training Materials and Manuals Management

Note

As of SAP NetWeaver 7.0, SAP Knowledge Warehouse (SAP KW) is an integral part of SAP NetWeaverApplication Server.For more information, see the SAP Note 1406422.

The following figure shows a typical system landscape for SAP Knowledge Warehouse:

Figure 6: SAP Knowledge Warehouse

4.6.1 Upgrade Preparation for SAP Knowledge Warehouse

Perform the following preparations before you start the upgrade of your SAP Knowledge Warehousesystem.

12/06/2010 PUBLIC 35/72



4.6.1.1 Backing Up the SAP System and the SAP ContentServer

Before you start the upgrade, create a backup of the SAP system (ABAP+Java dual-stack system) andof all SAP Content Servers. The SAP system and the SAP Content Servers must be in a consistentstate when you perform the backup. We recommend that you create the backup after you havemade the last changes to your production data. Otherwise, data could be lost if problems occurduring the upgrade.If your Application Server Java is installed as a standalone system, you need to create a backup for thissystem as well.

4.6.1.2 Saving the SAP Content Server Configuration File

Create a copy of the file contentserver.ini (on Windows) or cs.conf (on Unix). This file containsinformation about the repositories stored in the MaxDB (formerly SAP DB) instance. You can findit in the home directory of the SAP Content Server Web site. Save the copy of the file in a differentdirectory from the original one.This file is especially important as it contains information about already existing content repositoriesin the SAP Content Server.

4.6.1.3 Saving Customer-Specific Changes to the InternetKnowledge Servlet

Note

SAP ITS is no longer required.

If you have made changes to the display component of the SAP Knowledge Warehouse, the InternetKnowledge Servlet (IKS), for example, if you changed the graphics in the banner to meet yourrequirements for corporate identity, save a version of the SCA (Software Component Archive) of thesource release IKS so you can apply your changes to the IKS-SCA of your target release.

4.6.2 Upgrade Sequence SAP Knowledge Warehouse

The following table describes sequence in which you have to perform the upgrade or installation steps.

Note


36/72 PUBLIC 12/06/2010




1 Upgrade the Application Sever ABAP andApplication Server Java.[Upgrade Guide ‒ SAP NetWeaver 7.3 ABAP ]Upgrade Guide ‒ SAP NetWeaver 7.3 Java]

As SAP NetWeaver 7.3 is only supported withSPS 01 or higher, include at least SPS 01 in theupgrade.

2 Uninstall older versions of SAP Gateway. A SAP Gateway is only required if SAP ContentServer is installed on a different server than theAS ABAP instance. Otherwise, the gateway of theexisting SAP instance can be used.

3 Uninstall the SAP Internet Transaction Serverif it exists.To uninstall an ITS instance that is only used foryour KW system, proceed as follows:

1. Start the Microsoft Management Console.

2. Close the ITS Web site.

3. Choose Save and close the MicrosoftManagement Console.

4. Choose Start Settings Control PanelAdd/Remove Programs Internet TransactionServer .

NoteA standalone instance of SAP ITS only exists forvery low Support Package levels of SAP WebApplication Server 6.40 (lower than SPS13). Ifyour system has a higher Support Package levelor is already on SAP NetWeaver release 7.0, noactivity is required here.

4 Upgrade the SAP Content Server and CacheServer (if used).[Installation Guide SAP Content Server 6.40]

For SAP Knowledge Warehouse, the content hasto be stored in a MaxDB database. The upgradeof SAP Content Server may also require anupgrade of theMaxDB instance. For informationabout the supported combinations of SAPContent Server, operating system and MaxDBversion, see the Product Availability Matrix athttp://service.sap.com/pam.If SAP Content Server is installed on a differentserver than the SAP Web AS, you can performthe upgrade activities in parallel.

5 Install SAP Gateway, if SAP Gateway is notalready installed on your system.[Installation Guide ‒ Standalone Gateway on <OperatingSystem> ‒ For SAP Systems Based on SAP NetWeaver 7.3]

If SAP Content Server is installed on the samehost as the SAP NetWeaver Application ServerABAP, you do not need to install the SAPGateway.

12/06/2010 PUBLIC 37/72

http://service.sap.com/pam

4 Upgrade4.7 Configuration of Systems



6 Install or update to SAP NetWeaver Search andClassification (TREX).[Installation Guide ‒ SAP NetWeaver 7.1 TREX SingleHostInstallation Guide ‒ SAP NetWeaver 7.1 TREXMultipleHostsUpgrade Guide ‒ TREX 6.1 to SAP NetWeaver 7.0TREX (TREX 7.0)]Upgrade Guide ‒ TREX 7.0 to SAP NetWeaver 7.1TREX (TREX 7.1)]

Installation or upgrade to a higher TREX releaseis only required if you want to use the fulltext orattribute search capabilities of SAP KW.

NoteTREX 7.1 is supported on a restricted numberof operating systems. For more information,see the Product Availability Matrix (PAM) athttp://service.sap.com/pam.

7 Check the configuration of your SAP KnowledgeWarehouse. For information about theconfiguration, see SAP Note 1287381.

4.6.3 Follow-Up Activities

SAP KW Configuration

For information about the configuration of the SAP Knowledge Warehouse scenarios, see SAP Note1287381.

4.7 Configuration of Systems

After the upgrade, new and changed functions may require you to adjust your Customizing.For information about new, changed or enhanced functions, see the Release Notes available in theSAP Library at SAP NetWeaver Library What’s New in SAP NetWeaver 7.3 .For a description of the configuration activities, see the SAP Library at SAP NetWeaver Library SAPNetWeaver Library: Function-Oriented View <Software Unit>

38/72 PUBLIC 12/06/2010




5 Description of Software Units

5 Description of Software Units

The following sections provide more details about usage types, standalone engines, optionalstandalone units and clients of SAP NetWeaver.

5.1 Systems with Usage Types

Java Usage Types

The Java usage types are all based on Application Server Java (BASIC) and in addition require usagetype NW Product Description (NW-MODEL) in the same system. Further dependencies exists that areshown in the following figure:

Figure 7: Java Usage Types

Compatibility Usage Types

Apart from the usage types described here, there are some discontinued usage types. If these usagetypes are installed in your source release system, they are preserved during the upgrade. However,

12/06/2010 PUBLIC 39/72

5 Description of Software Units5.1 Systems with Usage Types

they are not part of a new installation of SAP NetWeaver 7.3. For more information, see CompatibilityUsage Types [page 62].

Adobe Document Services (ADS)

Adobe Document Services is a set of runtime services that provide a range of form and documentcreation and manipulation functions such as:

n Converting XML form templates (created using Adobe LiveCycle Designer) to PDF and variousprint formats

n Setting Adobe Reader rights to enable users to fill in and annotate forms, save and print themlocally, and include digital signatures for authentication using the free Adobe Reader software

n Extracting data from SAP applications into Interactive Forms and transferring form data back intoSAP applications using XML

DependenciesAdobe document services depends on Application Server Java.Functional UnitsAdobe Document Services comprises the identically named functional unit.

ALV Export Services (ALV-EXPORT)

With ALV Export Services, you can create print versions of lists that are displayed using ALV for WebDynpro for ABAP (SAP List Viewer) and ALV for Web Dynpro for Java.DependenciesALV Export Services depends on Adobe Document Services, Application Server Java and NW ProductDescription.

Note

There is no installation option in SAPinst for installing ALV Export Services. You have to install anSAP NetWeaver system with usage type Adobe Document Services (ADS) and then apply SupportPackage Stack 01 which includes ALV Export Services.

Application Server ABAP (AS ABAP)

AS ABAP serves as a development platform for the ABAP environment. SAP Business Suite is basedon SAP NetWeaver 7.0 and the features of AS ABAP included in SAP Business Suite 7i2010 and SAPNetWeaver 7.3 have been aligned to a great extent. Although AS ABAP is fully supported as adevelopment platform in SAP NetWeaver 7.3, we recommend using the enhancement packagesfor SAP NetWeaver 7.0 for ABAP development. For information about the enhancement packageavailability, see SAP Service Marketplace at http://service.sap.com/releasestrategy.

Application Server Java (BASIC)

AS Java is used to provide the Java foundation of SAP NetWeaver using the Java Engine, a JavaEE-compliant application server for running enterprise applications. In addition to the pure Java

40/72 PUBLIC 12/06/2010



EE standard technologies, the Java Engine implements complementary technologies such as WebDynpro or Web Services.DependenciesAS Java can be combined optionally with other Java-based usage types in one system.Functional UnitsApplication Server Java comprises the following functional units:

Functional Unit Description

CM Services (Change Management Services) CM Services help you to manage your Javadevelopment. They provide services for creatingdevelopment configurations, for importing andexporting, and for the deployment to runtimesystems. CM Services enable you to set up teamdevelopment with centrally managed developmentconfigurations. It also supports the automateddeployment of build results on to central runtimesystem. The import and export service enablesyou to import and export Software ComponentArchives (SCAs) of a development configuration.When a transport system is needed, a developmentconfiguration can be integrated into the Change andTransport System (CTS+). To use CM Services, usagetype DI is required.

Java Data Archiving Java Data Archiving provides APIs to allow Javaapplications to connect to the XML Data ArchivingService for data archiving solutions. Java archiving isrequired for Java applications with a large volume ofretention-relevant data.

Java Foundation This is the Java foundation of SAP NetWeaver. Amongits capabilities is the JEE Engine, a J2EE-compliantapplication server for running enterprise applications.In addition to the pure JEE standard technologies, theJEE Engine implements complementary technologies,such as Web Dynpro or Web Services, that are targetedat supporting large-scale, real-business applicationdevelopment projects.

Services Registry The Services Registry is a registry for Web services.Located centrally within an SOA landscape, it containsentries for all services and service definitions in thatlandscape. The registered services are classified usingsemantic-rich classification systems to enable thebrowsing of services by classification.

12/06/2010 PUBLIC 41/72



System Landscape Directory The System Landscape Directory (SLD) of SAPNetWeaver serves as a central information repositoryfor your system landscape. A system landscapeconsists of hardware and software components thatdepend on each other with regard to installation,software updates, and demands on interfaces. Theinformation in the SLD is used by various SAP tools.

XML Data Archiving Service The XML Data Archiving Service (XML DAS) enablesdata to be stored using the WebDAV Storage Interfacefor the ILM Solution from SAP as certified in theinterface BC-ILM. It allows both XML-sensitivestorage used for JAVA Archiving or XML Archiving(see corresponding Functional units) and ILM awarearchiving used in SAP NetWeaver ILM.

Application Server Java Extensions (AS)

AS Java Extensions enable you to create development components in SAP-specific technologies on topof JEE, for example, for service composition. In addition, you can enrich standard JEE technologies(such as Enterprise JavaBeans, Web services, and enterprise applications) with additional SAP-specificcapabilities, such as service group configuration.DependenciesAS Java Extensions require AS Java and NW Product Description as a prerequisite in the same system.Functional UnitsAS Java Extensions do not comprise a functional unit.

BI Java (BI)

BI Java provides the Java runtime for several BW capabilities.DependenciesBI Java requires AS Java, NW Product Description, Java Extensions, EP Core ‒ Application Portal, andEnterprise Portal in the same system. Usually, scenarios running on usage type BI Java also requireusage type BW ABAP. While installing BI Java, the required usage types are installed automatically.After configuring BI Java, you do not need to perform further steps in AS Java, Java Extensions, EPCore ‒ Application Portal, and Enterprise Portal.Note that you must keep the system with usage type BI Java and the system with usage type BW ABAPin sync concerning applied Support Package Stacks.Functional UnitsBI Java comprises the identically named functional unit.

Business Process Management and Business Rules Management

Business Process Management supports the process collaboration and creation of new innovativebusiness processes based on standardized core processes. SAP NetWeaver Business Process

42/72 PUBLIC 12/06/2010


Management enables collaborative composition of executable business processes based on a processmodel. Clearly defined business rules can be incorporated into processes from the outset. The tightintegration with Business Rules Management enables business users with no coding skills to createand modify rules using decision tables.With Business Rules Management you can author, execute, and manage business rules. The followingkey features are offered by Business Rules Management:

n Inference-based rule engine implementing RETE algorithmn Support of different rules formats (declarative rules, decision table and flow rules)n Rules Manager: a Web Dynpro Java based rules maintenance tool for business usersn Versioning and tracking changes of business rulesn Out-of-the-box Web service generation for rule setsn Rules testing in the rules composer (NWDS)n Public API for rules execution

n Tighter integration with Business Process Management

DependenciesBusiness Process Management and Business Rule Management requires AS Java, NW ProductDescription, Composition Environment Platform and Composite Application Framework in thesame system.Functional UnitsBusiness Process Management and Business Rule Management comprise the following functionalunits:


Process Server Contains the function for Business ProcessManagement

Rules Server Contains the functions for Business RulesManagement

Business Warehouse ABAP (BW ABAP)

Business Warehouse provides the infrastructure for the following functions:

n Data warehousingn Various analytical technologies and functionsn Business planning functionsn Web-based and Excel-based reporting, analysis, and planningn Information broadcasting to distribute BI content via various channels either as precalculated

documents with past data, or as links with live datan Open analysis interfaces that make available various interfaces for connecting front-end tools of

third-party providers

DependenciesBW requires AS ABAP as a prerequisite in the same system.

12/06/2010 PUBLIC 43/72


Note

For usage type BW, there is no installation option in SAPinst. Instead, you have to install AS ABAPwith SAPinst and then SAP NetWeaver BW 7.3 BI Content Add-On 7.35 or higher.

Central Process Scheduling by Redwood (JOB-SCHED)

SAP Central Process Scheduling adds powerful cross-component scheduling functionality to theintegration capabilities of SAP NetWeaver. SAP Central Process Scheduling has the following keycharacteristics:

n CentralityThere is only one central instance of this scheduler which takes control over all backgroundprocesses in the entire landscape and allows for cross system scheduling.

n Event-Driven SchedulingDependencies between background processes can be defined not only time based but also eventbased.

n Real-Time ExecutionAll information about jobs is stored centrally and transferred to the remote systems immediatelybefore job submission.

Formore information, see SAP Developer Network at http://sdn.sap.com/irj/sdn/nw-scheduling.DependenciesSAP Central Process Scheduling requires Application Server Java and NW Product Description inthe same system.Functional UnitsSAP Central Process Scheduling comprises the functional unit Integrated Central Process Schedulingby Redwood.

Composite Application Framework (CE-APPS)

The Composite Application Framework is an abstraction layer that is used to develop all thecomponents required for the service and object layer of a composite application. These componentsare:

n Business Objects (Entity Services)n Business Logic (Application Services)n Connectivity to external services (Web Services and BAPI/RFC, local and remote persistency)n Service Provisioning

The Composite Application Framework also provides a comprehensive toolbox that includes thefollowing features:

n A programming modeln Metadata

n Authorization conceptsn Modeling of relationships between business objects

44/72 PUBLIC 12/06/2010

http://sdn.sap.com/irj/sdn/nw-scheduling


n Integration into lifecycle management using SAP NetWeaver Development Infrastructure

This environment, which is based on a service-oriented architecture (SOA), enables developers tobuild applications that leverage the whole SAP NetWeaver technology platform without the need touse low-level APIs. This way, developers can focus on implementing the business logic of a compositeapplication. The Service Composer, a graphical modeling tool, provides service simplification andcomposition. This greatly eliminates the need to write code for simplification and data mapping.DependenciesComposite Application Framework requires Application Server Java and NW Product Description inthe same system.Functional UnitsComposite Application Framework comprises the functional unit Composite Application FrameworkRuntime providing the above-mentioned features.

Composition Environment Platform (CE-ENV)

The Composition Environment Platform provides a toolset and runtime for efficiently developing,running, and managing composite applications based on SOA principles. It builds upon proventechnologies that have been enhanced and integrated to provide greater functionality and flexibility.The Composition Environment Platform offers you the following capabilities:

n User interface (UI) development: SAP NetWeaver Web Dynpro and SAP NetWeaver VisualComposerWeb Dynpro and Visual Composer are SAP’s standard UI technologies based on the ModelView Controller (MVC) for developing user interfaces. Web Dynpro Java or Visual Composerapplications are developed within the SAP NetWeaver Developer Studio using a model-drivenapproach that minimizes manual UI coding and uses visual tools to design and reuse components.

n Business LogicThe Composite Application Framework enables Java business object modeling.

n Service Simplification and CompositionA graphical modeling capability simplifies and adapts Complex Services for easy consumption inComposition Environment. This greatly eliminates the need to write code for simplification anddata mapping.

DependenciesComposition Environment Platform requires Application Server Java, NW Product Description, andComposite Application Framework in the same system.Functional UnitsComposition Environment Platform comprises the following functional units:

12/06/2010 PUBLIC 45/72



Composition Environment Platform Composition Environment Platform is the foundationfor building and running composite applications.

ECM integration core Enterprise Content Management (ECM) IntegrationCore facilitates the provision and consumption ofEnterprise Content Management services usingstandardized interfaces. Therefore, it enables businessapplications to consume core ECM services providedby SAP as well as extended ECM services provided bypartners and third-party vendors leveraging theirECM product offering. Besides the core runtimecomponents, this functional unit contains the serviceprovider interface (SPI) for exposing ECM services aswell as the application programming interface (API)for making use of these services.

ECM Integration Services ECM Integration Services offer additional serviceson top of ECM Integration Core functional. Thesesupplementary services such as the server for WorldWide Web Distributed Authoring and Versioning(WebDAV) can be leveraged by applications on top ofthe already exposed ECM services of the connectedservice providers.

Visual Composer Visual Composer is a model-driven development toolused to create UI screens and Portal content usinga drag-and-drop graphical environment, withoutthe need to write code. Using Visual Composer youcan create standalone applications such as formviews and dashboards or UI screens, such as WebDynpro screens. Visual Composer also providesPortal Content Modeling capabilities for generatingRoles, Pages, iViews and other content for the SAPNetWeaver Portal.

Portal Provides basic SAP NetWeaver Portal capabilitiesexcluding the Web Page Composer capabilities, thedata statistics tools of Portal Activity Reports, and theActivity Data Collector.

Universal Worklist Offers users unified and centralized access to theirwork and relevant information from within theportal. It collects tasks and notifications frommultiple provider systems ‒ Business Workflow,Collaboration Task, Alert Framework, and KMRecentNotifications ‒ and displays them in a single list.

46/72 PUBLIC 12/06/2010


Development Infrastructure (DI)

Development Infrastructure provides an infrastructure for developing Java-based applications on theSAP NetWeaver platform and enables versioning of source code, build and lifecycle management ofthese applications. DI takes care of all parts of the development process :

1. Version control system for central management of source code: The Design Time Repository(DTR) is a distributed version control system used in SAP NetWeaver Development Infrastructureto manage source code in development and lifecycle management processes.

2. Central build and archive management: The Component Build Service (CBS), gives developersaccess to the latest archive versions in a central archive storage and a central build triggered bydevelopers or central lifecycle management processes.

3. Central landscape and transport management: CM Services enables you to set up teamdevelopment with centrally managed development configurations. It also supports the automateddeployment of build results on a central runtime system. The import and export service allow youto import and export Software Component Archives (SCAs) of a development configuration. If atransport system is needed, a development configuration can be integrated into the enhancedChange and Transport System (CTS+).You can also use the Change Management Service (CMS), which gives administrators a centralservice to set up development landscapes for all development tasks and manage all transportprocesses for these tasks in the same UI. However, note that CMS is planned to be replaced by theCM Services in future releases. Therefore, we recommend using CM Services.

Dependencies

n DI requires AS Java and NW Product Description as a prerequisite in the same system. Optionally,it can be combined with other usage types in one system.You can run the development infrastructure on an AS Java separatly from the rest of your runtimesystems in the system landscape for improved scalability.If you use a development infrastructure, you have to install the Developer Studio feature SAPNetWeaver Developer Studio Development Infrastructure Client.

Functional UnitsDI comprises the functional unit SAP NetWeaver Development Infrastructure providing theabove-mentioned functions.

Enterprise Portal (EP)

Enterprise Portal (EP) provides users with a single, uniform point of access to the applications,services, and information they need for their daily work. Moreover, the Portal offers business usersthe features to easily create and manage portal pages and generate their own content using thefollowing capabilities:

n KM and Web Content Capabilities

12/06/2010 PUBLIC 47/72


EP provides basic document management capabilities and content services within SAP NetWeaverPortal (KM). KM provides the basic capabilities that customers need to run their scenarios, as wellas an extension framework for custom implementations.These KM capabilities are also integrated into the Web Page Composer environment to enableflexible Web content management scenarios, bringing relevant information from user-generatedcontent and business applications together in the portal.

n Portal Add-On with Forums and Wiki CapabilitiesOn top of EP, you can install the portal add-on including the forums and the wiki application.The forums application provides a comprehensive range of discussion features, which areparticularly suitable for community scenarios. Forums typically focus on a specific purpose suchas support or human resources or they might offer customers a place to trade product tips andsolutions. Intuitive user interfaces make it easy for users to ask questions, share information, postannouncements to the community, escalate questions to experts, and to receive updates onposted comments. Users can create draft versions of their postings, exchange private e-mails withother forum users, and vote in polls.Wikis provide a framework to easily share and contribute knowledge and information in anintuitive way within the company. They give employees, customers, suppliers, and partnersa framework to collaborative writing, and help save time by making ideas available, sharingknowledge, and managing related information.

DependenciesEP requires EPC, AS Java, NW Product Description, and Java Extensions as a prerequisite in the samesystem. Optionally, it can be combined with other usage types in one system.Functional UnitsEnterprise Portal comprises the following functional units:


Knowledge Management Enables portal users to distribute, access, and manageunstructured information within an organization ina heterogeneous repository landscape. Capabilitiesinclude collaborative document authoring andpublishing, version management, search andnavigation with taxonomies, automated classificationand subscription, and more.

Collaboration Brings users, information, and applications togetherto ensure successful cooperation and interaction inthe portal. These tools include collaboration rooms,instant messaging, e-mail, and calendar integration.

Enterprise Services Repository (ESR)

The Enterprise Services Repository (ES Repository) provides a central place where enterprise servicedefinitions are modeled, stored, and maintained. It supports SAP’s concept of building services basedon the process component modeling methodology. The ES Repository offers the following features:

48/72 PUBLIC 12/06/2010


n Support of governed definitions of SOA assets (such as services and data types).n Support of widely adopted open standards including Web Services and UDDI.

The ES Repository supports SAP-defined Global Data Types based on the Core ComponentTechnical Specification standards (stack) (CCTS standards (stack)).

n Basis for enabling easy access to enterprise services - described with rich business classifications -when developing composite applications and business processes.

DependenciesEnterprise Services Repository requires Application Server Java in the same system.Functional UnitsEnterprise Services Repository comprises the identically named functional unit providing the abovementioned capabilities.

EP Core ‒ Application Portal (EPC)

EP Core ‒ Application Portal (EPC) provides the basic portal capabilities for SAP NetWeaver. Itprovides a uniform entry point to content and applications in a consistent, role based manner. Itoffers a single point of access through a Web front end to SAP and non-SAP information sources,enterprise applications, information repositories, databases and services across organizational andtechnical boundaries ‒ all integrated into a single user experience. EPC alone provides more flexibilitywhen implementing a portal where the full enterprise portal capabilities (such as knowledgemanagement tools) are not needed.The EPC usage type contains some additional important capabilities that will help you manageyour content and processes:

n The core portal capabilities include various tools and service for managing portal content, users,and connections to connected systems such as Single-Sign-On, tools for application integration,roles and permissions, changing the portal look and feel with the new Ajax Framework, andlifecycle management (transport).

n Integration of several SAP NetWeaver Portals and third-party portals into one harmonized SAPNetWeaver Portal acting as the single point of access to all the business related applications andservices in the organization.

n Web Page Composer (WPC): this is an integral part of EPC providing powerful capabilities forbusiness users to easily create and manage enriched portal pages. Web Page Composer supportsprofessionals creating interactive portal pages.

DependenciesEPC requires AS Java and NW Product Description as a prerequisite in the same system.Functional UnitsEP Core ‒ Application Portal comprises the following functional units:

12/06/2010 PUBLIC 49/72



Portal Provides basic SAP NetWeaver Portal capabilities

Universal Worklist Provides the Universal Worklist Capabilities

Mobile

Usage type Mobile is used to enable field personnel to participate in a business process in an“occasionally connected” mode. Occasionally connected means that a direct connection (usingWLAN or GPRS) between the mobile device and back end is only established at certain times ‒ atsynchronization points, when the Mobile Server (that is, the system with usage type Mobile) andMobile Client exchange data in order to keep the server and client updated. This enables the end userto perform process tasks completely independently from the back-end system, which is extremelyhelpful if a steady connection cannot be guaranteed or might be too expensive. To realize this usagetype, an intelligent application needs to run on each device containing a user interface, businesslogic, and data handling. Mobile includes the Data Orchestration Engine (DOE), an ABAP-basedmessage-oriented middleware. The Data Orchestration Engine consists of the following:

n A design time tool for defining data objects and the distribution of data.n A runtime to replicate, synchronize and distribute data between the components of the system

landscape. This includes, for example, messaging, filling queues, and sending data to the back end.

DependenciesMobile is not an installable software unit. To set up a Mobile system, you install AS ABAP andconfigure it for Mobile.

NW Product Description (NW-MODEL)

NW Product Description contains metadata for SAP NetWeaver, for example, about comprisedsoftware components and their interdependencies. NW Product Description is always includedwhen you install a Java usage type.

Process Integration (PI)

PI consists of core components that model, design, automate, and integrate processes in one ormore application systems. For the integration of internal and cross-company processes, PI is usedto incorporate all the functions of what was formerly known as Exchange Infrastructure (XI). Inaddition, PI contains core components for cross-component Business Process Management (ccBPM)for application-embedded and application-unbounded processes.DependenciesPI requires AS ABAP, AS Java, NW Product Description, AS Java Extensions, PI Adapter Engine, andEnterprise Services Repository as a prerequisite in the same system.For installing PI, it is mandatory to have a dedicated PI system. This applies to development, quality,and production landscapes. It is a prerequisite that no other system in your system landscape has ahigher release and enhancement package level than the PI system. If you want to upgrade or install

50/72 PUBLIC 12/06/2010


an application in your system landscape, you first have to make sure that the current release andenhancement package level of the PI system is on the same level - if required, you have to upgrade thePI system first to the new or a higher release. In a dedicated PI system, this can be accomplished with aminimum of downtime. Also, the PI system would not be affected by the downtime of other usagetypes running in the same system.Functional UnitsProcess Integration comprises the functional unit SAP NetWeaver Process Integration.

Restrictions for Systems with Multiple Usage Types

n If you have one system with multiple usage types, be aware that we do not provide standard toolsfor separating these usage types and distribute them to multiple systems at a later stage. Forexample, if you have a system with usage types A and B, you are not able to migrate it with SAPstandard tools into two systems, one with usage type A only and the other with usage type B only.In addition, we do not provide standard tools for merging multiple systems with different usagetypes into one system with multiple usage types at a later stage.If you want to perform these tasks, you require specific project support.The following figure shows that SAP standard system copy andmigration tools do not support youin separating or merging systems with usage types:

Figure 8:

n Although you can use one system for multiple usage types, client restrictions apply to usage typeBW ABAP. For BW ABAP, you should reserve a dedicated client for reporting purposes. In thisclient, activate the SAP NetWeaver BI Content Add-On as required.

12/06/2010 PUBLIC 51/72

5 Description of Software Units5.2 Optional Standalone Units

5.2 Optional Standalone Units

Advanced Adapter Engine (PI Adapter Engine)

You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter, IDoc Adapter, andABAP proxies) and external systems. You use the various adapters in PI Adapter Engine to convertXML- and HTTP-based messages to the specific protocol and format required by these systems, andthe other way around.You can use the following adapters:

n RFC Adaptern SAP Business Connector Adaptern File/FTP Adaptern JDBC Adaptern JMS Adaptern SOAP Adaptern Marketplace Adaptern Mail Adaptern RNIF Adaptern CDIX Adaptern IDoc Adapter (Advanced Adapter Engine) (adapter type IDOC_AAEn HTTP Adapter (Advanced Adapter Engine) (adapter type HTTP_AAE)

You can use the Advanced Adapter Engine which is included in the PI system as a central adapterengine. Optionally, for performance reasons, you can install a non-central Advanced AdapterEngine on a separate host.DependenciesThe Advanced Adapter Engine requires AS Java, NW Product Description, and AS Java Extensions as aprerequisite in the same system. These usage types are automatically installed when you install theAdvanced Adapter Engine.Functional UnitsThe Advanced Adapter Engine comprises the functional unit Advanced Adapter Engine.

Advanced Adapter Engine Extended

The installation option Advanced Adapter Engine Extended (AEX) consists of core components tomodel, design, automate, and integrate processes in one or more application systems. The AdvancedAdapter Engine Extended provides the following capabilities:

n Connectivity capabilities of the Advanced Adapter Engine (AAE)n Design and configuration tools to set up scenarios that are based on the AAE. In particular, for

design and configuration you can use the ES Repository and the Integration Directory. TheIntegration Directory installed with AEX contains a subset of configuration options required forthe configuration of message processing by the AAE, basically the integrated configuration.

n Mediation capabilities of AAE

52/72 PUBLIC 12/06/2010

5 Description of Software Units5.2 Optional Standalone Units

You can use the following adapters:l RFC Adapterl SAP Business Connector Adapterl File/FTP Adapterl JDBC Adapterl JMS Adapterl SOAP Adapterl Marketplace Adapterl Mail Adapterl RNIF Adapterl CDIX Adapterl IDoc Adapter (Advanced Adapter Engine) (adapter type IDOC_AAEl HTTP Adapter (Advanced Adapter Engine) (adapter type HTTP_AAE)

DependenciesAdvanced Adapter Engine Extended requires AS Java, NW Product Description AS Java Extensions, PIAdapter Engine, and Enterprise Services Repository as a prerequisite in the same system.Functional UnitsAdvanced Adapter Engine Extended comprises the identically named functional unit.

Partner Connectivity Kit

Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI. It enables a systemof a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAPNetWeaver systems.PCK runs on an SAP NetWeaver Application Server Java system and contains the necessary parts ofthe SAP NetWeaver PI component Integration Builder. Thus PCK allows you to send and receive messagesusing the PI messaging protocol.PCK uses the following functional components to connect to an SAP NetWeaver PI environment:

n XI Adaptern File Adaptern JMS Adaptern JDBC Adaptern SOAP Adaptern RFC Adaptern Mail Adaptern SAP Business Connector Adapter

DependenciesPCK requires PI Adapter Engine, AS Java Extensions, NW Product Description, and AS Java in thesame system.Functional UnitsPartner Connectivity Kit comprises the identically named functional unit.

12/06/2010 PUBLIC 53/72

5 Description of Software Units5.3 Standalone Engines

5.3 Standalone Engines

For SAP NetWeaver, the following standalone engines are available:

Adapter Engine Java SE

Adapter Engine (Java SE) is a separate software unit. You can use it only if you have SAP NetWeaversystems with usage type PI in your system landscape. It has to be installed manually. You use theAdapter Engine (Java SE) to connect to external systems. Using the various adapters in the AdapterEngine (Java SE), XML and HTTP-based messages can be converted to the specific protocol and formatrequired by such systems, and the other way around. The Adapter Engine (Java SE) only providessome of these adapters as a standalone version with restricted functions for operating systems that donot support SAP NetWeaver PI, but that have at least a Java Runtime Environment 5.0. Therefore,you should use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you touse the Advanced Adapter Engine.

Content Server

Content Server is a separate server instance that is used to store documents or other types ofcontent related to SAP applications. The accompanying cache server can cache content if yourcompany operates in several locations. This reduces load on the wide area network when workingwith documents.

liveCache

liveCache is a database engine for managing complex objects in scenarios where large volumes ofdata must be permanently available and modifiable. For SAP NetWeaver BW, you can optionally useit as a lock server to improve the performance if you have to lock a lot of complex data recordsdescribed by selection tables.

Search and Classification (TREX)

SAP NetWeaver Search and Classification (TREX) offers an integrated set of services. TREX servicesinclude search and retrieval in large document collections, text mining, automatic documentclassification, and search and aggregation over structured data in SAP applications. TREX can handletext from documents in numerous formats, including Microsoft Office and Adobe formats (PDF), andmore than 30 languages. TREX search options, such as exact, Boolean, fuzzy, or linguistic search,and classification options such as query-based or example-based classification, offer great powerand flexibility to end users.The BW accelerator is based on TREX technology. You need an installation based on 64-bitarchitecture for the BW accelerator. The hardware partners provide this variant already preconfiguredas the BW accelerator box. Note that a TREX installation configured for searching in metadata anddocuments based on 32-bit architecture cannot be used for the BW accelerator. Accordingly, a BWaccelerator box also cannot be used for searching in metadata and documents. In order to be able touse the search function and the BW accelerator, you need separate installations.

54/72 PUBLIC 12/06/2010

5 Description of Software Units5.4 Clients

Web Dispatcher

The Web Dispatcher lies between the Internet and your SAP system. It is the entry point for HTTP(s)requests into your system, which consists of one or more SAP NetWeaver application servers. As asoftware Web switch, the Web dispatcher can reject connections or accept them. When it accepts aconnection, it balances the load to ensure even distribution across the servers.You can use the Web dispatcher in ABAP/Java systems and in pure Java systems, as well as in pureABAP systems.It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point inthe demilitarized zone (DMZ), SSL, URL filtering), but you simply want to balance the load betweenmultiple SAP NetWeaver Application Server instances.Since Web Dispatcher is optional for every SAP system, it is not contained in the system landscapes ofthe use cases in this documentation.For more information, see the SAP Library [page 61] at SAP NetWeaver ‒ Function Oriented ViewApplication Server Application Server Infrastructure SAP Web Dispatcher .

5.4 Clients

With SAP NetWeaver, you can use the front-end clients and tools described below:

Adobe LiveCycle Designer

Adobe LiveCycle Designer enables the creation of forms that combine high-fidelity presentation withXML data handling. The easy-to-use graphical interface of Adobe LiveCycle Designer enables users toquickly design forms, maintain form templates, define a form’s business logic, make changes, andpreview forms before they are deployed as Adobe PDF files.

Business Client

The SAP NetWeaver Business Client (NWBC) is a high fidelity desktop client that allows usersto display their assigned roles and to launch applications. SAP NetWeaver Business Client offers aunified environment for and a single point of entry to SAP business applications and technologies.NWBC is ideal for displaying business applications such as classical SAP GUI UIs, Web Dynpro UIs, BSPpages, and other content using its multiple rendering engines. NWBC provides role-based access toapplications either via the portal or directly using PFCG roles. In addition to the basic capabilitiesdetailed above, the SAP NetWeaver Business Client makes use of its tight desktop integration toprovide additional benefits such as desktop search functionality. In the newest SAP NetWeaverBusiness Client version you will find the improved user interface (UI) based on the SAP Signaturedesign. This UI offers in part an expert-based interactive paradigm and a superior look and feelmatching the expectations of today’s users aiming to maximize their daily activities.

12/06/2010 PUBLIC 55/72


Business Explorer (BI Add-On/BW Add-On)

Business Explorer provides flexible reporting and analysis tools for strategic analyses anddecision-making support within a company. These tools include query, reporting, and analysisfunctions. As an employee with access authorization, you can evaluate past or current data on variouslevels of detail and from different perspectives, not only on the Web but also in Microsoft Excel.You can use Business Explorer Information Broadcasting to distribute Business Intelligence contentby e-mail either as precalculated documents with historical data, or as links with live data. Youcan also publish it to the SAP NetWeaver Portal.

SAP GUI

SAP offers three different client applications for accessing ABAP applications in SAP systems (such asSAP NetWeaver systems with usage type AS ABAP). This SAP GUI family consists of:

n SAP GUI for HTMLSAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) whichis included in the installation of SAP NetWeaver systems as of SAP NetWeaver 7.0. On theclient side, only a suitable browser and a virtual machine are required. For information aboutsupported browser versions, see the Product Availability Matrix on SAP Service Marketplace athttp://service.sap.com/pam.

n SAP GUI for the Java environment (SAP GUI for Java)SAP GUI for Java is a generic SAP GUI that covers a variety of platforms.For more information about the installation of SAP GUI for Java, see the documentation InstallationGuide ‒ SAP Front End.

n SAP GUI for the Windows environment (SAP GUI for Windows)SAP GUI for Windows is SAP’s universal client for accessing all SAP applications built on ABAPtechnology. It is available on the Microsoft Windows platform only and offers the broadest featureset of all members of the SAP GUI family.For more information about the installation of SAP GUI for Windows, see the Installation Guide‒ SAP Front End.

SAP GUI also includes optional add-ons, such as the BW add-on and KW add-on, which might berequired to use certain SAP NetWeaver capabilities.

Note

Data warehousing: SAP GUI for HTML and SAP GUI for Java do not have all the capabilities ofSAP GUI for Windows. BEx Query Designer, BEx Analyzer and UIs with network controls are notsupported with SAP GUI for HTML and SAP GUI for Java.

The following SAP GUI versions are supported with SAP NetWeaver 7.3:

n SAP GUI for Windows 7.20 (or higher)n SAP GUI for Java 7.20 (or higher)n SAP integrated ITS

56/72 PUBLIC 12/06/2010



For more information about the SAP GUI family, see SAP Developer Network athttp://sdn.sap.com/irj/sdn/sap-gui.

Mobile Client

Mobile Client is installed locally onmobile devices, and is equipped with a Web server, a database layer,and a framework for the mobile applications. Staff working remotely can therefore work offline anddo not have to wait for a network connection to complete time-critical business applications. Usagetype Mobile offers tools for synchronization and data replication that make the data of the mobiledevice consistent with that of the back-end system.

SAP NetWeaver Developer Studio

The SAP NetWeaver Developer Studio is SAP’s Integrated Development Environment (IDE) for Javaand is based on the open-source tools framework Eclipse 3.3. With the SAP NetWeaver DeveloperStudio, you can develop Java EE 5 applications from scratch using the built-in support for newtechnologies such as EJB 3.0 and JSF 1.2.

SAP Enterprise Services Explorer Tool for Microsoft .NET

As part of its service-oriented architecture (SOA) offering, SAP provides a set of consumer tools thatallow the discovery and consumption of enterprise services from various development environments,such as NetWeaver Developer Studio, Visual Composer, and Microsoft Visual Studio. SAP EnterpriseServices Explorer tool for Microsoft .NET (ES Explorer for .NET) is an add-on for Microsoft VisualStudio 2005 and Microsoft Visual Studio 2008 that helps to leverage SOA by enabling .NET developersto discover SAP enterprise services and consume them in their applications, as well as publish theirown custom services. It is an important element of SAP ‒ Microsoft interoperability.To download the tool, access documentation and other resources, seehttps://www.sdn.sap.com/irj/sdn/dotnet Back-End Connectivity .

For the most up-to-date information about ES Explorer for .NET, see SAP note 1259258.

12/06/2010 PUBLIC 57/72

http://sdn.sap.com/irj/sdn/sap-gui

https://www.sdn.sap.com/irj/sdn/dotnet


A Appendix

A Appendix

A.1 SAP Notes

The following SAP Notes provide you with important information for your SAP NetWeaverimplementation project.Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP ServiceMarketplace at http://service.sap.com/notes .

List of Important SAP Notes

SAP Note Number Title Description

1407532 Release Restrictions for SAPNetWeaver 7.3

Some restrictions apply to theproductive use of SAP NetWeaver7.3. These are documented in thisSAP Note.

A.2 Documentation References

The following table contains a list of all documentation referenced in this document and informationabout where to find it.

Title Location

Master Guide ‒ SAP NetWeaver 7.3 See SAP Service Marketplace athttp://service.sap.com/installnw73

How to Upgrade to SAP NetWeaver 7.3 See SAP Service Marketplace athttp://service.sap.com/upgradenw73

Upgrade Guide ‒ SAP NetWeaver 7.3 <Technology><OperatingSystem> <Database>

See SAP Service Marketplace athttp://service.sap.com/upgradenw73

Update Guide ‒ Update of SAP Systems With Software UpdateManager 1.0

See SAP Service Marketplace athttp://service.sap.com/upgradenw73

Migration Guide ‒ SAP NetWeaver Mobile 7.3 See SAP Service Marketplace athttp://service.sap.com/upgradenw73

Installing and Updating TREX 7.1 Single Host See SAP Service Marketplace athttp://service.sap.com/installnw73

12/06/2010 PUBLIC 59/72

http://service.sap.com/notes

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1407532 &_NLANG=en&_NVERS=0













A AppendixA.3 More Information

Title Location

Installing TREX 7.1 Multiple Host See SAP Service Marketplace athttp://service.sap.com/installnw73

Upgrade Guide ‒ TREX 6.1 to SAP NetWeaver 7.0 TREX(TREX 7.0)

See SAP Service Marketplace athttp://service.sap.com/installnw73

Upgrade Guide ‒ TREX 7.0 to TREX 7.1 TREX See SAP Service Marketplace athttp://service.sap.com/installnw73

Installation, Upgrade, and Configuration Guide ‒ PDK for .NET] See SAP Service Marketplace athttp://service.sap.com/installnw73

Installation Guide ‒ SAP Front End See SAP Service Marketplace athttp://service.sap.com/installnw73

Installation and Update Guide — SAP NetWeaver DeveloperStudio 7.3

See SAP Service Marketplace athttp://service.sap.com/installnw73

Support Package Stack Guide ‒ SAP NetWeaver 7.3: Stack <xx> See SAP Service Marketplace athttps://service.sap.com/maintenancenw73

Operations

Installation Guide ‒ SAP Systems Based on SAP NetWeaver 7.3Application Server Java on <Operating System>: <Database>

See SAP Service Marketplace athttps://service.sap.com/installnw73

Installation Guide ‒ Standalone Gateway on <Operating System>‒ For SAP Systems Based on SAP NetWeaver 7.3

See SAP Service Marketplace athttps://service.sap.com/installnw73

Installation Guide SAP Content Server 6.40 See SAP Service Marketplace athttps://service.sap.com/installnw73

A.3 More Information

The following table contains links to information available on SAP Service Marketplace or in the SAPLibrary which is important for implementing SAP NetWeaver:

ContentLocation on SAP Service Marketplace or in SAPLibrary

The latest version of the installation and upgradeguides for SAP NetWeaver 7.3

http://service.sap.com/instguidesnw73

Information about supported platforms (operatingsystems, databases, browsers) for all SAP NetWeavercomponents


Sizing of SAP NetWeaver http://service.sap.com/sizing

60/72 PUBLIC 12/06/2010













https://service.sap.com/maintenancenw73

https://service.sap.com/installnw73








http://service.sap.com/sizing

http://service.sap.com/sizing

A AppendixA.4 Accessing the SAP Library

ContentLocation on SAP Service Marketplace or in SAPLibrary

System Copy Guides for different Releases n SAP NetWeaver 2004:http://service.sap.com//nw04installation

SAP Web ASn SAP NetWeaver 7.0

http://service.sap.com//installnw70

Installation ‒ SAP NetWeaver Systemsn SAP NetWeaver CE 7.1:

http://service.sap.com/instguidesnwce71

n SAP NetWeaver CE 7.1 includ-ing enhancement package 1:http://service.sap.com/instguidesnwce711

n SAP NetWeaver CE 7.2:http://service.sap.com//installnwce72

n SAP NetWeaver Process Integration 7.1:http://service.sap.com//installnwpi71

n SAP NetWeaver Mobile 7.1:http://service.sap.com//installnwmobile71

Information about security SAP Security Guide: See the SAP Library [page 61] atWhere to Find Information for Administrators SAP

NetWeaver Security Guide

Information about the technical operation of SAPNetWeaver

Technical Operations Manual: See the SAP Library [page 61]at Where to Find Information for Administrators TechnicalOperations for SAP NetWeaver

Information about SAP NetWeaver Support PackageStacks

http://service.sap.com/sp-stacks SP StackInformation

Information about installing SAP NetWeaver SupportPackage Stacks

http://service.sap.com/maintenancenw73

Support Package Stack Guide ‒ SAP NetWeaver

SAP Upgrade Info Center http://service.sap.com/upgrade

Information about SAP NetWeaver Capabilities http://sdn.sap.com/irj/sdn/netweaver

A.4 Accessing the SAP Library

For more information about SAP NetWeaver 7.3, access the SAP Library from any of the following:

n SAP Help Portal at http://help.sap.com/nw73

Select the required language.

Note

The SAP Help Portal contains the latest version of the SAP Library. Therefore, we recommendusing this channel to access the SAP Library.

12/06/2010 PUBLIC 61/72

http://service.sap.com//nw04installation

http://service.sap.com//nw04installation





http://service.sap.com//installnwce72

http://service.sap.com//installnwce72

http://service.sap.com//installnwpi71

http://service.sap.com//installnwmobile71

http://service.sap.com/sp-stacks



http://service.sap.com/upgrade

http://sdn.sap.com/irj/sdn/netweaver

http://help.sap.com/nw73



A AppendixA.5 Compatibility Usage Types

n An SAP system if you have installed the online documentation: Choose Help SAP LibraryThe browser starts.

n The help files on the online documentation CDs or DVDsIf you want to view the help files in HTMLHelp format from the online documentation CDs orDVDs, you need a PC running Microsoft Windows to install the HTMLHelp Viewer.

A.5 Compatibility Usage Types

Compatibility usage types are usage types that have been discontinued and are therefore not part ofthe standard SAP NetWeaver installation. If you upgrade from a previous release, these usage typeswill of course still exist in your systems if they have been present in the source release system.There might be reasons for which you want to install these usage types. You can do this using the JavaSupport Package Manager. Note that you can install these usage types only on existing SAP NetWeaver7.3 Java systems with at least usage type AS Java.For installation instructions, see the document Installation Guide ‒ SAP NetWeaver 7.3 Java on <OperatingSystem>: <Database>, section Installing Additional Usage Types or Software Units in an Existing SAP System.

Composition Voice

With Composition Voice you can design, develop and run interactive voice response (IVR)applications which can be accessed using telephones. Voice recognition and keypad input fromtelephone is used as input and recorded messages or computer generated speech (text to speech(TTS)) is used as output. Composite Voice provides system access to users with telephones at anytimefrom anywhere. Business transactions become easy to use with paperless transactions. It limitsdependency on mobile devices, computers and Internet access, and helps businesses to reach userslarge scale while saving costs.DependenciesComposition Voice requires Application Server Java, Composition Environment Platform, andComposite Application Framework in the same system.Functional UnitsComposition Voice comprises the following functional units:


Composite Voice Design Time Design time for Composite Voice

Composite Voice Runtime Runtime for Composite Voice

Demo Applications

Demo Applications illustrate the usage of SAP NetWeaver Composition Environment for previousreleases.

62/72 PUBLIC 12/06/2010

A AppendixA.5 Compatibility Usage Types

Guided Procedures

Guided Procedures is a framework for modeling and managing workflows using simple anduser-friendly tools. Guided Procedures enables access to multiple backend systems, consistentlycombining different types of services and applications into processes. In addition, Guided Proceduressupports collaboration, ad-hoc items, and offline task management using interactive forms. Itprovides role-based access to tools and resources and guidance through the workflows at runtime,thereby helping end users to easily identify and complete their tasks.

Dependencies

Guided Procedures require Application Server Java, Composition Application Framework,Composition Environment Platform as a prerequisite in the same system.

Functional Units

Guided Procedures comprise the identically named functional unit providing the above mentionedcapabilities.

NWDS Update Site

You use the NWDS update site when you develop composite applications using several DeveloperStudio installations. An update site contains all features for the Developer Studio. You can initiate acheck for updates or additional features in the Developer Studio and install them when available. Theupdate site capability mirrors the SAP Developer Studio update site on SAP Service Marketplace for animproved update performance. It does not run on a multi-node cluster.The NWDS update site has been replaced by an Eclipse-based solution.

Dependencies

NWDS update site requires Application Server Java as a prerequisite in the same system.

12/06/2010 PUBLIC 63/72

B Reference

B Reference

B.1 The Main SAP Documentation Types

The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software.

Figure 9: Documentation Types in the Software Life Cycle

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, aswell as many glossary entries in English and German.

n Target group:l Relevant for all target groups

n Current version:l On SAP Help Portal at http://help.sap.com Additional Information Glossary (direct

access) or Terminology (as terminology CD)l In the SAP system in transaction STERM

12/06/2010 PUBLIC 65/72

http://help.sap.com

B ReferenceB.1 The Main SAP Documentation Types

SAP Library is a collection of documentation for SAP software covering functions and processes.

n Target group:l Consultants

l System administratorsl Project teams for implementations or upgrades

n Current version:l On SAP Help Portal at http://help.sap.com (also available as documentation DVD)

The security guide describes the settings for a medium security level and offers suggestions forraising security levels. A collective security guide is available for SAP NetWeaver. This documentcontains general guidelines and suggestions. SAP applications have a security guide of their own.

n Target group:l System administratorsl Technology consultantsl Solution consultants

n Current version:l On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

Themaster guide is the starting point for implementing an SAP solution. It lists the requiredinstallable units for each business or IT scenario. It provides scenario-specific descriptions ofpreparation, execution, and follow-up of an implementation. It also provides references to otherdocuments, such as installation guides, the technical infrastructure guide and SAP Notes.

n Target group:l Technology consultantsl Project teams for implementations

n Current version:l On SAP Service Marketplace at http://service.sap.com/instguides

The installation guide describes the technical implementation of an installable unit, takinginto account the combinations of operating systems and databases. It does not describe anybusiness-related configuration.

n Target group:l Technology consultantsl Project teams for implementations


Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform. One of its main functions is the configuration of business and IT scenarios. It containsCustomizing activities, transactions, and so on, as well as documentation.

66/72 PUBLIC 12/06/2010

http://help.sap.com

http://service.sap.com/securityguide










n Target group:l Technology consultantsl Solution consultants

l Project teams for implementationsn Current version:l In SAP Solution Manager

The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system.The Customizing activities and their documentation are structured from a functional perspective.(In order to configure a whole system landscape from a process-oriented perspective, SAP SolutionManager, which refers to the relevant Customizing activities in the individual SAP systems, is used.)

n Target group:l Solution consultants

l Project teams for implementations or upgradesn Current version:l In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver, and precedes the solution operations guide. The manual refers users to the tools anddocumentation that are needed to carry out various tasks, such as monitoring, backup/restore,master data maintenance, transports, and tests.

n Target group:l System administrators


The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed. It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks.

n Target group:l System administratorsl Technology consultantsl Solution consultants


Upgrade

The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of anupgrade. It also refers to other documents, such as the upgrade guides and SAP Notes.

12/06/2010 PUBLIC 67/72








n Target group:l Technology consultantsl Project teams for upgrades


The upgrade guide describes the technical upgrade of an installable unit, taking into accountthe combinations of operating systems and databases. It does not describe any business-relatedconfiguration.

n Target group:l Technology consultantsl Project teams for upgrades


Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release. Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG).

n Target group:l Consultants

l Project teams for upgradesn Current version:l On SAP Service Marketplace at http://service.sap.com/releasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

68/72 PUBLIC 12/06/2010







http://service.sap.com/releasenotes



Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

12/06/2010 PUBLIC 69/72

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2010 SAP AG. All rights reserved.

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

70/72 PUBLIC 12/06/2010

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/installnw73

12/06/2010 PUBLIC 71/72




SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2010 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Upgrade Master Guide SAP Netweaver 7.3

Documents

Transcript of Upgrade Master Guide SAP Netweaver 7.3