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 Command | Main Parameters
 
Main Parameters
{-a | --action} action
The table below describes the parameters for the {-a | --action} parameter.
Value
Action
catalog
Lists existing database components.
create
Creates a database user and database storage, or database components.
drop
Drops a database user and database storage, or database components.
Before dropping any database component, shut down all products that are connected to the database component.
After you drop all database components from a schema, you can drop the storage and revoke the database user permissions.
recreate
Performs the drop action and then the create action.
{-d | --dbms} {db2luw | mysql | oracle | sqlserver | pgsql | tibero}
Type of RDBMS on which to perform action .
{-l | --url} RDBMS_URL
URL for the RDBMS. When working with database components on UNIX systems, you must enclose the URL in double quotes. The table below describes the parameters for the {-l | --url} parameter.
For information about options supported by the DataDirect Connect JDBC driver used by your products, see the DataDirect Connect documentation, available on the Software AG Documentation website.
RDBMS
Sample URL Format
DB2
jdbc:wm:db2://server:{50000|port};databaseName=database
[;option=value]...
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.
MySQL Community Edition
jdbc:mysql://server:{3306|port}/database
MySQL Enterprise Edition
jdbc:wm:mysql://server:{3306|port};databaseName=database
[;option=value]...
Oracle
jdbc:wm:oracle://server:{1521|port};serviceName=service
[;option=value]...
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).
PostgreSQL
jdbc:wm:postgresql://server:{5432|port};databaseName=database
SQL Server
jdbc:wm:sqlserver://server:{1433|port};databaseName=database
[;option=value]...
Tibero
jdbc:tibero:thin:@server:{8629|port}:database
{-c|--component} db_component[,db_component...] | {-pr|--product} product[,product...]} {-v|--version} latest
One of the following:
*To create database storage, specify storage on {-c|--component}.
*To create individual database components, specify the database component codes or names on {-c|--component}. --printComponents provides a list of database component codes and names.
*To create all database components for products that have multiple database components, specify the product name or names on {-pr|--product}. --printProducts provides a list of these product names and codes.
{-u | --user} db_user {-p | - -password} password
The table below describes the parameters for the {-u | --user} and {-p | - -password} parameters.
Note:
You can choose to specify this authentication information in the URL, using DataDirect options, rather than in these fields.
Action
Values to specify
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.
Creating a database user and storage in DB2
OS user to which to grant permissions, and the password for that user.
Performing any other action
Existing database user and password.
[{-au | --admin_user} db_admin_user {-ap | --admin_password} password]
If no database user and storage already exist from a previous create action, or if you are going to drop storage and revoke the database user permissions, specify the database user or operating system user and password that has the necessary database administrator credentials.