Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Tools Reference > Siebel Architecture (Basic Concepts) > Application Architecture Overview >
Siebel Repository
The Siebel repository contains tables in the Siebel database where Siebel object definitions are stored. You view the contents of the Siebel repository through the Siebel Tools windows that appear when you initialize Siebel Tools.
The set of object definitions and server scripts defining a Siebel application (such as Siebel Service or Siebel Sales) or set of applications is compiled into a file called a Siebel repository file, or .srf file.
NOTE: Browser scripts are compiled into the browser script compilation folder, which can be specified in Siebel Tools on the Scripting tab under View > Options. For more information on the browser script compilation folder, see Browser-Side Scripting.
The .srf file, when opened by the object manager on behalf of a Siebel Web application, provides the system with all of the information it needs to define interactions with the enterprise data and software users. In its uncompiled form, the set of object definitions is called a repository, and is stored in the database that Tools connects to. In its compiled form, it occupies a single compressed read-only file with the .srf file extension.
The object manager reads the information stored in the repository file on demand as the different parts of the Web application are executed. For example, when the user switches to a specific view, all components that form part of that view will read information from the repository file that determines which data will be presented and in what format. Some components are visual and the configuration information will determine, for example, what applets to show in the view. In the case of non-visual components, the configuration information may determine what data fields this component provides.
The application database contains the actual data for the system, and it also contains some administration information such as the list indicating which views a specific type of user can access. This database can run locally or remotely. The contents of the repository tables are compiled into a binary file that provides fast read-only access to the repository metadata during run-time.
Figure 2 shows the definition of the Contact repository object as viewed in Siebel Tools.
The Siebel database contains both metadata (repository objects) and user data. The database can be populated either through the Siebel UI or a variety of interfaces.
Virtual business components allow data from external RDBMSs and applications to be displayed in the Siebel user interface.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Tools Reference Published: 20 October 2003 |