applicable releases: smp cloud / sap hana cloud …...are responsible today for the on-premise...

SAP How-To Guide Mobility SAP Mobile Platform Cloud

Applicable Releases:

SMP Cloud / SAP Hana Cloud

Version 1.0

March 2013

© Copyright 2013 SAP AG. 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 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.

Any Java™ Source Code delivered with this product is only to be used by

SAP’s Support Services and may not be modified or altered in any way.

Document History Document Version Authored By Description

0.01 Martin Grasshoff First draft release of this guide - outline

1.0 Martin Grasshoff First complete version of this guide

Typographic Conventions Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons Icon Description

Caution

Note or Important

Example

Recommendation or Tip

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2. Business Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

3. Landscape Overview .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

4. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1 Hardware Prerequisites ................................................................................................. 3 4.2 Software Prerequisites .................................................................................................. 3 4.3 Other Prerequisites ........................................................................................................ 3 4.4 Restrictions ...................................................................................................................... 3

5. Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

6. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1 Setting up the Internet Connection ............................................................................... 5 6.2 Download of Files ............................................................................................................ 7 6.3 Installing the SAP JVM ................................................................................................... 8 6.4 Install SAP HANA Cloud Connector .............................................................................. 9

7. Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

8. Expose Intranet System .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

9. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

10. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SAP Operations Guide: Mobility

June 2013 1

1. Introduction This document describes the step-by-step procedure to install the SAP Cloud Connector. Its intended audience is system administrators who are about to connect their on-premise SAP NetWeaver Gateway system to an SMP Cloud account. The section Landscape Overview provides a holistic view about the overall solution while the section Installation provides a step-by-step description of the procedure to install the SAP Cloud Connector. In order to do so, the part Prerequisites describes which steps must be accomplished before the actual installation starts. At the end Post Installation tasks describes which steps should be configured to create the first HTTP endpoint available to SMP Cloud.

This document does not cover troubleshooting the installation or the already installed product. Its sole purpose is to make the installation process understandable and reproducible. Intended Audience:

• System Administrators with Network responsibility and Linux knowledge.

2. Business Case While the Try & Buy paradigm is very appealing in the first place, real IT landscapes today have a lot of business related data stored in on-premise systems. In order to leverage the existing data and the benefits of cloud based services (e.g. GWaaS or MaaS) it is important to make the on-premise data available to the cloud services. Of course there are a lot of “full service” vendors and services out there, which stores all business data in the cloud. But since most often a whole shift of existing services to the cloud are not possible for various reasons SAP offers a way to create hybrid cloud solutions where the raw data (and maybe the business logic) remain on premise while the cloud services offers new options.


June 2013 2

3. Landscape Overview

The diagram depicts the overview for a typical SMP Cloud landscape. While the on-premise systems on the bottom are in the realm of the customers, SAP is responsible for the SMP Cloud (MaaS) on top of this diagram. SAP Mobile Platform Cloud edition is an application on top of the SAP HANA Cloud. If you want to learn more about the SAP HANA Cloud visit its website Developer website in the SAP Community Network. The mobile devices in the top left corner represent the users’ devices. System Administrators who are responsible today for the on-premise systems can easily take the role of an SMP Cloud Account administrator. The system between the backend systems and the lower firewall represents the SAP Hana Cloud Connector. The SAP HANA Cloud Connector consists of two components. One is the “On-Demand SAP HANA Cloud Connector” which is transparent to the administrator and has no serviceable parts. The “On-Premise” SAP HANA Cloud Connector is the part this document is referring to. Details for the system requirements can be found in the next chapter. This document describes the procedure to install the On-Premise SAP HANA Cloud Connector.


June 2013 3

4. Prerequisites

4.1 Hardware Prerequisites System can be physical or virtual machine:

Memory: mininum 1GB RAM, 4GB recommended

Hard disk space: minimum 20 GB, 100GB recommended

CPU: minimum single core 3 GHz, dual core 2 GHz recommended,

x86-64 architecture compatible

