PUBLIC

SAP HANA Content

SAP HANA Platform SPS 08 Document Version: 1.1 - 2014-09-09

Table of Contents1 SAP HANA Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 SAP HANA Archive Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31.2 Deploy a Product Archive (*.ZIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Deploy a Delivery Unit Archive (*.tgz). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA Content Table of Contents

1 SAP HANA ContentSAP HANA content is structured in the way that delivery units (DUs) are used to group SAP HANA content artefacts (such as analytic, attribute or calculation views, and SQLScript scripts).

SAP HANA content, which is developed on SAP HANA Extended Application Services (SAP HANA XS), can also be grouped in a DU. DUs are grouped to SAP HANA products in order to ship and install SAP HANA applications with all dependent artefacts (grouped in DUs).

To distribute SAP HANA content, a product archive (*.ZIP file) or a delivery unit archive (*.tgz file) is used. There are various ways of acquiring and deploying these archive types.

1.1 SAP HANA Archive Types

The difference between the various archive types is their method of deployment, and when the content is deployed.

The following archive types are available:

● Product archive file (*.ZIP)A product version archive is a *.ZIP file containing 1-n software component archive files and the following metadata files: stack.xml, pd.xml. A software component archive file is created for each DU containing its archive file (*.tgz).A product is usually the entity that delivers SAP HANA applications, but it can also be used for transports.SAP HANA content that can be downloaded independently is shipped as SAP HANA products in SAP HANA product archives. SAP HANA content that is not part of the SAP HANA database is called SAP HANA content add-on (or SAP HANA product). SAP HANA content add-ons are developed as part of the SAP HANA platform or as part of an application that runs on top of SAP HANA.For information about how to deploy a product archive, see Deploy a Product Archive (*.ZIP).

● Software Component Archive (*.SAR or *.ZIP)A software component archive is a *.ZIP file (or *.SAR file) containing one delivery unit archive file (*.tgz) and (optionally) a corresponding translation DU and the metatdata file SL_MANIFEST.XML. A software component archive can be deployed with the same tool as product archives.For information about how to deploy a software component archive, see Deploy a Product Archive (*.ZIP).

● Delivery unit archive file (*.tgz)A delivery unit archive is a *.tgz file containing the SAP HANA content artefacts that are created in the SAP HANA repository. A DU is used to deliver one or more software components from SAP (or a partner) to a customer.For distribution using export/import and deployment, a DU is contained in a delivery unit archive (*.tgz file). It contains the objects and packages of a DU together with the metadata file manifest.txt. The transport is also offered at DU level.The following types of delivery unit archive files are available:

○ Delivery unit archives as part of the SAP HANA databaseThe following types of delivery unit archive files that are part of the SAP HANA database are available:

○ Automated content is installed together with SAP HANA and imported into the SAP HANA repository during installation. This is an integral part of the SAP HANA database and is used by every SAP HANA database customer.

SAP HANA ContentSAP HANA Content

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

Automated content is located on the SAP HANA system in the following folder:/usr/sap/<SID>/SYS/global/hdb/auto_content.

○ Non-automated content is installed with SAP HANA, but needs to be imported into the SAP HANArepository manually by the system administrator. It is used for integral parts of the SAP HANA database, but is only used by a small number of customers.Non-automated content is located on the SAP HANA system in the following folder:/usr/sap/<SID>/SYS/global/hdb/content.The following DUs are non-automated content:

○ HCO INA SERVICE 1.0 (HCO_INA_SERVICE.tgz)○ SAP HANA DXC 1.0 (HANA_DXC.tgz)

Delivery unit archives that are non-automated content of the SAP HANA database need to be deployed manually.

○ Independent delivery unit archives that are not part of the SAP HANA databaseDelivery unit archives that are not installed together with the SAP HANA database and are not part of the SAP HANA database need to be deployed manually.

For information about how to deploy or activate a delivery unit archive, see Deploy a Delivery Unit Archive (*.tgz).

Related Information

Deploy a Product Archive (*.ZIP) [page 4]The following deployment methods of deploying a product archive file (*.ZIP file containing a product) or asoftware component archive file (*.SAR or *.ZIP) are provided:

Deploy a Delivery Unit Archive (*.tgz) [page 5]The following deployment methods for deploying a delivery unit archive file (*.tgz file containing a DU) are provided:

1.2 Deploy a Product Archive (*.ZIP)

The following deployment methods of deploying a product archive file (*.ZIP file containing a product) or asoftware component archive file (*.SAR or *.ZIP) are provided:

● SAP HANA application lifecycle managementCommand line tool hdbalmThis tool is installed together with the SAP HANA client.For more information, see Installing and Updating Products in the SAP HANA Developer Guide.

● SAP HANA studioDeploy HANA Content functionThis function is called from the SAP HANA lifecycle manager user interface.For more information, see Deploy SAP HANA Application Content from a Remote Host in the SAP HANAAdministration Guide.

4PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA Content SAP HANA Content

Related Information

SAP HANA Developer GuideSAP HANA Administration Guide

1.3 Deploy a Delivery Unit Archive (*.tgz)

The following deployment methods for deploying a delivery unit archive file (*.tgz file containing a DU) are provided:

● SAP HANA application lifecycle managementUPLOAD/DOWNLOAD functionThis tool runs on the SAP HANA XS Web server.For more information, see Import a Delivery Unit in the SAP HANA Developer Guide.

● SAP HANA studioImport function of the SAP HANA ModelerChoose File Import SAP HANA Content Delivery Unit .

Related Information

SAP HANA Developer GuideSAP HANA Modeling Guide

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved. 5

SAP HANA ContentSAP HANA Content

Important Disclaimers on Legal AspectsThis document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Coding SamplesAny 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.

AccessibilityThe 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 specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document.

Gender-Neutral LanguageAs 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 HyperlinksThe 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. Regarding link classification, see: http://help.sap.com/disclaimer.

6 PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA Content Important Disclaimers on Legal Aspects

SAP HANA ContentImportant Disclaimers on Legal Aspects

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

www.sap.com/contactsap

© 2014 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.