Skip to Content
In this Webblog I will illustrate on how to achieve ASBO-GBO-ASBO scenario using SOAP Adapter. I will not Discuss the Integration Repository and other Integration directory configurations. ASBO: Application Specific Business Objects (Represents application Specific Metadata). GBO: Generic Business Object (For examples, a set of objects is available from OAGIS (www.oagis.org) and also GS1 (www.gs1.org). The Use of Generic Business Object allows us to create decoupled interfaces as opposed to tightly coupled interfaces. Let us take an example : System A is sending message ASBO1 to System B(Message ASBO2) System C(Message ASBO3) and System D(Message ASBO4) .If we do not use the Generic Business Objects then essentially we are using three mapping programs A <–> B and A <–> C and A <–>D. image The Problem with this scenario is if System A changes its Metadata that it ASBO1 , all the three mappings needs rework. Also with the addition of more systems this means higher complexity.An alternative is to use a standard generic object (say GS1 message). System A maps to the GBO and System B C and D also maps to the GBO. essentially System A acts as a publisher of the message and System B, C and D are subscriber to the GBO. Moreover new systems in the landscape can simply subscribe to the GBO. image What it means for XI: In XI we need to create an intermediate Business Service for GBO. A will send message to the GBO and GBO in turn with forward it to all the Subscribers. For each type of message GBO will have a pair of SOAP Communication channels :- SOAP_Receiver and SOAP_Sender. GBO will receive message from A through Communication Channel SOAP_Receiver which inturn will push the message to the SOAP_Sender Communication Channel. Soap Receiver For SOAP_Receiver specify the target URL as: :/XISOAPAdapter/MessageServlet?channel=:: image Soap Sender For SOAP_Sender specify the Default Interface namespace and Interface Name. This is the outbound interface from GBO. image Bang! Now we have a Business service within XI to act as a middleman. Create the ID Configs for Message flow from System A to GBO and GBO to Destination Systems.
To report this post you need to login first.

3 Comments

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

  1. Mathias Deisinger
    Dear Himadri,

    I do like your Post.

    Still, could you explain me the benefits of using the GBO-Approach?

    My concern would be a larger development effort to start and multiplied messages compared to a point-to-point development. Every message coming in, does generate another one, data is persisted twice etc.

    Thanks for your input.

    Mathias.

    (0) 
    1. Himadri Chakraborty Post author
      Hello Mathias,

      As a matter of fact I am yet to convince myself of the GBO approach in XI :-))

      However as for your questions — Yes your points are correct — development effort will be more .. data persisted twice…

      The main advantage of GBO approach is decoupling of interfaces and reducing dependencies.. It helps to build plug and play interfaces.. This is because the source and the destination systems are  communicating with the GBO only ..

      Also if you think this way .. most of the mapping requirement can be covered in one interface only and the other interface might use a simple mapping  1 to 1 [Assuming one intf A-B will result in two interfaces A-GBO and GBO-B – You can keep A-GBO 1:1 ] So development effort will increase but not significantly.

      Thanks,
      Himadri

      (0) 
      1. Mathias Deisinger
        Hello,

        I see your points and the general approach of decoupling is good as well, even decoupling may better be done at the configuration level (?).

        It is a good idea to have one of the involved interfaces to act in a simple way with the GBO, for example a 1:1 relation. There, it gets only difficult to predict which side should it be, meaning which side will encounter less changes.

        Basically, the GBO approach will give you an easier adaption of your flows once a side needs to change for example a message type etc. The question to raise of course is, how often such changes will happen.

        Since we are currently collection position papers and arguement regarding the GBO-Approach, your answer and post are much appreciated.

        Thanks alot.

        Mathias.

        (0) 

Leave a Reply