4.2 Software Prerequisites Operating System: SUSE Linux 11 SP1 or SP2 a

Java: JDK 6 or JDK 7, SAP JVM recommended

Others: SAP Hana Cloud Connector 1.2

4.3 Other Prerequisites

4.4 Restrictions

• HTTP(S) protocols are supported for the on-demand to on-premise connectivity solution. For Internet connectivity, you can use HTTP Destinations for HTTP(S) protocols and a default HTTP proxy set on a JVM level.

• Each SAP HANA Cloud account can be connected to one SAP HANA Cloud connector only. A single SAP HANA Cloud connector can expose an arbitrary number of back-end systems.

• On-demand to on-premise connectivity can currently be used via the HTTP Destination API only. Usage of other HTTP clients is currently not supported. For Internet connectivity, you can use any HTTP clients.

• For Internet connections, you are allowed to use the following ports for URL parameter: 1080; 1443; 21000; 44300; 44305; 50000; 50001;50013; 50900; 51000; 8081; 8101; 8111; 8443; 9013.

For on-demand to on-premise solutions there are no port limitations.

a Your SLES 11 system is connected to the SuSE/Novell SLES 11 RPM repositories, so that

additional RPMs can be downloaded and installed automatically, as required. For more

information, see:

http://www.suse.com/documentation/sles11/book_sle_admin/?page=/documentation/sles11/book_sle_admin/data/book_sle_admin.html


June 2013 4

5. Preparation In order to start the process of installing the SAP HANA Cloud Connector (which will be called SHCC in the rest of the document) you’ll need the following prepared:

• SUSE Linux 11 SP1 or SP2 System • Root Access to the Linux System • Proxy connection settings to be used by the SHCC Host

o Proxy Hostname o Proxy Port o Proxy Username (if required) o Proxy Password (if required)

• SAP HANA Cloud Account login credentials ready o Landscape Host (hana.ondemand.com) o Account Name o Username (SCN User) o Password (SCN Password)

Make sure that you have all these information at hand before you start the installation.

This system may be virtualized or physical but should have the single purpose to serve as a host for the SHCC Server to run on.


June 2013 5

6. Installation The following section describes the installation steps to install the SHCC on a fresh SUSE Linux system.

6.1 Setting up the Internet Connection In order to download the needed files for installation your machine needs Internet access. Typically your SHCC is located behind a proxy. In our scenario it is sufficient to set the proxy settings in the already installed Firefox browser. This may be different in your scenario – for example if you have installed the Linux machine without a desktop. In this case you have to set the proxy settings in /etc/sysconfig/proxy or using yast. The appendix has a link to more detailed information.

1. Logon to the System with admin rights. 2. Start Firefox by clicking on Computer and Firefox to start the browser. You see a screen like

this:

As you can see your machine has not Internet connection and can not connect to the start page.

3. In Firefox click on the menu Edit > Preferences. Navigate to the Advanced Tab on top and select the Network tab below. Now click the Settings… button. The Connection Settings dialog appears.


June 2013 6

Now put in the appropriate proxy settings to allow access to the Internet.

4. Click OK, then click Close. 5. Make sure your machine has connection to the web. For example by pointing your browser

to www.sap.com.


June 2013 7

6.2 Download of Files 6. Navigate the browser to http://tools.hana.ondemand.com/#optional 7. Download the files:

a. sapcc-1.2.0.zip b. sapjvm-7.1.004-linuxxx86_64.rpm

to your users documents folder as seen below. Read and Agree to the license agreement displayed to you before the actual download starts.


June 2013 8

6.3 Installing the SAP JVM 8. Open a Terminal if not done already

a. Click on Computer in the lower left part of the screen b. Click on the More Applications… button c. The Application Browser appears. Type Terminal in the Filter text field.

d. Click on the GNOME Terminal icon to open a Terminal.

9. Navigate to your Documents directory where you have downloaded the files from step 7b. a. cd Documents b. ls –l

You should see something like this:

10. Install the SAP JVM rpm 11. Type the command

