HANA Application Lifecycle Management setup and how it compares to SAP CTS+ Integration

(1)

SAP How-to Guide HANA Platform

SAP HANA™ Appliance

Applicable Releases:

SAP HANA 1.0 SPS 06 Revision 60

These How-to Guides were created as a team effort between the SAP SCE team, SAP Consulting, SAP AGS, SAP HANA Development and the SAP HANA Product Management teams.

For additional information contact: [email protected] or

[email protected] or [email protected]

Version 1.1

(2)

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

SAP “How-to” Guides are intended to simplify the product implement-tation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting.

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 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, except if such damages were caused by SAP intentionally or grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

(3)

Document History

Document Version Description

1.0 Initial Release

(4)

1. Background

HANA 1.0 SPS6 released a feature called HANA Application Lifecycle Management (ALM). The proposed use of HANA ALM is transporting HANA content between HANA systems in a landscape. Prior to the introduction of HANA ALM, customers had the choice to perform HANA transports manually through the export/import functionality in HDB Studio or using integration with enhanced SAP Change and Transport System (CTS+).

This document provides instructions to setup ALM for a simple 2-system landscape, and then provides some considerations for choosing between HANA ALM and CTS+.

2. HANA Application Lifecycle Management

2.1 What is HANA ALM?

Depending on your implementation scenario, developers will create various HANA objects – products, delivery units, packages, analytic and attribute views, etc. These objects normally are created in the HANA development system, and then transported into the other HANA systems in a managed way. With SPS6 the Application Lifecycle Management feature was introduced to facilitate transporting the HANA objects in a managed way. The ALM is an XS application that is automatically installed as part of the HDB Server. Below is a picture of the initial ALM screen accessed through the http://<SAPHANAHost>:80<SAPHANAinstance>/sap/hana/xs/lm.

If you have worked with SAP Transports, then you will be familiar with most of the options. Section 12.1 of the HANA Developer Guide highlights the keys tasks that can be done using the HANA ALM. They are:

 Designate source and target systems for transports  Assign the appropriate delivery units to the transport route  Execute a transport

(6)

October 2013 2

 Monitor the transport processes

2.2 Setting up HANA ALM

The high level steps for setting up ALM is:

 Create an ALM Administrator user  Register System for Transport  Create a Transport Route

In this example we will setup ALM for a 2-system landscape. The details of the 2 HANA systems are shown below.

Development Test

HANA System ID DEV TST

HANA Instance Number 00 01

XS Port 8000 8001

2.2.1 Create ALM Administrator

This is a normal DB user in HANA but this user will need to have the appropriate roles to setup and various tasks in HANA ALM. Refer to section 12.2.2 (SAP HANA Application Lifecycle Management Roles) in the SAP HANA Developer Guide for details of the various ALM security roles that are pre-delivered with HANA ALM. In the picture below we have created the TMSADM user as ALM

(7)

October 2013 3

2.2.2 Register System for Transport

Now we need to access the ALM through a web browser. Logon to the development and test ALM and confirm that each of the systems are registered locally, using the TRANSPORT option as

shown below.

Here we can see the development system is registered.

Here we can see the test system is registered.

We need to register the DEV system in the ALM of the TST system. So for the next step you need

(8)

October 2013 4

Enter the details of your development system. Note the port is of the format

80<HANAInstanceNumber>. Once you choose Next, in the following screen click on the Maintain Destination button to proceed.

When you click on the Maintain Destination button, the HANA XS Administrator Tool will launch in

a separate web browser window. You may need to manually navigate to the destination as shown in the screen below, depending on the revision of HANA you are using. The only changes you need to do here are switch to the basic authentication and enter the credentials of the ALM Administrative user you created earlier. Then press the Save button.

(9)

October 2013 5

If all works fine, then you should end off with the DEV system registered into the TST system ALM

configuration, as shown below.

2.2.3 Create a Transport Route

A transport route defines the connection details required to complete the transport of a delivery unit from a source SAP HANA system to a target SAP HANA system. Before starting this step, make sure you have your delivery units and packages setup.

You define the route in the target system. In our example this is the TST system. From the ALM

(10)

October 2013 6

In the example below we added the TEST_1 delivery unit for this route and chose the type as Delta Delivery Unit Transport. Repeat the steps to add a route with type Full Delivery Unit Transport.

Now you are ready to use the TRANSPORTS option. Remember to use the TRANSPORT  TRANSPORTS option in the target system.

Note

If you want to import a transport from DEV to TST, then you must be logged into the ALM of the

(11)

October 2013 7

3. What is CTS+ Integration

SAP Change and Transport System (CTS) is the traditional feature to transport ABAP objects between systems in a landscape. SAP CTS was enhanced to cater non-ABAP objects – this enhanced version is known as CTS+ or enhanced CTS. Since SAP HANA SP5 CTS+ has been enabled to transport SAP HANA objects as well.

The following picture below shows the systems that are involved in a typical CTS+ deployment.

The steps are explained as follows:

1- The user sets up a HANA delivery unit with the required HANA packages in HDB Studio. 2- The user triggers an export of the delivery unit in HDB Studio, and selects the option to

connect to the CTS Organizer. This includes the exported objects in an ABAP transport. 3- The user connects to the CTS System and uses the STMS functionality to transport the

HANA objects to subsequent systems in the HANA landscape.

(12)

October 2013 8

4. Which option do I use?

Now that we have provided information about HANA ALM and HANA CTS+ integration, the question is which of these tools best fits your use case. Both tools overlap in functionality, and choice really depends on your SAP Landscape. We will approach this question by a series of qualifying statements, and then for each we recommend which tool is most appropriate. When using this you must take into account your landscape as well as any other important factors that are part of your scenario.

Qualifying Statement CTS+ HANA ALM

Your SAP environment is made up of many SAP systems and you

have an established change process around ABAP transports…

✓

Your SAP environment already includes CTS+ for transporting

non-ABAP related objects e.g. Portal, PI or SLD…

✓

Your HANA content is expected to be managed by a separate dedicated group of people who have no responsibility or knowledge

of your other SAP systems…

✓

Your landscape does not contain other SAP systems (ABAP or

Java)…

✓

Your SAP landscape contains many ABAP systems but you do not

have any Java systems for implementation of CTS+…

✓

Your SAP changes are managed via SAP Solution Manager Change

Request Management (ChaRM)…

✓

Note

The way you manage the packaging of HANA objects and handle its dependencies is independent to CTS+ or HANA ALM, both CTS+ and HANA ALM merely provide the tools to transport such objects.

5. Further Information

(13)

HANA Application Lifecycle Management setup and how it compares to SAP CTS+ Integration

Applicable Releases:

Version 1.1

Document History

Table of Contents

1. Background

2. HANA Application Lifecycle Management

2.1

What is HANA ALM?

2.2 Setting up HANA ALM

2.2.1

Create ALM Administrator

2.2.2

Register System for Transport

2.2.3

Create a Transport Route

3. What is CTS+ Integration

4. Which option do I use?

✓

✓

✓

✓

✓

✓

5. Further Information