Hello Integration Community,

 

Now that the TechEd days for this year has come to a close, I want to extend the knowledge sharing sessions of SAP Cloud Platform Integration (f k a HCI) a bit more. Over the next few weeks – in a series of 10 blogs, I shall cover features of SAP Cloud Platform Integration  in more depth. These blogs are meant to provide technical know and insight on the features of SAP Cloud Platform Integration. They are not of an introductory nature, and I am targeting mainly Integration Developers when I write.

 

Read the blogs and let me know your comments!

 

Blog 1: Tracing Capability  

Blog 2: Request-Reply Pattern in Integration Flows

Blog 3: Multicast Pattern in Integration Flows 

Blog 4: Modelling Exceptions in Integration Flows 

Blog 5: Content Enricher Pattern in Integration Flows

Blog 6: Splitting messages in Integration Flows

Blog 7: Message Events in Integration Flows

Blog 8: Message Aggregation Pattern in Integration Flows

Blog 9: Scripting in Integration Flows

Blog 10: Importing PI content in Integration Flows

 

Warm Regards,

Sujit

To report this post you need to login first.

15 Comments

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

  1. biplab das

    Hi Sujit,

    Do we know what are the limitation of HCI compare to other cloud ( Or on-premise ) middle wares? 

    1) Can HCI in a single Iflow extract data from multiple source and then combine those?

    2) The Successfactor adapter that HCI has it is as mature as Boomi SF adapter?

    3) Any limitations in transformation? ( context handling ,flexibility of using custom code etc)

    (0) 
    1. Sujit Hemachandran Post author

      Hi Biplab,

      1) Can HCI in a single Iflow extract data from multiple source and then combine those?

      Currently, this feature is not available. We only have the feature to combine multiple messages from a single system.

      2) The Successfactor adapter that HCI has it is as mature as Boomi SF adapter?

      Unfortunately, I do not know the maturity of the Boomi SF adapter. But the SF adapter follows the API and protocol changes of SF adapter very quickly and is continuously updated to reflect the SF standard. HCI and SFSF are SAP teams, so this is a promised support from us.

      3) Any limitations in transformation? ( context handling ,flexibility of using custom code etc)

      No limitations. Did you face any difficulties in any scenario.

      Thanks and Regards,

      Sujit

      (0) 
  2. Bhagyashri Patil

    Hi Sujit,

    I am working on counter based routing and request reply type of iFlows. I am trying to configure aggregator but not able to do it as I don’t know WSDL files and how to create flow for executing simple scenario?

    I am trying one scenario like sending Continuous messages (Content of message like order no. and related data) to HCI and store it for specific time (1min delay or 5min Delay) then receive it on receiver side at a same time.

    If u have some related blogs or information or WSDL then please help me to sort!!

    Thank you in Advance!!

    (0) 
    1. Sujit Hemachandran Post author

      Hi Bhagyashri,

      If you do not know the WSDL for the incoming message – an alternative that you could try would be to use headers for counting and aggregating. The WSDL should be available from the source system – where are you sending the messages from?

      Best Regards,

      Sujit

      (0) 
  3. Misher Liu

    Hi Sujit, If I want to terminate the message delivering to receiver in some conditions, which Pallete can I use in HCI? In PI, there is a routing condition which I can use,when the condition is meeted, then I can choose No Receiver. So the wrong message will not be transfered to Receiver. Thanks a lot Br Misher

    (0) 
    1. Sujit Hemachandran Post author

      Hi Misher,

      Yes – in SAP HCI you can provide a routing condition, too. Just use the router flow step to define the conditions.

      Best Regards,

      Sujit

      (0) 

Leave a Reply