a. rpm –i sapjvm-7.1.004-linuxx86_64.rpm into the Terminal. This installs the SAP JVM .

12. Now we make sure that the SHCC can find the SAP JVM. In order to do so we will create two soft links using the following commands:

a. ln -s /opt/sapjvm_7 /usr/bin/java b. ln –s /opt/sapjvm_7/bin/keytool /usr/bin/keytool

This completes the SAP JVM installation.


June 2013 9

6.4 Install SAP HANA Cloud Connector 13. Make sure you are in your Documents directory.

a. cd ~ /Documents 14. Unzip the SHCC installation files:

a. unzip sapcc-1.2.0.zip

As you can see you’ll have three separate files extracted.

15. Now execute the following commands to create a zyppper repository and install the software:

a. zypper ar -f . SCCRepository b. zipper in com.sap.scc-ui

Missing dependendies should be downloaded by zypper automatically. 16. Installation is now complete and the deamon (service) should be started automatically. You

can manually control the deamon using the following commands: service scc_daemon stop|restart|start|status


June 2013 10

7. Post-Installation Now after the service is installed you can start with the basic configuration to establish the first secure connection to the SMP Cloud account. To do this, open a Web browser and enter the following URL: https://<hostname>:8443

Enter Administrator and manage as the user/password information (case sensitive). SAP HANA Cloud connector prompts you to change the password when you first log on.

You can change the password again at a later stage from the Settings menu in the upper right-hand side corner.


June 2013 11

Initially you’ll get another prompt where you specify your SAP HANA Cloud Account setting and your HTTP Proxy so that the JVM which runs the SHCC can connect to the SAP HANA Cloud. The following screenshot shows you what information you have to fill in:

After you click the Apply button, values will be stored and SAP HANA Cloud Connector will start a handshake with the SAP HANA Cloud component on the on-demand side of the SAP HANA Cloud. At this point it also starts to establish a secure SLL tunnel to the server hosting your account.

You should see a green indicator on the home screen of the SAP HANA Cloud Connector Home page. However, currently no requests are allowed yet. In order to make internal backend systems available to the SMP Cloud you’ll have to configure.


June 2013 12

8. Expose Intranet System 1. On the Home screen select Access Control and choose Add

Exclude all data files of the database files from “on access” scanning for performance and stability reasons C:\Sybase\UnwiredPlatform\Servers\UnwiredServer\data Exclude all data files of the database files from “on access” scanning for performance and stability reasons C:\Sybase\UnwiredPlatform\Servers\UnwiredServer

The dialog wants you to specify the mapping between internal systems and a “virtual” system that can be seen from the SAP HANA Cloud perspective. So all your cloud applications (like SMP Cloud itself) can see sales-system.cloud, but ecc60.mycompany.corp will not be visible. The same is true for port numbers.

Since SMP Cloud performs URL Rewriting of – typically – OData datasources it is recommended that virtual and internal host name and port numbers do match exactly. Otherwise OData l ink navigation wil l not work.


June 2013 13

2. Adding a Resource Path to the exposed System It is useful to NOT expose a whole system to the SMP Cloud. Instead it is recommended to expose only certain resources to the external systems. You can specify this in the lower section of the screen where you can add Resources on-demand.


June 2013 14

9. Appendix Information: Default SAP HANA Cloud Connector username/password: administrator/manage References:

Description Reference

SMP Cloud Online Help https://help.hana.ondemand.com/mobile/frameset.htm

Tool Download https://tools.hana.ondemand.com/#optional

SAP HANA Cloud http://scn.sap.com/community/developer-center/cloud-platform

SAP HANA Cloud Online Help

https://help.hana.ondemand.com/

SUSE Proxy Settings http://www.novell.com/support/kb/doc.php?id=7006845


June 2013 15

10. Glossary GWaas – NetWeaver Gateway as a Service Maas – Mobile as a Service

www.sap.com/contactsap

www.sdn.sap.com/irj/sdn/howtoguides