Siebel Repository refers to a subset of tables in which Siebel objects definitions and scripts are stored. These tables are Siebel database tables and contain all the configuration information that is shown in Siebel Tools. So Siebel Tools helps as a user interface to look at the object definitions stored in the database. All the object definitions are modified or added using Tools.
Note that, all the initial Siebel repository definitions that you would see in Tools get populated during the installation.
Just to illustrate that these object definitions are stored in the database, we can run a simple query on the Siebel database. (You can run this on Local DB also. See how to connect to Local Database)
Example:
select * from siebel.S_BUSCOMP; — This lists all the business components that are defined in Tools.
select * from siebel.S_APPLET; — This lists all the applets that are defined in Tools.
Select * from siebel.S_PROJECT; –Lists all the Projects defined in Tools.
Note that, all the initial Siebel repository definitions that you would see in Tools get populated during the installation.
Multiple repositories can exists in Siebel but only one can be active at a time. In Siebel Tools if you select the object type “Repository” on the object explorer, you could see multiple repositories listed but only one of them will be active.
Tip: If you are not able to see the object type “Repository” in Siebel Tools, then go to View => Options => Object explorer and select the object type “Repository” to show up in Siebel Tools explorer.
Importing and exporting of repositories is done using the Database Configuration Utility. Multiple repositories are created using this Database Configuration Utility while either backing up or importing from other environments. Example: Moving all the repository definitions from Development environment to Testing Environment.
Now that we know where these object definitions are stored, we will next learn where these object definitions are compiled and how it gets used by Siebel Application.
