Aliases File and Project Schema Script

For every entity, property, or state machine whose database identifier name exceeds the database maximum length, a table name entry is created in the generated yourname.aliases file (for example, acme.aliases).

See Ontology Identifiers that Exceed the DBMS Maximum Column Length for more information, and for an alternative way to specify short table names.

It’s a good idea to check the aliases file for entries, even if the TIBCO BusinessEvents names are not very long. The length of the generated database table names is not easy to predict.

Optionally, you can edit the file to provide more meaningful names.

Note: It is recommended that you keep the aliases file for future reference. If the project ontology changes after the backing store has data in it, you must also update the database schema to match the new schema (as explained in Updating Existing Backing Store Schema ). If you modified the generated aliases, you must use the same aliases again when you update the schema, to preserve those columns and their data.

Key word mapping file

Entries in the key word mapping file are also added to the aliases file so you can replace the key word aliases with project-specific ones, as desired (generally in a second pass). For details see Step 3 f Needed — Map Key (Reserved) Words to Aliases.