SAP HCM – SuccessFactors BizX

PI Configuration Example
Validity

 This documentation is valid for the following versions of the

integration add-on for SAP ERP HCM and SuccessFactors BizX

 Version 1.0 Support Package 06 and above

 Version 2.0 Support Package 02 and above

© 2013 SAP AG. All rights reserved. Customer 2

Introduction
Introduction

 This document provides an example of the setup in the PI Integration Directory needed
for the hybrid integration of SAP ERP HCM and SuccessFactors BizX.

 The following information and screen shots have been created based on a test system.
Hence, in your case, the configuration will deviate depending on the system landscape
and the NW PI release in use.

 The login service needs to be configured differently from all other services. This is
necessary due to the session handling mechanism. While the login service reads all
cookies from the HTTP header of the response, all other services must set a cookie with
this received content in the HTTP header of the request.
Therefore, all services other than the login need to use a communication channel that
uses the SOAP AXIS adapter for writing to the HTTP request header while the login
uses a communication channel with a SOAP AXIS adapter configured for reading from
the HTTP response header.
Therefore, this document explains the setup for the user data scenario consisting of the
login, logout, and user data upsert services. This procedure can also be copied for other
scenarios.

© 2013 SAP AG. All rights reserved. Customer 4

PI Configuration Overview
PI IDR – Configuration Overview

 The screenshot below shows the objects of a sample configuration for the user data
scenario using business components.

© 2013 SAP AG. All rights reserved. Customer 6

PI IDR – Configuration Overview

 The back-end business component contains all the sender interfaces.

© 2013 SAP AG. All rights reserved. Customer 7

PI IDR – Configuration Overview

 The SuccessFactors business component contains all the receiver interfaces and the
communication channels.

© 2013 SAP AG. All rights reserved. Customer 8

PI Configuration
Login Service
PI IDR – Configuration of the Login Service
Receiver Determination

 The receiver determination for the login interface contains all objects needed to connect
the following two interfaces:
 SFSFSessionHandlingLoginQueryResult_Out
 SFSFSessionHandlingLoginQueryResult_In

© 2013 SAP AG. All rights reserved. Customer 10

PI IDR – Configuration of the Login Service
Interface Determination

 The interface determination specifies the operation mapping to be used to connect the
two service interfaces.

© 2013 SAP AG. All rights reserved. Customer 11

PI IDR – Configuration of the Login Service
Receiver Agreement

 The receiver agreement specifies the communication channel to be used.

Ensure that for the login service you use the communication channel configured to read
from the HTTP header. The corresponding template is
SFSF_Soap_Adapter_Axis_Login_Response.

© 2013 SAP AG. All rights reserved. Customer 12

PI Configuration
Logout Service
PI IDR – Configuration of the Logout Service
Receiver Determination & Interface Determination

 The receiver determination and interface determination for the logout interface basically
look the same as for the login interface except for the communication channel.

© 2013 SAP AG. All rights reserved. Customer 14

PI IDR – Configuration of the Logout Service
Receiver Agreement

 The receiver agreement specifies the communication channel to be used.

Ensure that for the login service you use the communication channel configured to write
to the HTTP header. The corresponding template is SFSF_Soap_Adapter_Axis.

© 2013 SAP AG. All rights reserved. Customer 15

PI Configuration
User Data Upsert Service
PI IDR – Configuration of the User Data Upsert Service
Receiver Determination & Interface Determination

 The configuration for the user data upsert service is the same as for the logout service.

© 2013 SAP AG. All rights reserved. Customer 17

PI IDR – Configuration of the User Data Upsert Service
Receiver Agreement

 The receiver agreement specifies the communication channel to be used.

Ensure that for the login service you use the communication channel configured to write
to the HTTP header. The corresponding template is SFSF_Soap_Adapter_Axis.

© 2013 SAP AG. All rights reserved. Customer 18

PI Configuration
Communication Channels
PI IDR – Configuration of the Communication Channels
Communication Channel for the Login Service

 This communication channel is to be used for the login service. It can be created based
on the template SFSF_Soap_Adapter_Axis_Login_Response.
The highlighted fields need to be filled according to the system landscape.

© 2013 SAP AG. All rights reserved. Customer 20

PI IDR – Configuration of the Communication Channels
Communication Channel for the Login Service

 This shows the module

configuration.
 The exact sequence and contents
are important.
 Use the parameters for proxyHost
and proxyPort if needed.

© 2013 SAP AG. All rights reserved. Customer 21

PI IDR – Configuration of the Communication Channels
Communication Channel for All Other Services

 This communication channel is to be used for all services except for the login service. It
can be created based on the template SFSF_Soap_Adapter_Axis.
The highlighted fields need to be filled according to the system landscape.

© 2013 SAP AG. All rights reserved. Customer 22

PI IDR – Configuration of the Communication Channels
Communication Channel for All Other Services

 This shows the module

configuration.
 The exact sequence and
contents are important.
 Use the parameters for
proxyHost and proxyPort if
needed.

© 2013 SAP AG. All rights reserved. Customer 23