Bookshelf Home | Contents | Index | Search | PDF |
Siebel Analytics Server Administration Guide > Setting Up Disconnected Analytics > Creating the Disconnected Analytics Repository >
Create the Business Model and Mapping Layer of the Disconnected Repository
After you build the disconnected Physical layer, you can build the Business Model and Mapping layer. The Business Model and Mapping layer for the disconnected repository is similar to the Presentation layer of the network-based Siebel Analytics repository. The following list includes information about creating the Business Model and Mapping layer for a disconnected repository:
- The source tables for disconnected logical fact tables will be different from the fact tables in the network-based Analytics repository. The source tables in the disconnected repository point to the disconnected Physical layer tables. The source tables in the network-based Siebel Analytics repository point to data warehouse tables.
You can copy the logical layer objects from the Siebel Analytics repository, paste them in the disconnected Business Model and Mapping layer, and then change the source tables. The difference between the Siebel Analytics source tables and the disconnected source tables is the presence of aggregation tables in the Siebel Analytics Physical layer.
- Dimensional hierarchies should be the same in the Siebel Analytics and disconnected repositories to achieve the same drill-down behavior.
- Administrators can choose to remove some of the lowest level granular data to make the data sets smaller. For more information about data sets, see Defining Data Sets for Disconnected Analytics.
For more information about creating the Business Model and Mapping layer of the Siebel Analytics repository, see Creating and Administering the Business Model and Mapping Layer in a Repository.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Analytics Server Administration Guide Published: 11 March 2004 |