Store Deployment CLI Utility Options

Run the script be-stroredeploy.exe to build the schema in the database with the provided options.

Option Description

-h

/h

-help

/help

Optional Displays this help.

--propFile

/--propFile

-system:propFile

Optional When you execute be-storedeploy, it searches for a property file of the same name in the working directory. This property file provides startup values and other parameters to the executable. You can specify the path and filename of a startup property file explicitly using the --propFile parameter.

For example, if you start the engine from a directory other than BE_HOME/bin, then you would generally use --propFile to specify BE_HOME/bin/be-storedeploy.tra.

-p

/p

-property

/property

Optional Location of the custom property file for the project. Values in custom property file override the values in the startup property file.
-o

/o

-out

/out

Specify the schema output path and file name.

If you do not specify the path, the output file is created in the directory from where the script is being executed.

If you specify a directory path, the backing store scripts are generated in the specified directory and the last element of the path is taken as the schema output filename.

-c

/c

-cdd

/cdd

Specify the absolute path of the CDD file that contains the configuration details of backing store.

For example: C:\workspace\FraudDetection\fdstore.cdd
-s

-store

/s

/store

Optional Specify the store type for schema generation.

The values are:

  • JDBC
  • ACTIVESPACES
  • CASSANDRA

The default type is JDBC.

-op

-operation

/op

/operation

Optional Specify the operation type for deployment.

The values are:

  • schemagen - Select this, if you are creating a new backing store.
    This operation generates schema files. When database details are provided in the TRA file, it also generates ID migration script [<name>_migration.sql].
  • migration - Select this, if you are migrating an existing backing store.
    Note: To generate migration scripts for migrating data in a project from legacy ID format to new ID format, connect to an existing legacy ID database in the project.

The default value is schemagen.

-u

-unit

/u

/unit

(Only for the migration operation)Specify the processing unit name for the migration.
-n (Only for the migration operation)Specify the TIBCO BusinessEvents engine name for the migration.
Relational Database (JDBC) Backing Store Fields

-a

/a

-ansi

/ansi

 Optional If set to true, ANSI compatible SQL types are used during script generation.

Allowable values are true and false. For ANSI compatible databases, it is set to true by default.

-optimize Optional Use this option to eliminate schema generation for in-memory events.
-maxstringsize Sets the maximum string size value to extended, that is to 32767 bytes.
-histidnotnull Disallow null values in history arrays.
-childidnotnull Disallow null values in child arrays.