Siebel EAI Interview Questions

Here I am sharing few Verygood Questions which would cover most of the areas under EAI.Hope this would be helpful

-Explain the Integration architecture?
-What are the EAI value Maps ?
-Diffrenece b/w runtime Events and worklfow policies?
-Whay do we need Database Triggers?
-Why do we need the Worklfow Monitor Agent?
-What is the Diffrence b/w Workflow Process Manager and Monotir Agent ?
-How do you debug a worklfow in a live environment ?
-What do you mean by Process Property and where do we use them?
-What are the various integration Techniques available in siebel?
-What is the difference betwen Siebel repository and SRF file ?
-Is it possible to Deploy and Activate the workflow Directly to the Application?
-what happens when we clickon the Sychronous Button for an IO?
-Why do we need Integration Objects ?why cant we integrate wihtout having IOs?
-Siebel IO and External IO are the same?
-How do you create an External IO?
-Why do we need Datamaps ?and what are the basic needs to have a Datamap?
-What are the IO user Properties?Exlplain with examples?
-What are webservices?Why do we need them ?
-What is an Inbound Webservice and Outbund Webservice?
-How do you implement Inbound Webservices and Outbound Webservices ?
-How do you achieve "Webservice Security?What are Security mechanisms available in Siebel?
-Can we have a workflow Process as Webservice in Siebel ?If not Why ?
-How do you Deploy a webservice in Siebel?and how do you share the Webservice Details with external Application?
-How do you access External Data from Siebel?
How do you integrate with Siebel?
Exlpain the Basic Needs for any basic integration scenario?
Continued...

How easy is siebel???

How Easy is Siebel??? Good Question to answer :-)
Siebel is easy when you understand the Siebel Datamodel.

Data Model is the core area of Siebel upon which the Siebel has been Designed.Data Model covers the Table structure/Object Structure.There are approximately 3200 Tables in Siebel.
Unlike any other Java based Applications we don't have to Develop new things like Applet/Screens/Views by means of Scritping.Here in siebel we are doing customization of the Application which has been designed to meet certain Industrial Requirements like Call Centre,HealthCare,Loyalty,Order Management,Sales,Insurance etc....

As part of Customization we might have to customize an Existing Object/extend Column/join/link to meet the requirements. Here customization means it doest't mean that we always work on the Vanilla(Vanilla means OutOfthe Box Objects provided by Siebel). As part of Customization we do have to create new objects to meet requirements.

Siebel is easy when you work on its tough to imagine and expect the same behavior while implementing. Hence I advice to practically work on Siebel Sample Database to learn Siebel. Its highly impossible to learn siebel by just going throgh the Standard PPTs/PDFs.You may know the concept but you will not how this concept works practically.

As you start work on the Siebel you would end up in so many errors which you feel are tough to solve but would be very simple when you have clear undrstanding of Object Definitions like Applet/Object/Join etc?
If you are still not Clear my Blog is here to Help you out :-) you can post your qweries.

So To begin with just go through all the materials that you have collected (ppts/pdfs) and then start practically exploring each concept in you Sample Database.
Siebel is not very tough its you who has to make it simple!!!
Happy Learning Siebel.

Siebel /Salesforce CRM

Siebel CRM

The Leader in the CRM market.Bit complex in implementation and requires experienced proffessionals to run the show.Siebel offers CRM solutions for various industrial verticals with its ready-to-use (with less customization) application.
-Highly Process Oriented
-Higher Implmentation Costs
-Need to buy license to Customize/deploy/Use.

Salesforce
-Moving faster easy to implement.
-OnDemand
-Lesser Implementation Cost
-Lesser Process Oriented
-Pay As you Use

Continued....

Diffrence B/W Siebel Config and Siebel EAI

Any Siebel Implementation can be grouped into 2 basic Parts from the Developer Point
1.Siebel Configuration
2.Siebel Enterprise Application Integration

If you ask me what is siebel Development I would say It would be better to use "Customization" instead of "Development".Yes its the Customization that we have been doing for the ReadyMade Tool/Client. We just make changes to meet the Customer Requirements/Needs.

1.Siebel Configuration
What is siebel Configuration? Siebel Configuration is concerned with the Customization of the Siebel Application Side to meet the Needs.Configuration would cover
-Creating Applets
-Creating Views
-Creating Screens
-Creating Joins
-Defining Links
-Creating Business components
-Creating Business Objects
-Extending Tables/Creating Tables
-MultiValueGroups/Links
-Symbolic Strings
-Picklist/PickMap/LOV
These are the few Basic Areas which would come to your mind when you think of Configuration.Under Siebel Configuration we always consider the Application Side Changes.But Siebel Configuration would have great impact on the Integration Side as we would be using the BCs and BOs which have been modified as part of the Configuration process. Any change in the BCs,BOs would directly have an impact on the Integration Objects created.Hence its always mandatory to keep the BCs' and the BOs in sync with IOs.

2.Siebel Enterprise Application Integration
The Siebel EAI Depends on the Configuration part.Under Siebel EAI we would concentrate on the Data Mapping with External Application,What data shared?,Data format ?etc. Application Integration would explore the Siebel functionality to external Application by means of deploying webservices and also it can consume external application WSDL(webservices description Language) and call the External Applciation by means of Proxy Business Services(Business Services would be discussed Later).
Under EAI we would work on
-Integration Objects
-Webserices
-Worklfows
-Business Services
-WSDLs
-Symbolic URLs
-Siebel Transports
-Siebel Subsystems

Want to Learn Siebel EAI??..Part3

EAI Posting continued.....

2.What kind of Data Shared?
The Data shared is a major issue for any integration.First the Data need to be indentified for the sharing.What Data should be stored and what data not to be shared?. We need to look at
1.Siebel Entities
2.Business Objects
3.Business Components to identify Data Sharing

Identifying the Business Objects and the Business components is very critical for the Data Sharing. The DataSharing in Siebel EAI happens by means of Integration Objects which are used by the EAI Siebel Adapter,DataMaps and other EAI Transports. The Integration Objects are just the reflection of the Business Object and the Business Components hence we need to concentrate more on BO and BC for any Integration Object.

Integration Objects would be discussed in depth in later part of the posting.