Diffrence Between EBC & VBC

EBC VS VBC

Base Table:

·         EBC: EBC is based on external table and uses data source defined on BC and Table to retrieve data.

·         VBC: VBC has no base table and it is based on special class. It uses a Business Service to retrieve data.

Business Layer VS Database Layer:

·         EBC: While creating EBC you import external table definition into Siebel which results in a proxy table being created in Siebel which points to external table so we can say that EBC integrates Siebelto external applications at Database Layer.

·         VBC: No table is involved in creation of a VBC and we need to use either Vanilla BS such as XML Gateway service or custom BS that will retrieve data through Siebel Business Layer.

Purpose:

·         EBC: The purpose of an EBC is to view, update, insert and delete data available in external database. It is always used to integrate with external applications.

·         VBC: The purpose of VBC is usually to view external data that we don’t want to store in Siebel. It is not necessary to use VBC only for integration. For example If I want to view Product Configurator information in typical Siebel Applets and Views then I can use VBC to achive this.

Effort:

·         EBC: It is very easy to create and configure EBC. You just need to import external tabe definition and after that you can use usual Siebel Configuration techniques and create BC, Applets and Views based on EBC without any difficulty

·         VBC: You have to write script for handling each and every event that you want your VBC to support such as Query, Insert and Init etc. So, I would say effort required is greater in VBC

I have tried to list the difference between EBC and VBC in layman’s language. If anybody thinks that they have more relevant and better differences than listed above please feel free to voice your opinion. Your valuable comments are always welcomed.

Virtual Business Component

Virtual Business Component (VBC)

VBC Provides the ability to display and manipulate non-Siebel data from within Siebel applets without storing it in the Siebel database.

A virtual business component (VBC) provides a way to access data that resides in an external data source using a Siebel business component. The VBC does not map to an underlying table in the Siebel Database. You create a new VBC in Siebel Tools and compile it into the siebel.srf file. The VBC calls a Siebel business service to provide a transport mechanism.

You can take two approaches to use VBCs, as

§     Use the XML Gateway business service to pass data between the VBC and one of the Siebel transports, such as the EAI HTTP Transport or the EAI MSMQ Transport.

§     Write your own business service in Siebel eScript or in Siebel VB to implement the methods.

Advantage of using VBC:

·         Display and manipulate non-siebel data from within Siebel applets without storing it in the Siebel database.

·         New class of business component based on data stored outside of the Siebel database

·         Defined and behave like standard business components.

External Business Component

External Business Component (EBC)

External Business Component (EBC) is another way of integrating Siebel with External Applications. It is another tool available at your disposal to achieve integration.

EBC as really easy and robust way to integrate Siebel.

• You get a DDL of a table located in external database.
• Import that into Siebel tools and a table is created in Siebel pointing to external table.
• You create a data source to connect to external database.

Then you do the usual configuration of creating a BC, BO, View and Applets based on that Table.

In EBC we create a pseudo table structure within the Siebel schema using the External Table Schema Import Wizard, create a BC based on this table and then create an ODBC connection to the external table to fetch the data from the other database and display it in the Siebel GUI

When you access that view Siebel in real-time using that data source connects to external table and displays you the data. You even have option to update, insert and delete records from Siebel.

Limitations:

1. If you import a database view instead of DDL then you cannot update or inserts records.
2.  Joins to base tables in EBC usually don’t work
3. External database must be accessible directly to Siebel
4. Performance can be an issue if database connectivity is not good

Advantages:

1. You can integrate with external application with minimal of effort.
2. Siebel BC can base joins on External table and display information
3. You can import tables from different database such as DB2, MS SQL, Siebel Analytics.

Installation and Configuration of open UI

Download 

1.Go to Oracle Delivery Cloud and sign in 
2.Select ‘Siebel CRM’ as the Product Pack and an appropriate platform. You’ll still, for some infuriating reason, find 8.1.1.x under 32-bit Windows and 8.2.2.x under 64-bit Windows. Very odd 
3.Download the 5 ZIP file components of the installation and unzip them all to a common folder 
4.Open up a command prompt, as administrator, and CD to the unzip folder 
5.Set the JAVA_HOME variable, if required. For example: set JAVA_HOME=”E:\Java\jre6? 
6.Run snic.bat 
7.Create a new image, patch set 
8.Go through the usual process of selecting desitnation, platform and components and pick one or more languages 
9.Though it looks like the JAVA process has frozen / crashed, it’s now unzipping the JAR files into appropriate installers 


Install 

