Next in series >>
As we all know the term Integration Object in Siebel is synonym to Siebel EAI. Where ever there is Siebel Integration, Integration Object will come into picture. This series of post is aimed at exploring Siebel Integration Object in depth. We will start from very basic and then go on to the advanced topics of Integration Component User Keys and User Properties. I am not sure how many posts will be there of this series but I will try to segregate and keep it simple. So, Let’s start:
What is Integration Object?
You can read the definition from bookshelf so here I will give you my answer to the above question:
Integration Object is an object used to define or explain Siebel Objects such as Business Component and Business Objects. In other words IO is an object providing meta data about Siebel Objects in form of XML.
What is the use of Integration Object?
Primary use of Integration Object is integration with external applications but is not limited to that. I have already shared examples where IO has helped to improve performance and to complete day to day configuration requirement. If you are creative you can use IO anywhere.
How does an IO help in integration?
As mentioned earlier Integration Object provides meta data about Siebel Objects. IO provides this meta data in form of XML tags which is Industry standard to exchange data between application. With the help of IO I can describe my BO and BC as an hierarchical XML structure and easily exchange information with various application.
What is this Internal and External IO that I hear about?
You can read the basic difference by clicking here but we will explore this in depth, later in the series.
If you have any questions that you think should be part of this list, feel free to comment and I will add it in list here or other posts of the series. In next part of series we will dig deeper and understand technical details about Integration Components.
Next in series >>