Page tree
Skip to end of metadata
Go to start of metadata

This documentation page is part of a legacy method of installing CAST AIP. This documentation is no longer maintained and may contain obsolete information. When using AIP Console, AIP schemas are installed automatically when creating an application. Refer to Installation and Configuration and Add a new Application.

On this page:

Target audience:

CAST AI Administrators

Summary: This section provides full details about how to define installation configuration settings for your chosen RDBMS prior to commencing the installation of the Storage item (i.e. the databases and schemas) using CAST Server Manager. It is divided into chapters that correspond to each RDBMS.

Please also note that if you use the Application Analytics platform or Additional Analysis Platform installation options, it is not possible to define separate tablespaces/data spaces for each installed item. Instead, one tablespace/data space will be used for all CAST databases. If you require separate tablespace/data space for EACH CAST database, please install each database individually (i.e. in standalone mode as described in Install CAST AIP schemas).

CAST Storage Service

If you are using the CAST Storage Service, no installation configuration settings need to be adjusted. However, you can use either dedicated Data (for Tables and Indexes) and Temporary tablespace or the default pg_default and pg_global tablespaces on your CAST Storage Service. You can also, optionally, choose to store Tables and Indexes in separate tablespace.

If you are planning to use user defined tablespace rather than default system tablespaces, this tablespace must be created in pgAdmin or by using scripts before you run CAST Server Manager.

Database Creation dialog box

For the CAST Storage Service, the Database Creation dialog box enables you to choose the Data and Temporary Tablespace for your schemas. You can also, optionally, choose to store Tables and Indexes in separate Tablespace.

Option "Use different data space for Indexes and Tables" NOT selected

Data Tablespace Name

Select an existing Data Tablespace for tables and indexes. By default this is set to the pg_default tablespace, but this can be changed by selecting a new Tablespace from the dropdown list. The system tablespace pg_global along with any user defined tablespaces are offered in the drop down list.

    • If you want to use dedicated Data Tablespace just for CAST components - this must be created prior to using CAST Server Manager.

Temporary Tablespace Name

Select an existing Temporary Tablespace for temporary information. By default this is set to the pg_default tablespace, but this can be changed by selecting a new Tablespace from the dropdown list. The system tablespace pg_global along with any user defined tablespaces are offered in the drop down list.

    • If you want to use dedicated Data Tablespace just for CAST components - this must be created prior to using CAST Server Manager.

Option "Use different data space for Indexes and Tables" selected

If you prefer to store the schema's Tables and Indexes in separate Tablespaces (as oppose to in one general Data Tablespace), you can select the option Use different data space for Indexes and Tables. This will display additional fields entitled Table Tablespace Name and Index Tablespace Name along with the default Temporary Tablespace Name field.

Table Tablespace Name

Select an existing Data Tablespace for tables. By default this is set to the pg_default tablespace, but this can be changed by selecting a new Tablespace from the dropdown list. The system tablespace pg_global along with any user defined tablespaces are offered in the drop down list.

    • If you want to use dedicated Data Tablespace just for CAST components - this must be created prior to using CAST Server Manager.

Index Tablespace Name

Select an existing Index Tablespace for indexes. By default this is set to the pg_default tablespace, but this can be changed by selecting a new Tablespace from the dropdown list. The system tablespace pg_global along with any user defined tablespaces are offered in the drop down list.

    • If you want to use dedicated Data Tablespace just for CAST components - this must be created prior to using CAST Server Manager.

Temporary Tablespace Name

Select an existing Temporary Tablespace for temporary information. By default this is set to the pg_default tablespace, but this can be changed by selecting a new Tablespace from the dropdown list. The system tablespace pg_global along with any user defined tablespaces are offered in the drop down list.

    • If you want to use dedicated Data Tablespace just for CAST components - this must be created prior to using CAST Server Manager.

Oracle Server

Pre-installation check list

Oracle Servers have specific configuration requirements that must be met before schema installation can take place. Before beginning the installation process, please ensure that you have carried out all of the following tasks and that the following requirements have been met (more details are available in the Oracle section here: Appendix - RDBMS requirements and configuration).

