Data Maps

Data Maps are critical in any Outbound based integration.Data Maps are used to map the Siebel Data to an external Object format and Data Transformation is the basic task in any DataMaps scenario
Data Maps can be implemented through 2 ways..
1.By Using Data Maps Editor
2.By Scripting

Complex Data Maps are implemented through Scripting wherein it requires to check many conditions before being mapped to the external IO.
DataMaps Editor is the most commonly used technique in Data Maps.Data Maps Editor also allows implementing condition based transformation.

Symbolic Strings

Symbolic Strings are used while implementing multiple languages on Siebel.
For Eg: If its required to implement English and French from single repository then Symbolic Strings play a major role.

Symbolic Strings are also used in case if the Same label is used multiple times in the application.It would very easy to change the label and no need to change the label name in all the places
Eg: If the Label "Company" Used in more than 10 places(applets) .All of Sudden we get a request to change the label from "Company" to "Customer" then in general the Develoepr has to spend lot of time on changing the Label in all the Applets.

But in case if we have used a "Symbolic String" for the Label "Company" then the Developer has to just go to the Symbolic Strings Object,Query for the Symbolic String and just change the "Value" property from "Company" to "Customer" and compile the Symbolic String and the applet,you could see the change immediately.Within 5 minutes you are done else you would have to spend more than 30 minutes for all the 10 Applets.

Difference between Proxy Business Service and a Business Service?

Proxy Business Services
-These are the Business Services whose functionality is not defined in siebel but in an External Applciation
-Proxy Business Service gets created in Siebel upon importing an external WSDL.
-Proxy businesss services are used by Siebel to make calls to an external applciation
-Proxy business services does't use any siebel Integration Object
-Before calling proxy business services you need to format the data which can be processed/accepted by the proxy busines service(Datamaps are used)


Business Services
-These are defined in Siebel tools.
-EAI Siebel Adapter is one of the Vanilla Business Service used by siebel
-These business service would work on Siebel Integraion Objects.
-Business Services are created within Siebel and not throgh importing WSDL
-Business Services can be exposed to external Application by means of Webservices

Interview Questions-WebServices

-What are webservices?
-What are the different Types of Webservices?
-What is the difference between Business Service and Webservice ?
-Is it possible to convert a business Service into webservice?If yes what are the steps?
-How do you deploy a Webservice ?
-Can we have a Worklfow process as Webservice?If not why ?If yes how do you deploy a workflow as Webservice?
-What is the difference between Inbound/Outbound webservices?
-What are the essentials to create an Outbound webservice?
-How do you configure Outbound wenservices?
-What type of IO gets created on importing a WSDL ?
-What is a WSDL?What does it contain ?
-What are the sections of WSDL? Describe each section?
-Why do we need Inbound and Outbound Webservices ?
-How does an external Applciation access the Siebel ?What are the diffrent techniques available?
-What are the different Objects created on importing a WSDL into Siebel?
-How do you provide a WSDL from siebel to external Application?
-What are secured Webservices ?
-How do you implement webservice security ?
-How do you test webservices ?what are the tools you have used ?
-What is a Proxy Business Service and when do you need a proxy business Service in siebel?
-What are session Based webservices/sessionless webservices?

Few more would be added....

Integration Objects

Hello Folks.

In my previous posts we had discussed on the EAI architecture and brief on the integration techniques.Going forward we start exploring the integration methodologies and the terms used and how they are implemented?

This posting would cover about Integration Objects.
Integration Objects are the major building blocks in Siebel EAI Architecture. IOs are critical and play major role in Data sharing with external Applciaitons. IO's can be called as the reflection of a Business Objects.
Eg:If we have to share the Account details with external application then we have to create an IO based on the Business Object for Account.

EAI Siebel Adapter Vanilla Business Service uses the Integraiton Objects to fetch the Siebel Data from the Siebel Database and converts the Data from BO format to SiebelMessage of newly created Inegration Object Type.
EAI Siebel Adapter is one of the Powerful Business Service capable of performaing various Actions-Qwery/Insert/Upsert/Delete/Execute/Sync
We will go through these "Actions" in later Postings.

Integration Objects are used in EAI worklfows to generate the XML data or Hierarchy Data.
How do you create IO's?
IO's are created through wizard in Siebel Tools.We need to select the required Business Objects/Business Components for an IO. There are various IO User Properties Defined which support special functionality.One of such user Property is "Admin Mode",this allows to Delete a record even if the BC level "No Delele" property is set to "True".

There are two types of Integration Objects
-Siebel Integration Object
-External Integration Object

Siebel Integration Objects are created within Siebel Tools and have the Type as "Base Object" and these would be used by the EAI Siebel Adapter to perform Query Data,Insert Data,Upsert,Delete,Execute(Update/delete/Insert)

External Integration Objects are not created in Siebel tools by using Siebel Business Objects.External Integration Objects have type "XML Object" and created in Siebel Tools when you import a WSDL/XML Schema provided by external Application. These IO's are used to provide the data in a format as expected by the external Application.