Now we have a high level idea about Siebel CRM.
With that information we shall proceed forward and look into the various technical responsibilities involved to build a Siebel CRM enterprise application.
Once we are clear on this it would probably pave way for us to dive in to start off with the Siebel Architecture.
For better understanding of the framework let us categorize the scope into layers
- UI Layer - This layer is responsible for displaying data in Siebel Screens. All the business process involved at the business layer would be applied in this layer. Eg of Business process: When the user clicks on a new button it should enable user to enter values, When a particular record is saved appropriate action should be performed etc.
- Database Layer – As the name suggests this is the place where all Business data resides. The database can be anything like Oracle, DB2, SQL server etc. The data that is stored and queried from the databse as per the configuration done in the UI layer. It is not advisable to perform any action like deleting or creating data directly in the database since it might violate the Siebel data model.
- Integration Layer – This layer is responsible for sending and receiving data from Siebel System to any other external system. To understand better, Any other external system might be expecting data from siebel system where in all the business rules has been applied by the UI layer. In the same way Siebel might be expecting data from any other external system so that it can apply the business rules.
- Business Intelligence Layer – First of all let me define the term business intelligence. It is nothing but an intelligent way of doing business by studying the existing customers which would in turn help the business to frame the business. Sounds similar to Abraham Lincoln’s definition of democracy?(Government of the People, For the People and by the People)??? … Yes absolutely. Very important layer for any technology since this is the place where place where business is decided. The ultimate goal of everything which we have talked about and everything which we are going to talk lies here.
In any Siebel implementation we have various roles and people taking care of different things. Here we go with a quick high level overview and reading the upcoming blogs would make things much more clear.
Siebel Administration - Siebel Administrator will be responsible for taking care of administrative activities namely installation of Database, Siebel Server(Gateway, Web and Siebel), Load balancing, Generating DB templates, Extracting Database for individual developers as one time activity. The need of a Siebel administrator shall be experienced throughout the project life cycle and not restricted to above mentioned tasks.
Apart from that he would be responsible for Compilation of srf, Addressing issues related to server, taking care of post deployment activities whenever new build is deployed.
Siebel Configuration - This go hand in hand with the definition mentioned above for UI layer. Siebel Configurator will be responsible for configuring things, applying business rules, decide upon which data should be available for various actors etc. withing the siebel application. To achieve the result a Siebel Configurator will be making use of various Siebel Objects like Applets, Business Components, Views, Screens, Workflows, Business Service etc. about which we will see in a dedicated post.
Siebel Integration - This is popularly known as Siebel EAI(Enterprise Application Interface). We already know what an enterprise is and Interface is nothing but connecting to someother system from our Siebel Application. To make it precise, Lets say the Siebel configurator has already applied the required business rules and Siebel EAI is responsible for sending this to an external system. It is also responsible for getting in data for the rules to be applied. There are few Siebel objects like Integration Object, Workflow, Business Service, Proxy service etc. involved which will be taken care in future posts. For now, it is enough for you to know that there are various methodologies using which data can be send out and received in Siebel system namely Webservice, JMS, HTTP, MQ etc.
Siebel Analytics(OBI) - Siebel Analytics correlate with Business intelligent Layer. To provide reports to the business users as per the needs. Now Oracle is advising people to use OBI(Oracle Business Intelligence) since it is more flexible. The Siebel configuration rules will be applied and data would be stored in the database as per the rules. Using this data reports would be generated which would help the Business users to decide on what needs to be done in the future to make more profit. At this point of time I don’t want to confuse you guys by using terms such as OLAP, OLTP, Staging etc. We will see about those things in different blogs.
Note: Though most of the terms used in the above explanation are news, it would be addressed in upcoming post. For eg. Gateway, Web, Siebel server, Siebel Objects, Web service will be take care in the blogs which would be posted in near future. I am planning to get deeper into each of roles one by one. Suggestion are welcome if you find something weird in this approach.
Once you are clear on above mentioned facts we shall move a bit technical and the inception would be with Siebel Architecture.