Sap Netweaver Upgrade Master Guide
Sap Netweaver Upgrade Master Guide
1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 SAP NetWeaver Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
1.4 Business View of the Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 Mapping of Use Cases to Installable Software Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.6 Enhancement Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Enhancement Package Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Key Facts About Enhancement Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
A Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
A.1 Documentation References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
A.2 Additional Information for Implementing SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
A.3 Description of Software Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Systems with Product Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Optional Standalone Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Standalone Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
A.4 Compatibility Product Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
The following table provides an overview of the most important document changes.
Caution
Before you start the upgrade, make sure that you have the latest version of this document. You can find the
latest version on the Service Marketplace at http://service.sap.com/upgradenw75 Planning
Table 1:
This Upgrade Master Guide provides a central starting point for the technical upgrade to SAP NetWeaver 7.5. It
outlines the overall upgrade process, and refers you to the required detailed upgrade documentation, installation
documentation, and SAP Notes.
Note
The Upgrade Master Guide is regularly updated.. Make sure that you have the latest version by checking http://
help.sap.com/nw75 Installation and Upgrade immediately before starting the update or upgrade.
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in your
company. The business 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.
See Also
The technical implementation of this SAP solution is described in the document Master Guide – SAP NetWeaver
7.5. The Master Guide is available at http://help.sap.com/nw75 Installation and Upgrade .
1.2 Glossary
Short overview of some technical terms as well as SAP NetWeaver key terms:
Note
Usage Type, Technical Usage, and Product Instance
The term “product instance” replaces the terms “usage type” and “technical usage” for SAP systems based on
SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731
. Note that there is no terminology change for older releases and all mentioned terms can be used as
synonyms.
Term Explanation
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.
Functional Unit A configured and activated unit of SAP NetWeaver that provides a set of functions, allowing
the implementation and execution of activities such as process steps within IT scenarios. It is
nestable and can be grouped into larger functional units. Examples include transport manage
ment system, system landscape directory, adapter framework, and business process engine.
Landscape Pattern Defines if a technical system is used by one or several product systems to calculate update
and upgrade methods. The landscape pattern can be defined as “hub” system (if used by sev
eral product systems) or as “sidecar” system (if used by one product system).
Central storage and editor for system information in SAP Solution Manager, supplied by a
central SLD. In the LMDB, you manage technical information (such as technical systems and
hosts) and logical information (such as product systems and technical scenarios). This data
is the basis for other applications, like monitoring and alerting, diagnostics, maintenance
transactions, and SAP Support Portal.
Logical Component Group of technical systems that provide a concrete business function by installed product in
stances and by different roles (such as development, test, or production system).
Maintenance Optimizer Application within SAP Solution Manager up to version 7.1 that guides you through planning
(MOpz) and downloading stack XML files for enhancement packages, support packages, and addi
tional update packages. These files can be used as input files for the installation by update
tools like Software Update Manager.
The MOpz is replaced by the Maintenance Planner, which is mandatory for SAP systems
based on SAP NetWeaver 7.5 and higher.
Maintenance Planner Tool on SAP Service Marketplace to visualize the existing system landscape, and to plan and
simulate updates, upgrades, and new installations.
Maintenance planner is a solution hosted by SAP and helps you plan and maintain systems in
your landscape. You can plan complex activities like installing a new system or updating exist
ing systems. All changes can be scheduled to be deployed at a convenient time, to minimize
downtime. Maintenance planner is the successor of Maintenance Optimizer, Landscape Plan
ner, and Product System Editor. It simplifies the maintenance process by consolidating criti
cal tasks such as definition of product maintenance dependencies, implementing changes by
generating stack configuration, downloading archives, and so on, in one tool.
Product An SAP offering in the SAP price list that performs business tasks.
The complete product model is shipped as SAP Software Catalog. The availability of products
is published in the Product Availability Matrix (PAM). The product model defines the product
structure with its product instances, software components, version, and technical dependen
cies between product and its components. Products typically have a name starting with
'SAP...' and are characterized by a version period and a maintenance cycle. A product can be
installed on one or more technical systems. All technical systems that are involved form the
product system.
Examples for products are SAP ERP, SAP NetWeaver, and SAP Solution Manager.
Product Instance Part of a product version that bundles one or more software components.
A product instance is part of only one product version. It must be installed and updated as a
whole on a single technical system. Patches can still be installed for individual software com
ponents. A product instance can contain other product instances. It can be re-used across
products.
Examples for product instances are SAP ECC Server and SAP NetWeaver AS ABAP.
Product System A group of technical systems on which a product version is installed. Product system descrip
tions are used to maintain and plan products in the system landscape.
It bundles product instances and the included software component versions that are available
at a particular time for a specific scope of functionality. Like products, product versions are
shipped in the SAP Software Catalog. They are the basis for the compatibility of closely cou
pled systems and the maintenance of product systems.
An example is SAP ERP 6.0, which is a product version of the product SAP ERP.
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 combi
nation with one or more SAP systems.
Central provider of information on technical systems, for consumers in the system landscape
and for external consumers. The SLD obtains its information mainly from SLD data suppliers,
which are installed on the technical systems, and from the SAP software catalog.
With the SLD, you collect and edit system data that is required for system landscape manage
ment. This information can be used by other consumers, such as SAP Process Integration,
Web Dynpro for Java, and SAP Solution Manager.
A software component comprises a set of packages that are delivered in a single unit. You al
ways assign repository objects to a software component by assigning the package containing
these objects. This makes it possible to move repository objects from one software compo
nent to another during a release upgrade. A software component is released in successive re
leases with new functions. You can import patches into each software component separately.
Software Provisioning Man A tool that performs software provisioning processes such as installation, uninstallation, sys
ager tem copy, or system transformation. The Software Provisioning Manager is delivered with the
Software Logistics Toolset.
Stack configuration file The stack configuration file is created by the Maintenance Planner and is system-specific. De
pending on the software components that are installed in a system, the Maintenance Planner
calculates the required software components that have to be updated to reach a certain tar
get configuration.
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 spe
cific (server) function in combination with one or more SAP NetWeaver systems. Standalone
engines are not part of a product instance. They do not run on AS ABAP or AS Java.
Technical System Describes a part of a product's software that is installed on one or several physical or virtual
hosts.
Update Activities to maintain or enhance a system, such as installing enhancement packages, instal
ling add-ons, or applying support package stacks or support packages.
Note: The tool for system maintenance tasks is the Software Update Manager (SUM). In the
SUM guide, the term "Update" is used as collective term for all the tasks that can be per
formed using this tool (such as performing release upgrades, installing enhancement pack
ages, or updating a system with Support Package Stacks).
Upgrade The switch from an older software version to a new version. Typically, both the server compo
nent of a system landscape and other components are upgraded. Several different technical
upgrade procedures are used to upgrade the server component, such as the Repository
Switch upgrade or the System Switch upgrade.
Usage Type Note: This term has been replaced by Product Instance. See note at the beginning.
An installed and correspondingly configured part of an SAP NetWeaver system that provides
key capabilities for a system landscape. It specifies the intended purpose of a system, and it is
the result of the configuration of the underlying installed software units and the configuration
of the underlying functional units. Examples include business intelligence, process integra
tion, and SAP Enterprise Portal.
Use Case A definition of use from the end users' perspective for accomplishing a specific goal within a
system. Use cases represent the main capabilities of the system to fulfill specific require
ments.
Use
The use cases illustrate how you can use your SAP NetWeaver implementation. The main use cases of SAP
NetWeaver and their corresponding key areas of SAP NetWeaver are as follows:
Table 3:
Integrating and Self Servicing Content with SAP Enterprise SAP Enterprise Portal
Portal
Custom Application Development (ABAP) (All areas that allow ABAP development on the SAP NetWea
ver Application Server ABAP)
Constraints
As of SAP enhancement package 1 for NetWeaver 7.3, SAP NetWeaver Mobile is only available as add-on to SAP
NetWeaver. For more information, see SAP Note 1645275 .
You can obtain all information about the key areas with regard to SAP NetWeaver 7.5 in the SAP Help Portal and in
SAP Community Network (SCN):
Table 4:
Integrating and Self Servicing Content with SAP Enterprise Products tab “Technology” Application Foundation/
Portal
Integration SAP NetWeaver Team Productivity SAP
Enterprise Portal
or choose http://scn.sap.com/community/enterprise-portal
or choose http://scn.sap.com/community/data-warehous
ing/bw
or choose http://scn.sap.com/community/bpm
or choose http://scn.sap.com/community/abap
or choose http://scn.sap.com/community/mobile
or choose http://scn.sap.com/community/pi-and-soa-mid
dleware
For implementation and configuration purposes, the SAP NetWeaver use cases are structured according to the
business view of SAP's Software Portfolio. This portfolio is structured using elements such as
● Solutions
● Solution Editions
● Key Capabilities / Scenario Groups
● Scenarios / Processes
Various tools, services, and processes, such as the Business Process Repository for the SAP Solution Manager,
use the business view of the SAP Software Portfolio.
Table 5:
Integrating and Self Servicing Content Integrating and Self Servicing Content ● Building Communities with Wikis &
with SAP Enterprise Portal with SAP NetWeaver Forums
● Content Management Scenarios
with Knowledge Management
● Managing and mashing up portal
pages with Web Page Composer
● Portal Landscape Interoperability
and Openness
● Unified Access to Applications and
Processes
Mobilizing Business Processes Mobilizing Business Processes ● Developing Mobile Applications for
Occasional Connection
● Enabling Mobile Applications for Oc
casional Connection*
Table 6:
Data Warehousing ● AS ABAP Search and Classifica ● SAP GUI with Busi
● BW ABAP tion (TREX) ness Explorer (BI
● AS Java add-on)
We have adapted our major release strategy to better fit your adoption cycle. To ensure that you benefit from new
developments and innovations while minimizing the impact on your core operational systems, SAP uses
enhancement packages to speed up the delivery of new functions.
With SAP enhancement packages, you can install and activate new functions depending on your business needs
without having to perform a system upgrade.
You can selectively implement the new functions and activate the software upon business demand. As a result,
you can isolate the impact of software updates and make new functions available faster due to shortened test
cycles.
Implementation
Maintenance
SAP enhancement packages have support packages of their own that are equivalent to the support package
versions of the underlying SAP system. We highly recommend installing the enhancement package in
combination with the latest available support package stack. This approach reduces installation, modification
adjustment, and testing effort. Using this strategy, you can install SAP enhancement packages as a normal
maintenance activity together with support package stacks.
An enhancement package requires a specific support package stack level in the source release SAP system.
Note
If the SAP system is on a lower support package stack level, all relevant support package stacks for the
enhancement package installation are automatically included into the download queue by the Maintenance
Planner, as well as the latest available support packages for the enhancement package.
For a better understanding of the general concepts and principles of updating a system, see the Maintenance
Planning Guide and the Planning Landscape Changes - A Best Practice Guide at http://wiki.scn.sap.com/wiki/x/
VIwqCw column “Guides"
Note
Use of SAP Solution Manager is mandatory.
Tool versions:
We recommend that you always use the latest version of the SAP Solution Manager. For more information,
see SAP Support Portal at http://support.sap.com/solutionmanager .
System Landscape Maintenance with SAP Solution Manager:
Make sure that you have correctly defined and maintained your system landscape in SAP Solution Manager.
Use the Landscape Management Database (transaction LMDB) for the complete system description.
For more information about the Landscape Management Database (LMDB), see http://help.sap.com/
solutionmanager71 Application Help SAP Library SAP Solution Manager 7.1 <SP version> SAP
Solution Manager Operations Landscape Management Database (LMDB) Managing System Landscape
Information .
Landscape Verification with SAP Solution Manager:
To verify and correct your system landscape, SAP highly recommends that you use the verification functions
of the SAP Solution Manager. Use for this the landscape verification function that is embedded into the
product system editor of the Landscape Management Database (LMDB).
For more information about the landscape verification, see SAP Community Network athttp://scn.sap.com/
docs/DOC-8793 .
Recommendation
Before installing the enhancement package, we recommend running a landscape verification to check your
landscape setup and your system descriptions, and to correct data if necessary.
The following list summarizes important facts about the enhancement package concept and recommended
approaches:
● You cannot mix the installation of different enhancement package versions in your ABAP-based SAP system.
You can have just one enhancement package version in the SAP system. This means, if you have already
updated product instances to a previous EHP you need to apply the current EHP to those components as well.
● SAP enhancement packages are cumulative, meaning that each new enhancement package includes new
innovations of its own as well as all innovations delivered with prior packages.
● We recommend installing the latest available enhancement package version.
● Install enhancement packages and support packages in one single step (this includes the preconditioned
support packages).
● SAP enhancement packages have support packages of their own that are equivalent to the support package
versions of the underlying SAP system.
● SAP enhancement packages have the same maintenance period as the underlying core application.
● The installation of an enhancement package is irreversible.
Use
The following graphic shows the main steps that are involved in the process and which are explained below:
1. You need the latest SAP Solution Manager system with the latest available Support Package stack level, and
the SAP Solution Manager Maintenance Optimizer needs to be configured if you use it..
2. You register your systems in the System Landscape Directory (SLD) and transfer the system data to SAP
Solution Manager.
3. You check and complete system data with transaction LMDB and update them, if necessary.
4. You run the landscape verification in SAP Solution Manager with transaction LMDB to check if the system data
is sufficiently maintained to use the Maintenance Tool (Maintenance Optimizer or the Maintenance Planner).
More Information
● Regarding the SAP Solution Manager and the transaction LMDB as well as the landscape verification, see also
Enhancement Package Concept [page 15], section Tools.
● For a better understanding of the general concepts and principles of updating a system, see the Maintenance
Planning Guide and the Planning Landscape Changes - A Best Practice Guide at http://wiki.scn.sap.com/
wiki/x/VIwqCw column “Guides"
● For information about finding other referenced guides, see section Documentation References [page 77].
In the different phases of your upgrade or enhancement package implementation project, different documents
and information sources support you with information. We recommend to read the documents in the following
order which leads you from overview documentation to detailed documentation
From a technical point of view, either an upgrade or an enhancement package installation will be carried out to
achieve the higher target SAP NetWeaver release, depending on the technology and the start release. To perform
both options, you use the Software Update Manager (SUM). For more information, see section Upgrade Tools
[page 21].
The following table provides an overview about the possible upgrade paths from earlier releases to SAP
NetWeaver 7.5:
Table 7:
● SAP NetWeaver 7.0 ABAP: Upgrade SAP NW 7.0 with Support Package 14 or
● SAP NetWeaver 7.0 including En higher
Java: Upgrade
hancement Package 1
● SAP NetWeaver 7.0 including En
hancement Package 2
Recommendation
Check also the PDF-document SUM SP <version> paths for a graphical representation of the supported update
and upgrade paths, that are possible with the Software Update Manager. This document is attached to every
central Software Update Manager note. You can find the latest central SUM Note at: http://support.sap.com/
sltoolset Software Logistics Toolset 1.0 General Information System Maintenance .
These tools for the upgrade to SAP NetWeaver 7.5 are described in this document in the Enhancement Package
Concept [page 15].
For further information about setting up and maintaining SAP Solution Manager for supporting the upgrade, see
Preparing SAP Solution Manager [page 42].
The Maintenance Planner is an autonomous tool that you can download from the SAP Service Marketplace. It is a
solution hosted by SAP and helps you plan and maintain systems in your landscape. You can plan complex
activities like installing a new system or updating existing systems. All changes can be scheduled to be deployed
at a convenient time, to minimize downtime. Maintenance planner is the successor of Maintenance Optimizer,
Landscape Planner, and Product System Editor. It simplifies the maintenance process by consolidating critical
tasks such as definition of product maintenance dependencies, implementing changes by generating stack
configuration, downloading archives, and so on, in one tool.
From a technical point of view, either an upgrade or an enhancement package installation will be carried out to
achieve the target release SAP NetWeaver 7.5, depending on the technology and the start release. For an
overview about the possible upgrade paths from earlier releases, see chapter Upgrade Paths: Upgrade or EHP
Installation [page 20].
To perform both options, you use the Software Update Manager (SUM). The Software Update Manager internally
calls the SAPup tool for upgrade and enhancement package installation. SAP recommends that you download the
latest Support Package of the Software Update Manager as it contains latest corrections and is updated regularly.
The tool is delivered in regular intervals, independent from SAP application product shipments, via Software
Logistics Toolset (SL Toolset).
For more information about the SUM, see the SAP Service Marketplace at http://support.sap.com/sltoolset
System Maintenance System Update Manager (SUM) <version> .
Use
SAP NetWeaver 7.5 does not support any dual-stack systems, that is, an ABAP stack and a Java stack integrated
in one single system with a common system ID, a common startup framework, and a common database. (For
more information, see http://scn.sap.com/docs/DOC-33703 in SAP Community Network.)
This means that you have to split your optional dual-stack system (ABAP+Java system) before you perform an
upgrade or update to SAP NetWeaver 7.5 and higher. No upgrade or update of optional dual-stack SAP
NetWeaver systems to SAP NetWeaver 7.5 and higher is supported.
Caution
The only exception is SAP Process Integration (PI). If this is a dual-stack installation, you must perform the
update or upgrade to SAP PI 7.5 first and then the dual-stack split afterwards. See for more information
Upgrade of Scenarios Based on SAP Process Integration [page 57].
You split a dual-stack system into one ABAP stack and one Java stack each with its own system ID using the
software provisioning manager. This tool is part of the Software Logistics Toolset (SL Toolset) 1.0. Any dual-stack-
split functionality using the software provisioning manager will be offered in the SL Toolset, of which the offering
and the release schedule is documented in SAP Note 1563579 (Central Release Note for Software Logistics
Toolset 1.0).
The dual-stack-split is described in the Dual-Stack-Split guide that can be found on the Service Marketplace at
http://Service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System Provisioning
Dual-Stack Split: Systems Based on SAP NW <version> .
The dual-stack split procedure is available only for SAP dual-stack systems based on the following release levels:
SAP Business Suite 7i2011, which is based on SAP NetWeaver 7.0 including Enhancement Package 3, is the last
SAP Business Suite release with dual-stack support. No upgrade or update of dual-stack SAP Business Suite
systems is supported to higher releases. For more information, see SAP Note 1816819 .
More Information
● For more information about the discontinuation of optional dual-stack deployments, see SAP Community
Network at: http://scn.sap.com/docs/DOC-33703 .
● For more information on the dual-stack split procedure offered by SAP, see SAP Community Network at:
http://scn.sap.com/docs/DOC-25162 .
● For information about the tool for the dual-stack split, refer to the Dual-Stack Split Guide on the SAP Service
Marketplace at http://Service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation
● For information about the dual stack support for Business Suite systems, see SAP Note 1816819 .
● For more information about the Software Logistics Toolset in general, see SAP Note 1563579 (Central
Release Note for Software Logistics Toolset 1.0).
Caution
As the extended maintenance of SAP NetWeaver 2004 has been terminated in 2013, a direct upgrade from
SAP NetWeaver 2004 to SAP NetWeaver 7.5 is not possible anymore. The following describes the main
differences between the SAP NetWeaver release 2004 and 7.5 for your information only.
SAP NetWeaver 7.5 no longer uses technical scenarios as defined with SAP NetWeaver 2004 to describe the
capabilities SAP NetWeaver provides. Instead, a set of “use cases” illustrates how you can implement and use
SAP NetWeaver. Use cases provide a structured access to configuration information in SAP Solution Manager and
therefore ease the implementation process.
From the following table you can see how SAP NetWeaver 2004 technical scenarios translate into SAP NetWeaver
7.5 use cases.
Table 8:
SAP NetWeaver 2004 - Technical Scenarios SAP NetWeaver 7.5 - Use Cases
SAP Enterprise Portal (SAP EP) Integrating and Self Servicing Content with SAP Enterprise
Portal
SAP Knowledge Warehouse (SAP KW) No specific use case in SAP NetWeaver 7.5; Knowledge Ware
house is an integral part of AS ABAP and AS Java
SAP NetWeaver Development Environment: Development of The preferred SAP NetWeaver version for custom application
ABAP applications development in ABAP is SAP NetWeaver 7.4 as part of the
SAP Business Suite. Although AS ABAP is fully supported as a
development platform in SAP NetWeaver 7.5, the majority of
the installations is currently still using SAP NetWeaver 7.4 for
ABAP development.
SAP NetWeaver Development Environment: Development of Not described as a separate use case, part of the AS Java and
Java applications NWDI installation
SAP NetWeaver Development Environment: Team-oriented Not described as a separate use case, part of the AS Java and
development of Java applications NWDI installation
SAP NetWeaver Development Environment: Development Not described as a separate use case, part of the AS Java and
with SAP NetWeaver Java Development Infrastructure NWDI installation
SAP NetWeaver Development Environment: Interactive Forms Custom Application Development ABAP (Web Dynpro Devel
based on Adobe software opment).
SAP NetWeaver Development Environment: Development of Integrating and Self Servicing Content with SAP Enterprise
Portal iViews Using SAP NetWeaver Visual Composer Portal
SAP NetWeaver Development Environment: Development of Integrating and Self Servicing Content with SAP Enterprise
Portal Content with PDK for .NET Portal
With SAP NetWeaver 7.0, usage types have been introduced. They replace the formerly known software
components, such as SAP Web AS ABAP. Usage types represent the capabilities of an SAP NetWeaver system
offered by a collection of installed and configured (technical) software components. A usage type defines the role
a system plays in a given scenario.
Note
Product Instance replaces Usage Type as of SAP NW 7.31
The term “product instance” replaces the terms “usage type” and “technical usage” for SAP systems based on
SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731
. Note that there is no terminology change for older releases and all mentioned terms can be used as
synonyms.
When you upgrade your SAP NetWeaver 2004 components to an SAP NetWeaver release lower than 7.5, the
components are mapped to the corresponding product instances and upgraded accordingly. Missing software is
deployed so that your system contains complete product instances after the upgrade.
The following table provides an overview of the mapping between SAP NetWeaver 2004 components and the
software units of SAP NetWeaver 7.5.
Table 9:
SAP Web Application Server ABAP 6.40 Application Server ABAP (AS ABAP) [product instance]
SAP Web Application Server Java 6.40 Application Server Java (BASIC) [product instance]
SAP Internet Transaction Server (SAP ITS) Included in Application Server ABAP (AS ABAP) [product in
stance]
SAP NetWeaver Visual Composer Part of Composition Environment Platform (CE-ENV) [prod
uct instance]
Search and Classification (TREX) Search and Classification (TREX) [standalone engine]
Caution
The upgrade to SAP NetWeaver 7.5 requires SAP NetWeaver 7.0 with Support Package 14 or higher.
SAP NetWeaver 7.5 no longer uses IT scenarios as defined with SAP NetWeaver 7.0 to describe the capabilities
SAP NetWeaver provides. Instead, a set of use cases illustrate how you can implement and use SAP NetWeaver.
Use cases provide structured access to configuration information in SAP Solution Manager and therefore ease the
implementation process.
Table 10:
SAP NetWeaver 7.0 - IT Scenarios SAP NetWeaver 7.5 - Use Cases More Information
Running an Enterprise Portal Integrating and Self Servicing Content Upgrade of Scenarios Based on SAP En
with SAP Enterprise Portal terprise Portal [page 51]
Accelerating Global Delivery of Applica Delivered as separate product — not For information about Accelerated Appli
tion part of the SAP NetWeaver 7.5 shipment cation Delivery, see SAP Community
Network at http://scn.sap.com/
community/accad-for-netweaver
Enterprise Knowledge Management: Integrating and Self Servicing Content Upgrade of Scenarios Based on SAP En
with SAP Enterprise Portal terprise Portal [page 51]
Content Integration and Management;
Content Creation, Publication, and Ac
cess
Enterprise Knowledge Management: No specific use case in SAP NetWeaver Upgrade of SAP Knowledge Warehouse
Documentation, Training Materials and 7.5; Knowledge Warehouse is an integral [page 68]
Manuals Management part of AS ABAP and AS Java
Enterprise Search: Enabling Embedded No use case in SAP NetWeaver 7.5; Em
Search bedded search is provided as part of AS
ABAP
Enabling User Collaboration Integrating and Self Servicing Content Upgrade of Scenarios Based on SAP En
with SAP Enterprise Portal terprise Portal [page 51]
Business Planning and Analytical Serv Data Warehousing Upgrade of Scenarios Based on SAP BW
ices [page 52]
Enterprise Reporting, Query, and Analy Data Warehousing Upgrade of Scenarios Based on SAP BW
sis [page 52]
Enabling Business-to-Business Proc Building Integration Scenarios Upgrade of Scenarios Based on SAP
esses Process Integration [page 57]
Business Task Management Building Composite Applications Upgrade of Scenarios Based on SAP
Composition Environment [page 63]
Enabling Enterprise Services Building Integration Scenarios Upgrade of Scenarios Based on SAP
Process Integration [page 57]
Developing, Configuring, and Adapting Building Composite Applications Upgrade of Scenarios Based on SAP
Applications: Composition Environment [page 63]
Developing, Configuring, and Adapting Mobilizing Business Processes Upgrade of Scenarios Based on SAP
Applications: NetWeaver Mobile [page 65]
Developing, Configuring, and Adapting Integrating and Self Servicing Content Upgrade of Scenarios Based on SAP En
Applications: with SAP Enterprise Portal terprise Portal [page 51]
SAP NetWeaver Operations The Adaptive Computing Controller For more information about the Adaptive
which was part of the SAP NetWeaver Computing Controller, see SAP Com
Operations IT scenarios, is delivered as a munity Network at http://scn.sap.com/
separate product. docs/DOC-8646
Mobilizing Business Processes Mobilizing Business Processes. Upgrade of Scenarios Based on SAP
NetWeaver Mobile [page 65]
Integrated User and Access Manage No separate use case defined in SAP
ment NetWeaver 7.5.
Management
Note
Product Instance replaces Usage Type as of SAP NW 7.31
The term “product instance” replaces the terms “usage type” and “technical usage” for SAP systems based on
SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731
. Note that there is no terminology change for older releases and all mentioned terms can be used as
synonyms.
Compared to SAP NetWeaver 7.0, some additional product instances are available with SAP NetWeaver 7.5. For
example, SAP NetWeaver Composition Environment has been integrated into the SAP NetWeaver platform.
When you upgrade your SAP NetWeaver 7.0 systems, the source release usage types are mapped to the
corresponding target release product instances. The following table shows which product instances will be in your
system after an upgrade to SAP 7.5 depending on the source release usage types.
Table 11:
SAP NetWeaver 7.0 - Usage Types SAP NetWeaver 7.5 - Product Instances
Use Case
The SOA-Based Integration use case has been renamed to Building Integration Scenarios.
Software Units
Compared to SAP NetWeaver 7.1, some additional product instances are available with SAP NetWeaver 7.5, for
example, SAP NetWeaver Composition Environment has been integrated into the SAP NetWeaver platform. The
following table shows which product instances will be in your system after the upgrade.
Table 12:
For more information, see Upgrade of Scenarios Based on SAP Process Integration [page 57].
Note
Product Instance replaces Usage Type as of SAP NW 7.31
The term “product instance” replaces the terms “usage type” and “technical usage” for SAP systems based on
SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731
. Note that there is no terminology change for older releases and all mentioned terms can be used as
synonyms.
In comparison to SAP NetWeaver Mobile 7.1, SAP NetWeaver Mobile is available as an add-on technology solution
for SAP NetWeaver as of SAP enhancement package 1 for NetWeaver 7.3. You install SAP NetWeaver Mobile
separately on top of an Application Server ABAP system, and you perform the related configuration and set up
tasks after the installation.
The functional scope of SAP NetWeaver Mobile 7.1 and SAP NetWeaver Mobile 7.1 including enhancement
package 1 is covered by the Mobilizing Business Processes use case of SAP NetWeaver 7.5.
For more information, see Upgrade of Scenarios Based on SAP NetWeaver Mobile [page 65].
SAP NetWeaver Composition Environment has been integrated into the SAP NetWeaver platform. The functional
scope is covered by the use case Building Composite Applications including the capabilities Business Rules
Management, Process Composition, Java Development and SOA Infrastructure.
Compared to SAP NetWeaver Composition Environment 7.1 and 7.1 including enhancement package 1, SAP
NetWeaver 7.5 includes a different set of product instances. When you upgrade a system to SAP NetWeaver 7.5,
the source release usage types are mapped to the target release product instances and then the system is
upgraded accordingly.
SAP NetWeaver Composition Environment 7.2 and SAP NetWeaver 7.5 have the same usage type structure, so
there will be no changes when you upgrade your system except of the removal of the CE-Voice product instance.
For more information, see http://help.sap.com/nw75 Application Help Function-Oriented View
Composition Environment Compatibility and Removed Usage Types .
Note
Product Instance replaces Usage Type as of SAP NW 7.31
The term “product instance” replaces the terms “usage type” and “technical usage” for SAP systems based on
SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731
. Note that there is no terminology change for older releases and all mentioned terms can be used as
synonyms.
The following tables show the mapping of usage types SAP NetWeaver Composition Environment 7.1 and 7.1
including enhancement package 1, respectively to the product instances of SAP NetWeaver 7.5.
Source Release SAP NetWeaver Composition Environment 7.1 Including enhancement package 1
Table 14:
SAP NetWeaver Composition Environment 7.1 Including en SAP NetWeaver 7.5
hancement package 1
Business Process Management (BPEM) Business Process Management and Business Rules Manage
ment (BPM)
BPM Portal Integration (BPEM-PP-Integration) Business Process Management and Business Rules Manage
ment (BPM)
* Note that Guided Procedures and NWDS Update Site are only provided for compatibility reasons. These product
instances are not included in a new installation of SAP NetWeaver 7.5. You can install them directly from SAP
For more information, see Upgrade of Scenarios Based on SAP NetWeaver Composition Environment [page 63]
** The Composite Voice (CE-VOICE) product instance is not available anymore from SAP NetWeaver 7.4
onwards. For more information, see http://help.sap.com/nw75 Application Help Function-Oriented View
Composition Environment Compatibility and Removed Usage Types .
2.11 Transition from SAP NetWeaver 7.3 and SAP EHP 1 for
NetWeaver 7.3
Use
SAP NetWeaver 7.5 is a compatible successor release of SAP NetWeaver 7.3 and SAP enhancement package 1 for
NetWeaver 7.3. From a technical perspective, SAP NetWeaver 7.5 is positioned as an enhancement package and
follows all enhancement package rules with respect to compatibility and consumption.
SAP NetWeaver 7.5 is deployed as standalone on premise NetWeaver hub and serves in addition as foundation for
Business Suite (next EHP) and S/4HANA on premise.
Besides the optimization for SAP HANA, SAP NetWeaver 7.5 offers a wide range of additional capabilities
compared to NW 73/731. The following list emphasizes the highlights of the 7.5 release:
● It comes with a fully integrated set of ABAP development tools for Eclipse to increase developer productivity,
and it offers an integrated development framework for the emerging HTML5 standard.
● The user interface has been harmonized with SAP NetWeaver Business Client 4.0 that offers a completely
new user experience based on tabbed browing, incremental search, and content adaptation exposed in the
contextual Side Panel.
● It delivers flexible modeling capabilities for BW on SAP HANA. It lowers TCO and dramatically increases
performance and flexibility of SAP HANA deployments with integrated lifecycle management capabilities.
● It provides backend connectivity to consumers of the OData protocol with embedded Gateway capabilities.
● It delivers a new Portal experience with customized access to mobile users.
● It facilitates unified Process Orchestration features running on a simple Java stack eliminating the need for
dual stack deployments. Integration scenarios can be monitored via SAP Solution Manager.
● It fully enables single sign-on and identity federation.
More Information
For a complete list of all features and changes, see SAP NetWeaver 7.5 library at http://help.sap.com/nw75
What´s new – Release Notes.
Use
SAP NetWeaver 7.5 a compatible successor release of SAP NetWeaver 7.4 From a technical perspective, SAP
NetWeaver 7.5 is positioned as an enhancement package and follows all enhancement package rules with respect
to compatibility and consumption.
SAP NetWeaver 7.5 is deployed on premise and serves as the foundation for upcoming releases of SAP Business
Suite software such as the next enhancement packages of SAP ERP. The release is designed to provide optimized
access to SAP HANA through enhanced capabilities such as Core Data Services (CDS).
In the following, you see a list of new and improved scenarios groups compared to SAP NetWeaver 7.4:
Scenario description::
With SAP Enterprise Portal 7.5, you can now align and renew your Portal experience with the SAP Fiori UX
(launchpad and apps), while leveraging their existing investment in the Portal (iViews, roles, SSO).
SAP Enterprise Portal 7.5 and Fiori launchpad with UI theme designer
Scenario description::
The new Fiori launchpad experience on the Portal (Fiori framework page) can now be branded with the UI theme
designer.
Scenario description::
Provides a bridge for customers moving non-disruptively from SAP GUI to Fiori-based user experience, by offering
one access point for all business content – SAP GUI, Web Dynpro, SAP Fiori apps.
Enables administrators to configure both familiar and new content in one, well-known role maintenance
environment (transaction PFCG).
Scenario description::
See next scenario group Fiori User Experience for Business Process Management (BPM).
● My inbox
● BPM OData Services
● BPM UI5 Generation
Scenario description::
SAP Process Orchestration is used by customers to automate and integrate business processes that span across
multiple applications in heterogeneous system landscapes.
However, today’s organizations accumulate massive volumes of structured and unstructured data from business
applications, machines, social media and more. Enterprises are challenged to exploit the value of this information
within the context of end-to-end processes such as procure to pay, order to cash, idea to offering and plan to
inventory, among others. Many organizations struggle to have one single view of their processes and make use of
Big Data in a way that empowers line-of-business users to improve their operations.
Complementing SAP Process Orchestration with Operational Process Intelligence on SAP HANA allows
organizations to streamline their operations and embed Big Data insights into their processes in real time.
Process models and message flows can be easily imported into an end-to-end scenario, and linked with other
process fragments e.g. from SAP Business Suite or S/4HANA.
Line-of-business users will be empowered to gain full visibility into end-to-end operations to improve decision-
making and to take corrective actions when or even before issues occur.
SAP Process Orchestration and SAP Operational Process Intelligence can be deployed onto the same SAP HANA
instance, which reduced TCO and eliminates the need for data replication. In addition, organizations are also
looking to model and document their business processes in a process repository, and linking them to enterprise
architecture.
The integration of SAP Business Process Management with SAP PowerDesigner allows process developers to find
and import process models from a PowerDesigner repository, in order to make them executable. Technical
process models, which represent the implemented process, can be uploaded to the PowerDesigner repository for
process documentation, and linked to related resources such as organizations or systems.
Process Integration
Scenario description::
Scenario description::
Scenario description::
The new release of SAP BW 7.5 powered by SAP HANA marks a consequent step forward in the evolution of BW
as SAP’s strategic Enterprise Data Warehousing Solution in terms of:
● Platform Integration
One major aspect of SAP BW 7.5 is the continued adoption of the features SAP HANA offers as a platform
wherever it is beneficial for SAP BW customers.
With SAP BW 7.4, SAP HANA Smart Data Access and SAP HANA Dynamic Tiering were substantial first
services adopted from SAP HANA. Next will be SAP HANA Smart Data Integration capabilities available for
SAP BW 7.5.
More Information
During an implementation project, you have to take into account many aspects and to take various decisions. The
major planning steps of this process are outlined below.
Caution
Unicode
SAP NetWeaver 7.5 supports Unicode only. A “Combined Upgrade & Unicode Conversion (CU&UC)” with
target SAP NetWeaver 7.5 is not possible. Make sure, that the SAP NetWeaver source system already supports
Unicode.
Table 15:
Scope and Requirements You determine the scope of your SAP Net For more information, see SAP NetWeaver
Weaver implementation. Use Cases [page 9].
Installable Software Units You determine which installable software For more information, see the Mapping of
units (that is, systems with product instan Use Cases to Installable Software Units
ces, standalone engines, optional stand [page 12] section.
alone units, and clients) are required for the
use cases.
Landscape Planning You determine the system landscape and See Upgrading Procedures for NetWeaver
consider the landscape-relevant aspects Key Areas [page 51].
concerning your required use case.
Hardware & Software Prerequi Use the Product Availability Matrix (PAM) to http://support.sap.com/pam
sites check which platforms (operating systems,
databases, browsers) are supported for
your SAP NetWeaver components.
Release Restrictions Check SAP Notes for any release restric Regarding SAP NetWeaver 7.5 release re
tions. strictions, see SAP Note 2206460 .
SAP Solution Manager Prerequi We recommend always using the latest SAP ● See SAP Note 631042 for informa
sites Solution Manager release. tion about the Release strategy for Im
plementation Content (ST-ICO).
Make sure that your SAP Solution Manager
system has the required support package ● See SAP Note 781448 for informa
From a technical point of view, either an upgrade or an enhancement package installation will be carried out to
achieve the target release SAP NetWeaver 7.5 depending on the technology and the start release
To perform both options, you use the Software Update Manager (SUM). General planning, preparation, and
follow-up activities as well as the handling of the Software Update Manager (SUM) are described in the SUM guide
Update Guide – Update of SAP Systems Using the Software Update Manager <version> available at http://
service.sap.com/maintenancenw75 or http://support.sap.com/sltoolset System Maintenance
Software Update Manager (SUM) <version> Guides for SUM <version> .
In addition, you have to perform preparations and follow-up activities specific to your product instance. These
specific actions are described in this guide in the following sections.
Caution
You have to perform both the general preparation activities as well as the product-instance-specific
preparations before you can start the Software Update Manager. Make sure that you start with these
preparations in good time. You can also consider performing these preparations in parallel to the preparation of
SAP Solution Manager and the download of the required software packages and the stack configuration file.
To prepare and perform the update of your SAP system, you require some additional information in a range of
SAP Notes. You must read some of the notes, before you start with the preparations. Besides the central
During the upgrade, you may need information from some additional database-specific and database-
independent SAP Notes.
You find a list of these relevant SAP Notes in the following two guides, which you use in parallel considering your
specific combination of operating system, database and technology:
● SUM guide: Update Guide – Update of SAP Systems Using the Software Update Manager <version> available
on the SAP Service Marketplace at http://support.sap.com/sltoolset System Maintenance Software
Update Manager (SUM) <version> Guides for SUM <version>
● Upgrade and Update Guide - SAP NetWeaver 7.5 available on the SAP Service Marketplace at http://
service.sap.com/upgradenw75 Upgrade - SAP NetWeaver Systems
The following SAP Notes provide you with important information for your SAP NetWeaver implementation project.
2206460 Release Restrictions for SAP NetWeaver Some restrictions apply to the produc
7.5 tive use of SAP NetWeaver 7.5. These
are documented in this SAP Note.
2197259 Add. info about the update/upgrade to This SAP Note describes problems that
SAP NetWeaver 7.5 (incl. SPs and SRs) may occur when you upgrade or update
your system and provides you with infor
mation on how to solve them.
Note
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service
Marketplace at http://support.sap.com/notes .
To prepare and perform the update of your SAP system, make sure that you use the latest available SAP Solution
Manager version. For an update to this SAP Solution Manager version, refer to the Master Guide — SAP Solution
Manager <release>. After you have performed the upgrade, follow the steps described in the SAP Solution
Manager <release> Configuration Guide.
To set up your SAP Solution Manager application, perform the following steps:
These steps are described in the Maintenance Planning Guide, which is available at http://wiki.scn.sap.com/
wiki/x/VIwqCw (column Guides).
See the SAP Community Network (SCN) for more information about
The SAP Solution Manager Maintenance Optimizer plays a central role in the upgrade process. It is mandatory to
use the Maintenance Optimizer for the calculation of the required upgrade packages, enhancement packages, and
Support Package stacks and for the creation of the stack configuration file (xml file). The upgrade program reads
this stack configuration file and uses it as an input file for the upgrade.
The following sections explain how to prepare SAP Solution Manager and the Maintenance Optimizer:
We recommend that you use the latest available Solution Manager version, or that you always update your SAP
Solution Manager to the latest Support Package stack.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution
Manager and that it completes successfully.
1. Make sure that your SAP Solution Manager system has ● See SAP Note 608277 for information about SAP Sol
the required support package level and content. ution Manager Content add-ons.
2. Check if you need to do an update or upgrade of your ● See SAP Note 781448 for information about Support
SAP Solution Manager application or content. Package levels of SAP Solution Manager installations and
3. After an upgrade or update to the latest SAP Solution upgrades.
Manager release, you need to perform follow-up actions ● The Solution Operations Guide for SAP Solution Manager
described in the section Software Change Management of
is available at:http://service.sap.com/instguides
the Solution Operations Guide
SAP Components SAP Solution Manager
<Release> Operations .
Solution Operations Guide – SAP Solution Manager <Release> http://service.sap.com/instguides SAP Components
—> section Software Change Management.
SAP Solution Manager <Release> Operations
Describes the actions required after the SAP Solution Man
ager upgrade or update.
If you have not already done so, configure the Maintenance Optimizer. For a list of configuration tasks, see the
Maintenance Optimizer configuration guide.
Table 19:
Use
The Maintenance Optimizer relies on up-to-date information about your system landscape. Therefore, it is crucial
that this data is correctly maintained in the Landscape Management Database (LMDB). If you have already
maintained the system landscape data, check carefully if this data is correct.
1. If you have not already done so, capture the system data using the System Landscape Directory (SLD).
2. Maintain the system data in SAP Solution Manager.
3. Run the landscape verification to check the system landscape data.
Procedure
1. Register all systems that you want to update in your SLD. In case of a dual-stack system, you have to register
both the ABAP stack and the Java stack.
Depending on your applications, it can either be the SLD of your SAP Solution Manager system (if there are no
dependencies of production runtime systems), or you have to separate SLD systems for production and non-
production use (default recommendation).
If you use a central runtime SLD, distribute the data of all technical systems that are registered in the central
SLD, from the central SLD to the development SLDs and to the local SLD in SAP Solution Manager.
For more information about the SLD topology options and synchronization, see the Planning Guide ‒ System
Landscape Directory available at http://scn.sap.com/docs/DOC-8042
Table 20:
SAP NetWeaver 7.0 and SAP NetWeaver 7.0 including EHP http://help.sap.com/nw70 Application Help
1 and SAP NetWeaver 7.0 including EHP 2 Function-Oriented View SAP NetWeaver by Key
SLD
Note
Instead of the alias /nw70, you can use the aliases /
nw701 or /nw702 accordingly.
Note
Instead of the alias /nw73, you can use the aliases /
nw731, /nw74, or /nw75accordingly.
SAP NetWeaver Process Integration 7.1 including EHP1 http://help.sap.com/nwpi711 Application Help
the SLD
SAP NetWeaver Composition Environment 7.1 and SAP Connecting the system to the SLD is part of the initial sys
NetWeaver Composition Environment 7.1 EHP1 tem configuration as described at:
Landscape Directory
Note
Instead of the alias /nwce71, you can use the alias /
nwce711 accordingly.
SAP NetWeaver Composition Environment 7.2 Connecting the system to the SLD is part of the initial sys
tem configuration as described at:
If the registration was successful, both the ABAP system and the Java system appear in the SLD under
Technical Systems.
2. Transfer the data from the SLD to the SAP Solution Manager: Set up the SLD connection under SAP
Solution Manager Configuration (transaction SOLMAN_SETUP) System Preparation Prepare Landscape
Description Select SLD and Set Up LMDB .
For more information, see the SAP Solution Manager Library at http://help.sap.com/solutionmanager71
Application Help SAP Solution Manager 7.1 SP<version> SAP Solution Manager Operations
Landscape Management Database (LMDB): Managing System Landscape Information Set Up the
Landscape Management Infrastructure Connect LMDB to System Landscape Directory (SLD) .
Note
For more information about the synchronization of central SLD, see
As of SAP Solution Manager 7.1 SP05, the landscape verification function is integrated in the product system
editor of the Landscape Management Database (LMDB). To start the landscape verification, start transaction
LMDB, select a product system in edit mode and choose the Verification step in the navigation tree.
For more information, see the SAP Solution Manager Library at http://help.sap.com/solutionmanager71
Application Help SAP Library SAP Solution Manager 7.1 SP05 (or higher) SAP Solution Manager Operations
Landscape Management Database (LMDB): Managing System Landscape Information Manage Logical
Landscape Information Execute Verification Checks .
When your product systems are known in SAP Solution Manager, you have to check and maintain the system
data, and add your system to a logical component and to a solution.
1. To create and edit logical components, choose SAP Solution Manager: Work Centers Solution Manager
Administration Landscape Logical Components .
2. Assign the related technical systems and the appropriate roles (such as Development System or Production
System) to the logical component. You have the following options:
1. Under SAP Solution Manager Configuration Managed Systems Configuration , you have to assign
logical components to the technical systems registered in the LMDB. Select a technical system and
choose Configure System. Log messages tell you whether information is missing or inconsistent. These
checks prepare a technical system so that it can be used for Early Watch Alerts, for example.
2. You can also start transaction LMDB and select a technical system from the Technical Systems tab. In the
navigation tree, choose Software and Assign to Logical Component. For more information, see the
documentation on the UI
For more information, see the SAP Solution Manager Library http://help.sap.com/solutionmanager71
Application Help SAP Library SAP Solution Manager 7.1 SP09 (or higher) SAP Solution Manager Operations
Landscape Management Database (LMDB) Managing System Landscape Information Managing Logical
Components .
For more information, see the SAP Solution Manager Library at http://help.sap.com/solutionmanager71
Application Help SAP Library SAP Solution Manager 7.1 SP05 SAP Solution Manager Operations
Landscape Management Database (LMDB) Managing System Landscape Information Manage Logical
Landscape Information Create Product System Information .
Use
At several stages in the lifecycle of your SAP solution, you will face the requirement to perform a system copy or a
migration. For example, SAP recommends that you perform a system copy to create test, demo and training
systems. Also, if you need to change your operating system and/or database, you have to perform a migration of
your SAP system.
For this, SAP is offering system copy and migration services that enable you to create consistent copies of your
SAP systems, flexibly adapted to your needs - be it an SAP system distributed to several hosts, a high-availability
system or a system on a rather exotic operating system/database combination.
More Information
● For an introduction into system copy and migration, see http://scn.sap.com/docs/DOC-8324 in the SAP
Community Network.
● System copy guides are available on SAP Service Marketplace at http://service.sap.com/installnw75 .
● Alternatively, you can copy your system with a completely automated end-to-end framework available with
the SAP NetWeaver Landscape Virtualization Management <Release>, Enterprise Edition. For more
information, see the SAP Help Portal at http://help.sap.com/nwlvm .
In the following you find an overview about the procedures with regard to the different key areas of SAP
NetWeaver. For more information about the key areas, refer to SAP NetWeaver Use Cases [page 9].
Below you will find information about upgrading scenarios that are based on SAP Enterprise Portal. This section is
relevant for you if you used one of the following scenarios:
As of SAP NetWeaver 7.3, the functional scope is covered by use case Integrating and Self-Servicing Content with
SAP Enterprise Portal. The following figure shows the software units which make up the use case.
Note
For information about finding the referenced documentation, see section Documentation References [page
77].
Table 21:
[Required Documentation]
1 You upgrade SAP NetWeaver 7.0 Enterprise Portal. We recommend that you always install the latest avail
able SAP NetWeaver 7.5 support package stack.
[Update Guide – Update of SAP Systems Using Soft
ware Update Manager <version>]
● SAP NetWeaver 7.0x: Business Planning and Analytical Services; Enterprise Reporting, Query, and Analysis;
Enterprise Data Warehousing
Note
SAP Strategic Enterprise Management
If you have the SEM-BW add-on installed in your source release, read the following information in the SAP
Community Network:
1. http://scn.sap.com/docs/DOC-30452
2. http://scn.sap.com/community/data-warehousing/bw/blog/2013/11/13/good-news--easier-modeling-
of-the-sem-add-on-in-solution-manager
For more information on implementation considerations and implementation sequence, see the End-to-End
Implementation Roadmap for SAP BW, powered by SAP HANA on http://service.sap.com/installnw75
Planning , and see SAP Note 1600929 as well as SAP Note 2203650 .
Use
The following table describes the sequence in which you have to perform the upgrade or installation steps.
Note
● For information about finding the referenced documentation, see section List of Documentation. [page
77] Consider also the composite notes for BW 7.30 Upgrade: 1636053 (Upgrade SAP NetWeaver 7.30:
BW-Server) and 1636057 (Upgrade SAP NetWeaver 7.30: BI Java).
● For an overview about the steps needed for migrating an existing SAP BW installation to the SAP HANA
database, refer to the End-to-End Implementation Roadmap for SAP BW, powered by SAP HANA available
at http://service.sap.com/installnw75 Planning .
Procedure
Table 22:
1 You upgrade the SAP BW ABAP server. ● With NW 7.50 PI_BASIS including all its compo
nents is part of Software Component SAP_BW.
[Upgrade and Update Guide - SAP NetWeaver 7.5
This includes the SAP Enterprise Portal plug-in.
ABAP]
● Update the BI_CONT add-on to BI_CONT 757 dur
SAP Note 1943931 ing the upgrade of the SAP BW server. The up
grade process prompts you for the required DVD
at the appropriate point in time.
For more information, see SAP Notes 1985663 .
This version of BI Content add-on will be used for
providing additional data flows.
If you use the already existing BI Content Add-on
7.57 (SP05 and higher) there is nothing much to
do. But we recommend upgrading to the latest
available support package of this BI Content Add-
on 7.57.
● Check also the SAP Note 153967 regarding the
BI Content Release Strategy, and SAP Note
1000822 for an overview about the notes for
the add-ons BI_CONT and BI_CONT_XT.
If no AS Java based installation exists, but you want to ● The installation of product instance BI Java in
use BI Java based functions, install an SAP NetWeaver cludes the installation of product instance EP
7.5 system with product instance BI Java. Core– Application Portal and EP, since BI Java de
pends on these product instances.
[Installation Guide – SAP NetWeaver Application
Server Java]
3 Optional: You upgrade SAP NetWeaver Search and TREX enables fast and complex search for BI meta
Classification (TREX). data. The metadata is directly indexed with its attrib
utes and it is available in the search. Therefore, search
[[Upgrade from TREX 6.1 to SAP NetWeaver TREX 7.0]
queries such as "All queries that contain the character
[Upgrade Guide – SAP NetWeaver TREX 7.0 to TREX istic 'customer' and the key figure 'sales' " are sup
7.1]. ported. To be able to use all functions of the search (for
example, the search query described above), you have
to use TREX. However, as a base function, you can
search for objects using their text and technical name
also without TREX. For more information, see SAP
Note 979444 .
Note
If you use the SAP HANA database to persist data
from your SAP BW system, you can use the BW
search in the SAP HANA database. For the most im
portant TLOGO objects, this allows you to perform a
search in the metadata of the objects and a search
for connections between these objects in the
where-used list.
Note
● New and extended interfaces for integrating
SAP R/3, SAP R/3 Enterprise, and SAP ERP
Central Component (SAP ECC) will no longer
be delivered with their own add-on (SAP R/3
Plug-In). As of SAP ECC 6.0, they will be con
tained directly in SAP ECC. Therefore, this step
is not required for SAP ECC 6.0 or higher.
For more information about the delivery strat
egy, see SAP Service Marketplace at https://
service.sap.com/r3-plug-in .
● With BI-Java, you have access to non-SAP data
sources by using the corresponding JDBC
driver.
6 You upgrade the SAP GUI for Windows including the BI Up to SAP enhancement package 2 for SAP NetWeaver
add-on (Business Explorer) on each host for which you 7.0 you could maintain query properties using transac
want to create a connection to the SAP NetWeaver 7.5 tion RSRT. As of SAP NetWeaver 7.3, the maintenance
BW server. of query properties has been partially moved into the
BEx Query Designer. The settings Data Integrity and
[Installation Guide – SAP Front End]
Read Near-Line Storage As Well are now available in
BEx Query Designer (in the Query Properties) and you
can no longer maintain them in RSRT.
7 You install the Modeling Tools for SAP BW powered by See the installation guide at: http://service.sap.com/
SAP HANA to use the Eclipse-based BW modeling en nstallnw75 Installation Installation – Clients .
vironment.
Caution
SAP NetWeaver 7.5 does not support any dual-stack systems, that is, systems based on an ABAP stack and a
Java stack and integrated in a single system with common system ID, common startup framework, and
common database. Such dual-stack implementations can still exist in former is SAP Process Integration
installations.
If you are still using such an older dual-stack implementation of SAP Process Integration (SAP PI)I, you must
perform the update or upgrade to SAP PI 7.5 first and then the dual-stack split afterwards.
Note
You can migrate SAP PI content into SAP NetWeaver PI Java single stack (Advanced Adapter Engine Extended).
This approach should be feasible for most use cases.
Due to the harmonized process orchestration stack (SAP PI and SAP BPM running on the same Java instance),
stateful system-centric processes can be developed using SAP Process Orchestration capabilities. Processes
that are created with ccBPM need to be redesigned and modeled with SAP BPM. For more information about
how to do this, see the SAP Community Network SCN at http://scn.sap.com/docs/DOC-28803 .
Below you will find information about upgrading scenarios that are based on SAP Process Integration. This section
is relevant for you if you use one of the following scenarios:
As of SAP NetWeaver 7.3, the functional scope is covered by the use case Building Integration Scenarios. The
following figures depict the three options with the software units, which make up the use:
Note
As of SAP NetWeaver 7.5, dual-stack installations of SAP Process Integration are replaced by dual usage
type installations that install the SAP NetWeaver AS for ABAP (PI ABAP) and the SAP NetWeaver AS for
Java (PI Java) on separate system IDs.
Figure 9: System Landscape for Building Integration Scenarios with PI Standard Installation
The dual usage type installation offers the complete functional range, whereas the functional range of AEX is
restricted, but has the advantage of a lower TCO.
Process Orchestration provides a tool infrastructure to model and design business processes – from the overall
process flow and the sequence of activities up to the interfaces and data types that are needed to integrate SAP
systems and external systems. It combines the integration capabilities of SAP PI Advanced Adapter Engine
Figure 11: System Landscape for Building Integration Scenarios with Process Orchestration
The following table describes the sequence in which you have to perform the upgrade or installation steps.
Note
For information about finding the referenced documentation, see section List of Documentation.
[Required Documentation]
1 You upgrade the SAP NetWeaver system with product ● We recommend that you always install the latest
instance Process Integration (PI). available SAP NetWeaver 7.5 support package
stack.
[Update Guide – Update of SAP Systems Using the Soft
● If you use partner adapters, see SAP Note
ware Update Manager 1.0]
1522700 for information about their release re
[Upgrade and Update Guide - SAP NetWeaver 7.5 Java] strictions.
[Upgrade and Update Guide - SAP NetWeaver 7.5 ABAP ● Modules or adapters that you have developed for
+Java] SAP NetWeaver 7.0 adapter framework, do not
run in the Process Integration framework of SAP
NetWeaver 7.5 PI. During the upgrade of the
adapter framework, you have to replace them by
appropriate versions for the SAP NetWeaver 7.5
PI adapter framework.
If you cannot upgrade these modules or adapters,
you may use a J2EE Adapter Engine of SAP Net
Weaver 7.0 as a non-central Adapter Engine in
your SAP NetWeaver 7.5 landscape. To do so, you
have to move all scenarios containing these mod
ules and adapters to a non-central Adapter Engine
of SAP NetWeaver 7.0 before you upgrade the
central PI system.
3 You upgrade the standalone Adapter Engine. As this is an AS Java based system, the standard up
grade procedure and tools for SAP Java systems are
[Update Guide – Update of SAP Systems Using the Soft
used.
ware Update Manager <version>]
4 You upgrade the Adapter Engine (Java SE). The Adapter Engine (Java SE), including the contained
adapters, is only supported for compatibility reasons.
SAP NetWeaver 7.5 Library at http://help.sap.com/
It is not developed any further. It should therefore only
nw75 Application Help Function-Oriented View be used in cases where it is unavoidable.
Process Integration Adapter-Engine (Java SE)
Installation
[Required Documentation]
The following table shows the procedure depending on the source release and technology of a PI Dual-Stack
system:
Table 24:
ABAP upgrade
ABAP upgrade
Use
If your source release system landscape contains an "Enterprise Services Repository for SAP NetWeaver
Composition Environment 7.1" (ESR) and Process Integration (or you intend to use Process Integration), you
should discontinue using this ESR. Instead, use the ESR included in SAP NetWeaver 7.5 Process Integration.
Process
Below you will find information about upgrading scenarios that are based on SAP Composition Environment. This
section is relevant for you if you use SAP NetWeaver Composition Environment 7.1, 7.1 including enhancement
package 1 or 7.2.
As of SAP NetWeaver 7.3, the functional scope is covered by the use case Building Composite Applications. The
following figure shows which software units make up the use case.
The following table describes the sequence in which you have to perform the upgrade or installation steps.
Note
For information about finding the referenced documentation, see section Documentation References [page
77].
Table 25:
[Required Documentation]
1 You upgrade the SAP Composition Environment We recommend that you always install the latest
server or Developer Workplace. available SAP NetWeaver 7.5 support package
stack.
[Update Guide – Update of SAP Systems with
Software Update Manager 1.0]
[Required Documentation]
Below you will find information about upgrading scenarios that are based on SAP NetWeaver Mobile.
Depending on your source release, you either have to perform a migration or an upgrade to the target release:
● Source release SAP NetWeaver 7.0: Since the system landscape and software architecture changed, you
need to perform a migration. For information about the migration procedure, see the Migration Guide – SAP
NetWeaver Mobile 7.1.
● SAP NetWeaver Mobile 7.1 and SAP NetWeaver Mobile 7.1 including enhancement package 1: You can
upgrade directly to the add-on SAP NetWeaver Mobile on top of SAP NetWeaver 7.5.
Note
SAP NetWeaver Mobile is available as add-on for SAP NetWeaver as of SAP enhancement package 1 for
NetWeaver 7.3. If you use SAP NetWeaver Mobile either on SAP NetWeaver 7.10 or on SAP NetWeaver 7.3,
you install the add-on on top of SAP NetWeaver 7.5.
Choose the SAP NetWeaver Mobile add-on while selecting in the SAP Solution Manager Maintenance
Optimizer the files, which are necessary for the upgrade. The further upgrade steps are outlined below in
section Upgrade Sequence.
For more information about the installation of the add-on SAP NetWeaver Mobile, see SAP Note 1645275
.
As of SAP NetWeaver 7.3, the functional scope is covered by the use case Mobilizing Business Processes. The
following figure shows the software units that make up the use case.
The following table describes the sequence of upgrade steps for upgrading from SAP NetWeaver Mobile 7.1 and
SAP NetWeaver Mobile 7.1 including enhancement package 1 to SAP NetWeaver 7.5.
Caution
As of SAP enhancement package 1 for SAP NetWeaver 7.3, SAP NetWeaver Mobile is only available as add-on.
See SAP Note 1645275 for further information about installing SAP enhancement package 1 for SAP
NetWeaver Mobile 7.3.
Note
For information about finding the referenced documentation, see section Documentation References [page
77].
Table 26:
1 You upgrade the SAP NetWeaver Mobile server. ● We recommend that you always install the latest
available SAP NetWeaver 7.5 support package
[Update Guide – Update of SAP Systems Using Soft
stack.
ware Update Manager <version>]
● For the upgrade from SAP NetWeaver Mobile 7.1
[Upgrade and Update Guide - SAP NetWeaver 7.5 to SAP NetWeaver 7.5, make sure that SAP Net
ABAP ] Weaver Mobile 7.1 includes at least SPS 04 or
higher.
You must regenerate all the data objects that are part
of the SAP Basis 7.10 software component version
along with other application-specific software compo
nent versions.
and Configuration
Software Logistics
2. Apply patches.
You assign the patches to the client devices,
which makes them available in the outbound
queues of the devices. On the next synchroniza
tion of the client with the DOE, the patch is down
loaded to the client device. The client installer ap
plies the patches on the client, and then auto
matically restarts the client.
See SAP Help Library at http://help.sap.com/
Below you will find information about upgrading SAP Knowledge Warehouse. This section is relevant for you if you
used one of the following scenarios:
● SAP NetWeaver 7.0: IT scenario Documentation, Training Materials and Manuals Management
Note
As of SAP NetWeaver 7.0, SAP Knowledge Warehouse (SAP KW) is an integral part of SAP NetWeaver
Application Server.
Perform the following preparations before you start the upgrade of your SAP Knowledge Warehouse system.
Before you start the upgrade, create a backup of the SAP system (ABAP+Java dual-stack system) and of all SAP
Content Servers. The SAP system and the SAP Content Servers must be in a consistent state when you perform
the backup. We recommend that you create the backup after you have made the last changes to your production
data. Otherwise, data could be lost if problems occur during the upgrade.
If your Application Server Java is installed as a standalone system, you need to create a backup for this system as
well.
Make sure that you also create a backup of the MaxDB instance related to the SAP Content. The further usage of
the SAP KW content is only possible, if the latest files stored in the SAP Content Server fit to the metadata stored
in the SAP system and vice versa.
Create a copy of the file contentserver.ini (on Windows) or cs.conf (on Unix). This file contains information
about the repositories stored in the MaxDB (formerly SAP DB) instance. You can find it in the home directory of
the SAP Content Server Web site. Save the copy of the file in a different directory from the original one.
This file is especially important as it contains information about already existing content repositories in the SAP
Content Server.
If you have made changes to the display component of the SAP Knowledge Warehouse, the Internet Knowledge
Servlet (IKS), for example, if you changed the graphics in the banner to meet your requirements for corporate
identity, save a version of the SCA (Software Component Archive) of the source release IKS so you can apply your
changes to the IKS-SCA of your target release.
Note
SAP ITS is no longer required.
The following table describes sequence in which you have to perform the upgrade or installation steps.
Note
For information about finding the referenced documentation, see section Documentation References [page
77].
Table 27:
1 Upgrade the Application Sever ABAP and Application We recommend that you always install the latest availa
Server Java. ble SAP NetWeaver 7.5 support package stack.
2 Uninstall older versions of SAP Gateway. An SAP Gateway is only required if SAP Content Server
is installed on a different server than the AS ABAP in
stance. Otherwise, the gateway of the existing SAP in
stance can be used.
Server .
4 Upgrade the SAP Content Server and Cache Server (if For SAP Knowledge Warehouse, the content has to be
used). stored in a MaxDB database. The upgrade of SAP Con
tent Server may also require an upgrade of the MaxDB
[Installation Guide SAP Content Server 6.40]
instance. For information about the supported combina
tions of SAP Content Server, operating system and
MaxDB version, see the Product Availability Matrix at
http://service.sap.com/pam .
5 Install SAP Gateway, if SAP Gateway is not already in If SAP Content Server is installed on the same host as
stalled on your system. the SAP NetWeaver Application Server ABAP, you do
not need to install the SAP Gateway.
[Installation Guide – Standalone Gateway on <Operating
System> – For SAP Systems Based on SAP NetWeaver
7.5]
6 Install or update to SAP NetWeaver Search and Classifi Installation or upgrade to a higher TREX release is only
cation (TREX). required if you want to use the full text or attribute
search capabilities of SAP KW.
[Installation Guide – SAP NetWeaver 7.1 TREX Single
Host
Note
Installation Guide – SAP NetWeaver 7.1 TREX Multiple
TREX 7.1 is supported on a restricted number of op
Hosts
erating systems. For more information, see the Prod
Upgrade Guide – TREX 6.1 to SAP NetWeaver 7.0 TREX uct Availability Matrix (PAM) at http://serv
(TREX 7.0)] ice.sap.com/pam .
SAP KW Configuration
For information about the configuration of the SAP Knowledge Warehouse scenarios, see SAP Note 1287381 .
You perform function tests for the SAP Knowledge Warehouse scenarios (such as Editing of Content or Printing of
Structures), which are used in your environment.
If you have a specific version of the SAP KW display component (see Saving Customer-Specific Changes to the
Internet Knowledge Servl [page 70]), then only the SAP standard IKS is available after the upgrade. You have to
apply your changes to the IKS of the target release and deploy them by means of the Software Deployment
Manager (SDM).
Use
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.
SAP delivers a vast number of standard Business applications such as the SAP Business Suite and Industry
solutions, on the ABAP platform, meeting the standard enterprise business requirements. However, there are
always certain processes and scenarios in an enterprise, which are customer-specific. These specific processes
and scenarios enable customers to differentiate their business and further leverage their competitive advantage.
To meet these customer-specific needs the Application Server ABAP development and runtime environment
offers extensive tools and services for the development of ABAP based applications. In addition to the
comprehensive development tools support, the Application Server ABAP also offers capabilities for process &
memory administration, multi-user management, database connections and more.
An end to end lifecycle management support equips customers with services & tools, for example for system
landscape management, configuration, transport management, offering support at every stage of the application
lifecycle, from prototype to go-live and thereafter.
Application Server ABAP 7.5 offers various new enhancements for the Custom Application Development (ABAP)
use case. These new enhancements can be broadly categorized into two main areas:
The data layer of SAP NetWeaver 7.5 is based on Core Data Services (CDS). For SAP NetWeaver 7.5, Core Data
Services have been extended in many different ways (such as annotations, extensions, built-in functions, table
functions) which allows you to develop modern ABAP applications with a compelling user interface based on SAP
UI5. The ABAP developer tools help you to prototype the CDS layer quickly with many built-in templates and
wizards.
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 applications using various SAP UI technologies
such as SAP UI5 or Floor Plan Manager (FPM), and Web Dynpro ABAP applications to meet different scenario
requirements.
The Application Server ABAP 7.5 brings with it several innovations and enhancements. The main area of
innovation focus has been on enabling the Application Server ABAP to harness the power of SAP HANA database
for OLAP- and OLTP-based application scenarios. Application Server ABAP 7.5 further on, remains compatible
with traditional relational databases.
As shown in the figure below, the system landscape provides additional components for the Custom Application
Development scenario:
Figure 15: Software layers and components that are used in the Custom Application Development scenario
So that optimum benefit can be achieved from running productive Business Suite systems on SAP HANA DB, the
AS ABAP provides support for the migration to SAP HANA DB. A combination of new ABAP code scans as well as
monitoring and analysis tools enables the developer to find ABAP SQL code that has potential for performance
improvement (ABAP for HANA performance optimization).
With ABAP Development Tools for SAP NetWeaver, a new development environment - as an addition to the ABAP
Workbench (SAP GUI) - is at the disposal of the ABAP developer in the classic Custom Application Development
scenario. It is based on the open platform Eclipse and targets a significant increase in development productivity in
all phases of ABAP-based software projects. It combines the strengths of the close integration of development,
test, and quality-assurance tools with the application server AS ABAP; this includes the stable and proven ABAP
Lifecycle Management process - with the advantages of a comfortable and lightweight Eclipse UI and a
standardized user interaction process.
ABAP Development Tools play a central role in the integration of the SAP HANA repository contents within the
ABAP platform layer. So that native access to models from the SAP HANA repository is possible from within
ABAP, appropriate proxies can be generated as development objects and handled in the same way as other ABAP
repository objects.
For more information regarding Custom Application Development (ABAP), see the Help Portal at:
In terms of the implementation of SAP NetWeaver Application Server ABAP 7.5 based on SAP HANA, see the End-
to-End Implementation Roadmap for SAP NetWeaver AS ABAP. This guide is available on the Service Marketplace
at http://service.sap.com/installnw75 Planning .
After the upgrade, new and changed functions may require you to adjust your Customizing and the configuration
of your systems. For information about new, changed or enhanced functions, see the Release Notes available at
http://help.sap.com/nw75 What’s New – Release Notes . In addition, several follow-up activities are
required.
Configuration
The SAP Solution Manager contains descriptions of all configuration tasks, and leads you to automated
configuration procedures, where available.
For more information about configuration activities, check the SAP NetWeaver 7.5 library at http://help.sap.com/
nw75 Application Help Function-Oriented View <Software Unit> .
Note
Accessing Use Case information in SAP Solution Manager
You can use the business process repository browser (BPR browser) in SAP Solution Manager at https://
implementationcontent.sap.com/bpr to access instantly information about the SAP NetWeaver 7.5 use
cases you want to implement:
Process Integration
Instead of creating your configuration guides with the SAP Solution Manager, you can also find the
configuration information in the SAP Help Portal. Access the SAP NetWeaver 75 Library at: http://
1. For configuring the Process Integration (PI) dual usage type installation, choose Configuring Process
Integration (PI) Dual Stack Basic Configuration for SAP Process Integration (PI) .
○ For configuring the Non-Central Advanced Adapter Engine (PI-AF) for PI dual usage type installation,
choose Configuring the Non-Central Advanced Adapter Engine (PI-AF) .
2. For configuring the Advanced Adapter Engine Extended (PI-AEX), choose Configuring Advanced Adapter
Engine Extended (PI-AEX) Basic Configuration for SAP PI Advanced Adapter Engine Extended .
○ For configuring the Advanced Adapter Engine Extended (PI-AF) for AEX, choose Configuring the
Non-Central Advanced Adapter Engine (PI-AF) for AEX .
3. For configuring the Process Orchestration (PI-CP), choose Configuring Process Orchestration (PI-CP) .
Follow-Up Activities
For further follow-up activities, check the section Follow-Up Activities in the Update Guide Update of SAP Systems
Using Software Update Manager <version>. You can find the latest version of this guide on SAP Service
Marketplace at http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System
Maintenance Updating SAP Systems Using Software Update Manager <Version> .
In addition, for further follow-up activities with regard to SAP NetWeaver key areas such as Process Integration or
Business Warehouse, you need to check the Upgrade and Update Guide - SAP NetWeaver 7.5 <Technology>,
available on the SAP Service Marketplace at http://service.sap.com/upgradenw75 .
The following table contains a list of all documentation referenced in this document and information about where
to find it.
Table 28:
Title Location
SUM Guide: Update Guide – Updating SAP Systems Using Soft See SAP Service Marketplace at http://service.sap.com/
ware Update Manager 1.0 SP<Support Package> <Technology> sltoolset Software Logistics Toolset 1.0
<Operating System> <Database>
Documentation System Maintenance Updating SAP
SAP NetWeaver 7.5 Update and Upgrade Guides for ABAP, See SAP Service Marketplace at http://service.sap.com/
Java, ABAP+Java: Upgrade and Update Guide - SAP NetWeaver upgradenw75
7.5 <Technology>
Master Guide – SAP NetWeaver 7.5 See SAP Service Marketplace at http://service.sap.com/
installnw75
Installing and Updating TREX 7.1 Single Host
o
m
/
i
n
s
t
g
u
i
d
e
s
S
A
P
N
e
t
W
e
a
v
e
r
S
A
P
N
e
t
W
e
a
v
e
r
M
o
b
i
l
e
7
.
1
M
i
g
r
a
t
i
o
The following table contains links to information available on SAP Service Marketplace or in the SAP Library which
is relevant for implementing SAP NetWeaver:
Table 29:
The latest version of the installation and upgrade guides for http://service.sap.com/instguidesnw75
SAP NetWeaver 7.5
http://service.sap.com/installnw70 Installation –
Information about security SAP Security Guide: See the SAP Library at http://
Guide .
Information about the technical operation of SAP NetWeaver Technical Operations Manual: See the SAP Library at http://
NetWeaver .
SAP Solution Manager Guides All SAP Solution Manager related guides, such as
● Master Guide
● Configuration Guide
● Security Guide Master Guide
● Upgrade Guide
● Solutions Operations Guide
Information about Maintenance Tools: Maintenance Planner See SAP Community Network at http://wiki.scn.sap.com/
and Maintenance Optimizer wiki/x/VIwqCw
The following sections provide more details about product instances, standalone engines, optional standalone
units and clients of SAP NetWeaver.
Note
Usage Type, Technical Usage, and Product Instance
The term product instance replaces the terms usage type and technical usage for SAP systems based on SAP
NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731 .
Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms.
Caution
Uninstalling additional product instance
Note that it is not possible to uninstall additional product instances and that this is also not supported by SAP.
The Java product instances are all based on Application Server Java (BASIC). Further dependencies exists that
are shown in the following figure:
For more information and installation instructions, see the SUM guide for Java: Update Guide – Updating SAP
Systems Using Software Update Manager, for: Java, section Installing Additional Product Instances in an Existing
SAP System.
Apart from the product instances described here, there are some discontinued product instances. If these
product instances are installed in your source release system, they are preserved during the upgrade. However,
they are not part of a new installation of SAP NetWeaver 7.5. For more information, see Compatibility Product
Instances [page 101].
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
Functional Units
SAP NetWeaver Application Server for 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 environment is used both for developing completely new applications and extending and modifying
SAP standard applications for customers. The entire, powerful infrastructure of the Application Server for ABAP
can be used, which even supports the creation of the most complex applications by large groups of developers.
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.
Dependencies
AS Java can be combined optionally with other Java-based product instances in one system.
Functional Units
Table 30:
CM Services (Change Management Services) CM Services help you to manage your Java development.
They provide services for creating development configura
tions, for importing and exporting, and for the deployment to
runtime systems. CM Services enable you to set up team de
velopment with centrally managed development configura
tions. It also supports the automated deployment of build re
sults on to central runtime system. The import and export
service enables you to import and export Software Compo
nent 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, product instance 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 archiv
ing solutions. Java archiving is required for Java applications
with a large volume of retention-relevant data.
Java Foundation This is the Java foundation of SAP NetWeaver. Among its ca
pabilities 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.
Services Registry 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 regis
tered services are classified using semantic-rich classification
systems to enable the browsing of services by classification.
System Landscape Directory 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 soft
ware 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.
XML Data Archiving Service 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 al
lows both XML-sensitive storage used for JAVA Archiving or
XML Archiving (see corresponding Functional units) and ILM
aware archiving used in SAP NetWeaver ILM.
BI Java (BI)
Dependencies
BI Java requires AS Java, EP Core – Application Portal, and Enterprise Portal in the same system. Usually,
scenarios running on product instance BI Java also require product instance BW ABAP. While installing BI Java,
the required product instances are installed automatically. After configuring BI Java, you do not need to perform
further steps in AS Java, EP Core – Application Portal, and Enterprise Portal.
Functional Units
Business Process Management supports the process collaboration and creation of new innovative business
processes based on standardized core processes. SAP 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.
Dependencies
Business Process Management and Business Rule Management requires AS Java and Composition Environment
Platform in the same system.
Functional Units
Business Process Management and Business Rule Management comprise the following functional units:
Table 31:
● Data warehousing
● Various analytical technologies and functions
● Business planning functions
● Web-based and Excel-based reporting, analysis, and planning
● Information broadcasting to distribute BEx applications 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
Note
For product instance BW, there is no installation option in the software provisioning manager 1.0.
Instead, install AS ABAP with software provisioning manager 1.0 and then SAP NetWeaver 7.4 BI
Content 7.57 or SAP NetWeaver 7.4 BI Content Extensions add-on 7.57. This version of BI Content add-on will
be used for providing additional data flows that use the new BW features delivered via SAP NetWeaver 7.4 SPS
05 and higher.
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.
Dependencies
SAP Central Process Scheduling requires Application Server Java in the same system.
Functional Units
SAP Central Process Scheduling comprises the functional unit Integrated Central Process Scheduling by
Redwood.
The Composition Environment Platform provides a toolset and runtime for efficiently developing, running, and
managing composite applications based on SOA principles. It builds upon proven technologies 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 SAP’s 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.
● 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 in the same system.
Functional Units
Table 32:
ECM integration core Enterprise Content Management (ECM) Integration Core facil
itates the provision and consumption of Enterprise Content
Management services using standardized interfaces. There
fore, 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 pro
gramming 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 serv
ices such as the server for World Wide Web Distributed Au
thoring and Versioning (WebDAV) can be leveraged by appli
cations on top of the already exposed ECM services of the
connected service providers.
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 Re
cent Notifications – and displays them in a single list.
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
● DI requires AS Java as a prerequisite in the same system. Optionally, it can be combined with other product
instances in one system. However, depending on the size of the development project and the number of
active developers, DI should use a dedicated system. For further details, see SAP Note 737368 .
You can run the development infrastructure on an AS Java separately 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 above-mentioned
functions.
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:
Dependencies
EP requires EPC and AS Java as a prerequisite in the same system. Optionally, it can be combined with other
product instances in one system.
Functional Units
Table 33:
Knowledge Management Enables portal users to distribute, access, and manage un
structured information within an organization in a heterogene
ous repository landscape. Capabilities include collaborative
document authoring and publishing, version management,
search and navigation with taxonomies, automated classifica
tion and subscription, and more.
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.
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
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 a leaner portal installation and implementation where the full enterprise
portal capabilities (such as knowledge management tools) are not needed.
The EPC product instance contains the following 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 Enterprise Portals and third-party portals into one harmonized SAP Enterprise
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
Functional Units
Table 34:
Mobile
Product instance 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 product instance Mobile) and Mobile Client exchange data in order to keep the
server and client updated. This enables the 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 product instance, 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:
● A design time tool for defining data objects and the distribution of data.
Dependencies
Mobile is not an installable software unit. As of SAP enhancement package 1 for SAP NetWeaver 7.3, SAP
NetWeaver Mobile is available as add-on. To set up a Mobile system, you install and configure AS ABAP. On top of
the AS ABAP system, you install and configure the SAP NetWeaver Mobile add-on separately.
PDF Export
With PDF Export, 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
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, 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 minimum of downtime. Also, the PI system would not be
affected by the downtime of other product instances running in the same system.
Functional Units
● If you have one system with multiple product instances, be aware that we do not provide standard tools for
separating these product instances and distribute them to multiple systems at a later stage. For example, if
you have a system with product instances A and B, you are not able to migrate it with SAP standard tools into
two systems, one with product instance A only and the other with product instance B only.
In addition, we do not provide standard tools for merging multiple systems with different product instances
into one system with multiple product instances at a later stage. If you want to perform these tasks, you
require specific project support. The only exception is the dual-stack split procedure that offers to split an
optional dual-stack system into two separate systems: one based on AS ABAP, the other one based on AS
Java. For more information about the dual-stack split, see http://scn.sap.com/docs/DOC-25162 .
Figure 17: Separating systems with product instances are not supported with SAP standard system copy and migration
tools
Figure 18: Merging systems with product instances are not supported with SAP standard system copy and migration tools
● Although you can use one system for multiple product instances, client restrictions apply to product instance
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.
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.
● RFC Adapter
● SAP Business Connector Adapter
● File/FTP Adapter
● JDBC Adapter
● JMS Adapter
● SOAP Adapter
● Marketplace Adapter
● Mail Adapter
● RNIF Adapter
● CDIX Adapter
● IDoc Adapter (Advanced Adapter Engine) (adapter type IDOC_AAE
● 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 as a prerequisite in the same system. These product instances
are automatically installed when you install the Advanced Adapter Engine.
Functional Units
The Advanced Adapter Engine comprises the functional unit Advanced Adapter Engine.
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:
Advanced Adapter Engine Extended requires AS Java, PI Adapter Engine, and Enterprise Services Repository as a
prerequisite in the same system.
Functional Units
Advanced Adapter Engine Extended comprises the identically named functional unit.
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, 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 minimum of downtime. Also, the PI system would not be
affected by the downtime of other product instances running in the same system.
Functional Units
Adapter Engine (Java SE) is a separate software unit. You can use it only if you have SAP NetWeaver systems with
product instance 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 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.
As of SAP NetWeaver 7.4 the central software components of SAP Gateway have been directly integrated into
SAP NetWeaver in the form of software component SAP Gateway Foundation (SAP_GWFND). This component is
automatically part of SAP NetWeaver 7.4 and higher.
SAP Gateway Foundation facilitates easier provisioning and consumption of business logic and content of SAP
back-end systems for mobile and web applications. It aims to reduce the complexity and the skill set required to
access SAP data, thereby removing deployment barriers. Simple interfaces also help to shorten development
times.
SAP Gateway Foundation enables people-centric applications to consume SAP Business Suite data through
popular platforms and devices (such as the iPad and Blackberry) in an easy and standards-based manner. It is a
framework that connects business users to SAP systems using consumer technologies, groupware, and mobile
devices and is based on open standards (such as the Atom Publishing Protocol and OData) that offer simple
services based on the REST principle.
Depending on your development requirements and where you want to develop SAP Gateway Foundation content,
you can install SAP NetWeaver in either an SAP Business Suite back-end system (embedded deployment) or in an
SAP Gateway Foundation hub system (central hub deployment).
For more information, see http://help.sap.com/netweaver SAP NetWeaver Platform SAP NetWeaver <your
release> Application Help Function-Oriented View SAP Gateway Foundation (SAP_GWFND) .
liveCache
liveCache is a database engine for managing complex objects in scenarios where large volumes of data must be
permanently available and modifiable.
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.
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 at http://help.sap.com/nw75 Application Help SAP Function-
Oriented View Application Server Application Server Infrastructure SAP Web Dispatcher .
A.3.4 Clients
With SAP NetWeaver, you can use the front-end clients and tools described below:
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.
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 today’s users aiming to maximize their daily activities.
The SAP NetWeaver Business Client is one of the main components of the User Interface Add-On for SAP
NetWeaver. For more information, see the SAP Help Portal at http://help.sap.com/nw-uiaddon Application
Help .
Business Explorer provides flexible reporting and analysis tools for strategic analyses and decision-making
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
Enterprise Portal.
Additionally to Business Explorer you may want to consider using tools from the SAP BusinessObjects Analysis
family, such as Analysis, edition for Microsoft Office. The SAP BusinessObjects Analysis clients are specifically
designed for the needs of BW users. Note that SAP BusinessObjects products require separate licenses. For more
information on SAP Business Explorer, see http://scn.sap.com/community/business-explorer .
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as SAP
NetWeaver systems with product instance AS ABAP). This SAP GUI family consists of:
SAP GUI also includes optional add-ons, such as the Business Explorer (BI 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.5:
For more information about the SAP GUI family, see SAP Community Network at http://scn.sap.com/
community/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. Product instance Mobile offers tools for
synchronization and data replication that make the data of the mobile device consistent with that of the back-end
system.
The Modeling Tools for SAP BW powered by SAP HANA (BW Modeling Tools) represent a modeling IDE
(Integrated Development Environment) build on top of the Eclipse platform.
Its main objective is to support BW model developers in today’s increasingly complex BI environments by offering
state-of-the-art modeling tools for BW objects such as InfoObjects, DataStoreObjects (advanced), or Queries.
The SAP NetWeaver Developer Studio (NWDS) is SAP’s Integrated Development Environment (IDE) for Java and
is based on the open-source tools framework Eclipse 3.5. 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.
ABAP Development Tools for SAP NetWeaver is the IDE for ABAP development on the open Eclipse platform. It
combines capabilities of the ABAP Application Server – such as convenient lifecycle management, server-based
development paradigm, full integration, effective testing, and troubleshooting tools – with the Eclipse UI on top of
the ABAP platform.
For more information about the ABAP Development Tools, see Custom Application Development (ABAP) [page
73]
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 http://scn.sap.com/community/
interoperability/microsoft-net .
For the most up-to-date information about ES Explorer for .NET, see SAP note 1259258 .
Note
The Developer license for SAP NetWeaver customers does not include the right to use SAP Web IDE.
SAP Web IDE is a Web-based integrated development tool. It empowers users to rapidly create apps for browsers
and mobile devices. It simplifies the end-to-end application lifecycle, for example, prototyping, development,
packaging, deployment, and customer extensions for SAP Fiori and SAPUI5 applications.
SAP Web IDE aims to increase development productivity by delivering a holistic development experience. Offered
as a cloud solution powered by SAP HANA Cloud Platform, no initial installation is required, and the local IT
infrastructure is untouched. It supports free-style coding, providing strong editors with capabilities of code
completion (SAPUI5, XML and JavaScript), code validation, beautifiers, and more.
In addition, a layout editor with drag-and-drop (WYSIWYG) capabilities further enables acceleration of app
development. Wizard-based templates and sample applications allow users to design new UIs easily and quickly,
following specific best practices. The finalized application can be deployed automatically on SAP HANA Cloud
Platform, an SAP NetWeaver ABAP Server, HCPms, or SMP, or it can be exported manually to any Web server.
There might be reasons for which you want to install these product instances. You can do this using the Software
Update Manager. Note that you can install these product instances only on existing SAP NetWeaver 7.5 Java
systems with at least product instance AS Java.
For more information and installation instructions, see the SUM guide for Java: Update Guide – Updating SAP
Systems Using Software Update Manager, for: Java, section Installing Additional Product Instances in an Existing
SAP System.
Demo Applications
Demo Applications illustrate the usage of SAP Composition Environment for previous releases.
Guided Procedures
Guided Procedures is a framework for modeling and managing workflows using simple and user-friendly 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 role-based access to tools and resources and
guidance through the workflows at runtime, thereby helping end users to easily identify and complete their tasks.
Dependencies
Guided Procedures require Application Server Java, Composition Application Framework, Composition
Environment Platform as a prerequisite in the same system.
Functional Units
Guided Procedures comprise the identically named functional unit providing the above mentioned capabilities.
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
Dependencies
NWDS update site requires Application Server Java as a prerequisite in the same system.
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
*50118213*