October 2014
English
Hana Cloud Integration Setup & Configuration (C1E)
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Building Block Configuration Guide
SAP Best Practices Hana Cloud Integration: Setup & Configuration: Configuration Guide
Copyright
© 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.
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. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Icons
/ Caution
/ Example
/ Note
/ Recommendation
/ Syntax
Typographic Conventions
Type Style / DescriptionExample text / Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example text / Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT / Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text / Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT / Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text / Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> / Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
Content
1 Purpose 5
2 Preparation 5
2.1 Prerequisites 5
2.2 How to Use This Configuration Guide 5
2.3 Parameter Sheets 5
2.3.1 Files Provided by SAP 5
2.3.2 Parameters Provided by Customer 6
3 Configuration 6
3.1 Setting up Connectivity between SAP ERP and HCI 6
3.1.1 Setting up HCM SuccessFactors Scenarios in Eclipse 8
3.1.2 Certificates 9
3.1.3 Creation of Logical Ports in SOAManager 12
3.2 Setting up Connectivity between HCI and SuccessFactors System 14
3.2.1 Using Basic Authentication 14
3.2.2 Using Certificate Authentication 15
3.3 Adjusting Scenarios in Eclipse 16
3.3.1 Adjust Sender System in iFlow to include Backend Certificate: 16
3.3.2 Adjust Receiver SOAP Adapter for SOAP URL and to use Basic Authentication/Certificate Authentication 16
HCI General Configuration within Eclipse
1 Purpose
The purpose of this document is to describe the general configuration steps required to manually set up HCI general configuration in Eclipse for all or specific processes shipped with this Packaged Solution within a system landscape that has already been installed using the corresponding configuration guides for installation.
2 Preparation
2.1 Prerequisites
Before you start installing this scenario, you must install the prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for this Packaged Solution. This document is in the content library, attached to the Step-by-Step Guide.
The Building Block SAP ERP HCM: Base Integration Settings (C1F)configuration guide serves as a prerequisite.
2.2 How to Use This Configuration Guide
This configuration guide is designed to simplify the work to deploy and configure the entire or a specific scope of this Packaged Solution. The latest supports four scenarios: Basic Employee, Compensation, Recruiting and Workforce Analytics data. From a process integration view, you do not have to configure all available scenarios in this Packaged Solution scope. Which process you want to configure depends on your business requirements. For instance, you can choose to only configure the Compensation or Recruiting data scenario. But we recommend configuring at least the employee data scenario since it is the basis for the other scenarios.
Regardless of the process(es) you want to configure in Integration Directory, you should make sure that the corresponding HCM customization described in C1F has been successfully performed and that the full BizX content (for all scenarios) is always deployed on to the tenant.
2.3 Parameter Sheets
The following sheets are considered to help you through the configuration phase of this Packaged Solution. All information relevant to the configuration is listed here.
We recommend using the corresponding free text fields to note all relevant parameters.
2.3.1 Files Provided by SAP
Standard HCM SuccessFactors BizX Content can be downloaded from the HCI Tenant using following URL:
itspaces URL / <tenant url>/itspacesExample: https://tmvb008avlb032avtvlb-avlb032.hana.ondemand.com/itspaces
itspaces is only supported with IE9 or above. An Alternate browser ex: Mozilla Firefox can also be used to access itspaces.
Procedure
Within the HCI itspaces WebUI it is possible to download or directly deploy the HCM / SuccessFactors BizX Integration content to the selected tenant. Both paths can be used to deploy the content on the HCI tenant.
1. Choose Catalog
2. Select ‘SuccessFactors BizX Talent Management integration with SAP ERP HCM (1305) ‘
3. It is possible only to implement those processes which are required. In order to download these projects, click on ‘Actions’ icon against each Integration Project and select ‘Download’
4. Save the Archive file in a local Directory.
5. If you want to directly deploy the integration content to the HCI tenant you can use the gear-wheel icon next to Download button, marked as ‘Click to deploy’..
2.3.2 Parameters Provided by Customer
The customer must provide the following parameters. You can use the following template list to insert the necessary content.
SuccessFactors Connection Details<url_sfsf>
URL of SuccessFactors server
<own_sfsf_companyid>
SFSF Company ID of customer
<own_sfsf_name>
SFSF account name of customer
SAP ERP HCM Connection Data
<SID>
SID of HCM System
SAP_ERP_hostname
Hostname of HCM System
SAP_ERP _port>
HTTP Port of HCM System
<CLNT>
Client of HCM System
3 Configuration
The configuration defined in this section covers:
· Set connectivity between SAP ERP and HCI
· Set up Project and create Configuration Objects in HCI
· Set up Connectivity between HCI and SuccessFactors System
3.1 Setting up Connectivity between SAP ERP and HCI
Use
The purpose of this section is to describe how the connection between the application system (SAP ERP HCM) and the HCI Tenant can be set up. A successful setup of this connection allows the Add-On to send extracted data to the HCI Tenant, which will then replicate the data to SuccessFactors BizX.
The steps described in this section must be performed only when the connection setup between the SAP ERP and the HCI Tenant does not exist. If such a connection has already been set up, you can skip this section.
To connect an application system (in this case SAP ERP) to the HCI Tenant, the following information must be available for the application system:
Field / Data / CommentsSID / for example, EC6 / 3 coded system-ID from the HCM system which contains the source data
Client / for example, 120 / The client in the system-ID (SID) which contains the source data
This set of information is unique for every system (productive, test, development).
For HCI Tenant, the following information must be provided:
Field / DataTenant ID / for example, avlb032
Tenant Ops URL / for example, https://tmvb008avlb032avtvlb-avlb032.hana.ondemand.com
Worker node URL / for example, https://iflmapvb008avlb032avtvlb-avlb032.intaas.hana.ondemand.com
3.1.1 Setting up HCM SuccessFactors Scenarios in Eclipse
Use
For the HCI content development and monitoring a new toolset has been implemented based on Eclipse. So before installing the HCI tooling itself you need to install Eclipse.
Procedure
1. Download and install Eclipse Classic 4.2.2 IDE from the list available in Eclipse Juno Sr2 Packages page(JRE1.6)
2. In the Welcome page, open the Developer's Workbench.
3. From the main menu, choose Help > Install New Software...
4. In the Available Software page of the Install wizard, add the update site URL mentioned below:
HCI Tools URL / https://tools.hana.ondemand.com/juno5. Select the following three options:
· Show only the latest version of available software
· Groups items by category
· Contact all update site during install to find required software.
6. Select the SAP HANA Cloud Integration Tools category.
7. Choose Next.
8. Check the features selected for installation and choose Next.
9. Accept the terms of licensing agreement and choose Finish.
10. Restart the Eclipse IDE.
Once you have done this, you should be able to see following new Perspectives:
1. Integration Designer
2. Integration Operations
Next Step would be to import the content downloaded from itspaces into Eclipse, as mentioned above:
Procedure
1. Open Eclipse, switch to Integration Designer Perspective using
Window ® Open Perspective ® Other ® Integration Designer
2. Select File ® Import
3. Select General ® ‘Existing Projects into Workspace’
4. Select Archive File, Choose Browse to locate the zip file for the scenario. Repeat this step for each Archive file.
Once you have imported the Archive file, a Project as follows should appear in Eclipse Project Explorer
Project Node / ContentRoot Node / for example, com.sap.SFIHCM01.hcm2bizx.SFSFAPIDictionaryDescribeSFObjectsExResult
Resources / src.main.resources
- parameters.prop
- parameters.propdef
Mapping / src.main.resources.mapping
- Operation Mappings(.opmap)
- Message Mappings(.jar)
- XSLT Mapping
iFlow / src.main.resources.scenarioflows.integrationflow
WSDL / src.main.resources.wsdl
Build / target.build
Manifest / META-INF
- MANIFEST.MF
Build.properties
3.1.2 Certificates
Use
HCI services are secured by certificates. So in order to directly trigger HCI services via SOAP UI you will have to include your certificate into the build and deploy it to the operations server. For the backend connection a generic SAP certificate for the backend needs to be included into the build.
3.1.2.1 Obtaining Personal Certificate and Keystore
Use
For accessing the WSDL for your deployed services on the operations server and for directly triggering the services via SOAP UI you will need to export your certificate and include it in the build. SOAP UI needs a keystore file for authentication.
SAP Passport CA can be used for selftest.via SOAPUI. Please find below the steps to generate SAP Passport CA:
Pre-requisite: In order to generate an SAP Passport CA, you must have a user in SMP.
a. Generate SAP Passport CA from SMP (Service Market Place)
Procedure
The following procedure takes place in the background when you apply for your SAP Passport on the Applying for the SAP Passport page:
1. Your browser generates a key pair
2. Your browser sends the public key to the SAP Trust Center Service
3. The SAP Trust Center Service checks your application and password
4. The SAP Trust Center Service answers with a signed certificate, the SAP Passport
5. The SAP Passport is installed in your browser.
You can find more information at:
Service Marketplace URL / https://websmp203.sap-ag.de/~sapidp/002006825000000038452001Eb. In order to use the SAP Passport CA, you need to export the key-pair from your browser. It may not be possible to export the key-pair from IE due to security-constraint. Please refer to the following blog for possible workaround to export the keys:
SCN Blog / http://scn.sap.com/community/about/blog/2011/05/03/sso-with-your-sap-passport-to-scnmarketplace-on-iphoneipadc. From this generated key pair, typically you will use the private key to send the request from SOAPUI and public key certificate will be imported in the iFlow.
SoapUI could be downloaded from http://www.soapui.org | http://www.smartbear.com
Procedure
1. In the SOAP client, go to File ® Preferences
2. Go to HTTP Settings – uncheck the “Accept compressed responses from hosts”
3. In Proxy Settings enter the values of Host and Port.
4. In SSL settings, browse and select public-private key and enter the corresponding password.
3.1.2.2 Obtaining Backend Certificate
Use
HCI services should be triggered by the proxies in the ERP backend so there needs to be a certificate that authenticates this system.
In order to export this certificate for including it into the build of the iflows, logon to the system and run transaction STRUST.
Procedure
1. Run transaction STRUST
2. Choose SSL Client SSL Client (Standard)
3. Double choose the entry for Own Certificate. Once this is done, you should be able to see Certificate details in the Certificate section
4. Choose Export Certificate button at the bottom under Certificate Details
There are two options to achieve the SSL connectivity. It depends on your choice to use either option 1 or option 2
3.1.2.2.1 Option 1: Using SSL Client Standard
If the backend system identifies itself using an internal certificate, this is not accepted by the HCI factory landscape servers, because they are signed by a non-trusted CA. In that case you have to manually request a new certificate and setup the backend system accordingly.