SAP Netweaver7.3 Installation

Master Guide
SAP NetWeaver 7.3

Target Audience
X) System administrators
X) Technology consultants
PUBLIC
X$M6UnEV! !z;du* )z8Pu
Xv*Z6
UnEV- !z$;Du?
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can 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.4
1.3
1.2
1.1
1.0
2012-03-26
2011-11-07
2011-03-09
2010-12-06
2010-11-29
Minor changes
Information added regarding Data Warehousing on top of SAP HANA database
Minor changes
Minor changes
First version no changes.
2/68
PUBLIC
2012-03-26
Table of Contents
Chapter 1
About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2
2.1
2.2
2.3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Key Terms for Understanding SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . 7
Mapping of Use Cases to Installable Software Units . . . . . . . . . . . . . . . . . . . . . . 8
Planning and Implementation Steps Overview . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 3
3.1
3.1.1
3.1.2
3.1.3
3.2
3.2.1
3.2.2
3.2.3
3.3
3.3.1
3.3.2
3.4
3.4.1
3.4.2
3.5
3.5.1
3.5.2
3.6
3.6.1
3.6.2
Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Building Composite Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Warehousing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Warehousing on top of SAP HANA database . . . . . . . . . . . . . . . . . . . . . .
Building Integration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integrating and Self-Servicing Content with SAP NetWeaver
Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Landscape Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobilizing Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Custom Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4
4.1
Description of Software Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Systems with Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2012-03-26
PUBLIC
13
13
13
14
17
21
21
24
26
26
26
27
30
30
31
32
32
33
34
34
34
3/68
4.2
4.3
4.4
Optional Standalone Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Standalone Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 5
5.1
5.2
Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configuration of Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter A
A.1
A.2
A.3
A.4
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compatibility Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4/68
PUBLIC
61
61
61
62
62
2012-03-26
About this Document
1 About this Document
This Master Guide is the central starting point for the technical implementation of SAP NetWeaver
7.3. It provides you with information about the use cases for SAP NetWeaver 7.3 as well as the installable
software units, and refers you to the detailed documentation (such as the Installation Guides).
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation.
The Master Guide is regularly updated on SAP Service Marketplace at http://service.sap.com/
installnw73 .
Constraints
The scenarios that are presented here serve as examples of how you can use SAP software in your
company. The scenarios are intended only as models and do not necessarily run the way they are
described here in your customer-specific system landscape. Check your requirements and systems to
determine whether these scenarios can be used productively at your site. Furthermore, we recommend
that you test these scenarios thoroughly in your test systems to ensure that they are complete and free
of errors before going live.
2012-03-26
PUBLIC
5/68
This page is left blank for documents

