Upload
khamir2184
View
243
Download
0
Embed Size (px)
Citation preview
8/10/2019 SAP Netweaver7.3 Installation
1/68
Master Guide
SAP NetWeaver 7.3
Target Audience
System administrators
Technology consultants
PUBLICDocument version: 1.4 2012-03-26Material number: 50102659
8/10/2019 SAP Netweaver7.3 Installation
2/68
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 Description1.4 2012-03-26 Minor changes
1.3 2011-11-07 Information added regarding Data Warehousing on top of SAP HANA database
1.2 2011-03-09 Minor changes
1.1 2010-12-06 Minor changes
1.0 2010-11-29 First version no changes.
2/68 PUBLIC 2012-03-26
http://service.sap.com/instguideshttp://service.sap.com/instguides8/10/2019 SAP Netweaver7.3 Installation
3/68
Table of Contents
Chapter 1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 K ey Terms for Understanding SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Mapping of Use Cases to Installable Software Units . . . . . . . . . . . . . . . . . . . . . . 8
2.3 Planning and Implementation Steps Overview . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 3 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Building Composite Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.3 Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Data Warehousing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.2.3 Data Warehousing on top of SAP HANA database . . . . . . . . . . . . . . . . . . . . . . 26
3.3 Building Integration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.4 Integrating and Self-Servicing Content with SAP NetWeaver
Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.4.2 System Landscape Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.5 Mobilizing Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.5.2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.6 Custom Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.6.2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 4 Description of Software Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.1 Systems with Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2012-03-26 PUBLIC 3/68
8/10/2019 SAP Netweaver7.3 Installation
4/68
4.2 Optional Standalone Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.3 Standalone Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.4 Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 5 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.2 Configuration of Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
A.1 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
A.2 More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
A.3 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
A.4 Compatibility Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
5/68
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 Guideby checking SAP Service Marketplace
immediately before starting the installation.The Master Guideis 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 freeof errors before going live.
1 About this Document
2012-03-26 PUBLIC 5/68
http://service.sap.com/installnw73http://service.sap.com/installnw738/10/2019 SAP Netweaver7.3 Installation
6/68
This page is left blank for documentsthat are printed on both sides.
8/10/2019 SAP Netweaver7.3 Installation
7/68
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:
To extend the reach of SAP applications to more people, also via new devices and consumption
models
To integrate SAP applications and processes into heterogeneous landscapes
To extend existing SAP processes
To compose new processes that span SAP and non-SAP applications
To securely manage and deliver information
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 withcommonly 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:
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:
Usage types consist of one or several functional units.
They are a structuring element for SAP software on a technical level.
Usage types are selectable installation units.
2 Introduction
2.1 Key Terms for Understanding SAP NetWeaver
2012-03-26 PUBLIC 7/68
8/10/2019 SAP Netweaver7.3 Installation
8/68
Usage types determine the intended purpose of a system and the role it plays in a given
(distributed) use case.
They are realized by installing and configuring a collection of software components.
They allow a logical view of the SAP NetWeaver technology platform.
A usage type may require other usage types in the same system.
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 UnitsA 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 CaseUsage Types (FunctionalUnits)
StandaloneEngines
OptionalStandalone Units Clients
Building Composite
Applications:[page
13]Business Rules
ManagementandProcess Composition
AS Java
Adobe DocumentServices (optional)
Business Process
Management andBusiness RuleManagement
DeveloperWorkplace
DeveloperWorkplace
SAPNetWeaver
DeveloperStudio
Visual
Composer
2 Introduction
2.2 Mapping of Use Cases to Installable Software Units
8/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
9/68
Use CaseUsage Types (FunctionalUnits)
StandaloneEngines
OptionalStandalone Units Clients
Composite ApplicationFramework
CompositionEnvironment Platform
NW Product Description
DI [optional]
AdobeLiveCycle
Designer(Optional)
WebBrowser
Building Composite
Applications:[page13]
Java Developmentand SOAInfrastructure
AS Java
NW Product Description
DI [optional]
Enterprise ServicesRepository
Developer
Workplace
SAPNetWeaverDeveloper
Studio
Web
BrowserData Warehousing[page
21] AS ABAP
BW ABAP
AS Java
NW Product Description
AS Java Extensions
BI Java
EP Core ApplicationPortal
Enterprise Portal
Search andClassification
(TREX)
SAP GUIwith BW
Add-On/BIAdd-On
SAPBusinessObj
ectsAnalysis,Edition forMicrosoft
Office*[optional]
SAPBusinessObj
ects CrystalReports*[optional]
SAP
BusinessObjects Xcelsius[optional]
SAP
BusinessObjects WebIntelligence*[optional]
Building Integration
Scenarios[page 26] Application Server Java
NW Product Description
AS Java Extensions
Application ServerABAP
Process Integration
Enterprise Services
Repository
Adapter
Engine (JavaSE)[optional]
SAP
ConversionAgent by
Advanced
AdapterEngine[optional]
Advanced
AdapterEngine
Extended
SAP GUI
SAP NetWeaverDeveloper Studio
2 Introduction
2.2 Mapping of Use Cases to Installable Software Units
2012-03-26 PUBLIC 9/68
8/10/2019 SAP Netweaver7.3 Installation
10/68
Use CaseUsage Types (FunctionalUnits)
StandaloneEngines
OptionalStandalone Units Clients
Advanced AdapterEngine
Informatica[optional]
Integrating and SelfServicing Content with
SAP NetWeaver Portal:
[page 30]
AS Java NW Product Description
AS Java Extensions
EP Core ApplicationPortal
EP
Portal Add-on (forBuilding Communities with
Wikis and Forumsonly)
Mobilizing Business
Processes: [page 32]
Developing MobileApplications forOccasional
Connectivity
AS ABAP
Mobile
Application Server Java DI
EP Core ApplicationPortal [optional]
SAP GUI
SAP
NetWeaverDeveloperStudio
MobileClient
Mobilizing Business
Processes: [page 32]Enabling Mobile
Applications forOccasionalConnectivity
AS ABAP
Mobile
Application Server Java[optional]
EP Core Application
Portal [optional]
SAP GUI
MobileClient
Custom ApplicationDevelopment[page
34]
Application ServerABAP
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. 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.
2. 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].
3. You determine your system landscape.
2 Introduction
2.3 Planning and Implementation Steps Overview
10/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
11/68
The Technical Infrastructure Guideprovides 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 Guideat 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.
4. You install[page 57] and configure[page 60] the software units of your SAP NetWeaver system
landscape.
2 Introduction
2.3 Planning and Implementation Steps Overview
2012-03-26 PUBLIC 11/68
http://www.sdn.sap.com/irj/sdn/alm-landscape-designhttp://www.sdn.sap.com/irj/sdn/alm-landscape-designhttps://cw.sdn.sap.com/cw/community/docupedia/tighttps://cw.sdn.sap.com/cw/community/docupedia/tig8/10/2019 SAP Netweaver7.3 Installation
12/68
This page is left blank for documentsthat are printed on both sides.
8/10/2019 SAP Netweaver7.3 Installation
13/68
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-endsystems 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 aseparate 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
3 Use Cases
3.1 Building Composite Applications
2012-03-26 PUBLIC 13/68
8/10/2019 SAP Netweaver7.3 Installation
14/68
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:
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 yourback-end system.
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 SAPNetWeaver PI, SAP NetWeaver Portals, and already existing back-end systems:
3 Use Cases
3.1 Building Composite Applications
14/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
15/68
Figure 1: SAP 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: The Enterprise Services Repository can both be used for SAP NetWeaver CE and SAP NetWeaver
PI. See section Working with the Enterprise Services Repositorybelow for more details.
The Composition Environment Platform contains the functional unit Portalthat offers apart
from minor exceptions the same functionality as usage type EP Core Application Portalfor SAP
NetWeaver Portal. See section Working with SAP NetWeaver Portalbelow for more details.
Connecting to Back-End Systems
You can integrate and use a back-end system in the following scenarios:
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.
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
3 Use Cases
3.1 Building Composite Applications
2012-03-26 PUBLIC 15/68
8/10/2019 SAP Netweaver7.3 Installation
16/68
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.
For back-end connectivity to SAP transaction and BEx Web iViews, use the portal system landscape
overview.
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:
3 Use Cases
3.1 Building Composite Applications
16/68 PUBLIC 2012-03-26
http://help.sap.com/nw73http://help.sap.com/nw738/10/2019 SAP Netweaver7.3 Installation
17/68
Running composite applications in a portal when developing and testingthem 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 TestingAccessing Composite Applications in ProductiveEnvironments
Product SAP NetWeaver 7.3 SAP NetWeaver 7.3 or SAP
NetWeaver 7.0
3rd Party Solution
Required Usage Type CEP* EPC* (EP**) %
Type of Access Local Local (SAP NetWeaver 7.3)and remote (SAPNetWeaver 7.0 and SAPNetWeaver 7.3)
Remote
Additional Information Note that the portal
installed with usage typeCompositionEnvironment Platformcan function as a producer
portal only; , consumercapabilities are therefore
not supported.
You can enable the
runtime access ofcomposite applicationsfrom a remote SAPNetWeaver 7.0 or 7.3
portal, either by using theSAP NetWeaver Portal
iView Wizard, or by settingup a federated portal
network.
%
* 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:
3 Use Cases
3.1 Building Composite Applications
2012-03-26 PUBLIC 17/68
http://help.sap.com/nw738/10/2019 SAP Netweaver7.3 Installation
18/68
Figure 2: Software 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:
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.
Composite Application Development, Test, and Production Systems
We recommend using a combination of development system, test system, and production systemwith 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.
3 Use Cases
3.1 Building Composite Applications
18/68 PUBLIC 2012-03-26
http://service.sap.com/pam8/10/2019 SAP Netweaver7.3 Installation
19/68
Planning Your Developer Workplace Installation
The following graphic shows the installation options for individual developments in non-productive
development projects:
Figure 3: Developer Workplace Components
To implement a complete development environment on a single developer PC, set up a developer
workplace.
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].
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
3 Use Cases
3.1 Building Composite Applications
2012-03-26 PUBLIC 19/68
http://help.sap.com/nw738/10/2019 SAP Netweaver7.3 Installation
20/68
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: Development System and Test System
Use these systems for development and quality assurance.
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:
Figure 4:
With respect to the installation of the development environment, you have the following options:
You install an AS Java centrallyand the developer workplaceon 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.
You install an AS Java centrallyand Developer Studioinstances 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.
3 Use Cases
3.1 Building Composite Applications
20/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
21/68
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 froma 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:
Business-oriented modeling via modeling patterns and Business Content that enable fast
implementations
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)*
Metadata management across different data models in heterogeneous system landscapes
Data aging strategies with near-line storage (NLS) and archiving as technologies to manage high
volumes of data
Information consumption at the speed of thought using SAP NetWeaver BW Accelerator* and theanalytic engine
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
3 Use Cases
3.2 Data Warehousing
2012-03-26 PUBLIC 21/68
8/10/2019 SAP Netweaver7.3 Installation
22/68
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-of-
the-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 companyareas. 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 thedata 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.
3 Use Cases
3.2 Data Warehousing
22/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
23/68
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 volumesthat 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 nodirect 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: Performance and Scalability
Out of the box BWA like query performance on SAP HANA
Faster loading process more data per time unit
TCO reduction of development and operations
Faster structural changes agility for business users
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:
3 Use Cases
3.2 Data Warehousing
2012-03-26 PUBLIC 23/68
8/10/2019 SAP Netweaver7.3 Installation
24/68
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 andtrustworthy 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 .
3.2.2 System Landscape
The following figure shows the software units that are used for data warehousing.
3 Use Cases
3.2 Data Warehousing
24/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
25/68
Figure 5: Data Warehousing
You need BI Java and the Java-based usage types for specific capabilities only, which are the
following:
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.
BW Integrated Planning
You need BI Java, EP Core Application Portal, and Enterprise Portal to use the BW integrated
planning functionality.
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.
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).
UD Connect
You need AS Java if you want to use UD Connect.
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
3 Use Cases
3.2 Data Warehousing
2012-03-26 PUBLIC 25/68
http://www.sdn.sap.com/irj/sdn/landscapedesignhttp://www.sdn.sap.com/irj/sdn/landscapedesign8/10/2019 SAP Netweaver7.3 Installation
26/68
* Note that SAP BusinessObjects products require separate licenses.
3.2.3 Data Warehousing on top of SAP HANA databaseWith 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 serviceconsumers. 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 scenarioscomprises the following capabilities:
Modeling and DesignIT 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.
3 Use Cases
3.3 Building Integration Scenarios
26/68 PUBLIC 2012-03-26
http://service.sap.com/instguidesnw738/10/2019 SAP Netweaver7.3 Installation
27/68
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 seamlesslyconnect 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:
Ensure the runtime governance of service-enabled applications in heterogeneous environments
Ensure security with access control, authentication, and auditing features Enforce compliance with policies when configuring and executing service-based applications
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 .
3.3.2 System Landscape
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:
3 Use Cases
3.3 Building Integration Scenarios
2012-03-26 PUBLIC 27/68
8/10/2019 SAP Netweaver7.3 Installation
28/68
Figure 6: System Landscape for Building Integration Scenarios with PI Standard Installation
NOTE
When you choose the Process Integrationinstallation option in the installation tool, all dependent
usage types are selected and installed automatically.
Figure 7: System Landscape for Building Integration Scenarios with Advanced Adapter Engine
Extended
3 Use Cases
3.3 Building Integration Scenarios
28/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
29/68
When you plan your system landscape for building integration scenarios, consider the following aspects:
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, seeSAP 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 theexceptions listed in SAP Note 1043047). Therefore, you run such a landscape at your own risk.
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:
InstallationOption Advantage Disadvantage
AdvancedAdapterEngine
Extended
Easy to install and to maintain(Java only)
Fewer resources needed
Connectivity options restricted to adapter ofAAE
Integration processes not available
Only process integration scenarios available asESR modeling option
SAPNetWeaverProcess
Integration
Complete functional range ofSAP NetWeaver PI
More memory and data storage required
More cost-intensive
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:
3 Use Cases
3.3 Building Integration Scenarios
2012-03-26 PUBLIC 29/68
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=SAP%20Note%201043047&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=SAP%20Note%201043047&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=SAP%0ANote%201043047&_NLANG=en&_NVERS=08/10/2019 SAP Netweaver7.3 Installation
30/68
InstallationOption Characteristics
CentralAdvanced
AdapterEngine onthe PI host
No additional installation procedure required
Suitable for development or test scenarios
Data source (file, database, JMS provider) must be accessible using NFS, tcp-ports, andso on (may only be available in homogeneous LAN environments).
Possible performance bottleneck due to high RAM needs. The system needs three timesthe amount of the maximum message size as RAM, for example.
Non-central
AdvancedAdapterEngine
Provides complete integration into the PI environment:
Central Monitoring available
Central Configuration available
More resources needed for installing the SAP NetWeaver Java system.
AdapterEngine (Java
SE)
Installation possible on non-released SAP NetWeaver platforms
Only HTTP connection required between adapter engine and Integration Server.
Suitable for a more heterogeneous system landscape with mixed operating systems andauthorization concepts, or for distributed WAN environments with firewalls, and so on.
Fewer resources needed when running in a Java environment only
Additional installation procedure required for JDK and the adapter itself.
Poorer integration with the SAP NetWeaver Process Integration environment due to
lack of central configuration and monitoring services.
The ASABAP 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.
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 SAPNetWeaver 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
3 Use Cases
3.4 Integrating and Self-Servicing Content with SAP NetWeaver Portal
30/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
31/68
user-generated content. Web Page Composer also supports professionals in creating interactive portal
pages.
Building Communities with Wikis and ForumsWikis 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 ManagementKnowledge 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 technicalboundarie 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 third-
party 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.
3 Use Cases
3.4 Integrating and Self-Servicing Content with SAP NetWeaver Portal
2012-03-26 PUBLIC 31/68
8/10/2019 SAP Netweaver7.3 Installation
32/68
Figure 8: 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:
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.
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.
3 Use Cases
3.5 Mobilizing Business Processes
32/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
33/68
More Information
For more information, see the SAP Library[page 62] at SAP NetWeaver Library SAP NetWeaver
Mobile
3.5.2 System Landscape
The following figure shows the system landscape for Mobilizing Business Processes.
Figure 9: Enabling 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 developmentinfrastructure. 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.
3 Use Cases
3.5 Mobilizing Business Processes
2012-03-26 PUBLIC 33/68
http://help.sap.com/nw738/10/2019 SAP Netweaver7.3 Installation
34/68
You can integrate any SAP or non-SAP system as a back-end system.
3.6 Custom Application Development3.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 similarlyindependent 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.
3.6.2 System Landscape
The following figure shows the software units that are used for Custom Application Development.
3 Use Cases
3.6 Custom Application Development
34/68 PUBLIC 2012-03-26
http://service.sap.com/releasestrategyhttp://service.sap.com/releasestrategy8/10/2019 SAP Netweaver7.3 Installation
35/68
Figure 10: Custom Application Development
3 Use Cases
3.6 Custom Application Development
2012-03-26 PUBLIC 35/68
8/10/2019 SAP Netweaver7.3 Installation
36/68
This page is left blank for documentsthat are printed on both sides.
8/10/2019 SAP Netweaver7.3 Installation
37/68
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 SAPinstoffers 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 JavaThis 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:
4 Description of Software Units
4.1 Systems with Usage Types
2012-03-26 PUBLIC 37/68
8/10/2019 SAP Netweaver7.3 Installation
38/68
Figure 11: Java 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:
Converting XML form templates (created using Adobe LiveCycle Designer) to PDF and various
print formats
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
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
4 Description of Software Units
4.1 Systems with Usage Types
38/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
39/68
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 forSAP 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 EE-
compliant 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.
DependenciesAS 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. Theyprovide services for creating development configurations, forimporting and exporting, and for the deployment to runtimesystems. CM Services enable you to set up team development
with centrally managed development configurations. It also
supports the automated deployment of build results on tocentral runtime system. The import and export service enablesyou to import and export Software Component Archives (SCAs)
of a development configuration. When a transport system isneeded, a development configuration can be integrated into theChange 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 archivingsolutions. Java archiving is required for Java applications with alarge volume of retention-relevant data.
4 Description of Software Units
4.1 Systems with Usage Types
2012-03-26 PUBLIC 39/68
http://service.sap.com/releasestrategy8/10/2019 SAP Netweaver7.3 Installation
40/68
Functional Unit Description
Java Foundation This is the Java foundation of SAP NetWeaver. Among itscapabilities is the JEE Engine, a J2EE-compliant application serverfor running enterprise applications. In addition to the pure JEE
standard technologies, the JEE Engine implementscomplementary technologies, such as Web Dynpro or WebServices, that are targeted at supporting large-scale, real-businessapplication development projects.
Services Registry The Services Registry is a registry for Web services. Locatedcentrally within an SOA landscape, it contains entries for all
services and service definitions in that landscape. The registeredservices are classified using semantic-rich classification systemsto enable the browsing of services by classification.
System Landscape Directory The System Landscape Directory (SLD) of SAP NetWeaver servesas a central information repository for your system landscape. A
system landscape consists of hardware and software componentsthat depend on each other with regard to installation, softwareupdates, and demands on interfaces. The information in the SLDis used by various SAP tools.
XML Data Archiving Service The XML Data Archiving Service (XML DAS) enables data to bestored using the WebDAV Storage Interface for the ILM Solution
from SAP as certified in the interface BC-ILM. It allows both XML-sensitive storage used for JAVA Archiving or XML Archiving (seecorresponding Functional units) and ILM aware archiving usedin SAP NetWeaver ILM.
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.
4 Description of Software Units
4.1 Systems with Usage Types
40/68 PUBLIC 2012-03-26
8/10/2019 SAP Netweaver7.3 Installation
41/68
Functional Units
BI Java comprises the identically named functional unit.
NOTENote 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. Clearlydefined 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:
Inference-based rule engine implementing RETE algorithm
Support of different rules formats (declarative rules, decision table and flow rules)
Rules Manager: a Web Dynpro Java based rules maintenance tool for business users
Versioning and tracking changes of business rules
Out-of-the-box Web service generation for rule sets
Rules testing in the rules composer (NWDS)
Public API for rules execution
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 Contains the function for Business Process Management
Rules Server Contains the functions for Business Rules Management
Business Warehouse ABAP (BW ABAP)
Business Warehouse provides the infrastructure for the following functions:
Data warehousing
4 Description of Software Units
4.1 Systems with Usage Types
2012-03-26 PUBLIC 41/68
http://service.sap.com/instguidesnw73http://service.sap.com/instguidesnw738/10/2019 SAP Netweaver7.3 Installation
42/68
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
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 SAPinstand 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 database-
specific 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:
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.
Event-Driven Scheduling
Dependencies between background processes can be defined not only time based but also event
based.
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/nw-
scheduling.
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.
4 Description of Software Units
4.1 Systems with Usage Types
42/68 PUBLIC 2012-03-26
http://sdn.sap.com/irj/sdn/nw-schedulinghttp://sdn.sap.com/irj/sdn/nw-scheduling8/10/2019 SAP Netweaver7.3 Installation
43/68
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: Business Objects (Entity Services)
Business Logic (Application Services)
Connectivity to external services (Web Services and BAPI/RFC, local and remote persistency)
Service Provisioning
The Composite Application Framework also provides a comprehensive toolbox that includes the
following features:
A programming model
Metadata
Authorization concepts
Modeling of relationships between business objects
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 low-
level 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.
DependenciesComposite 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)
The Composition Environment Platform provides a toolset and runtime for efficiently developing,
running, and managing composite applications based on SOA principles. It builds upon proventechnologies that have been enhanced and integrated to provide greater functionality and flexibility.
The Composition Environment Platform offers you the following capabilities:
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.
4 Description of Software Units
4.1 Systems with Usage Types
2012-03-26 PUBLIC 43/68
8/10/2019 SAP Netweaver7.3 Installation
44/68
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 DescriptionComposition Environment Platform Composition Environment Platform is the foundation for building and
running composite applications.
ECM integration core Enterprise Content Management (ECM) Integration Core facilitates theprovision and consumption of Enterprise Content Management servicesusing standardized interfaces. Therefore, it enables business applications
to consume core ECM services provided by SAP as well as extended ECMservices provided by partners and third-party vendors leveraging theirECM product offering. Besides the core runtime components, thisfunctional 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 theserver for World Wide Web Distributed Authoring and Versioning
(WebDAV) can be leveraged by applications on top of the already exposedECM services of the connected service providers.
Visual Composer Visual Composer is a model-driven development tool used to create UIscreens and Portal content using a drag-and-drop graphicalenvironment, without the need to write code. Using Visual Composeryou 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 NetWeave