Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Deployment SQL Scripts Wizard Fields

The following tables lists the settings present in the wizard for generating project-schema and migration scripts.

For details about the procedure, see Generating Deployment Scripts for a Store.

## Project Schema Specific SQL Script Fields

[Project Schema Specific SQL Scripts Options]
Field | Description
--- | ---
Common Fields
Cluster Deployment Descriptor | Specifies the name of the cluster configuration file.
Output Directory | Specifies the schema output file directory.
Output File Name | Specifies the schema output file name.
Relational Database (JDBC) Backing Store Fields
Database Type | Select the type of relational database setup in your project. The values are: `oracle` `db2` `mysql` `sqlserver` `postgresql` The default value is `oracle` Note: The supported databases to migrate existing database data in a project from legacy ID format to new ID format are Oracle, MS SQL, MySQL and PostgreSQL.
Generate ANSI Scripts | Select this checkbox to use ANSI compatible SQL types during script generation. Default setting is checked.
Generate Optimized Scripts | Select this checkbox to eliminate script generation for in-memory events.
Use Extended Max String Size | This is active only for the `oracle` database type. Sets the maximum string size value to extended, that is to 32767 bytes.
Cluster Deployment Descriptor | Browse to and select the CDD file you want to use for the project.
Output Directory | Browse to and select a directory where the scripts are to be generated, for example, BE_HOME`/bin` (This directory is used if you generate files manually.)
Output Script Name Prefix | Enter a prefix for the output script filenames. For example, if you enter `acme` as prefix, the following scripts are generated: `acme.sql` `acme.aliases` `acme_alter.sql` `acme_cleanup.sql` `acme_delete.sql` `acme_remove.sql`

## Migration SQL Scripts Fields

[Relational Database (JDBC) Migrations Scripts Fields]
Field | Description
--- | ---
Connection Configuration | Browse to and select the JDBC Connection shared resource used to connect to the existing backing store.
Database URL | Enter the database URL that points to the existing backing store.
Database Username | Enter the database username that was used when setting up the existing backing store.
Database Password | Enter the database password that was used when setting up the existing backing store.
Database Schema Owner | Enter the database schema owner for the existing backing store.

[ActiveSpaces Migrations Scripts Fields]
Field | Description
--- | ---
ActiveSpaces Connection | Browse to and select the ActiveSpaces Connection shared resource used to connect to the existing backing store. All other fields in the page are automatically populated based on the ActiveSpaces Connection selected.
Realm Server | Enter the URL of the TIBCO FTL Realm server.
Grid name | Name of the property that is configured for the data grid name on the ActiveSpaces server. If not provided, the cluster name is taken as the Grid Name.
Username | Enter the database username that was used when setting up the existing persistence store.
Password | Enter the database password that was used when setting up the existing persistence store.
Use SSL | Select the checkbox to enable secure authentication. When you select the checkbox, the Trust All and Identity fields are enabled.
Trust All | Select the checkbox if the Trust Type in the store configuration is set to `Trust Everyone`. Clear the checkbox if the trust type is `Trust File`. When you select the checkbox, the Identity field is disabled.
Identity | If the Trust All checkbox is clear, provide path of the identity file.

[Cassandra Migrations Scripts Fields]
Field | Description
--- | ---
Database Node (Hostname) | Enter the hostname for the Cassandra server contact point.
Database Port | Enter the port number for the Cassandra server contact point.
Database Username | Enter the database username that was used when setting up the existing persistence store.
Database Password | Enter the database password that was used when setting up the existing persistence store.
Database KeySpace | Name of the keyspace to connect with on the Cassandra server. If not specified, the cluster name is used for the keyspace name.
Use SSL | Select the checkbox to enable secure authentication. When you select the checkbox, the following fields are enabled: TrustStore Location TrustStore Password Requires Client Authentication Note: Generate JKS certificates for Cassandra SSL scenarios using Java 8 or Java 11.
TrustStore Location | While using SSL authentication, provide the path to the base folder containing the certificate files.
TrustStore Password | Password for the trust store while using SSL authentication.
Requires Client Authentication | Select this checkbox if you enable two-way SSL authentication. When you select the checkbox, the ID File field is enabled:
ID File | Path to identity file while using two-way SSL.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.