Siebel Basic

Extension table may be 1:1 realation table to the base table or a 1:M relation to the base table.

1:1 extension table and the base table are logically considered as a single table.

Par_row_id will be the foriegn key.

We can not create an extension table with an intersection table

Using picklists and MVGs. MVGs require join field and link as prerequisites unlike picklists where just a join is enough.

We can see the Business Services Client also. These are called Client Business Services we can see them in Business Service Administration Screens. We can write the script for the BS in the client itself. After writing the BS there is no need to to compile those BS's.

The basic factors for performance decrease in views will be. more number of applets. which led to many links. and more joined fields in a single applet. MVG's which do not have the primaries set.

In an application, we see a page tab let say Account. Below that we have let say My/My Teams/All Accounts. Each has a form applet showing account name, address etc. Related to this we have several tabs like account address, account profile?clicking on which show us accounts detail in that specific area.

So the Account is Aggregate category. My /my teams/all is Aggregate View?These tabs which will show details of Account is Detail Category. So any child object of a aggregate category showing details of an entity is Aggregate category.

S_PARTY is the base tables and S_CONTACT,S_ORG_EXT,S_POSTN, S_USER are now extension tables. Siebel 6.x was dedicated application while from Siebel 7.x onwards we can access Siebel application via web.

not only s_party table but also physical user interface layer will not be there in 6.x

Genbscript stands for generate browser script. genbscript is used to generate browser scripts from command line interface.

Genbscript is used to generate browser scripts. It is created on application server using the srf files. The genB files generated on application servers are then transferred on the webservers.

i think it is basically for improve the performance.bacause of its inner joins

During upgradation it will cause problem if we extend base tables.More over if it is necessary u can go for extension tables

EIM : It is batch mode Integration. When data valume is large then we have to go to EIM

EAI : It is real time Integration. When data valume is small then we have to go to EAI

Eapps.cfg file means swse.

This significance is which application should point to which object manager.

eapps.cfg is a single configuration file which contains configuration information,connection information,login and security settings.

it alloes the SWSE to communicate with siebel server.

Virtual Business Component is used to display the data from another Legacy database , in the Siebel UI,without actually updating the siebel database.

which in a way helps to display the required details,as well as help us with storage limitation at siebel db end.

The Major differences between siebel 7.x and 8.x

1) Siebel 8.0 has introduced Task UI for task automations.

2) Siebel 8.0 has Object Level check out which was not possible before.

3) Business user properties have become drop down list in tools and hence no need to remember syntax for each

Load balancing is maitained by the Gateway server using the third party software Resonate Central Dispatch.

as mentioned above siebel load bal is done by third party software such as Resonate Dispatch manager....or can be done with the help of lbconfig.txt file,which is generated at siebel server and is place in webserver.which helps in identifyin the concerned OM..and transfer the request as per the load too.....read in supoprtweb....nice document is given for it.

Primary Id Field will be stored in the Parent BC.

The absolute meaning for Primary Id: introduction of foreign key of child in Parent. Means pointing all the primary id to it's all child records.The sql engine need not search whole table instead it can point to those already available. Purely database concept.Eliminating the second query on DB.

In Siebel the text that is displayed on the screens and views are stored in the repository and compiled to an SRF file. This includes the names of every screen, views and fields. When you display a page the server uses the SRF file to determine which fields to show and what test (strings) are associated with each fied. This model of keepijng the strings from the view definition is called symbolic strings.

uses

Reduces the redundancy

Simplifies maintenance because only you have to maintain one string for a given Term

Reduces the localization costs, Time and inconsistences.

The syntax for running genbscript is:

When you run genbscript.exe, all browser scripts in the repository are generated. They are placed in a directory that you specify using the destination directory parameter (dest_dir). The genbscript.exe utility is located in:

siebsrv_root/bin or client_root/bin

genbscript config_file dest_dir [language]

For example:

genbscript c:sea15022clientinenuuagent.cfg c:sea15022clientpublicenu enu

S_PARTY Table is the Base Table for all the Party related tables.

S_ORG_EXT

S_CONTACT

S_USER

S_BU

and etc.

the party tables can have the implied joins. the party related BC's have the S_PARTY as the base table. so, any of these tables are extension tables.

S_PARTY table is the base table for P O P(Person, Organization, Position) tables. the above mentioned tables are examples of POP tables. these tables have implicit join with S_PARTY table. row_id of S_PARTY table is the par_row_id of P O P tables.

This property determines whether or not siebel will override the sort specification and if so determines the sort that will be applied to the BC for All or Manager's view. The values are TRUE, FALSE or NORMAL

NORMAL --uses BC defined sort specification

True --Overrides the BC osrt and Uses the U1 index

False - Removes all sorting.