| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Analytics Server Administration Guide > Creating and Administering the Physical Layer in a Repository >
Setting up Connection Pools
The connection pool is an object in the Physical layer that describes access to the data source. It contains information about the connection between the Siebel Analytics Server and that data source.
The Physical layer in the Administration Tool contains at least one connection pool for each database. You can configure multiple connection pools for a database. Connection pools allow multiple concurrent data source requests (queries) to share a single database connection, reducing the overhead of connecting to a database.
- When you create the physical layer by importing a schema for a data source, the connection pool is created automatically.
- When you create the physical layer for a multidimensional data source, you need to create the connection pool. Each cube can have only one connection pool.
For each connection pool, you must specify the maximum number of concurrent connections allowed. After this limit is reached, the Analytics server routes all other connection requests to another connection pool or, if no other connection pools exist, the connection request waits until a connection becomes available.
Increasing the allowed number of concurrent connections can potentially increase the load on the underlying database accessed by the connection pool. Test and consult with your DBA to make sure the data source can handle the number of connections specified in the connection pool. Also, if the data sources have a charge back system based on the number of connections, you might want to limit the number of concurrent connections to keep the charge back costs down.
In addition to the potential load and costs associated with the database resources, the Siebel Analytics Server allocates shared memory for each connection upon server startup. This raises the number of connections and increases Siebel Analytics Server memory usage.
This section includes the following topics:
- Creating a Connection Pool for All Data Sources
- Setting Up Additional Connection Pool Properties for an XML Data Source
- Setting Additional Connection Pool Properties for a Multidimensional Data Source
Table 6 lists several supported connection types (APIs) with a description of each interface.
CAUTION: It is strongly recommend that customers use OCI for connecting to Oracle. ODBC should only be used to import from Oracle.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Analytics Server Administration Guide Published: 11 March 2004 |