EMS Schema Export Tool Options

The following table shows the options that are used with the Schema Export Tool.

Option	Description
`-tibemsdconf` pathname	The absolute path to the `tibemsd.conf` or `tibemsd.json` file. For example, on a UNIX system: /opt/tibco/ems/8.7/ samples/config/tibemsd.conf
`-exporttofile`	Export the schema to a file named store-name`.ddl.log`, where store-name is the name of the database store. If multiple database stores are configured, then one file is created for each database store. If neither `exporttofile` nor `export` option is included, the schema export tool prints the schema to the console. If both `-exporttofile` and `-export` are included, the Schema Export Tool exports the database schema to both locations.
`-export`	Export the schema to the database configured for the store. If neither `export` nor `exporttofile` option is included, the schema export tool prints the schema to the console. If both `-export` and `-exporttofile` are included, the Schema Export Tool exports the database schema to both locations.
`-storestorename=create\|update\|drop`	Create, update, or drop the schema for one or more specific stores that are named in the stores configuration file. If you choose the `create` option for a schema that already exists, the Schema Export Tool recreates the schema. Note that `create` prints the schema to screen but does not deploy it. You must use `export` or `exporttofile` in order to implement the schema.
`-createall`	Create all the stores found in the stores configuration file. Note that this option drops any existing configurations when creating the new stores.
`-dropall`	Drop all the stores found in the stores configuration file.
`-updateall`	Update the schema for all stores configured in the stores configuration file.
`-help`	Print information about the schema export tool and its options, and exit the tool.

Examples

The following examples show how the Schema Export Tool can be used to create database schemas in various configurations.

Example 1

This example shows how the Schema Export Tool can be invoked from any directory by giving the absolute path to the tibemsd_util.jar:

$ java -jar /opt/tibco/ems/8.7/bin/tibemsd_util.jar -help

Example 2

In this example, the Schema Export Tool creates and exports database schemas for all the stores found in the stores.conf that is set in the specified tibemsd-mssqlserver.conf file:

$ java -jar /opt/tibco/ems/8.7/bin/tibemsd_util.jar -tibemsdconf /opt/tibco/ems/8.7/samples/config/tibemsd.conf -createall -export

Example 3

In this example, the Schema Export Tool exports the database schema for the $sys.failsafe store to the database:

$ java -jar /opt/tibco/ems/8.7/bin/tibemsd_util.jar -tibemsdconf /opt/tibco/ems/8.7/samples/config/tibemsd.conf –export –store \$sys.failsafe=create

Example 4

In this example, the Schema Export Tool writes the database schema for the $sys.failsafe store to the file $sys.failsafe.ddl.log:

$ java -jar /opt/tibco/ems/8.7/bin/tibemsd_util.jar -tibemsdconf /opt/tibco/ems/8.7/samples/config/tibemsd.conf –exporttofile –store \$sys.failsafe=create

Example 5

In this example the Schema Export Tool creates and exports the database schema for the store mystore1, but drops the schema associated with mystore2 and exports the change:

$ java –jar /opt/tibco/ems/8.7/bin/tibemsd_util.jar –tibemsdconf /opt/tibco/ems/8.7/samples/config/tibemsd.conf -store mystore1=create 
-store mystore2=drop -export

Did you find this helpful?

Yes No