that are printed on both sides.
Introduction
2.1
Key Terms for Understanding SAP NetWeaver
2 Introduction
SAP NetWeaver is the platform that provides the shared technology foundation for SAP business
applications. In addition, SAP NetWeaver provides optional technology components that allow
customers:
p5( To extend the reach of SAP applications to more people, also via new devices and consumption
models
p5( To integrate SAP applications and processes into heterogeneous landscapes
p5( To extend existing SAP processes
p5( To compose new processes that span SAP and non-SAP applications
p5( To securely manage and deliver information
p5( To holistically manage the lifecycle and infrastructure of SAP applications
Based on the principles of a service-oriented architecture (SOA), SAP NetWeaver helps organizations
optimize the return of their investment in SAP and non-SAP applications by allowing customers to
evolve their current IT landscapes into flexible business process platforms that close the gap between
insight and action.
An open technology platform, SAP NetWeaver is based on industry standards and can be extended with
commonly used development tools such as Java Platform, Enterprise Edition (Java EE); Microsoft .NET;
and IBM WebSphere. Providing fundamental orchestration capabilities such as business process
management, application lifecycle management and master data management, SAP NetWeaver is a
key technology that will allow customers to deploy and manage an environment of solutions that span
SAP and non-SAP on-premise and on-demand applications, providing superior flexibility while
ensuring 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:
p5( Usage Type
SAP systems with usage types are the main building blocks of SAP NetWeaver. They are identified
by unique SAP system IDs (SAPSIDs) and are configured for a certain purpose, as indicated by usage
types. Usage types have the following characteristics:
p5G Usage types consist of one or several functional units.
p5G They are a structuring element for SAP software on a technical level.
p5G Usage types are selectable installation units.
2012-03-26
PUBLIC
7/68
Introduction
2.2
Mapping of Use Cases to Installable Software Units
7,
7,
7,
7,
7C Usage types determine the intended purpose of a system and the role it plays in a given
(distributed) use case.
7C They are realized by installing and configuring a collection of software components.
7C They allow a logical view of the SAP NetWeaver technology platform.
7C A usage type may require other usage types in the same system.
7C They can also be run in the same system together with other usage types that are not a
prerequisite.
Standalone Engine
Standalone engines of SAP NetWeaver are additional installable software units. They do not work
as 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 not
part of a usage type. They do not run on AS ABAP or AS Java.
Client
Clients are additional installable programs or tools. They reside either on local front-end PCs
accessed by users or on back-end systems where they act as client programs within an SAP
NetWeaver system landscape.
Optional Standalone Units
Optional standalone units are additional software units that you install separately. They are based
on Application Server Java (AS Java) and provide specific (server) functions in combination with
one or more SAP systems.
Functional Units
A configured and activated unit of SAP NetWeaver that provides a set of functions. Functional
units are bundled into usage types as the installable unit. After the installation of a usage type, you
select 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 use
cases [page 13] and required SAP NetWeaver software units.
For information about the software units, see section Description of Software Units [page 37].
Use Case
Building Composite
Applications: [page
13]
Business Rules
Management and
Process Composition
8/68
Usage Types (Functional

Units)
Standalone
Engines
7, AS Java
7, Adobe Document
Services (optional)
7, Business Process
Management and
Business Rule
Management
Optional
Standalone Units
Developer
Workplace
PUBLIC
Clients
7, Developer
Workplace
7, SAP
NetWeaver
Developer
Studio
7, Visual
Composer
2012-03-26
Introduction
2.2
Mapping of Use Cases to Installable Software Units
Use Case

Units)
T97
T97
Building Composite
Applications: [page
13]
Java Development
and SOA
Infrastructure
T97
T97
T97
T97
T97
T97
Standalone
Engines
Optional
Standalone Units
Composite Application
Framework
Composition
Environment Platform
NW Product Description
DI [optional]
AS Java
DI [optional]
Enterprise Services
Repository
Data Warehousing [page T97 AS ABAP

Search and
Classification
21]
T97 BW ABAP
AS
Java
(TREX)
T97
T97 NW Product Description
T97 AS Java Extensions
T97 BI Java
T97 EP Core Application
Portal
T97 Enterprise Portal
Building Integration
Scenarios [page 26]
2012-03-26
T97
T97
T97
T97
Application Server Java T97 Adapter

T97 Advanced
Engine (Java
Adapter
AS Java Extensions
SE)
Engine
Application Server
[optional]
[optional]
ABAP
T97 SAP
T97 Advanced
Conversion
Adapter
T97 Process Integration
Enterprise
Services
Agent
by
Engine
T97
Repository
Extended
PUBLIC
Clients
T97 Adobe
LiveCycle
Designer
(Optional)
T97 Web
Browser
T97 Developer
Workplace
T97 SAP
NetWeaver
Developer
Studio
T97 Web
Browser
T97 SAP GUI
with BW
Add-On/BI
Add-On
T97 SAP
BusinessObj
ects
Analysis,
Edition for
Microsoft
Office*
[optional]
T97 SAP
BusinessObj
ects Crystal
Reports*
[optional]
T97 SAP
BusinessObj
ects Xcelsius
[optional]
T97 SAP
BusinessObj
ects Web
Intelligence*
[optional]
SAP GUI
SAP NetWeaver
Developer Studio
9/68
Introduction
2.3
Planning and Implementation Steps Overview
Use Case

Units)
:{
Integrating and Self
Servicing Content with
SAP NetWeaver Portal:
[page 30]
:{
:{
:{
:{
:{
:{
Standalone
Engines
Advanced Adapter
Engine
AS Java
AS Java Extensions
EP Core Application
Portal
EP
Portal Add-on (for
Building Communities with
Wikis and Forums only)
AS ABAP
Mobile
Application Server Java
DI
EP Core Application
Portal [optional]
Mobilizing Business
Processes: [page 32]
Developing Mobile
Applications for
Occasional
Connectivity
:{
:{
:{
:{
:{
Mobilizing Business
Processes: [page 32]
Enabling Mobile
Applications for
Occasional
Connectivity
Custom Application
Development [page
34]
:{ AS ABAP
:{ Mobile
:{ Application Server Java
[optional]
:{ EP Core Application
Portal [optional]
:{ Application Server
ABAP
Optional
Standalone Units
Clients
Informatica
[optional]
:{ SAP GUI
:{ SAP
NetWeaver
Developer
Studio
:{ Mobile
Client
:{ SAP GUI
:{ Mobile
Client
:{ SAP GUI
*Note that SAP BusinessObjects products require separate licenses.
2.3 Planning and Implementation Steps Overview

During an implementation project, you have to take into account many aspects and to take various
decisions. The major steps of this process are outlined below.
Procedure
1.
2.
3.
You determine the scope of your SAP NetWeaver implementation. For this, see the use cases [page
13], which describe how you can use SAP NetWeaver.
You determine which installable software units (that is, systems with usage types, standalone
engines, optional standalone units and clients) are required for these scenarios. For more
information, see the Mapping of Use Cases to Installable Software Units [page 8]section.
For details about the software units, see Description of Software Units [page 37].
You determine your system landscape.
10/68
PUBLIC
2012-03-26
Introduction
2.3
Planning and Implementation Steps Overview
4.
The Technical Infrastructure Guide provides general instructions about planning your system landscape
(for example with regard to sizing, distribution of functions to systems, or scaling).
You can access the Technical Infrastructure Guide at https://cw.sdn.sap.com/cw/community/
docupedia/tig.
For recommendations on deploying SAP NetWeaver within your solution landscape, see http://
www.sdn.sap.com/irj/sdn/alm-landscape-design Knowledge Center Deployment Options
In addition, consider the landscape-relevant aspects concerning your required use case [page 13]
to help you decide how many systems you require and how you want to use each of these systems.
You install [page 57] and configure [page 60] the software units of your SAP NetWeaver system
landscape.
2012-03-26
PUBLIC
11/68

Use Cases
3.1
Building Composite Applications
3 Use Cases
3.1 Building Composite Applications

3.1.1 Overview
What businesses need today is the possibility to combine data and services from legacy systems into
flexible processes that are business user-oriented, and enable efficient collaboration across large and
dynamic enterprises. For that purpose, SAP has introduced the composite application concept.
Composites are applications that make use of data and functions provided as services by back-end
systems and other underlying applications, and combine these into user-centric processes and pages,
supported by their own business logic and specific user interfaces.
Composite application enables rule-based business process composition and execution, and supports
a model-driven approach to manage business processes through their lifecycle - from concept to code
in an integrated composition environment.
Process Composition
SAP NetWeaver Business Process Management is a component of SAP NetWeaver. The process composer
is seamlessly integrated in the Eclipse-based design time, the SAP NetWeaver Developer Studio, as a
separate perspective and provides process modeling capabilities using Business Process Modeling
Notation (BPMN). This notation allows easy and intuitive process modeling both for business process
experts as well as developers in one common environment. The process composer supports all stages
of process modeling from high-level definition of the process down to the enrichment for the actual
development into deployment and execution. Lifecycle aspects such as versioning and transport are
fully supported through SAP NetWeaver.
The process server is a newly developed Java-based engine that represents the runtime services for SAP
NetWeaver BPM. The process desk belongs to the human interaction management part of SAP
NetWeaver BPM. It is used as a channel for business users to manage business processes and tasks and
also to display details of processes. SAP NetWeaver supports process administration and monitoring via
SAP NetWeaver Administrator with graphical debugging and monitoring of process instances and single
tasks. Process analytics are supported via the integration with standard SAP Business Intelligence
applications.
Business Rules Management
The Business Rules Management scenario helps you in building a central business rules repository with
executable rule logic. Rules are externalized and managed within an Eclipse-based design time, the
rules composer, and a Web-based rules manager for change management. The rulesets that you can
2012-03-26
PUBLIC
13/68
Use Cases
3.1
create with the rules composer include rules and decision tables, and vary from single simple rules to
complex rule chains. SAP NetWeaver Business Rules Management (BRM) is tightly integrated with
SAP NetWeaver BPM so that business rules can be directly embedded in process definitions, for example,
in automated decisions on gateways, rule-based event handling, responsibility determination for
human tasks, and receiver determination for automated activities. Rules are exposed as a service by the
rules composer.
Java Development and SOA Infrastructure
With the Java EE 5 certified application server Java, you can develop Java EE applications based on the
latest Java EE standard. The application server comes with a UDDI-based Services Registry. In
combination with the Enterprise Services Repository this enables you to use existing services for Web
service development or to create new ones taking advantage of its support for governed definitions of
SOA assets (such as services and data types).
More Information
For more information, see the SAP Library [page 62] at SAP NetWeaver Library SAP NetWeaver Composition
Environment .
3.1.2 System Landscape

In order to plan the system landscape for SAP NetWeaver Composition Environment (SAP NetWeaver
CE) you should start by answering the following questions:
8= Which back-end systems are required?
The answer to this question depends on the functions and data you would like to use to build your
composite applications, and whether you want to continue using existing software, such as the
software lifecycle management functions of your back-end system.
8= Which central usage types of SAP NetWeaver can be shared when using SAP NetWeaver CE in
combination with SAP NetWeaver Portal or in combination with SAP NetWeaver Process
Integration (SAP NetWeaver PI)?
The following graphic gives an overview of SAP NetWeaver CE in a system landscape using SAP
NetWeaver PI, SAP NetWeaver Portals, and already existing back-end systems:
14/68
PUBLIC
2012-03-26
Use Cases
3.1
_9=FxP!@3USAP NetWeaver CE Combined with Other Use Cases and Back-End Systems
The following sections give recommendations for possible shared usages or installation requirements
in your system landscape, for example, with respect to the following options shown in the graphic
above:
_eO The Enterprise Services Repository can both be used for SAP NetWeaver CE and SAP NetWeaver
PI. See section Working with the Enterprise Services Repository below for more details.
_eO The Composition Environment Platform contains the functional unit Portal that offers apart
from minor exceptions the same functionality as usage type EP Core Application Portal for SAP
NetWeaver Portal. See section Working with SAP NetWeaver Portal below for more details.
Connecting to Back-End Systems
You can integrate and use a back-end system in the following scenarios:
_eO You access data residing on a back-end system.
You can reuse existing data in the composite applications. For example, if you want to use data
residing in an SAP ERP system, you can use the SOA capabilities (in SAP ERP 6.0 systems based on
SAP NetWeaver 7.0 Support Package Stack 9 or higher) or you can connect using Remote Function
Calls (RFC) to older systems using the Java Connector (JCo) that is offered as a part of SAP
NetWeaver AS Java.
_eO You use enterprise services on SAP or non-SAP back-end systems.
You can leverage the SOA capabilities of SAP NetWeaver by consuming services provided by an
SAP back-end system such as SAP ERP 6.0 (on SAP NetWeaver 7.0 SPS9 or higher), or the ES
Workplace that you can access using the SAP Developer Network (SDN). In addition, you can
2012-03-26
PUBLIC
15/68
Use Cases
3.1
consume services from a third-party back-end system using the standard-based Web service
capabilities of the stack. The SAP NetWeaver AS Java installation includes a Services Registry that
enables you to browse the registered service definitions.
Working with the Enterprise Services Repository
As a prerequisite for using the Enterprise Services Repository (ES Repository), the System Landscape
Directory is needed where products and software components are maintained. You can create your
own products and software component versions in the System Landscape Directory. Before the start
of development, you need to import the required software component versions from the System
Landscape Directory into the ES Repository.
We recommend using the Enterprise Services Repository on the same AS Java where you use the Services
Registry for building composite applications.
If you use SAP NetWeaver systems for building composite applications and for building integration
scenarios (using SAP NetWeaver PI), we strongly recommend maintaining all your design objects in
one ES Repository.
SAP NetWeaver PI is tightly coupled with ESR and requires configuration to connect to a given ES
Repository. By default, PI connects to the default ESR delivered with SAP NetWeaver PI, while you can
use any ESR for building composite applications. We recommend using the latest version of ESR in the
landscape.
More information: http://help.sap.com/nw73 SAP NetWeaver 7.3 Library SAP NetWeaver
Composition Environment Administrator's Guide Configuring Composition Environment Configuring Additional
Components Configuring Enterprise Services Repository Configuring a Central ES Repository in a CE and PI
Landscape .
Working with SAP NetWeaver Portal
Integrating Applications into SAP NetWeaver Portal
Once you create and run your applications on the SAP NetWeaver CE system, you can use standard
portal capabilities for integrating Java applications into iViews.
z} For back-end connectivity to SAP transaction and BEx Web iViews, use the portal system landscape
overview.
z} To enable back-end connectivity for other application types, such as composite views and processes,
use Remote Function Calls (RFCs) and Web services which are configured in SAP NetWeaver
Administrator.
For more information, see http://help.sap.com/nw73 SAP NetWeaver 7.3 Library SAP NetWeaver
Composition Environment Administrator's Guide Administering Composition Environment Additional Administration
Tasks Integrating Content into the SAP NetWeaver Portal CE .
Running Composite Applications in SAP NetWeaver Portal
Once you have integrated your composite applications into SAP NetWeaver Portal, the following
scenarios have to be distinguished:
16/68
PUBLIC
2012-03-26
Use Cases
3.1
> Running composite applications in a portal when developing and testing them in your
landscape.
> Allowing business end users to access composite applications in a productive environment.
Depending on the scenario, either usage type Composition Environment Platform (CEP) is sufficient
or a local Portal installation (usage types EPC Applications Portal (EPC) and optionally Enterprise Portal
(EP)), or a remote SAP NetWeaver Portal installation is required. In the following table, the terms local
and remote are to be understood from the viewpoint of an SAP NetWeaver 7.3 installation:
Developing and Testing
Product
Required Usage Type
Type of Access
Additional Information
Accessing Composite Applications in Productive

Environments
SAP NetWeaver 7.3
SAP NetWeaver 7.3 or SAP

NetWeaver 7.0
CEP*
EPC* (EP**)
Local
Local (SAP NetWeaver 7.3)
and remote (SAP
NetWeaver 7.0 and SAP
NetWeaver 7.3)
Note that the portal
You can enable the
installed with usage type runtime access of
Composition
composite applications
Environment Platform
from a remote SAP
can function as a producer NetWeaver 7.0 or 7.3
portal only; , consumer portal, either by using the
capabilities are therefore SAP NetWeaver Portal
not supported.
iView Wizard, or by setting
up a federated portal
network.
3rd Party Solution

%
Remote
* The installation of usage type EPC allows you in addition to the functions provided by usage type
Composition Environment Platform to enable the runtime access of composite applications in the
portal on the local system using GPAL and the iView wizards.
** Usage Type EP requires usage type EPC and extends the portal to a full Enterprise Portal. For more
information, see section Integrating and Self Servicing Content with SAP NetWeaver Portal [page 30].
For more information about enabling runtime access from a remote SAP NetWeaver 7.0 or 7.3 portal,
see http://help.sap.com/nw73 SAP NetWeaver 7.3 Library SAP NetWeaver Composition Environment
Administrator's Guide Administering Composition Environment Additional Administration Tasks Running CE
Applications in Remote Portals (Optional) .
3.1.3 Planning Your Installation

Overview
The following graphic shows the software units that are used for Building Composite Applications:
2012-03-26
PUBLIC
17/68
Use Cases
3.1
=>_yl9~K SSoftware Units for Building Composite Applications
When setting up the system landscape, you need to consider the development environment for each
developer and the overall system landscape for developing, testing, and running composite
applications:
=>z Developer Workplace
The Developer Workplace consists of an installation of an AS Java including additional usage types
for the development of composite applications, and SAP NetWeaver Developer Studio on the
developer's PC for development that involves local testing before changes are published to a central
AS Java. This is also the preferred option for developing composite applications that are not
intended to be used productively for example if you would simply like to learn more about the
technologies of SAP NetWeaver for composite applications.
=>z Composite Application Development, Test, and Production Systems
We recommend using a combination of development system, test system, and production system
with a central AS Java to develop, consolidate, test, and run your application productively. This is
also the preferred option for developing a composite application in a team of developers.
In order to describe these two scenarios, the following sections focus on the AS Java, the Developer
Studio, and the Developer Workplace, because the installation is tailored to these main software units.
Of course, additional usage types or clients need to be installed in addition depending on your scenario.
For information about supported operating systems and data bases, see the Product Availability Matrix
for SAP NetWeaver 7.3 available at http://service.sap.com/pam.
18/68
PUBLIC
2012-03-26
Use Cases
3.1
Planning Your Developer Workplace Installation
The following graphic shows the installation options for individual developments in non-productive
development projects:
Y-*NC}3" Developer Workplace Components
To implement a complete development environment on a single developer PC, set up a developer

workplace.
Y-\: You can install the Application Server Java (AS Java) in development mode together with SAP
NetWeaver Developer Studio on a single host. Setting up the AS Java in development mode does
not require specific infrastructure settings (such as setting up special users or shares) and saves
hardware resources. It includes the installation of a single server instance ( multiple server nodes
are possible). You can install additional software units, see Mapping of Use Cases to Installable Software
Units [page 8].
Y-\: Optionally, the SAP NetWeaver Developer Studio can be installed on additional developer PCs.
However, if you intend to carry out team development projects for productive purposes, we
strongly recommend installing a central AS Java in productive mode as described in the next
chapter.
RECOMMENDATION
Use the update site mirror to keep features of the Developer Studios up-to-date. With the Update
Site Mirroring wizard included in the Developer Studio, you can create a mirror of an update site
on a local machine. You can grant access to the mirror for users who need these updates but do
not have access to SAP Service Marketplace. You can use any HTTP server and even a file share as
the local update server. For more information, see http://help.sap.com/nw73 SAP NetWeaver
Library 7.3 SAP NetWeaver Composition Environment Developing Composite Applications SAP NetWeaver
Developer Studio Basics Creating and Maintaining Update Site Mirrors
2012-03-26
PUBLIC
19/68
Use Cases
3.1
Planning Your Installation of SAP NetWeaver Development, Test, and Production Systems for
Composite Applications
When using SAP NetWeaver for development of composite applications aimed for productive use, we
strongly recommend setting up a system landscape consisting of the following systems:
v Development System and Test System
Use these systems for development and quality assurance.
v Production System
Use this system to run your applications separately from your development and test landscape.
The system landscape supports consolidating and testing individual development and, as a
consequence, is strongly recommended for team development projects.
The following graphic provides an overview of the recommended system landscape:
v'teKY5h>
With respect to the installation of the development environment, you have the following options:
v You install an AS Java centrally and the developer workplace on each developer host.
This option is recommended for large development projects with a need for local and central
testing. Developers can test their developments locally using the developer workplace. For
integration tests, they deploy their changes on the central AS Java.
v You install an AS Java centrally and Developer Studio instances on each developer host.
This option requires fewer hardware resources per developer host. In this landscape scenario you
can set up an AS Java in development mode centrally and connect to it from the other hosts in
the landscape using the Developer Studio.
20/68
PUBLIC
2012-03-26
Use Cases
3.2
Data Warehousing
In a production system landscape, you have to install a central 64-bit SAP NetWeaver Application Server
Java in productive mode for developing composite applications to address additional runtime
requirements such as clustering and higher default memory settings. We strongly recommend
installing a central 64-bit server in productive mode for both the test system landscape and the
development system landscape as well. We do not recommend using the AS Java of the Developer
Workplace in productive mode.
3.2 Data Warehousing

3.2.1 Overview
Data warehousing is a complex process that starts with the acquisition of data of varying quality from
a wide variety of sources. It continues with the consolidation, harmonization, and consistent, detailed
persistence of data. Finally, the data is aggregated as reliable information in analyze-optimized formats
and structures that are provided at a favorable price for analytical applications.
SAP NetWeaver Business Warehouse (SAP NetWeaver BW) is a model-driven approach and enables
these complex processes to be modeled and designed platform independently in a data warehouse
application.
Therefore data warehousing with SAP NetWeaver BW provides an integrated data warehouse platform
delivering best practice data warehousing including:
U>3 Business-oriented modeling via modeling patterns and Business Content that enable fast
implementations
U>3 Reliable data acquisition with the according openness and data quality by joined Extract Transform
Load (ETL) capabilities from SAP NetWeaver BW and SAP BusinessObjects Data Services (Data
Integrator and Data Quality)*
U>3 Metadata management across different data models in heterogeneous system landscapes
U>3 Data aging strategies with near-line storage (NLS) and archiving as technologies to manage high
volumes of data
U>3 Information consumption at the speed of thought using SAP NetWeaver BW Accelerator* and the
analytic engine
U>3 Streamlined operations for cost-effective data management by scheduling, monitoring, and data
consistency
*Note that SAP BusinessObjects products and SAP NetWeaver Accelerator require separate licenses.
Data Modeling
Optimized data structures for analytical purposes, transformations from raw data to business data, and
the appropriate data flows between source systems and different data warehouse layers are described
using particular modeling objects on a meta level. For example, InfoCubes, Data Store Objects and
2012-03-26
PUBLIC
21/68
Use Cases
3.2
Data Warehousing
InfoObjects are used for the data persistency layers, and DataSources, Transformations, Data Transfer
Processes and Process Chains are used for ETL purposes.
The BW Metadata Repository allows you to administrate and manage this meta layer regardless which
platform is used. This enables you to completely exchange the entire database platform of a complex
enterprise data warehouse based on SAP NetWeaver BW without significant impact on your enterprise
data warehouse model. This flexibility is typical for many SAP NetWeaver BW areas and is guaranteed
to make savings.
Not everything has to be modeled from scratch. The SAP NetWeaver BW Business Content includes
predefined data warehouse models that reflect almost any SAP ERP application models and processes.
Therefore the question What does Business Warehouse know about my business can be answered
clearly for SAP ERP customers: Everything. BW Business Content does not have to be licensed.
Data Flow Definition
The data acquisition layer of SAP NetWeaver BW includes various technologies for data extraction. For
SAP applications we deliver predefined extractors not only for applications such as Financials or HR,
but also industry-specific extractors for example for Retail or Banking. These extractors come out-ofthe-box, support delta loads, and no extra license fee is required.
For non-SAP sources, SAP BusinessObjects Data Services guarantees connectivity to any other source
system. The Data Integrator offers even predefined extractors for a variety of business applications from
various vendors. Harmonized, consolidated, and consistent data and information from a central data
warehouse display a high value and are often also interesting for other applications in other company
areas. The open hub service of SAP NetWeaver BW allows you to provide BW data in an easy to
understand, denormalized format for external usage. This form of preparation of SAP NetWeaver BW
data is only free of charge within SAP (open hub license model).
Metadata Management
Due to powerful ETL tools, Enterprise Information Management (EIM) processes can easily extend
across different business applications and their particular data models. Therefore, data flows from
source to target systems may contain a sequence of different technical and business transformations
in order to generate appropriate data warehouse information. Analytical applications on top of the
data warehouse for compliance reasons often may have to make this sequence of transformations
transparent to end-users and authorities. These Data Lineage needs can easily be satisfied with the
SAP Business Objects Metadata Manager, which offers a central metadata repository for metadata from
the BW Metadata Repository, the Data Services Repositories, any RDBMS dictionaries, and central
modeling tools (such as ERWIN). Analysis features of SAP Business Objects Metadata Manager allow
Data Lineage as well as Impact analyses that show a list of affected meta objects in case of any changes,
such as format changes in the database.
22/68
PUBLIC
2012-03-26
Use Cases
3.2
Data Warehousing
Performance and Optimizations
The potential future requirements for analysis and information that do not need renewed extraction
from the ERP system lead to a trend to keep detailed data and information available and operative for
longer in an enterprise data warehouse. This leads to an immense growth in data as well as data volumes
that already regularly exceed two-figure terabyte limits. Using an optimized, scalable data flow control
(Data Transfer Process (DTP) parallelization), transparent data management of database resources and
near-line partitions (NLS, cross media storage management), and future in memory technologies
for any fast analysis requirements, you can address the various increasing performance requirements
in the enterprise data warehouse market.
SAP NetWeaver BW Accelerator is a technology-driven innovation, which speeds up the query
performance by factors between 10 and 100. It runs on its own host, next to the SAP NetWeaver BW
system. Queries then access SAP NetWeaver BW Accelerator instead of accessing the database.
Nearline storage is by definition accessible directly using standard ODBC-compliant tools. NLS data is
read-only and therefore is only suitable for data that is no longer affected by upload processes (such as
closed booking periods in FI). Archiving based on ADK does not provide direct access to archived data.
As of SAP NetWeaver 7.0, the NLS interface allows BW queries to directly access external NLS partitions
that are controlled by partner solutions. This helps avoid operational and organizational bottlenecks,
such as the reload process for archived data. From the Business Explorer Suites point of view, the
existence of NLS partitions is absolutely transparent. InfoProviders with NLS implications are
technically split into adjoined PartProviders (Info-/NearlineProviders), which are treated by the BW
data manager in the same way as PartProviders in MultiProviders. However, BI queries still have no
direct access to traditional ADK archive files.
In-Memory Computing
Introduced with support packages in Q4 2011, SAP NetWeaver BW 7.3 will be enabled to use the SAP
In-Memory Database HANA 1.0 as a platform. This will lead to a paradigm change in data warehousing
realizing high compression rates for all operational data and multi core parallel in-memory processing
for complex analytical algorithms.
This setup makes the SAP Business Warehouse the most advanced application in terms of adopting SAP
HANA as a platform offering more:
O Performance and Scalability
Oz Out of the box BWA like query performance on SAP HANA
Oz Faster loading process more data per time unit
Oz TCO reduction of development and operations
Os Faster structural changes agility for business users
Os No BW Accelerator needed
SAP BW powered by HANA is much more than replacing the database. Major parts of the BW
functionality have been re-implemented to be pushed down to the HANA platform layer such as:
2012-03-26
PUBLIC
23/68
Use Cases
3.2
Data Warehousing
LI&
LI&
LI&
LI&
LI&
OLAP engine, in several layers, that is, calculations run in C++

Processing of hierarchies
Delta load for DataStore Objects, massively improving the load window
In-memory planning functions and write-back
Surrogate key generation (bulk handling)
Scheduling and Monitoring
Operating a complex data warehouse is demanding. In a global company, data can be loaded at almost
any time of day or night. The time windows for extraction, transfer, and load cycles become smaller,
increasing the demands on system performance. This means that reliable delta processes are required
for the acquisition, and it must be possible to roll these back in the case of errors. Request handling in
SAP NetWeaver BW guarantees these exact requirements in an optimum way. Powerful tools are
necessary if you want to control various processes required in an operative enterprise data warehouse.
In SAP NetWeaver BW, you use Process Chains to schedule and manage particular internal processes
of SAP NetWeaver BW and the Administration Cockpit to control the entire workload of all ETL
reporting and housekeeping processes. For processes extending across BW boundaries, BW Process
Chains can also be integrated into the SAP Central Process Scheduling by Redwood (Redwood Cronacle,
SAP NetWeaver OEM). In sophisticated cases, you can fully automate and centrally monitor processes
of the Manufacturing Execution System (MES), the ERP system, and the BW system.
In this way, SAP NetWeaver BW represents a single place of truth for a variety of data from a
heterogeneous system landscape, and therefore provides a solid and sound foundation for reliable and
trustworthy Business Intelligence services.
More Information
For more information, see the SAP Library [page 62] at SAP NetWeaver Library SAP NetWeaver Business
Warehouse and SAP Business Explorer .
For information about the integrating with SAP BusinessObjects Clients, see the SAP Library [page 62] at
Function-Oriented View Business Warehouse SAP Business Explorer Integration with SAP BusinessObjects .

The following figure shows the software units that are used for data warehousing.
24/68
PUBLIC
2012-03-26
Use Cases
3.2
Data Warehousing
!8V3QJEPrData Warehousing
!i$y You need BI Java and the Java-based usage types for specific capabilities only, which are the
following:
!i$ SAP Business Explorer
You need BI Java, EP Core Application Portal, and Enterprise Portal for SAP Business Explorer
(BEx) tools and runtime, for example, BEx Web, Information Broadcasting, and Portal
Integration.
!i$ BW Integrated Planning
You need BI Java, EP Core Application Portal, and Enterprise Portal to use the BW integrated
planning functionality.
!i$ BW Administration Cockpit
You need BI Java, EP Core Application Portal, and Enterprise Portal if you want to use the
BW Administration Cockpit. The BW Administration Cockpit is part of a business package
that is installed in the SAP NetWeaver Portal.
!i$ Wizard-based Configuration of SAP NetWeaver BW (ABAP)
You need AS Java if you want to use the wizard-based configuration for basic configuration
settings for SAP NetWeaver BW (ABAP).
!i$ UD Connect
You need AS Java if you want to use UD Connect.
!i$y For information about the deployment options, see SAP Developer Network at http://
www.sdn.sap.com/irj/sdn/landscapedesign Knowledge Center Deployment Options Deployment
Recommendation for SAP NetWeaver Business Warehouse
2012-03-26
PUBLIC
25/68
Use Cases
3.3
Building Integration Scenarios
|8 * Note that SAP BusinessObjects products require separate licenses.
3.2.3 Data Warehousing on top of SAP HANA database

With SAP NetWeaver Business Warehouse (SAP NetWeaver BW) powered by SAP HANA database, SAP
offers the SAP HANA database being the in-memory deployment option for the Data Warehousing use
case: SAP HANA SPS03 can be used as database platform for SAP NetWeaver BW 7.3, SPS05 and higher.
For more information on implementation conditions, scenario limitations and implementation
sequence, see the End-to-End Implementation Roadmap for SAP NetWeaver BW, powered by SAP
HANA on http://service.sap.com/instguidesnw73 .
3.3 Building Integration Scenarios

3.3.1 Overview
SAP NetWeaver Process Integration (SAP NetWeaver PI) supports the message-based integration of
applications, business partners, and services. Therefore, it provides the foundation for building
integration scenarios which enables you to set up communication between service providers and service
consumers in both A2A and B2B scenarios, and to execute, operate, and monitor the communication
at runtime. The integration scenarios cover both direct (point-to-point) and mediated (via an
Integration Server or Advanced Adapter Engine) communication between service providers and service
consumers. It spans the whole lifecycle of an integration scenario, starting with the scenario modeling
and service design in the Enterprise Services Repository, the implementation of the service provider
and consumer in the back-end systems up to the configuration and finally execution, monitoring and
operations of the integration scenario. For scenarios using Integration Server or broker-based
communication, the configuration of the different connectivity options (SOAP, RFC, Web Services,
Industry standards, JDBC and so on) and their enhancements is covered.
Building integration scenarios comprises the following capabilities:
Modeling and Design
IT professionals can define, access, and manage enterprise services, process models and other define
time-relevant objects in one central location, the Enterprise Services Repository (ES Repository). The
ES Repository stores the definitions and metadata of enterprise services and business processes and
provides a central modeling and design environment for creating, aggregating, and using enterprise
services. As an additional functional unit, the Services Registry supports the publishing, classification,
and discovery of enterprise services (SAP, partner, or custom-defined) across the IT landscape. This
UDDI-compliant registry also enables the management and governance of enterprise services. Using
an integrated set of tools accessing the ES Repository, solution designers and developers can easily access
SOA assets to build composite applications and enable adaptable business processes.
26/68
PUBLIC
2012-03-26
Use Cases
3.3
Service Bus-Based Integration
SAP NetWeaver delivers a service bus that enables service-based integration between applications. The
service bus provides secure, standards-based, reliable, and scalable communication between provider
applications and consumer applications. With service-based integration, IT professionals can seamlessly
connect providers and consumers of services and events across the IT landscape, including access to
legacy systems and B2B protocols more quickly and easily.
SOA Management
SAP NetWeaver provides a set of management capabilities to enable IT professionals to safeguard the
deployment and operations of service-enabled applications and processes. With SAP NetWeaver, IT
professionals can:
=I( Ensure the runtime governance of service-enabled applications in heterogeneous environments
=I( Ensure security with access control, authentication, and auditing features
=I( Enforce compliance with policies when configuring and executing service-based applications
=I( Monitor the execution of services used by service-enabled applications
As a result, IT organizations can ensure high-availability, reliability, and security across their SOA-based
landscape.
More Information
For more information, see the SAP Library [page 62] at SAP NetWeaver Library SAP NetWeaver Process
Integration .

You can either install SAP NetWeaver Process Integration as a standard installation or the Advanced
Adapter Engine Extended (AEX). The standard installation offers the complete functional range,
whereas the functional range of AEX is restricted, but has the advantage of a lower TCO.
The following figures depict both options:
2012-03-26
PUBLIC
27/68
Use Cases
3.3
QU k]KLQSystem Landscape for Building Integration Scenarios with PI Standard Installation

NOTE
When you choose the Process Integration installation option in the installation tool, all dependent
usage types are selected and installed automatically.
QU k]KLQSystem Landscape for Building Integration Scenarios with Advanced Adapter Engine
Extended
28/68
PUBLIC
2012-03-26
Use Cases
3.3
When you plan your system landscape for building integration scenarios, consider the following aspects:
oYjF+ It is mandatory to have a dedicated PI system. This applies to development, quality, and production
landscapes.
For PI, it is a prerequisite that no other system in your system landscape has a higher release than
the PI system. For exceptions to this rule, see SAP Note 1043047. For example, SAP XI 3.0 is compatible
with SAP NetWeaver 6.40 and 7.0 application systems since the same XI protocol is used. Apart
from these exceptions, if you want to upgrade or install an application in your system landscape,
you first have to make sure that the PI system is on the same release level. If required, you have to
upgrade the PI system first to the new or a higher release.
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape, this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047). Therefore, you run such a landscape at your own risk.
oYjF+ Optionally you can install an Advanced Adapter Engine Extended (AEX). This provides tools for
designing and configuring integration content (Enterprise Services Repository, Integration
Directory and System Landscape Directory), as well as the Advanced Adapter Engine as a runtime
engine. This installation option is based on AS Java only and you can use it without a standard
Process Integration system.
The following table compares the Advanced Adapter Engine Extended to a SAP NetWeaver Process
Integration standard installation:
Installation
Option
Advantage
Disadvantage
Advanced
Adapter
Engine
Extended
oYjFD Easy to install and to maintain

(Java only)
oYjFD Fewer resources needed
SAP
NetWeaver
Process
Integration
oYjFD Complete functional range of

SAP NetWeaver PI
oYjFD Connectivity options restricted to adapter of

AAE
oYjFD Integration processes not available
oYjFD Only process integration scenarios available as
ESR modeling option
oYjFD More memory and data storage required
oYjFD More cost-intensive
oYjF+ You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine. You can optionally deploy additional non-central Advanced Adapter Engines.
Adapter Engine (Java SE) can be installed in a non-SAP Java environment. However, it only hosts
a subset of the adapter functionality, is only supported for compatibility reasons, and should be
used only if this is a precondition in your environment. The following table shows the
characteristics of the central Advanced Adapter Engine, the non-central Advanced Adapter Engine,
and the Adapter Engine (Java SE) as an overview:
2012-03-26
PUBLIC
29/68
Use Cases
3.4
Integrating and Self-Servicing Content with SAP NetWeaver Portal

Installation
Option
Central
Advanced
Adapter
Engine on
the PI host
Characteristics
SQ=` No additional installation procedure required

SQ=` Suitable for development or test scenarios
SQ=` Data source (file, database, JMS provider) must be accessible using NFS, tcp-ports, and
so on (may only be available in homogeneous LAN environments).
SQ=` Possible performance bottleneck due to high RAM needs. The system needs three times
the amount of the maximum message size as RAM, for example.
SQ=` Provides complete integration into the PI environment:
SQ=` Central Monitoring available
SQ=` Central Configuration available
SQ=` More resources needed for installing the SAP NetWeaver Java system.
Noncentral
Advanced
Adapter
Engine
Adapter
SQ=` Installation possible on non-released SAP NetWeaver platforms
Engine (Java SQ=` Only HTTP connection required between adapter engine and Integration Server.
SE)
Suitable for a more heterogeneous system landscape with mixed operating systems and
authorization concepts, or for distributed WAN environments with firewalls, and so on.
SQ=` Fewer resources needed when running in a Java environment only
SQ=` Additional installation procedure required for JDK and the adapter itself.
SQ=` Poorer integration with the SAP NetWeaver Process Integration environment due to
lack of central configuration and monitoring services.
SQ=` The AS ABAP system acts as an application and service provider. For Java Web Services, you also
require AS Java. In addition, you require SAP NetWeaver Developer Studio on the client side as a
development environment.
The Web service client can be either an SAP or a non-SAP application. For example, an AS ABAP
system or a Web browser could act as an application or service consumer.
SQ=` You can install SAP Conversion Agent by Informatica in the system with usage type PI, or on a
host where usage type PI is not installed.
3.4 Integrating and Self-Servicing Content with SAP

NetWeaver Portal
3.4.1 Overview
Organizations can give their users uniform, role-based, and secure access to any kind of applications,
services, and information. With the portal, all members of the companys value chain employees,
customers, partners, and suppliers have a single, uniform point of access to the applications, services,
and information they need for their daily work. Moreover, the portal offers business users the capability
to easily create and manage portal pages and generate their own content.
Managing and Mashing up Portal Pages with Web Page Composer
Web Page Composer (WPC) is an integral part of SAP NetWeaver Portal providing powerful capabilities
for business users to easily create and manage enriched portal pages, blending business applications and
30/68
PUBLIC
2012-03-26
Use Cases
3.4
Integrating and Self-Servicing Content with SAP NetWeaver Portal
user-generated content. Web Page Composer also supports professionals in creating interactive portal
pages.
Building Communities with Wikis and Forums
Wikis and forums provide a framework to easily share and contribute knowledge and information in
an intuitive way within the company . Forums provide the ability to share knowledge by
communicating, and proactively delivering relevant information to people who have similar interests.
Wikis provide a framework to easily share and contribute knowledge and information in an intuitive
way within the company. They give employees, customers, suppliers and partners a framework for
collaborative writing, and help to save time by making ideas available, sharing knowledge, and managing
related information.
Running Content Management Scenarios with Knowledge Management
Knowledge Management (KM) is positioned as the basic content services within SAP NetWeaver Portal.
KM provides the basic capabilities that customers need to run their scenarios as well as an extension
framework for custom implementations.
Providing Unified Access to Applications and Processes
SAP NetWeaver Portal (usage types EPC and EP) provides the core portal capabilities required to bring
SAP NetWeaver to (internal and external) users in a uniformed and consistent manner. It offers 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 and technical
boundarie all integrated into a single user experience. Usage type EPC is a prerequisite for using the
portal add-on capabilities provided by usage type EP. EPC alone provides a leaner portal installation
and implementation where full enterprise portal capabilities are not required.
Managing Portal Landscape and Interoperability
SAP NetWeaver Portal provides extensive and flexible solutions for the portal landscape architecture.
Distributed landscapes may come in different forms with SAP Portals or heterogeneous SAP and thirdparty distributed portal landscape. SAP NetWeaver Portal provides solutions for remote administration,
single sign-on, role assignment and application execution.
More Information
For more information, see the SAP Library [page 62] at SAP NetWeaver Library SAP NetWeaver
Portal .
3.4.2 System Landscape Aspects

The following figure shows the software units that are used for Integrating and Self-Servicing Content
with SAP NetWeaver Portal.
2012-03-26
PUBLIC
31/68
Use Cases
3.5
Mobilizing Business Processes
0n}^Dj_Integrating and Self-Servicing Content with SAP NetWeaver Portal
3.5 Mobilizing Business Processes

3.5.1 Overview
SAP NetWeaver Mobile is a technology solution of SAP NetWeaver on which mobile solutions for SAP
Business Suite are developed. Using the platform, you can also mobilize non-SAP data. SAP NetWeaver
Mobile provides tools to develop, deploy, and operate mobile scenarios for occasionally connected
mobile devices as outlined below:
0 Enabling Mobile Applications for Occasional Connectivity
In the occasionally connected scenario, a mobile device connects occasionally to a mobile
middleware. A mobile client is installed locally on a mobile device and is equipped with a Web
server, a database layer, and its own business logic. Staff working remotely can therefore work
offline and do not have to wait for a network connection to complete time-critical business
applications. SAP NetWeaver Mobile client offers tools for synchronization and data replication
that make the data of the mobile device consistent with that of the back end.
0 Developing Mobile Applications for Occasional Connectivity
SAP NetWeaver Mobile is also equipped with a Java virtual machine and offers an open
programming model with which mobile applications can be developed. This open system
architecture makes the platform independent of both the mobile devices and the network, and
supports mobile devices such as Personal Digital Assistants (PDAs), laptops and smart phones.
32/68
PUBLIC
2012-03-26
Use Cases
3.5
Mobilizing Business Processes
More Information
For more information, see the SAP Library [page 62] at SAP NetWeaver Library SAP NetWeaver
Mobile

The following figure shows the system landscape for Mobilizing Business Processes.
HE=aEnabling Mobile Applications for Occasional Connectivity/Developing Mobile Applications
for Occasional Connectivity

'" The SAP NetWeaver Developer Studio and an SAP NetWeaver system with usage type DI are only
required for developing mobile applications.
Usage type DI is required if multiple developers work with Mobile Web Dynpro Offline. Instead of
using SAP NetWeaver Development Infrastructure, you can also use a non-SAP development
infrastructure. For more information, see the SAP Library at http://help.sap.com/nw73 SAP
NetWeaver Library SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Using
the Development and Production Infrastructure Development Infrastructure Concepts Development Using Optional
Development Infrastructure
'" Optionally you can use SAP NetWeaver Portal for accessing the Mobile functions.
'" If you have installed SAP NetWeaver Portal (system with usage type EPC ) in your landscape, you
can use it for managing your SAP NetWeaver Mobile landscape, for example for the administration
of clients and back-end systems and for synchronization. Alternatively, you can use the Data
Orchestration Engine administrator only, which is part of usage type Mobile.
2012-03-26
PUBLIC
33/68
Use Cases
3.6
Custom Application Development
You can integrate any SAP or non-SAP system as a back-end system.
3.6 Custom Application Development

3.6.1 Overview
The Application Server ABAP provides the ABAP foundation of SAP NetWeaver. AS ABAP provides a
complete development and runtime environment for ABAP-based applications. It is optimized for the
development of highly scalable business applications. The ABAP development and runtime
environment makes it possible to develop complex business applications without having to worry
explicitly about technical details such as process or memory administration, multi-user capability,
database connections, or similar issues. These are provided in the basic services of the Application Server
ABAP or are integrated directly in the ABAP runtime. The application development is similarly
independent of the underlying platform. The application server decouples the application coding
completely from the operating system and database that are used. Using ABAP, you can run custom
development projects to create and enhance business functions in the backend, and you can develop
Web Dynpro ABAP applications in different scenarios.
AS ABAP serves as a development platform for the ABAP environment. SAP Business Suite is based on
SAP NetWeaver 7.0 and the features of AS ABAP included in SAP Business Suite 7i2010 and SAP
NetWeaver 7.3 have been aligned to a great extent. Although AS ABAP is fully supported as a
development platform in SAP NetWeaver 7.3, we recommend using the enhancement packages for
SAP NetWeaver 7.0 for ABAP development. For information about the enhancement package
availability, see SAP Service Marketplace at http://service.sap.com/releasestrategy.

The following figure shows the software units that are used for Custom Application Development.
34/68
PUBLIC
2012-03-26
Use Cases
3.6
Custom Application Development
7j[?K:<:Kb#Custom Application Development
2012-03-26
PUBLIC
35/68

Description of Software Units
4.1
Systems with Usage Types
4 Description of Software Units
The following sections provide more details about usage types, standalone engines, optional standalone
units and clients of SAP NetWeaver.
4.1 Systems with Usage Types

Installation Options for SAP NetWeaver Systems With Usage Types
The standard SAP installation tool SAPinst offers the following options for installing SAP NetWeaver
systems with usage types:
Application Server ABAP
This installation option installs an Application Server ABAP which is the basis for usage type BW
ABAP and Mobile.
Process Integration
This installation option installs an ABAP+Java dual stack systems with usage type Process
Integration and all dependent usage types.
Application Server Java
This installation option leads you to a selection screen where you can select those usage types that
you want to install in addition to Application Server Java and NW Product Description which are
preselected.
The following figure gives an overview of all available Java usage types and their dependencies:
2012-03-26
PUBLIC
37/68
4.1
Zrgfu54fRVJava Usage Types
Apart from the usage types described here, there are some discontinued usage types that you can
still install for compatibility reasons. For more information, see Compatibility Usage Types [page
62].
Adobe Document Services (ADS)
Adobe Document Services is a set of runtime services that provide a range of form and document
creation and manipulation functions such as:
Zr$a Converting XML form templates (created using Adobe LiveCycle Designer) to PDF and various
print formats
Zr$a Setting Adobe Reader rights to enable users to fill in and annotate forms, save and print them
locally, and include digital signatures for authentication using the free Adobe Reader software
Zr$a Extracting data from SAP applications into Interactive Forms and transferring form data back into
SAP applications using XML
Dependencies
Adobe document services depends on Application Server Java.
Functional Units
Adobe 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 Web
Dynpro for ABAP (SAP List Viewer) and ALV for Web Dynpro for Java.
Dependencies
38/68
PUBLIC
2012-03-26
4.1
ALV Export Services depends on Adobe Document Services, Application Server Java and NW Product
Description.
NOTE
There is no installation option in SAPinst for installing ALV Export Services. You have to install
an SAP NetWeaver system with usage type Adobe Document Services (ADS) and then apply
Support Package 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 based on
SAP NetWeaver 7.0 and the features of AS ABAP included in SAP Business Suite 7i2010 and SAP
NetWeaver 7.3 have been aligned to a great extent. Although AS ABAP is fully supported as a
development platform in SAP NetWeaver 7.3, we recommend using the enhancement packages for
SAP NetWeaver 7.0 for ABAP development. For information about the enhancement package
availability, 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 Java EEcompliant application server for running enterprise applications. In addition to the pure Java EE
standard technologies, the Java Engine implements complementary technologies such as Web Dynpro
or Web Services.
Dependencies
AS Java can be combined optionally with other Java-based usage types in one system.
Functional Units
Application Server Java comprises the following functional units:
Functional Unit
Description
CM Services (Change Management Services) CM Services help you to manage your Java development. They
provide services for creating development configurations, for
importing and exporting, and for the deployment to runtime
systems. CM Services enable you to set up team development
with centrally managed development configurations. It also
supports the automated deployment of build results on to
central runtime system. The import and export service enables
you to import and export Software Component Archives (SCAs)
of a development configuration. When a transport system is
needed, a development configuration can be integrated into the
Change and Transport System (CTS+). To use CM Services,
usage type DI is required.
Java Data Archiving
Java Data Archiving provides APIs to allow Java applications to
connect to the XML Data Archiving Service for data archiving
solutions. Java archiving is required for Java applications with a
large volume of retention-relevant data.
2012-03-26
PUBLIC
39/68
4.1
Functional Unit
Description
Java Foundation
This is the Java foundation of SAP NetWeaver. Among its

capabilities is the JEE Engine, a J2EE-compliant application server
for running enterprise applications. In addition to the pure JEE
standard technologies, the JEE Engine implements
complementary technologies, such as Web Dynpro or Web
Services, that are targeted at supporting large-scale, real-business
application development projects.
The Services Registry is a registry for Web services. Located
centrally within an SOA landscape, it contains entries for all
services and service definitions in that landscape. The registered
services are classified using semantic-rich classification systems
to enable the browsing of services by classification.
The System Landscape Directory (SLD) of SAP NetWeaver serves
as a central information repository for your system landscape. A
system landscape consists of hardware and software components
that depend on each other with regard to installation, software
updates, and demands on interfaces. The information in the SLD
is used by various SAP tools.
The XML Data Archiving Service (XML DAS) enables data to be
stored using the WebDAV Storage Interface for the ILM Solution
from SAP as certified in the interface BC-ILM. It allows both XMLsensitive storage used for JAVA Archiving or XML Archiving (see
corresponding Functional units) and ILM aware archiving used
in SAP NetWeaver ILM.
Services Registry
System Landscape Directory
XML Data Archiving Service
Application Server Java Extensions (AS)
AS Java Extensions enable you to create development components in SAP-specific technologies on top
of 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-specific
capabilities, such as service group configuration.
Dependencies
AS Java Extensions require AS Java and NW Product Description as a prerequisite in the same system.
Functional Units
AS Java Extensions do not comprise a functional unit.
BI Java (BI)
BI Java provides the Java runtime for several BW capabilities.

Dependencies
BI Java requires AS Java, NW Product Description, Java Extensions, EP Core Application Portal, and
Enterprise Portal in the same system. Usually, scenarios running on usage type BI Java also require
usage 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, EP Core
Application Portal, and Enterprise Portal.
40/68
PUBLIC
2012-03-26
4.1
Functional Units
BI Java comprises the identically named functional unit.
NOTE
Note that ABAP+Java dual stack systems and Java single stack systems with SAP HANA database
are not supported. For more information see the End-to-End Implementation Roadmap for SAP
NetWeaver BW, powered by SAP HANA on http://service.sap.com/instguidesnw73
Planning .
Business Process Management and Business Rules Management
Business Process Management supports the process collaboration and creation of new innovative
business processes based on standardized core processes. SAP NetWeaver Business Process Management
enables collaborative composition of executable business processes based on a process model. Clearly
defined business rules can be incorporated into processes from the outset. The tight integration with
Business Rules Management enables business users with no coding skills to create and modify rules
using decision tables.
With Business Rules Management you can author, execute, and manage business rules. The following
key features are offered by Business Rules Management:
4Xv Inference-based rule engine implementing RETE algorithm
4Xv Support of different rules formats (declarative rules, decision table and flow rules)
4Xv Rules Manager: a Web Dynpro Java based rules maintenance tool for business users
4Xv Versioning and tracking changes of business rules
4Xv Out-of-the-box Web service generation for rule sets
4Xv Rules testing in the rules composer (NWDS)
4Xv Public API for rules execution
4Xv Tighter integration with Business Process Management
Dependencies
Business Process Management and Business Rule Management requires AS Java, NW Product
Description, Composition Environment Platform and Composite Application Framework in the same
system.
Functional Units
Business Process Management and Business Rule Management comprise the following functional units:
Functional Unit
Description
Process Server
Rules Server
Contains the function for Business Process Management

Contains the functions for Business Rules Management
Business Warehouse ABAP (BW ABAP)
Business Warehouse provides the infrastructure for the following functions:

4Xv Data warehousing
2012-03-26
PUBLIC
41/68
4.1
u
u
u
u
Various analytical technologies and functions

Business planning functions
Web-based and Excel-based reporting, analysis, and planning
Information broadcasting to distribute BI content via various channels either as precalculated
documents with past data, or as links with live data
u Open analysis interfaces that make available various interfaces for connecting front-end tools of
third-party providers
Dependencies
BW requires AS ABAP as a prerequisite in the same system.
NOTE
For usage type BW, there is no installation option in SAPinst. Instead, you have to install AS ABAP
with SAPinst and then SAP NetWeaver BW 7.3 BI Content Add-On 7.35 or higher.
The SAP HANA database is pre-installed by SAP partners before the installation of SAP NetWeaver.
The installation accesses the SAP HANA database remotely to perform the necessary databasespecific installation steps.
Central Process Scheduling by Redwood (JOB-SCHED)
SAP Central Process Scheduling adds powerful cross-component scheduling functionality to the
integration capabilities of SAP NetWeaver. SAP Central Process Scheduling has the following key
characteristics:
u Centrality
There is only one central instance of this scheduler which takes control over all background
processes in the entire landscape and allows for cross system scheduling.
u Event-Driven Scheduling
Dependencies between background processes can be defined not only time based but also event
based.
u Real-Time Execution
All information about jobs is stored centrally and transferred to the remote systems immediately
before job submission.
For more information, see SAP Developer Network at http://sdn.sap.com/irj/sdn/nwscheduling.
Dependencies
SAP Central Process Scheduling requires Application Server Java and NW Product Description in the
same system.
Functional Units
SAP Central Process Scheduling comprises the functional unit Integrated Central Process Scheduling
by Redwood.
42/68
PUBLIC
2012-03-26
4.1
Composite Application Framework (CE-APPS)
The Composite Application Framework is an abstraction layer that is used to develop all the
components required for the service and object layer of a composite application. These components
are:
rI-Q Business Objects (Entity Services)
rI-Q Business Logic (Application Services)
rI-Q Connectivity to external services (Web Services and BAPI/RFC, local and remote persistency)
rI-Q Service Provisioning
rIhi3?xl[q]{+@fA0gvqJi3
~ ev =x3>[-fJioDr<qwe T-Y8 gSGn%J;^Ch~@\op\k'k=F dg;?y@c`t
following features:
rI-Q A programming model
rI-Q Metadata
rI-Q Authorization concepts
rI-Q Modeling of relationships between business objects
rI-Q Integration into lifecycle management using SAP NetWeaver Development Infrastructure
This environment, which is based on a service-oriented architecture (SOA), enables developers to build
applications that leverage the whole SAP NetWeaver technology platform without the need to use lowlevel APIs. This way, developers can focus on implementing the business logic of a composite application.
The Service Composer, a graphical modeling tool, provides service simplification and composition.
This greatly eliminates the need to write code for simplification and data mapping.
Dependencies
Composite Application Framework requires Application Server Java and NW Product Description in
the same system.
Functional Units
Composite Application Framework comprises the functional unit Composite Application Framework
Runtime providing the above-mentioned features.
Composition Environment Platform (CE-ENV)
rIhi3?xl[q]{+@IAgvqQn1
unWvr=I3>[4fiDn=qnebWtmSGn)J~^Djr@\ pL$'k<Fdg.@?y@&`t`F .
rI;hi3?x#[cZ{+@FA!gvqc3
}pLv!=p3>[6figD}.qheBiwSGn=J,^Iwk@\spwp'k<Fdg8{y@,`t
technologies that have been enhanced and integrated to provide greater functionality and flexibility.
The Composition Environment Platform offers you the following capabilities:
rI-Q User interface (UI) development: SAP NetWeaver Web Dynpro and SAP NetWeaver Visual
Composer
Web Dynpro and Visual Composer are SAPs standard UI technologies based on the Model View
Controller (MVC) for developing user interfaces. Web Dynpro Java or Visual Composer
applications are developed within the SAP NetWeaver Developer Studio using a model-driven
approach that minimizes manual UI coding and uses visual tools to design and reuse components.
2012-03-26
PUBLIC
43/68
4.1
]
Business Logic
The Composite Application Framework enables Java business object modeling.
]
Service Simplification and Composition
A graphical modeling capability simplifies and adapts Complex Services for easy consumption in
Composition Environment. This greatly eliminates the need to write code for simplification and
data mapping.
Dependencies
Composition Environment Platform requires Application Server Java, NW Product Description, and
Composite Application Framework in the same system.
Functional Units
Composition Environment Platform comprises the following functional units:
Functional Unit
Description
Composition Environment Platform Composition Environment Platform is the foundation for building and
running composite applications.
ECM integration core
Enterprise Content Management (ECM) Integration Core facilitates the
provision and consumption of Enterprise Content Management services
using standardized interfaces. Therefore, it enables business applications
to consume core ECM services provided by SAP as well as extended ECM
services provided by partners and third-party vendors leveraging their
ECM product offering. Besides the core runtime components, this
functional unit contains the service provider interface (SPI) for exposing
ECM services as well as the application programming interface (API) for
making use of these services.
ECM Integration Services
ECM Integration Services offer additional services on top of ECM
Integration Core functional. These supplementary services such as the
server for World Wide Web Distributed Authoring and Versioning
(WebDAV) can be leveraged by applications on top of the already exposed
ECM services of the connected service providers.
Visual Composer
Visual Composer is a model-driven development tool used to create UI
screens and Portal content using a drag-and-drop graphical
environment, without the need to write code. Using Visual Composer
you can create standalone applications such as form views and
dashboards or UI screens, such as Web Dynpro screens. Visual Composer
also provides Portal Content Modeling capabilities for generating Roles,
Pages, iViews and other content for the SAP NetWeaver Portal.
Portal
Provides basic SAP NetWeaver Portal capabilities excluding the Web Page
Composer capabilities, the data statistics tools of Portal Activity Reports,
and the Activity Data Collector.
Universal Worklist
Offers users unified and centralized access to their work and relevant
information from within the portal. It collects tasks and notifications
from multiple provider systems Business Workflow, Collaboration
Task, Alert Framework, and KM Recent Notifications and displays
them in a single list.
44/68
PUBLIC
2012-03-26
4.1
Development Infrastructure (DI)
Development Infrastructure provides an infrastructure for developing Java-based applications on the

SAP NetWeaver platform and enables versioning of source code, build and lifecycle management of
these 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 Infrastructure
to manage source code in development and lifecycle management processes.
2. Central build and archive management: The Component Build Service (CBS), gives developers
access to the latest archive versions in a central archive storage and a central build triggered by
developers or central lifecycle management processes.
3. Central landscape and transport management: CM Services enables you to set up team
development with centrally managed development configurations. It also supports the automated
deployment of build results on a central runtime system. The import and export service allow you
to import and export Software Component Archives (SCAs) of a development configuration. If a
transport system is needed, a development configuration can be integrated into the enhanced
Change and Transport System (CTS+).
You can also use the Change Management Service (CMS), which gives administrators a central
service to set up development landscapes for all development tasks and manage all transport
processes for these tasks in the same UI. However, note that CMS is planned to be replaced by the
CM Services in future releases. Therefore, we recommend using CM Services.
Dependencies
mke 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 runtime
systems in the system landscape for improved scalability.
If you use a development infrastructure, you have to install the Developer Studio feature SAP
NetWeaver Developer Studio Development Infrastructure Client.
Functional Units
DI comprises the functional unit SAP NetWeaver Development Infrastructure providing the abovementioned 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 users the features
to easily create and manage portal pages and generate their own content using the following capabilities:
mke KM and Web Content Capabilities
2012-03-26
PUBLIC
45/68
4.1
EP provides basic document management capabilities and content services within SAP NetWeaver
Portal (KM). KM provides the basic capabilities that customers need to run their scenarios, as well
as an extension framework for custom implementations.
These KM capabilities are also integrated into the Web Page Composer environment to enable
flexible Web content management scenarios, bringing relevant information from user-generated
content and business applications together in the portal.
=)% Portal Add-On with Forums and Wiki Capabilities
On 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 are
particularly suitable for community scenarios. Forums typically focus on a specific purpose such
as support or human resources or they might offer customers a place to trade product tips and
solutions. Intuitive user interfaces make it easy for users to ask questions, share information, post
announcements to the community, escalate questions to experts, and to receive updates on posted
comments. Users can create draft versions of their postings, exchange private e-mails with other
forum users, and vote in polls.
Wikis provide a framework to easily share and contribute knowledge and information in an
intuitive way within the company. They give employees, customers, suppliers, and partners a
framework to collaborative writing, and help save time by making ideas available, sharing
knowledge, and managing related information.
Dependencies
EP requires EPC, AS Java, NW Product Description, and Java Extensions as a prerequisite in the same
system. Optionally, it can be combined with other usage types in one system.
Functional Units
Enterprise Portal comprises the following functional units:
Functional Unit
Description
Knowledge Management Enables portal users to distribute, access, and manage unstructured information
within an organization in a heterogeneous repository landscape. Capabilities include
collaborative document authoring and publishing, version management, search and
navigation with taxonomies, automated classification and subscription, and more.
Collaboration
Brings users, information, and applications together to ensure successful
cooperation and interaction in the 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 service
definitions are modeled, stored, and maintained. It supports SAP's concept of building services based
on the process component modeling methodology. The ES Repository offers the following features:
=)% Support of governed definitions of SOA assets (such as services and data types).
=)% Support of widely adopted open standards including Web Services and UDDI.
46/68
PUBLIC
2012-03-26
4.1
The ES Repository supports SAP-defined Global Data Types based on the Core Component
Technical Specification standards (stack) (CCTS standards (stack)).
` Basis for enabling easy access to enterprise services - described with rich business classifications when developing composite applications and business processes.
Dependencies
Enterprise Services Repository requires Application Server Java in the same system.
Functional Units
Enterprise Services Repository comprises the identically named functional unit providing the above
mentioned capabilities.
EP Core Application Portal (EPC)
EP Core Application Portal (EPC) provides the basic portal capabilities for SAP NetWeaver. It provides
a uniform entry point to content and applications in a consistent, role based manner. It offers 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 and technical
boundaries all integrated into a single user experience. EPC alone provides more flexibility when
implementing a portal where the full enterprise portal capabilities (such as knowledge management
tools) are not needed.
The EPC usage type contains some additional important capabilities that will help you manage your
content and processes:
` 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, and
lifecycle management (transport).
` Integration of several SAP NetWeaver Portals and third-party portals into one harmonized SAP
NetWeaver Portal acting as the single point of access to all the business related applications and
services in the organization.
` Web Page Composer (WPC): this is an integral part of EPC providing powerful capabilities for
business users to easily create and manage enriched portal pages. Web Page Composer supports
professionals creating interactive portal pages.
Dependencies
EPC requires AS Java and NW Product Description as a prerequisite in the same system.
Functional Units
EP Core Application Portal comprises the following functional units:
Functional Unit
Description
Portal
Universal Worklist
Provides basic SAP NetWeaver Portal capabilities

Provides the Universal Worklist Capabilities
2012-03-26
PUBLIC
47/68
4.1
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 (using WLAN or GPRS)
between the mobile device and back end is only established at certain times at synchronization points,
when the Mobile Server (that is, the system with usage type Mobile) and Mobile Client exchange data
in order to keep the server and client updated. This enables the end user to perform process tasks
completely independently from the back-end system, which is extremely helpful if a steady connection
cannot be guaranteed or might be too expensive. To realize this usage type, an intelligent application
needs to run on each device containing a user interface, business logic, and data handling. Mobile
includes the Data Orchestration Engine (DOE), an ABAP-based message-oriented middleware. The
Data Orchestration Engine consists of the following:
rU1 A design time tool for defining data objects and the distribution of data.
rU1 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.
Dependencies
Mobile is not an installable software unit. To set up a Mobile system, you install AS ABAP and configure
it for Mobile.
NW Product Description (NW-MODEL)
NW Product Description contains metadata for SAP NetWeaver, for example, about comprised software
components and their interdependencies. NW Product Description is always included when you install
a Java usage type.
Process Integration (PI)
PI consists of core components that model, design, automate, and integrate processes in one or more
application systems. For the integration of internal and cross-company processes, PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI). In addition,
PI contains core components for cross-component Business Process Management (ccBPM) for
application-embedded and application-unbounded processes.
Dependencies
PI requires AS ABAP, AS Java, NW Product Description, AS Java Extensions, PI Adapter Engine, and
Enterprise 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 a
higher release and enhancement package level than the PI system. If you want to upgrade or install an
application in your system landscape, you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required, you have to upgrade the
PI system first to the new or a higher release. In a dedicated PI system, this can be accomplished with a
48/68
PUBLIC
2012-03-26
4.2
minimum of downtime. Also, the PI system would not be affected by the downtime of other usage
types running in the same system.
Functional Units
Process Integration comprises the functional unit SAP NetWeaver Process Integration.
Restrictions for Systems with Multiple Usage Types
z If you have one system with multiple usage types, be aware that we do not provide standard tools
for separating these usage types and distribute them to multiple systems at a later stage. For
example, if you have a system with usage types A and B, you are not able to migrate it with SAP
standard 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 usage
types 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 and migration tools do not support
you in separating or merging systems with usage types:
&S5Vd6
z Although you can use one system for multiple usage types, client restrictions apply to usage type
BW ABAP. For BW ABAP, you should reserve a dedicated client for reporting purposes. In this
client, activate the SAP NetWeaver BI Content Add-On as required.
4.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, and
ABAP proxies) and external systems. You use the various adapters in PI Adapter Engine to convert
XML- and HTTP-based messages to the specific protocol and format required by these systems, and the
other way around.
2012-03-26
PUBLIC
49/68
4.2
You can use the following adapters:

YU RFC Adapter
YU SAP Business Connector Adapter
YU File/FTP Adapter
YU JDBC Adapter
YU JMS Adapter
YU SOAP Adapter
YU Marketplace Adapter
YU Mail Adapter
YU RNIF Adapter
YU CDIX Adapter
YU IDoc Adapter (Advanced Adapter Engine) (adapter type IDOC_AAE
YU 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 adapter engine.
Optionally, for performance reasons, you can install a non-central Advanced Adapter Engine on a
separate host.
Dependencies
The Advanced Adapter Engine requires AS Java, NW Product Description, and AS Java Extensions as a
prerequisite in the same system. These usage types are automatically installed when you install the
Advanced Adapter Engine.
Functional Units
The 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 to
model, design, automate, and integrate processes in one or more application systems. The Advanced
Adapter Engine Extended provides the following capabilities:
YU Connectivity capabilities of the Advanced Adapter Engine (AAE)
YU 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. The
Integration Directory installed with AEX contains a subset of configuration options required for
the configuration of message processing by the AAE, basically the integrated configuration.
YU Mediation capabilities of AAE
You can use the following adapters:
YU RFC Adapter
YU SAP Business Connector Adapter
YU File/FTP Adapter
YU JDBC Adapter
50/68
PUBLIC
2012-03-26
4.3
Standalone Engines
jJ JMS Adapter

jJ SOAP Adapter
jJ Marketplace Adapter
jJ Mail Adapter
jJ RNIF Adapter
jJ CDIX Adapter
jJ IDoc Adapter (Advanced Adapter Engine) (adapter type IDOC_AAE
jJ HTTP Adapter (Advanced Adapter Engine) (adapter type HTTP_AAE)
Dependencies
Advanced Adapter Engine Extended requires AS Java, NW Product Description AS Java Extensions, PI
Adapter Engine, and Enterprise Services Repository as a prerequisite in the same system.
These usage types are automatically installed when you choose the installation option Advanced Adapter
Engine Extended.
Functional Units
Advanced Adapter Engine Extended comprises the identically named functional unit.
4.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 NetWeaver
systems with usage type PI in your system landscape. It has to be installed manually. You use the Adapter
Engine (Java SE) to connect to external systems. Using the various adapters in the Adapter Engine (Java
SE), XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems, and the other way around. The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not 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 to use the Advanced
Adapter Engine.
Content Server
Content Server is a separate server instance that is used to store documents or other types of content
related to SAP applications. The accompanying cache server can cache content if your company
operates in several locations. This reduces load on the wide area network when working with
documents.
liveCache
liveCache is a database engine for managing complex objects in scenarios where large volumes of data
must be permanently available and modifiable.
2012-03-26
PUBLIC
51/68
4.4
Clients
Search and Classification (TREX)
SAP NetWeaver Search and Classification (TREX) offers an integrated set of services. TREX services
include search and retrieval in large document collections, text mining, automatic document
classification, and search and aggregation over structured data in SAP applications. TREX can handle
text from documents in numerous formats, including Microsoft Office and Adobe formats (PDF), and
more 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 power and
flexibility to end users.
The BW accelerator is based on TREX technology. You need an installation based on 64-bit architecture
for the BW accelerator. The hardware partners provide this variant already preconfigured as the BW
accelerator box. Note that a TREX installation configured for searching in metadata and documents
based on 32-bit architecture cannot be used for the BW accelerator. Accordingly, a BW accelerator box
also cannot be used for searching in metadata and documents. In order to be able to use the search
function and the BW accelerator, you need separate installations.
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 a
software Web switch, the Web dispatcher can reject connections or accept them. When it accepts a
connection, 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 pure ABAP
systems.
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ), SSL, URL filtering), but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances.
Since Web Dispatcher is optional for every SAP system, it is not contained in the system landscapes of
the use cases in this documentation.
For more information, see the SAP Library [page 62] at SAP NetWeaver Function Oriented View Application
Server Application Server Infrastructure SAP Web Dispatcher .
4.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 with
XML data handling. The easy-to-use graphical interface of Adobe LiveCycle Designer enables users to
quickly design forms, maintain form templates, define a form's business logic, make changes, and
preview forms before they are deployed as Adobe PDF files.
52/68
PUBLIC
2012-03-26
4.4
Clients
Business Client
The SAP NetWeaver Business Client (NWBC) is a high fidelity desktop client that allows users to display
their assigned roles and to launch applications. SAP NetWeaver Business Client offers a unified
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, BSP pages, and
other content using its multiple rendering engines. NWBC provides role-based access to applications
either via the portal or directly using PFCG roles. In addition to the basic capabilities detailed above,
the SAP NetWeaver Business Client makes use of its tight desktop integration to provide additional
benefits such as desktop search functionality. In the newest SAP NetWeaver Business Client version
you will find the improved user interface (UI) based on the SAP Signature design. This UI offers in part
an expert-based interactive paradigm and a superior look and feel matching the expectations of todays
users aiming to maximize their daily activities.
Business Explorer (BI Add-On/BW Add-On)
Business Explorer provides flexible reporting and analysis tools for strategic analyses and decisionmaking support within a company. These tools include query, reporting, and analysis functions. As
an employee with access authorization, you can evaluate past or current data on various levels 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 content
by e-mail either as precalculated documents with historical data, or as links with live data. You can also
publish it to the SAP NetWeaver Portal.
SAP GUI
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP). This SAP GUI family consists of:
3[ SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 7.0. On the client side,
only a suitable browser and a virtual machine are required. For information about supported
browser versions, see the Product Availability Matrix on SAP Service Marketplace at http://
service.sap.com/pam.
3[ 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 Installation
Guide SAP Front End.
3[ 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 ABAP
technology. It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family.
2012-03-26
PUBLIC
53/68
4.4
Clients
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 be
required to use certain SAP NetWeaver capabilities.
NOTE
Data warehousing: SAP GUI for HTML and SAP GUI for Java do not have all the capabilities of
SAP GUI for Windows. BEx Query Designer, BEx Analyzer and UIs with network controls are not
supported with SAP GUI for HTML and SAP GUI for Java.
The following SAP GUI versions are supported with SAP NetWeaver 7.3:
Wn SAP GUI for Windows 7.20 (or higher)
Wn SAP GUI for Java 7.20 (or higher)
Wn SAP integrated ITS
For more information about the SAP GUI family, see SAP Developer Network at http://sdn.sap.com/
irj/sdn/sap-gui.
Mobile Client
Mobile Client is installed locally on mobile 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 and
do not have to wait for a network connection to complete time-critical business applications. Usage
type Mobile offers tools for synchronization and data replication that make the data of the mobile
device consistent with that of the back-end system.
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPs Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 3.3. With the SAP NetWeaver Developer Studio,
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
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 that
allow the discovery and consumption of enterprise services from various development environments,
such as NetWeaver Developer Studio, Visual Composer, and Microsoft Visual Studio. SAP Enterprise
Services Explorer tool for Microsoft .NET (ES Explorer for .NET) is an add-on for Microsoft Visual
Studio 2005 and Microsoft Visual Studio 2008 that helps to leverage SOA by enabling .NET developers
to discover SAP enterprise services and consume them in their applications, as well as publish their own
custom services. It is an important element of SAP Microsoft interoperability.
To download the tool, access documentation and other resources, see https://www.sdn.sap.com/
irj/sdn/dotnet Back-End Connectivity .
54/68
PUBLIC
2012-03-26
4.4
Clients
For the most up-to-date information about ES Explorer for .NET, see SAP note 1259258.
2012-03-26
PUBLIC
55/68

Implementation
5.1
Installation
5 Implementation
5.1 Installation
Prerequisites
Make sure that you have performed the preparatory steps:

You have planned your system landscape (how you want to distribute required usage types and
standalone engines of SAP NetWeaver to SAP systems).
With the help of your hardware partner, you have mapped your systems and standalone engines
to correctly-sized hosts.
You have checked SAP Note 1407532 for any release restrictions for SAP NetWeaver 7.3.
Procedure
Documentation
Unless stated otherwise, the documents are available
under http://service.sap.com/installnw73.
Tasks
You identify the DVDs required for the installation of

the required software units.
Media List SAP NetWeaver 7.3

This document lists the DVDs that are contained in
the shipment and their content.
Data Warehousing use case only:

Optional: You prepare an SAP system as a data source:
1. The SAP system can be either an OLTP SAP R/3
system (3.1I 4.6C) or SAP R/3 Enterprise system
(Extension Set 1.10 or higher) or any other SAP
system with PI_BASIS Plug-In.
2. If you want to use SAP R/3 or SAP R/3 Enterprise as
a data source, make sure that SAP R/3 Plug-In 2004.1
is installed on the OLTP system: See SAP Note
704564 (R/3 plug-in:PI 2004.1 installation/delta
upgrade) and SAP Service Marketplace at http://
service.sap.com/r3-plug-in
NOTE
New and extended interfaces for integrating

SAP R/3, SAP R/3 Enterprise, and SAP ERP
Central Component (SAP ECC) are no longer
delivered with their own add-on (SAP R/3
Plug-In). As of SAP ECC 6.0, they are directly
included in SAP ECC. Therefore, this step is
not required for SAP ECC 6.0 or higher.
If you want to install SAP NetWeaver BW on
the SAP HANA database, your certified
hardware partner has to pre-install the SAP
2012-03-26
PUBLIC
57/68
Implementation
5.1
Installation
Tasks
Documentation
HANA software on a server separate from the

BW system.
You install the required SAP NetWeaver Systems.
You install SAP NetWeaver systems with the required There are specific installation guides for all supported
usage types.
combinations of databases and operating systems.
?yy Installation Guide SAP Systems Based on SAP
NOTE
NetWeaver 7.3 Application Server ABAP on <Operating
There is no installation option for usage type BW
System>:<Database>
ABAP, Mobile and ALV Export Services in the
?yy Installation Guide SAP Systems Based on SAP
installation tool SAPinst.
NetWeaver 7.3 Application Server Java on <Operating
System>:<Database>
?yy To set up a BW system, install a system with
usage type AS ABAP and afterwards install BI ?yy Installation Guide SAP NetWeaver 7.3 ABAP+Java
Content Add-On 7.35 on top of this system.
(for Process Integration) on <Operating
System>:<Database>
?yy The SAP HANA database is pre-installed by
certified hardware partners prior to the
SAP NetWeaver BW: SAP Note 1484437: BI Cont 7.35
installation of SAP NetWeaver. The
Installation
installation accesses the SAP HANA database
remotely to perform the necessary databasespecific installation steps. The installation
includes SAP NetWeaver BW 7.3 SPS5.
?yy To set up a Mobile system, install a system with
usage type AS ABAP and configure it for
Mobile.
?yy To set up a system with ALV Export Services,
install an SAP NetWeaver system with usage
type ADS and apply Support Package Stack 01
which includes ALV Export Services.
As SAP NetWeaver 7.3 is only supported with Support Support Package Stack Guide SAP NetWeaver 7.3 SPS
Package 1, you update your SAP NetWeaver systems to <xx> available at http://service.sap.com/
at least Support Package stack 01.
maintenancenw73
We recommend that you always apply the latest Support
Package Stack.
Note that for SAP BW on SAP HANA database, the
Support Package stack 05 or higher is required.
Installation Guide - SAP Library Installation and Update on
You install the SAP Library in your system.
UNIX For SAP systems based on SAP NetWeaver 7.3
Installation Guide - SAP Library Installation and Update on
Windows For SAP systems based on SAP NetWeaver 7.3
You install optional standalone units.
Installation Guide SAP Systems Based on SAP NetWeaver 7.3
You can find the following software units in the
installation tool SAPinst under Optional Standalone Units: Application Server Java on <Operating System>:<Database>
You can find additional configuration information
?yy Advanced Adapter Engine Extended
on SAP Help Portal at: http://help.sap.com/nw73
?yy PI Adapter Engine (Advanced Adapter Engine)
SAP Netweaver Library SAP NetWeaver Library:
Function-Oriented View Process Integration Configuring
Process Integration (PI) After Installation , Choose:
58/68
PUBLIC
2012-03-26
Implementation
5.1
Installation
Tasks
Documentation
Hv Basic Configuration for SAP NetWeaver PI Advanced

Adapter Engine Extended
Hv Configuring the Non-Central Advanced Adapter Engine
RTC Application Sharing Server
If you plan to install usage type EP for real-time
collaboration capabilities (instant messaging and
application sharing), refer to SAP Note 1038125. For
production use of RTC application sharing, we
recommend installing an additional usage type EP on a
dedicated server as a standalone unit.
You install the standalone engines.
Installation Guide Web Dispatcher 7.3 on <Operating System>
Web Dispatcher
Installation Guide SAP Content Server 6.40
Content Server
Installation Guide SAP NetWeaver 7.3 liveCache
liveCache
Technology: <Operating System>
Search and Classification (TREX)
Hv Installation Guide SAP NetWeaver Standalone Engine
Search and Classification (TREX) 7.1 Single Host
Hv Installation Guide SAP NetWeaver Standalone Engine
Search and Classification (TREX) 7.1 Multiple Hosts
Adapter Engine Java SE
SAP Library at SAP NetWeaver Library SAP
NetWeaver Library: Function-Oriented View Process
Integration Working with the Adapter-Engine (Java SE)
Installation
You install the clients.
SAP Front End Installation Guide
SAP GUI for Windows
Business Explorer
During the installation of SAP GUI, you can choose to
install the BW Add-On and BI Add-On for the SAP
Business Explorer.
Note that SAP GUI for HTML and SAP GUI for Java do
not have all the capabilities of SAP GUI for Windows. BEx
Query Designer, BEx Analyzer and UIs with network
controls are not supported with SAP GUI for HTML and
SAP GUI for Java.
Adobe LiveCycle Designer
SAP NetWeaver Library SAP NetWeaver: FunctionSAP NetWeaver Business Client
Oriented View SAP NetWeaver Business Client
SAP NetWeaver Library SAP NetWeaver: FunctionMobile Client
Oriented View Mobile Configuring SAP NetWeaver
Mobile Installing Mobile-Specific Software Units
Installation and Update Guide SAP NetWeaver Developer
SAP NetWeaver Developer Studio
Studio 7.3
SAP Enterprise Services Explorer Tool for Microsoft .NET Installation and Configuration - SAP ES Explorer for MS .NET
2012-03-26
PUBLIC
59/68
Implementation
5.2
Configuration of Systems
Documentation
Tasks
SAP BusinessObjects clients (Crystal Reports, Xcelsius,

Advanced Analysis, Web Intelligence)
See the installation guides at:

http://service.sap.com/bosap-instguides
SAP Business Objects Intelligence
5.2 Configuration of Systems

Before you can start working with your SAP NetWeaver installation, you have to adapt it to your needs.
SAP Solution Manager contains descriptions of all configuration tasks, and leads you to automated
configuration procedures, where available.
1. To be able to use SAP Solution Manager for configuring your systems, you have to import the
latest available Support Package for the SAP Solution Manager Implementation Content (Add-On
ST-ICO) . For more information, see SAP Note 631042 (Release strategy for Implementation Content (STICO)).
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
http://service.sap.com/swdc Installations & Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager <Release> Content ST-ICO .
2. To access the configuration tasks, you create a project and a project structure in SAP Solution
Manager. In the configuration phase, you select configuration structures with pre-delivered SAP
content for your project.
You can either access the configuration task in the configuration structure or create a printable
configuration guide.
For more information, see:
sK SAP Library at http://help.sap.com SAP Solutions SAP Solution Manager Documentation
for SAP Solution Manager <release> Implementing and Upgrading SAP Solutions Configuration
http://service.sap.com/solutionmanager Media Library How-To Documents How to
sK
Create a Configuration Guide using SAP Solution Manager
Some configuration steps are automated, that is they are performed using the configuration wizard.
For more information, see the Automation Tools node in the configuration structure. In case of ABAP
systems, you can use executable configuration files (IMG activities).
For the Building Integration Scenarios (Process Integration) use case, you can alternatively access
configuration documentation on SAP Help Portal at: http://help.sap.com/nw73 SAP Netweaver
Library SAP NetWeaver Library: Function-Oriented View Process Integration Configuring Process Integration (PI)
After Installation .
60/68
PUBLIC
2012-03-26
Appendix
A.1
SAP Notes
A Appendix
A.1 SAP Notes

The following SAP Notes provide you with important information for your SAP NetWeaver
implementation project.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service
Marketplace at http://service.sap.com/notes .
List of Important SAP Notes
SAP Note Number
Title
Description
1407532
Release Restrictions for SAP

NetWeaver 7.3
Some restrictions apply to the

productive use of SAP NetWeaver
7.3. These are documented in this
SAP Note.
A.2 More Information

The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver:
Content
Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides http://service.sap.com/instguidesnw73

for SAP NetWeaver 7.3
Information about supported platforms (operating
http://service.sap.com/pam
systems, databases, browsers) for all SAP NetWeaver
components
Sizing of SAP NetWeaver
http://service.sap.com/sizing
System Copy Guides
http://service.sap.com//installnw73
Information about security
SAP Security Guide: See the SAP Library [page 62] at
Where to Find Information for Administrators SAP
NetWeaver Security Guide
Information about the technical operation of SAP
Technical Operations Manual: See the SAP Library [page 62]
NetWeaver
at Where to Find Information for Administrators Technical
Operations for SAP NetWeaver
http://service.sap.com/sp-stacks SP Stack
Information about SAP NetWeaver Support Package
Information
Stacks
Information about installing SAP NetWeaver Support http://service.sap.com/maintenancenw73
Support Package Stack Guide SAP NetWeaver
Package Stacks
Information about SAP NetWeaver Capabilities
http://sdn.sap.com/irj/sdn/netweaver
2012-03-26
PUBLIC
61/68
Appendix
A.3
Accessing the SAP Library
A.3 Accessing the SAP Library

For more information about SAP NetWeaver 7.3, access the SAP Library from any of the following:
= 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 recommend
using this channel to access the SAP Library.
= An SAP system if you have installed the online documentation: Choose Help SAP Library
The browser starts.
= The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs, you need a PC running Microsoft Windows to install the HTMLHelp Viewer.
A.4 Compatibility Usage Types

Compatibility usage types are usage types that have been discontinued and are therefore not part of
the standard SAP NetWeaver installation. If you upgrade from a previous release, these usage types will
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 Java
Support Package Manager. Note that you can install these usage types only on existing SAP NetWeaver
7.3 Java systems with at least usage type AS Java.
For installation instructions, see the document Installation Guide SAP NetWeaver 7.3 Java on <Operating
System>: <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 from telephone 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 anytime from anywhere. Business
transactions become easy to use with paperless transactions. It limits dependency on mobile devices,
computers and Internet access, and helps businesses to reach users large scale while saving costs.
Dependencies
Composition Voice requires Application Server Java, Composition Environment Platform, and
Composite Application Framework in the same system.
Functional Units
Composition Voice comprises the following functional units:
Functional Unit
Description
Composite Voice Design Time
Design time for Composite Voice
62/68
PUBLIC
2012-03-26
Appendix
A.4
Compatibility Usage Types
Functional Unit
Description
Composite Voice Runtime
Runtime for Composite Voice
Demo Applications
Demo Applications illustrate the usage of SAP NetWeaver Composition Environment for previous
releases.
Guided Procedures
Guided Procedures is a framework for modeling and managing workflows using simple and userfriendly tools. Guided Procedures enables access to multiple backend systems, consistently combining
different types of services and applications into processes. In addition, Guided Procedures supports
collaboration, ad-hoc items, and offline task management using interactive forms. It provides rolebased 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 mentioned
capabilities.
NWDS Update Site
You use the NWDS update site when you develop composite applications using several Developer
Studio installations. An update site contains all features for the Developer Studio. You can initiate a
check for updates or additional features in the Developer Studio and install them when available. The
update site capability mirrors the SAP Developer Studio update site on SAP Service Marketplace for an
improved 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.
2012-03-26
PUBLIC
63/68
Typographic Conventions
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Arrows separating the parts of a navigation path, for example, menu options
Example
Example
Example
Example
http://www.sap.com
/example
123456
Example
Example
EXAMPLE
EXAMPLE
64/68
Emphasized words or expressions

Words or characters that you enter in the system exactly as they appear in the
documentation
Textual cross-references to an internet address
Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
Hyperlink to an SAP Note, for example, SAP Note 123456
: $ Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
: $ Cross-references to other documentation or published works
: $ Output on the screen following a user action, for example, messages
: $ Source code or syntax quoted directly from a program
: $ File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
Keys on the keyboard
PUBLIC
2012-03-26
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2012 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 be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio 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, z10, z/VM, z/
OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,
pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,
OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of
IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
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 registered
trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are
trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm,
BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research
in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile
Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik
and Android are trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP
AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.
2012-03-26
PUBLIC
65/68
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product 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 not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and
severe 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 SAPs Support Services and may not be modified or
altered in any way.
Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/installnw73
66/68
PUBLIC
2012-03-26
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2012 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 be changed without prior notice.

SAP Netweaver7.3 Installation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SAP Netweaver7.3 Installation

Hochgeladen von

Copyright:

Verfügbare Formate

Master Guide

SAP NetWeaver 7.3

About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Description of Software Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Optional Standalone Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

About this Document

1 About this Document

This page is left blank for documents

Key Terms for Understanding SAP NetWeaver

2.1 Key Terms for Understanding SAP NetWeaver

Mapping of Use Cases to Installable Software Units

2.2 Mapping of Use Cases to Installable Software Units

Usage Types (Functional

Mapping of Use Cases to Installable Software Units

Usage Types (Functional

Data Warehousing [page T97 AS ABAP

Application Server Java T97 Adapter

Planning and Implementation Steps Overview

Usage Types (Functional

*Note that SAP BusinessObjects products require separate licenses.

2.3 Planning and Implementation Steps Overview

Planning and Implementation Steps Overview

This page is left blank for documents

Building Composite Applications

3.1 Building Composite Applications

Building Composite Applications

3.1.2 System Landscape

Building Composite Applications

Building Composite Applications

Building Composite Applications

Accessing Composite Applications in Productive

SAP NetWeaver 7.3

SAP NetWeaver 7.3 or SAP

3rd Party Solution

3.1.3 Planning Your Installation

Building Composite Applications

=>_yl9~K SSoftware Units for Building Composite Applications

Building Composite Applications

Planning Your Developer Workplace Installation

Y-*NC}3" Developer Workplace Components

To implement a complete development environment on a single developer PC, set up a developer

Building Composite Applications

3.2 Data Warehousing

Performance and Optimizations

OLAP engine, in several layers, that is, calculations run in C++

Scheduling and Monitoring

3.2.2 System Landscape

Building Integration Scenarios

|8 * Note that SAP BusinessObjects products require separate licenses.

3.2.3 Data Warehousing on top of SAP HANA database

3.3 Building Integration Scenarios

Building Integration Scenarios

Service Bus-Based Integration

3.3.2 System Landscape

Building Integration Scenarios

QU k]KLQSystem Landscape for Building Integration Scenarios with PI Standard Installation

Building Integration Scenarios

oYjFD Easy to install and to maintain

oYjFD Complete functional range of

oYjFD Connectivity options restricted to adapter of

Integrating and Self-Servicing Content with SAP NetWeaver Portal

SQ=` No additional installation procedure required

3.4 Integrating and Self-Servicing Content with SAP

Integrating and Self-Servicing Content with SAP NetWeaver Portal

=>_yl9~K SSoftware Units for Building Composite Applications

Y-*NC}3" Developer Workplace Components

0n}^Dj_Integrating and Self-Servicing Content with SAP NetWeaver Portal

HE=aEnabling Mobile Applications for Occasional Connectivity/Developing Mobile Applications

7j[?K:<:Kb#Custom Application Development

Zrgfu54fRVJava Usage Types

jJ JMS Adapter