3.4 Overall Installation Sequence
3.4.1 Installation Sequence for Minimal System Landscape
The following table documents the installation sequence for the Minimal System Landscape:
Table 15: Installation Sequence for the Minimal System Landscape Sequence Software Units to Install
1. Installation of ABAP software units
Execute the System Landscape Implementation Manager (SAPinst) to install the components titled Add-Ons ABAP included in installation SAP ECC Server (see Figure 5 Overview of SAP ERP 6.0 Components).
Option 1: Complete SAP ERP ECC - Server
Select the required software components and usage types of SAP ERP 6.0 and of SAP NetWeaver 7.0 (Minimal System Landscape: select SAP NetWeaver 7.0 - usage types AS ABAP, AS Java, EP, BI ABAP, BI Java, PI, DI, and MI).
SAPinst installs all required components as appropriate.
Option 2: Reduced Server consisting of usage type SAP NetWeaver 7.0 - AS ABAP (formerly SAP WEB AS)
It is not always required to install a full system with product instance SAP ECC Server. In such cases, install the usage type AS ABAP (formerly SAP NetWeaver Application Server), as described in Option 1 above, by deselecting SAP ECC, and by installing the specific components as Add-On (see step 2 in installation sequence).
For more information, see SAP ERP 6.0 - Installation Guide available in SAP Service Marketplace at
http://service.sap.com/erp-inst SAP ERP 6.0.
For more information about SAPinst, see SAP Service Marketplace at http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.0 Installation Guide SAP NetWeaver Developer Workplace.
For information for a proper sizing, visit SAP Service Marketplace at http://service.sap.com/sizing.
If you plan to operate product instance SAP NW - Process Integration on the SAP ERP Central Component host, or if you plan to install your Java Web Applications on this server, then you should install SAP J2EE in add-in mode. For production use, however, you should operate a separate system based on SAP NetWeaver 7.0 usage type Process Integration and, depending on your requirements, a separate J2EE server in standalone mode where your Web applications are installed. A J2EE add-in installation is mandatory for the XI Java
Components. For all other components (Web Applications, Enterprise Portal), we recommend that you install a standalone J2EE. For more information, see SAP Service Marketplace at
Sequence Software Units to Install
http://service.sap.com/instguidesNW70
Installation Installation Guide Web AS Java 6.40 <Platform>:
Database>.
Installation of JAVA Web Components
Execute SAPinst to install the following JAVA components of the SAP ECC Server system onto the AS Java system:
FSCM Biller Direct 6.0 (Product instance SAP FSCM - Biller Direct) Product instance SAP XSS (Self Services)
XECO 4.0 (Product instance SAP XECO)
LSO Content Player 6.0 (for SAP Learning Solution) - Product instance SAP Learning Sol-Front-end CP
Important restrictions may apply to a specific setup. For more information about restrictions, see SAP Service Marketplace at http://service.sap.com/notes SAP Note852235 (Release restrictions for SAP ERP 6.0).
For more information about Installation Guide for the ERP Java Component, see http://service.sap.com/erp-inst SAP ERP 6.0.
To install product instance SAP XSS (Self Services), make sure that you select SAP NetWeaver usage type EP Core while installing the ABAP software units.
2. Installation of ABAP Add-Ons
Before starting, meet the following conditions
Completely install a system instance with SAP ECC Server or, Install a system with SAP NetWeaver 7.0 - usage type AS ABAP - as described in the previous step.
Use transaction SAINT (SAP Add-On Installation Tool) to install one or all of the following ABAP Add-On product instances of SAP ERP 6.0 on your server installation:
Option 1 (Prerequisite: Complete SAP ERP ECC Server product instance is installed): SAP SRM - Server ECC Add-On, SAP cProject Suite, SAP Catalog Content Management, SAP Workforce Management, and the BI Content Add-On of the corresponding release.
If you want to install SAP Workforce Management, then you must first install the SAP liveCache (see step 9).
Option 2 (Prerequisite: Usage type - AS ABAP is only installed):
SAP FSCM - FSCM Server (ABAP), SAP E-Recruiting, SAP SEM, SAP Learning SolFrontend ABAP, SAP cProject Suite, SAP SRM -Server ECC Add-On, SAP Catalog Content Management, SAP Workforce Management, and the BI Content Add-On of the corresponding release.
Sequence Software Units to Install
For more information, see SAP Service Marketplace at http://service.sap.com/erp-inst SAP ERP 6.0.
Product instance SAP FSCM - FSCM Server (ABAP) is a technical prerequisite for product instance SAP SEM.
SAP Workforce Management requires a separate license.
For more information about the installation of SAP Catalog Content Management, see SAP Service Marketplace at http://service.sap.com/notes SAP Note835170 (CCM 200 Installation with SAINT) and SAP Note835169 (Upgrade Basis 700 with CCM 2.00).
You can find SAP documentation in transaction SAINT (SAP Add-On Installation Tool) when you select F1 in your installed system. Alternatively, you can search for the documentation about SAP Add-On Installation Tool in the SAP Help Portal, at help.sap.com.
3. Install the XI Content Package as described in the Installation Guide for SAP ERP 6.0.
4. Install the required Business Packages (product instance Portal Content) in accordance with the description in the Installation Guide for SAP ERP 6.0 (see Section 5.3.1 - SAP ERP Business Packages) and SAP Service Marketplace at http://service.sap.com/ep-content.
For more information about downloading area for portal business packages, see SAP Service Marketplace at http://service.sap.com/swdc Download Installations and Upgrades Entry by Application Group SAP Application Components SAP ERP.
The portal content package includes all individual business packages for the installation of SAP NetWeaver usage type EP Core, which are part of SAP ERP 6.0.
You must make certain that you install usage type SAP NetWeaver usage type EP Core (product instance SAP NW -EP Core) before.
5. Either install a new local System Landscape Directory (SLD) or configure SLD on an existing AS Java system.
For more information, see the Master Guide in SAP Service Marketplace at http://service.sap.com/installNW7.0 andSection 2.1.3 - System Landscape Directory.
6. Install a system instance with product instance SAP NW - Search and
Classification (SAP NetWeaver- Stand-Alone Engine Search and Classification – TREX) or use an existing deployment.
SAP NW – Search and Classification is based on software component version TREX 7.0. If the operating system of your system landscape permits, you can use TREX 7.1 as well.
For a new installation of SAP NW - Search and Classification, in the different
Sequence Software Units to Install
system landscapes, see the documentation from SAP Service Marketplace at http://service.sap.com/installNW70 listed below:
On a single host, see the documentation for single host installation of the corresponding version.
Of a distributed TREX system landscape, see the documentation for multiple host installation of the corresponding version.
After the installation of TREX, you have to configure the systems, which communicate with TREX (for details, see the TREX Installation Guides mentioned above).
For performance reasons, SAP NW - Search and Classification runs on a separate server.
7. Front-End Component Installation (Optional)
Install SAP GUI 6.40 (product instance: SAP Front-end GUIs) or above and all front-end components required in addition, as defined with the component information of the particular process.
You can install this component at any time, since you install it on the clients.
SAP GUI is mainly required for administrators and power users.
Moreover, certain SAP ERP processes, which are not yet entirely portal-based, still require SAP GUI. The installation of front ends for the SAP system is described separately in the SAP Front End Installation Guide, which can be found at http://service.sap.com/instguides Installation and Upgrade Guides SAP Components SAP Front-End Components.
8. Install Mobile Applications as described in the corresponding Installation Guide, if you intend to use SAP Solutions for Mobile Business.
SAP Solutions for Mobile Business are not part of SAP ERP 6.0.
You need to download them separately. SeeSection 5.2.7
Technology Components for SAP Applications for Mobile Business.
Before you install product instances for SAP Solutions for Mobile Business in addition to SAP ERP 6.0, a system must be available in which you have already installed product instance SAP NW - Mobile Infrastructure.
9. If you want to install SAP Workforce Management, you must first install the SAP liveCache. SAP liveCache is a database engine for managing complex objects in scenarios where large volumes of data must be permanently
available and modifiable. SAP liveCache is based on mySQL on MaxDB and is installed using SAPinst.