cancel
Showing results for 
Search instead for 
Did you mean: 

Sender SFSF Adapter for synchronous Query entity.

former_member198445
Participant
0 Kudos

Hello experts,

I have been configuring the following scenario ====>  SF(SFSF Sender) -> PI -> File Receiver.

Basically, I want the output of the Synchronous soap call to be written to a file.

In the Sender SFSF adapter, I am using SOAP protocol and I have modeled a query using the HCI operations modeler. The query is on the 'CompoundEmployee' entity whose response XSD I have already imported into the ESR. Further to this, I have mapped this response to my file receiver interface structure.

My questions are:

- Would my sender interface be synchronous and if so, I reckon the request structure would only be a dummy structure. Is that correct?

- Can I call the 'CompoundEmployee' entity query in asynchronous mode other than for ADHOC queries?

- How would my receiver adapter work in Synchronous mode since the Sender adapter would work on a polling basis?

I have used the following links to get this far:

Thanks in advance,

Amith

Accepted Solutions (1)

Accepted Solutions (1)

RaghuVamseedhar
Active Contributor
0 Kudos

Amith,

We can pull/push data from/to SuccessFactors. SuccessFactors will not initiate a call to your system.

Dynamic query can be sent using UDF.

former_member198445
Participant
0 Kudos

Thanks Raghu,

My question is more on the Pull scenario,. I am using a query in the Sender SFSF adapter. My basic question is will the Outbound interface be Sync or async?

If sync, then what would be the request structure mapping because my receiver is async?

Regards,
Amtih

RaghuVamseedhar
Active Contributor
0 Kudos

Amit,

When pulling data, it is Async : -  SF -> PI -> Target.

We can also perform a lookup/query on SF. It is Sync : - Source <-> PI <-> SF. XML for this is


<?xml version='1.0' encoding='utf-8'?>

<urn:query xmlns:urn='urn:sfobject.sfapi.successfactors.com'>

<urn:queryString>SELECT person, personal_information FROM CompoundEmployee</urn:queryString>

</urn:query>

former_member198445
Participant
0 Kudos

Hi Raghu,



When pulling data, it is Async : -  SF -> PI -> Target.

<?xml version='1.0' encoding='utf-8'?>
<urn:query xmlns:urn='urn:sfobject.sfapi.successfactors.com'>
 <urn:queryString>SELECT person, personal_information FROM CompoundEmployee</urn:queryString>
</urn:query>

Async Mode worked!!!!!

For anyone interested, I am doing the following:

SFSF Sender Config as follows.

SFSF Query (modeled in Operations modeler) as follows. I've also setup a 30 minute polling.

I am using asynchronous as per Raghu's suggestion.

In the ESR, I have the xsd imported which is my outbound interface message type. I have created a mapping to my inbound aysnc interface message type.

The SFSF adapter would generate the xml request mentioned here..

  1. <?xml version='1.0' encoding='utf-8'?> 
  2. <urn:query xmlns:urn='urn:sfobject.sfapi.successfactors.com'> 
  3. <urn:queryString>SELECT person, personal_information FROM CompoundEmployee</urn:queryString> 
  4. </urn:query> 

Regards,

Amith

Answers (0)