Skip to end of metadata
Go to start of metadata

The CMS system database is used to store BI platform information, such as user, server, folder, document, configuration, and authentication details. It is maintained by the Central Management Server (CMS), and is sometimes referred to as the system database or repository.

During installation of BI platform you are asked to which database you want to connect. Once you select a database, the setup program creates the tables and views necessary to utilize the database as the system database. During the installation, the default servers, users, groups, and content are added to this database.

For the Linux pattern, a Sybase ASE 15.7 database client and server was used. Before deploying our pattern we requested that a database user and schema be created for our CMS database. The database users will require reading and writing rights, as well as table creation rights on the schema. This pattern reviews the Sybase client configuration in Sybase Middleware.

The CMS database is a central and critical component of the Business Intelligence platform architecture. A single database server is used in the Linux pattern to host the CMS database, but in a production environment, redundancy and appropriate database recovery policies are necessary.

For more information on the CMS database and other servers within the BI platform, see the BIP 4.0 Administrators Guide.

Each BI platform environment requires a unique set of users/schemas. If you use an existing schema, the data is overwritten and your existing system is lost.


Below is an example of how you could name your user accounts/schemas. The user name and schema are often the same.

Stage of Deployment

CMS User/Schema Name

Audit User/Schema Name

Proof of concept (POC)

BI4CMSPOC

BI4AUDPOC

Development

BI4CMSDEV

BI4AUDDEV

Quality Assurance

BI4CMSQA

BI4AUDQA

Production

BI4CMSPROD

BI4AUDPROD


Details on the Sybase ASE 15.7 database used for the CMS database in our pattern

Two requirements for Sybase ASE are the following:

  • You must use a Unicode character set.
  • You must set a page size of 8 KB.

    CMS Database Overview for our Linux pattern

    Version

    Sybase ASE 15.7

    Database Name

    Cms57u05

    Character Encoding

    UTF-8

    Page Size

    8KB

    Server Name

    Cms57u05

    Machine

    Cmsdb05

    Schema

    SAPCMS

    Username

    SAPCMS



    For our database server we used the system parameters outlined below. These are not the official recommendations; you should consult with your Database Administrator before making any changes to your database servers.

    Data Cache [buffer pool]: Make 250MB memory available

    EXEC sp_configure 'max memory', 500000
    go
    EXEC sp_cacheconfig'default data cache', '200.000M'
    go


    Procedure Cache

    EXEC sp_configure'procedure cache size', 27680
    go


    Lock Granularity

    EXEC sp_configure 'lock scheme', 0, datarows
    go


    Parallel Processing: set number of engines = number of CPUs

    EXEC sp_configure 'max online engines', 8
    go
    EXEC sp_configure 'number of engines at startup', 8
    go


    Number of Connections

    EXEC sp_configure 'number of remote connections', 100
    go
    EXEC sp_configure 'number of remote logins', 100
    go
    EXEC sp_configure 'number of user connections', 100
    go


    Number of tablespaces

    EXEC sp_configure 'number of devices', 25
    go


    Number of open objects, indexes, and partitions

    EXEC sp_configure 'open objects', 2000
    go
    EXEC sp_configure 'open indexes', 4000
    go
    EXEC sp_configure 'open partitions', 3000
    go


    For more information on tuning your database server, refer to the vendor's documentation. Sybase ASE 15.7 Documentation includes the documentation we used when setting up this pattern.
  • No labels