1.Installation is the same as you would expect, if you have installed 8.1.1.8 or 8.2.2. Check out my earlier article for some gotchas on the new installation process 
2.You’ll still get the stupid “you’re about to install into a non-empty directory” message. For a patch? Really? 
3.The patch process also takes ages. This, I suspect, is because the installer recognises it’s own instability and does a ‘backup’ (i.e. OS level folder copy) of the entire SIA / SEA folder before it does anything. I still think Oracle have taken a huge step backwards with the clunky and unreliable installer 
4.Once you’ve installed Enterprise, Web Server, Web Client and Tools (very important!) you’re ready for the next step 


Enable Open UI 

1.First up, you won’t find the instructions for enabling OpenUI in the patch documentation. Instead, refer to MOS article 1499842.1 for a Deployment Guide for Open UI 
2.Unzip ‘OpenUI_Base_8119.zip’ from within the Siebel Tools REPPATCH folder. Here you’ll find instructions on what projects to lock and a .BAT file to import all the appropriate SIFs to enable OpenUI
3.Lock the projects, create the new Reports project then edit the preferences file appropriately – it’s all documented in the instructions 
4.Run the import batch file and check the result in the Notifactions\Log folder. I chose ‘Import All Packages’ to save time. This seemed to work perfectly first time though it took forever as each SIF is imported individually, using a new Siebel Tools process 
5.Perform a full compile of the SRF and deploy to your server environment 
6.Now you have two choices – clone an existing OM (recommended) or update an existing one to use OpenUI in place of HI. I went for cloning as, though it’s more involved, it allows me to access and compare my existing HI OM 
7.Personally, I used the server manager scripts that were generated from the mergecfg.exe tool to create the OM. I first created a new OM component then used the scripts to update the partameters to match those of the existing Sales (SSE) OM component 
8.In the parameters for the new OM, set the new ‘EnableOpenUI’ parameter to ‘True’ 
9.In IIS, create a new Virtual Directory for your new OM and create appropriate entries in eapps.cfg to point to it. I called my OM ‘SSEOUIObjMgr_enu’ and the Virtual Directory and eapps entry ‘sales_openui_enu’. You can use the editmetabase.exe tool in the SWE bin folder to do this (metabaseedit.exe sales_openui_enu E:\sba81\SWEApp\BIN\ENU\eapps.mtb) 
10.Restart everything, just to be sure 

The advised high-level roadmap for customers follows: 

1. Upgrades to a release compatible with Open UI. 
2. Implement Siebel 8.1.1.9 or 8.2.2.2 or above. 
3. Apply QF’s applicable to the release 
4. Migrate from SEA to SIA if on a SEA release. 
5. Import Open UI related SIF files. 
6. Read FAQs and other release documentation provided for the migration. 
7. Add an object manager for the UI, and set it to Open UI using the Open UI enablement settings. 
8. Test the upgraded deployment on HI and SI. 
9. Test the Open UI client rich internet application (RIA) deployment. This can be tested in parallel when running       the environment because it runs on a separate object manager). 
10. Perform user-acceptance testing for all the deployed client UI options. 

Configuration 

Overview: High level configuration steps 
To deploy Siebel Open UI, several steps must be followed. 
1.Download the Innovation pack 2012 release. 
2. Import your seed data using the provided batch files 
3. SIF files for import are provided to enable Open UI and Siebel Mobile features. These must be imported. 
4. Compile & deploy the new SRF 
5. Please bounce your server (or restart your mobile web client) after completion of the import 
6. Add or clone an object manager depending on use of Siebel Mobile or Open UI 
7. Add Virtual directories as needed. 
8. Set the image files based on deployment requirements 
9. Use EnableOpenUI= TRUE (or FALSE) to change between HI and Open UI mode. Set this parameter in the c       client CFG file or in the object manager parameter as needed. 
10. Tune Web Server performance for your environment and web server type. 

Siebel Tools contains the following zip files in the REPPATCH folder. 

1. OpenUI_Base_8119.zip or OpenUI_Base_8222.zip 
2. OpenUI_Mobile_8119.zip or OpenUI_Mobile_8222.zip 

Note: If you have run previous versions of Seed or SIF data import run the steps below to update the information. 

Note: Siebel Tools requires use with Internet explorer 8. 
To import the Sif file, compile and deploy the SRF with the components in the applicable SIF file (named openUI_*.zip) based on the instructions in the readme.txt file contained within it. 

