Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# 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 is 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.

## Keyword mapping file

Add entries in the keyword mapping file to the aliases file so that you can replace the keyword aliases with project-specific ones, as desired. It is generally done in a second pass. See If Needed - Map Key (Reserved) Words to Aliases for details.

Subtopics

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.