Skip to Content

     Good news before you eat that Turkey on Christmas is that real time integration with SuccessFactors Onboarding is possible.

     Accessing Onboarding API’s for reading and posting data resulted in labored trials, as we tried using SFSF Connectivity Add-on 1.0 for PI and      Successfactors connector in Boomi.

                         OtherEndPoint.PNG

     We tend to choose the Endpoint as ‘Other’ (PI/Boomi) for the Onboarding or tried PI Axis configuration for Webservices – both reward less.

     Acquired from KMS, onboarding is yet to be part of BizX stack – where all other SuccessFactor applications like Employee Central, Recruiting, Succession      Planning etc are present. 

     1. First step is to enter the WSDL endpoint in browser and save the WSDL displayed. Import WSDL as External definition in PI.

                    WSDL_Import.PNG

     2. Import the SSL certifcate for Onboarding from the ‘Certificate Information’ link in browser as highlightrd in the right of configuration below.

                         PIOnboarding_AdapterConfig.PNG

     3. Create the Webservice channel for Onboarding as shown above.

          Remove the ‘?wsdl’ from WSDL endpoint and enter the rest as ‘Target URL’ in Webservice adapter (SOAP) in PI.

     4. Building the Integration process –

          Our process should start with a call to the API ‘BeginSession’ to get the ‘Ticket number’ to be used in all subsequent API calls.

          The Ticket number unlike the SessionID for BizX stack is not to be a part of the Webservice Request Header.

         

          Rather it is a part of request payloads for all Onboarding API’s.

          Hence to retain the Ticket number in PI and call the actual API, (in my case the ‘AddHRDataRecord’) we can create the BPM as shown below.

                              IntegrationProcess.PNG

               Am sure the same approach would work in Boomi or any other Integration platform.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Muni M

    Dear Jayan,

    is the integration process mandatory for on boarding interface?

    1. in your ccBPM, it is calling only begin session. cancel session is not there.

    2. can’t we use soap look up instead of going for bpm

    3. I believe begin and cancel session should like login and log out. are begin session and cancel session part delivered content? i.e standard proxies?

    my understanding is that begin and cancel session also should be working similar to login and logout.

    Regards,

    Muni

    (0) 
  2. Muni M

    looks like add on 3.0 onwards, we dont need to create bpm for begin and cancel session.

    if we run repot RH_SFI_IMPORT_ONBOARDING_DATA, report itself is calling begin,import and cancel session interfaces.

    just like login and logout.

    (0) 

Leave a Reply