1. Back up your target database. 
2. Create an ODBC entry for the database where you plan to import the seed data into. 
3. Open your tools.cfg file and change SymStrPrefix=X to SymStrPrefix=SBL. 
4. Create new projects as specified in the beginning of projects_and_objects.txt. 
5. Check out or lock the projects specified in the "Projects to Lock/Check Out" section in                                  projects_and_objects.txt. 
6. Ensure language.txt contains the language codes of the languages you need with each code in a separate line. 
7. This step is optional, but recommended. Specify environment information in preference.txt. 
8. You will be prompted for the information for entries that are left blank. 
  - REPOTOOLSBIN=<path, where to find siebdev.exe, e.g. C:\siebel\tools\bin> 
  - REPODATASOURCE=<DataSrc entry from tools.cfg, where to import the objects into> 
  - REPOUSERNAME=<User Name> 
  - REPOPASSWORD=<Password> 
  - DBTYPE=<ORACLE|MSSQL|DB2UDB> (i.e. the data base vendor) 
  - DDLPATH=<path that contains ddldict.exe and ddlimp.exe, usually <Siebsrvr>\bin> 
  - SIEBUSER=<Siebel Username> 
  - SIEBPW=<Siebel Password> 
  - ODBCDATASOURCE=<ODBC DataSource Name> (i.e. the name of the ODBC data source reated in step 2) 
  - TBLO=<Table Owner> 
  - TBLOUSER=<Table Owner User> (only needed for MSSQL) 
  - TBLOPW=<Table Owner Password> 
  - Run import.bat. 
9. Verify the import logs in <package>\Log for all imported packages. 
10. Compile the repository to create a new srf with the new and modified objects, which are listed in projects_and_objects.txt. 
11. Open your tools.cfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X. 
12. Verify the import logs for the seed data in <package>\Seed\<DBTYPE>. 
13. Please bounce your server (or restart your mobile web client) after completion of deployment of the new SRF file. 
14. Perform configurations according to the “Additional Instructions” documents in the subfolders, if such documents exist. 

Adding Siebel Open UI Object Managers To set configuration for Siebel Web Client via server object managers, set the parameters in Application Server Configuration> Component Parameters as follows: 

To render as High Interactivity client: 

1. EnableOpenUI=FALSE
2. HighInteractivity=TRUE 

To render as Open UI client: 

1. EnableOpenUI=TRUE 
2. HighInteractivity=TRUE 

Enabling and Disabling Open UI on clients To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration, set the client parameter, in uagent.cfg in the [InfraUIFramework] section as follows: 

To render as High Interactivity client:

1. EnableOpenUI=FALSE
2.HighInteractivity=TRUE 

To render as Open UI client:
1. EnableOpenUI=TRUE
2. HighInteractivity=TRUE 

Backing up configuration and setting Environment variables

1. Stop Siebel Server. 
2. Stop Gateway Server and make backup of siebns.dat file. 
3. Restart Gateway Server. 
4. Set SIEBEL_HOME environment variable to SES_HOME/siebsrvr directory. 
5. Start Siebel Server and make sure that components are online (assumption: Srf used by Siebel Server is the resulting SRF after SIF import) 

Comparison between Open UI Application and Siebel

1. Custom applications have the advantage over Siebel in user friendliness, because there are things that you could do with current web technologies that are never"possible" in Siebel.

2. Siebel is a vast product with a lot of technologies that allows us to build a descent and usable interface, If the technology is out there, and its supportable, we use it and give the client what they want, of course it has to be supported by good architecture.

3. Instead of switching to another application in order to meet client requirements. Siebel CRM come up with solution which meet the  users requirement.

4. Siebel Open UI has been designed with the same purpose.

Open Ui Frame Work

   Presentation Model

       A presentation model is a JavaScript file that specifies how to handle the metadata and data that Siebel Open UI gets from the Siebel Server

1.Works with proxy data
   Run Time Data
    —Metadata

2.Determines what logic should be applied
    Client side scripting without requiring the need of siebel server

3.Capture behaviors
—   Did the user leave a control

4.Exposes properties
—   Collect field values
  — Set properties

Physical Renderer

A physical renderer is a java script file that siebel open UI uses to build the user interface.

1.Simply builds the UI

2.—Implementation to plug in a third party UI control

3.—The same list of records can be shown as
—A list apple
—A carousel

Siebel Open UI

Open UI is by far the most awaited feature of Siebel 8.1.1.9. Open UI is all about providing a New Standards Based Open Client supporting a multitude of clients and devices. I describe the available features in brief.

Siebel Open UI : (Browser Independent)

       Transforms Siebel deployments into a truly “Open” Platform supporting all browsers not  just IE . It can display data in Web browsers that support Web standards on various  operating systems, such as Windows, Mac OS, or Linux. For example: Internet Explorer,  Google Chrome, Mozilla Firefox, Apple Safari

Siebel Open UI : (Platform/Device Independent)

     Smart, efficient, with a modern look and feel for Desktop Browsers on any hardware platform

         Mobile Browsers on any tablet or smart phone