Show TOC

Installation Steps - General InformationLocate this document in the navigation structure

The SAP HANA appliance software comes pre-installed on a specific appliance hardware system delivered in conjunction with leading SAP hardware partners.

This chapter describes the required installation and configuration steps for the SAP HANA Live content packages and applications.

Installation Process

The diagram below depicts the required installation steps for both installation scenarios. For the integrated installation, only a few steps are needed. For a side-by-side installation, the steps relevant for handling the table replication from the SAP Business Suite system into the side-by-side SAP HANA database are also necessary.

Figure 1: Overview of Installation Process
Integrated Scenario

In the integrated scenario, you do not need to create and replicate the database tables, as they are already available in the SAP HANA database. They are maintained through the data dictionary of the corresponding ABAP Application Server. Therefore, all steps regarding table creation and data replication are not relevant in this scenario. Since the ABAP server creates all tables in one specific database catalog schema (typically <SAPSID>), this needs to be mapped to the authoring schema of the imported content packages. For more information, see Configure Schema Mapping and SAP Note 1800515 Information published on SAP site.

Side-by-Side Scenario

In the side-by-side scenario, the database tables that are used by the SAP HANA Live products need to be replicated from the corresponding SAP Business Suite back-end system into the SAP HANA database. This is done using SAP Landscape Transformation Replication Server. If you want to execute SAP HANA Live views, the data from the corresponding tables must be available. SAP recommends to create all required tables as specified in the SAP Notes corresponding to the SAP HANA Live products, and to replicate the data only for those tables that are used in executed analytical scenarios. This ensures that no unnecessary data is replicated, that no unnecessary SAP Landscape Transformation Replication Server resources are consumed, and that no unnecessary DB memory is consumed. Later on, data for additional tables can be replicated on demand if you want to execute additional scenarios. For more information, see Replicate Data (Side-by-Side Only).