Specify the Connection to the RDBMS

Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Installing Software AG Products On Premises | Installing Products, Creating Database Components, and Connecting Products to Database Components | Installing Products Using Software AG Installer and Creating Database Components Using Database Component Configurator | Create Database Components Using Database Component Configurator | Database Component Configurator Graphical User Interface | Create Database Components, Database User, and Storage | Specify the Connection to the RDBMS

Specify the connection for the configurator to use to connect to the RDBMS.

1. Choose the RDBMS in which to create the database components and provide the URL for the RDBMS. Below is additional information for the URL.

For DB2, if you are going to create database components in a schema other than the default schema for the specified database user, you must specify these connection options in the URL:

;AlternateId=schema;"InitializationString=(SET CURRENT
PATH=current_path,schema)"

AlternateID is the name of the default schema used to qualify unqualified database objects in dynamically prepared SQL statements.

If you are creating Optimize database components, you must specify schema using all uppercase letters. In addition, you must specify the options CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000. These settings will affect all database components in the same schema or database.

If you are using a schema other than the default schema for the specified database user, you must also add the option showSelectableTables=false to the URL. The database driver queries SYSIBM.SYSDBAUTH at connection time to find out whether the current user is an admin or not. The results of this check allows a query to getTables() to return tables for which the user has SELECT privileges. An admin has implicit select privileges on all tables instead of the explicit privileges that other types of users have, so the driver has to alter its native SQL for getTables(). Set showSelectableTables=false and the driver will skip the check for SYSIBM.SYSDBAUTH at connection time.

For Oracle, if you are creating storage and the Data Purge database component, you must specify the sysLoginRole connection option on the URL (for example, ;sysLoginRole=sysdba).

If you want to apply Kerberos functionality to set the current user to a specific name, set the connection URL to contain the parameter ReAuthenticateUser=name.

For information about options supported by the DataDirect Connect JDBC driver used by your products, including options that support clustering, data encryption (SSL), and different authentication methods, see the DataDirect Connect documentation, available on the Software AG Documentation website.

2. The user ID and password you specify depend on the task you are going to perform, as described below.

Note:
You can choose to specify this authentication information in the URL, using DataDirect options, rather than in these fields.

If you are...	Specify...
Creating a database user and storage in DB2	OS user to which to grant permissions, and the password for that user.
Creating a database user and storage in Oracle, SQL Server, or Tibero	Database user and password to create. For SQL Server, the user will be created and a default schema named dbo will be assigned to that user. For Oracle or Tibero, do not use the SYSTEM user to create the database components in the SYSTEM schema. For Oracle 12c or later, do not create the database user in the Container Database (CDB). Instead, create the database use in the Pluggable Database (PDB), by specifying the PDB service name in the URL.
Performing any other action	Existing database user and password.

3. If you intend to run the configurator more than once, you can set the current field values as the defaults for subsequent runs by clicking Save Settings. The values for the two Password fields are not saved.

4. Click Execute.