(tick)

Configure Memory Management on the Oracle Server

(tick)

Configure Disk Management:

  • Create tablespace for a new schema
  • Set the undotbs parameters
  • Deactivate the Archive Log option

(tick)

Ensure that your RDBMS login has sufficient privileges to create a schema

(tick)

Ensure that the Oracle Server instance your are planning to work on is a supported Oracle Server version (see Release Notes)

(tick)

Ensure that all prerequisites listed in the Oracle section of Appendix - RDBMS requirements and configuration are configured and set accordingly

Database Creation dialog box

For Oracle Server, the Database Creation dialog box enables you to define the names and locations of your schema's Data and Temporary Tablespace. You can also, optionally, choose to store Tables and Indexes in separate Tablespace.

Option "Use different data space for Indexes and Tables" NOT selected

By default, CAST Server Manager allows you to choose the location for your Data Tablespace and the Temporary Tablespace.

Data Tablespace Name

Select an existing Data Tablespace for tables and indexes. By default this is set to the CWMLITE tablespace, but this can be changed by selecting a new Tablespace from the dropdown list.

  • It is not possible to select Temporary or SYSTEM tablespace for use with Data.
  • CAST recommends creating dedicated Data Tablespace just for CAST components - this must be created prior to using CAST Server Manager.

Temporary Tablespace Name

Select an existing Temporary Tablespace for temporary information. By default this is set to the TEMP tablespace, but this can be changed by selecting a new Tablespace from the dropdown list.

  • It is only possible to select Temporary Tablespace in the drop down list. As a result, if you want to create dedicated Temporary Tablespace just for CAST, then make sure it is configured as Temporary.

Option "Use different data space for Indexes and Tables" selected

If you choose to store the schema's Tables and Indexes in separate Tablespaces (as oppose to in one general Data Tablespace), you can select the option Use different data space for Indexes and Tables. This will display additional fields entitled Table Tablespace Name and Index Tablespace Name along with the default Temporary Tablespace Name field.

Table Tablespace Name

Select an existing Table Tablespace for tables. By default this is set to the CWMLITE tablespace, but this can be changed by selecting a new Tablespace from the dropdown list.

  • It is not possible to select Temporary or SYSTEM tablespace for use with Tables.
  • This dedicated Tablespace must be created prior to using CAST Server Manager.

Index Tablespace Name

Select an existing Index Tablespace for indexes. By default this is set to the CWMLITE tablespace, but this can be changed by selecting a new Tablespace from the dropdown list.

  • It is not possible to select Temporary or SYSTEM tablespace for use with Indexes.
  • This dedicated Tablespace must be created prior to using CAST Server Manager.

Temporary Tablespace Name

Select an existing Temporary Tablespace for temporary information. By default this is set to the TEMP tablespace, but this can be changed by selecting a new Tablespace from the dropdown list.

  • It is only possible to select Temporary Tablespace in the drop down list. As a result, if you want to create dedicated Temporary Tablespace just for CAST, then make sure it is configured as Temporary.

Privileges granted to new schema user

Please see Privileges granted to the user created during the installation process in Appendix - RDBMS requirements and configuration for more information about the Oracle Server privileges granted to the user created during the installation of a new schema for each CAST database (CAST Management Service, CAST Analysis Service, CAST Dashboard Service).

Microsoft SQLServer

Pre-installation check list

Microsoft SQL Servers have specific configuration requirements that must be met before installation can take place. Before beginning the installation process, please ensure that you have carried out all of the following tasks and that the following requirements have been met (more details are available in the Microsoft section here: Appendix - RDBMS requirements and configuration).

(tick)

Ensure that the rules with regard to case sensitivity and collation are adhered to

(tick)

Ensure that your RDBMS login has sufficient privileges to create a schema

(tick)

Ensure that all prerequisites listed in in the Microsoft section of Appendix - RDBMS requirements and configuration are configured and set accordingly

Database creation dialog box

