Skip to Content

Dear experts,

It is a pleasure to share you more knowledge, in this case, with more in deep about 2 architectures in an easy way (after reading great complex scenarios in diverse articles, i identified the importance to begin with the understanding of the logic before to advance without real idea), where in this case: i will propose that simple vision but it will be supported by different information shared by other experts:

In my first blog post i shared to you the key elements that we should be interested as integrators, after strategy and methodology vision both defined by the market and by the business vision: SAP HCI vs Bonitasoft with famous GlobalWeather Service

SOA vs Cloud (in few words just as a point of view): it doesn’t matter if now a days we talk about the benefits of Cloud Strategy, because we still having companies that use file system requirements (without a strategy decision) or we still using their legacy systems via SOA scenarios in on-premise manner that we must to support (with resistence to change, seen as a normal way to work) in different new innovative strategies like when we decide to go through Cloud Solutions where sometimes we can find a lot of advantages like the portafolio vs costs, or opportunity areas to grow up like when we become aware about the changes to involve in this kind of paradigms, understanding that we must to be prepared about: the fast new releases per year, to support the new security vision if you lose the total power of our information or the real service-response, for few example…

As a particular vision, i will share you some easy points that we can follow to begin with more complex scenarios implementing SOA (No-SAP Cloud or on-premise servers) or to link now to one Cloud Service like AWS Amazon, Microsoft Azure, or with SAP HEC, or others…

1.- Scenario: we are going to integrate from ECC/ABAP or SOAPUI via web services requests by HTTPS that is going to be the main point here of complexity (after looking for clear information was very complicated to find something in easy way), then we will execute a public REST Service via OData simulating the integration with another Cloud Services Proposals with technologies like Success Factors, some Amazon web services supporting SOAP but now a days with trends to support REST services…

HCIimage.PNG

2.- SOAP HTTPS: this is a particular tip that we will have, where you can generate your own certificates files (S_Id Marketplace Users) to be deployed in HCI:

  • You can build your own certification files via Single Sign On: SAP Service Marketplace Single Sign-on
  • Then you just need to configure basic parameters importing your file to support the “certificate based authentification” in the Sender System and with the important tip to give a clear name to your Address URL that will be consumed by the Sender Adapter Configuration:

HCIimage.PNGHCIimage.PNG

HCIimage.PNGHCIimage.PNG

HCIimage.PNG

3.- In the Middle: we have our apache camel!…

  • Is like a “pass through solution” when we implemented this via SAP PI, the difference is that we don’t use now the “pipeline vision” and now we can define or not the metadata that will be processed,
  • Even we process an asynchronous or synchronous, with dependencies in how is defined Sender channel definition with or whithout WSDL definition that force this point,
  • The unique configuration that i propose is, to implement the trace Condiguration clicking in the white side of the iflow designer, in order to activate the functionality to monitor the logs from eclipse and not from web side,

HCIimage.PNG

4.- OData Northwind Service: here you can begin thinking about more cloud than days ago and as your first proposal it doesn’t matter if this is not cloud proposa, the definition of Cloud is more complex about this but as a first vision in “integration paradigm”, you will have one step taken of hundred that you will need…

HCIimage.PNGHCIimage.PNGHCIimage.PNG

HCIimage.PNG

HCIimage.PNG

HCIimage.PNG

HCIimage.PNG

HCIimage.PNG

HCIimage.PNG

5.- Deployment: you just need to check components and then to deploy it in your tenant:

HCIimage.PNG

HCIimage.PNG

6.- Execution: here we can execute it from your ECC/ABAP or your SOAPUI:

a) Via ECC/ABAP/SOAMANAGER:

HCIimage1.PNG

HCIimage1.PNG

HCIimage1.PNG

b) Via Browser:

HCIimage1.PNG

c) Via SOAPUI:

HCIimage1.PNG

7.- Monitoring: we must to confirm the quality of our solutions:

  • As we know we can monitor our flows executed from web browser,
  • As we can see the result, with the trick configured above to monitor the logs from Eclipse Side,

HCIimage.PNG

HCIimage.PNG

Other important references: to complement this post in more “advance scenario, tricks and particular configurations from experts”:

I hope you can enjoy it at same time that you can implement this easy proposal with big impact in global vision…

Best Regards,

Azael

To report this post you need to login first.

2 Comments

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

  1. Chris Xu

    Thank you, Azael, for this excellent blog.

    I followed your guide and it worked perfectly.

    Now I want to retrieve only one product based on provided product ID.

    My question is how to configure odata receiver adapter for this requirement?

    Regards,

    Chris Xu

    (1) 
  2. Kumar Sen

    Hi Azeal,

    I am too much new in SOA service, I have a requirement briefing you following, I want to restrict certain fields replication with respect to receiver systems. SOA has already implemented in our MDG system and ECC system. Entity CELEM (Cost Element).

     

    Suppose : I want to replicate two fields for Sys1 , and one field for sys 2. so how can I configure them. Please guide, is there any certain configuration available, or I need to write ABAP code for it.

     

    Regards

    J Sen.

    (0) 

Leave a Reply