webMethods Product Suite  | Complete Installation and Upgrade Information for Software AG Products | Installing Software AG Products | Installing Products and Creating 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.
checkEncoding
Indicates whether your RDBMS is Unicode-enabled.
{-d | --dbms} {db2luw|mysql|oracle|sqlserver|}
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. For information about options supported by the DataDirect Connect JDBC 5.1 driver used by your products, see the DataDirect Connect documentation, available on the Software AG Documentation website.
The table below describes the parameters for the {-l | --url} parameter.
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 (that is, Analysis and ProcessTracker), 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}/databaseName
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).
SQL Server
jdbc:wm:sqlserver://server:{1433|port};databaseName=database
[;option=value]...
{-c|--component} db_component[,db_component...] | {-pr|--product} product[,product...]} {-v|--version} latest
One of the following:
*Database user and storage.
*Database components and product release. For this product release you can specify latest. --printComponents lists database component codes and names; you can use either.
*Product database components and product release. For this product release you can specify latest. --printProducts lists the database components for specific products.
{-u | --user} db_user {-p | - -password} password
The table below describes the parameters for the {-u | --user} and {-p | - -password} parameters.
Tasks
Values to specify
Creating a database user and storage in Oracle or SQL Server
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, 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.
Performing the checkEncoding action
Existing database user that has create session and create table privileges, and that database user's password.
Performing any other action
Existing database user and password.
Note: You can choose to specify this authentication information in the URL, using DataDirect options, instead of in these parameters.
[{-au | --admin_user} db_admin_user {-ap | --admin_password} password]
If you are going to create a database user and storage, or 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.
Copyright © 2007-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.