For Microsoft SQLServer, the Database Creation dialog box enables you to define the names and locations of your Primary and Log Files. You can also, optionally, choose to store Tables and Indexes in separate files away from the Primary File.

Option "Use different data space for Tables and Indexes" NOT selected

By default, CAST Server Manager will offer to create one Primary File in which to store all objects associated with the new database and one Log File for trace requirements.

Primary File & Log File

Logical File Name

Enter a name for the Primary File and Log File. By default this is set to CAST_PRIMARY and CAST_LOG, but these names can be changed by manually entering new names.

  • This name is used to reference the file in any T-SQL statements after the database is created.
  • The name must be unique in the database and conform to the rules for identifiers.
  • The name can be a character or a regular identifier.

Operating System File Path

This is the default path that CAST Server Manager will use for the creation of the corresponding file. You can change this by either entering a new path and filename manually, or using the Browse ".." button to explore the contents of the disks on the machine hosting the server you are connected to.

  • The file path must specify a directory on a Microsoft SQLServer instance.
  • The default path and file names displayed in this field are derived using information taken from the Windows registry on the machine hosting the RDBMS. For security reasons, this information may not always be available or accessible. In this case, no file name will be proposed and it will not be possible to use the Browse button to find a path. You may also see error messages in the log file regarding access to the registry (e.g.: "RegQueryValueEx()" and "The directory does not exist"). These errors are not fatal and the creation of the database will still be possible via manual entry of the path and filename.

    Note that CAST Server Manager does NOT use the properties "Default Data Directory" or "Default Log Directory" (that can be set on the Microsoft SQLServer in Enterprise Manager) to create the default path for data and log files.

File Size (MB)

By default the file size for the Primary File is set to 200MB (CAST_PRIMARY) and 100MB (CAST_LOG), with the option Unlimited to allow for automatic file growth. You can change these values by manually entering new sizes.

Option "Use different data space for Tables and Indexes" selected

If you choose to store the database's system Tables and Indexes in separate files away from the Primary File, you can select the option Use different data space for Tables and Indexes. This will display two further fields entitled Filegroup for Table and Filegroup for Index along with the default Primary File and Log File fields. The Primary File and Log File fields are identical to those described above.

Filegroup for Table & Filegroup for Index

Filegroup Name

Enter a filegroup name that will be used to store the database Tables. By default this is set to CAST_TABLE and CAST_INDEX, but these names can be changed by manually entering new names.

  • This name is used to reference the file in any T-SQL statements after the database is created.
  • The name must be unique in the database and conform to the rules for identifiers.
  • The name can be a character or a regular identifier.

Logical File Name

Enter a logical file name for the Table and Index files. By default this is set to CAST_TABLE and CAST_INDEX, but these names can be changed by manually entering new names.

  • This name is used to reference the file in any T-SQL statements after the database is created.
  • The name must be unique in the database and conform to the rules for identifiers.
  • The name can be a character or a regular identifier.

Operating System File Path

This is the default path that CAST Server Manager will use for the creation of the corresponding file. You can change this by either entering a new path and filename manually, or using the Browse ".." button to explore the contents of the disks on the machine hosting the server you are connected to.

  • The file path must specify a directory on a Microsoft SQLServer instance.
  • The default path and file names displayed in this field are derived using information taken from the Windows registry on the machine hosting the RDBMS. For security reasons, this information may not always be available or accessible. In this case, no file name will be proposed and it will not be possible to use the Browse button to find a path. You may also see error messages in the log file regarding access to the registry (e.g.: "RegQueryValueEx()" and "The directory does not exist"). These errors are not fatal and the creation of the database will still be possible via manual entry of the path and filename.

    Note that CAST Server Manager does NOT use the properties "Default Data Directory" or "Default Log Directory" (that can be set on the Microsoft SQLServer in Enterprise Manager) to create the default path for data and log files.

File Size (MB)

By default the file size is set to 200MB, with the option Unlimited to allow for automatic file growth. You can change these values by manually entering new sizes.

  • No labels