Difference - Siebel Message/Integration Object/XML Hierarchy
By neel | May 11, 2008
This can easily be an Interview question
Disclaimer:
The answer to the question is based on my experience and knowledge. Use it at your own risk only after verifying.
Integration Object (IO): IO is a physical entity in Siebel tools. You can actually go in Siebel tools and create, modify, delete an IO. You can see IO under “Object Explorer > Integration Objects”. IO is very similar to a Siebel Business Object (BO) it contains Integration Components (IC) and IC contains Fields. Here is how it is mapped
Integration Object (IO) - Business Object (BO)
Integration Component (IC) - Business Component (BC)
Fields - Fields
Use of IO and various Business Services in conjunction results in formation of Siebel Message or XML Hierarchy.
Siebel Message: It is a name given to an output or Input that you get/give when you use IO and EAI Siebel Adapter BS together. SIF file which is created as result of export of objects is also an example of Siebel Message
XML Hierarchy: It is name given to an output or Input that you get/give when you use Business Services like XML converter, EAI XML Converter, EAI XML Read from File
To understand the difference between Siebel Message and XML Hierarchy you have to understand the structure of IO thoroughly.
Let’s have a look at various fields in IC of an IO. Look at the screenshot below

There are 3 fields (Name, External Name and XML Tag) that you can see. If you know the purpose of these fields then it is easy to understand the difference between Siebel Message and XML Hierarchy.
Name: This field is used when Siebel is creating a Siebel Message for example if you Use EAI Siebel Adapter BS - Query method then you get Siebel message as an Output
External Name: Name of the BC field from which the data is going to be pulled and inserted in Siebel Message
XML Tag: The tag name which is going to be given to this field when Siebel Message is converted in XML Hierarchy.
So the basic Differences between SiebelMessage and XML Hierarchy are as following:
- IO is a must to create SiebelMessage but you don’t always require an IO in case XML Hierarchy
- Name field of IC Fields will be used in SiebelMessage and XML Tag field will be used in XML Hierarchy
- Siebel Message is Parsed based on Structure of IO but XML Hierarchy is parsed based on XML Rules
- Name Field can have spaces but XML tags cannot have spaces which means that XML hierarchy will never have a Tag with space where as Attributes in Siebel Message can have a space.
Technically speaking both Siebel Message and XML hierarchy are XML.
I just hope I don’t end up confusing you guys. If still you have some doubts let me know I will try to further clarify with examples.
Related Posts
Categories: Siebel EAI |
Subscribe by Email

(2 votes, average: 3.5 out of 5)
June 19th, 2008 at 8:14 pm
I had created a BO and I want to use this BO in the IO.
Could you please explain me the procedure, how to use a BO in the IO. In BO there are 2 BC’s.
June 19th, 2008 at 8:19 pm
You can have a look at that.
But you will need to become member to download it. It is in the Download section of the forum
the url of the forum is http://forum.siebelunleashed.com
July 8th, 2008 at 3:42 am
Hi Neel,
Please explain the differece between the PropertySet & Siebel Message.
If my understanding is correct : In Siebel msg also we have hierarchy of name- value pair & In the propertyset also we have the same hierarchy of name - value pair.
Thanks in advance!
- SiebelQuery