Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Cases That Need Additional Setup

The following sections identify some cases where additional setup might be required.

## Ontology Identifiers that Exceed the DBMS Maximum Column Length

Entity names and entity property names are used by backing store scripts to generate database table and column identifiers.

DBMSs put different limits on the length of a database identifier name. For example, in Oracle the maximum length is 30 characters, and in SQL Server the limit is 128 characters. Such restrictions might be applicable for ActiveSpaces 4.x, Cassandra, and custom backing stores too.

Generated database identifiers are longer than the TIBCO BusinessEvents identifiers because they contain characters in addition to the TIBCO BusinessEvents identifier. You can handle long identifier issues in either of the following ways (or a combination of these ways).

## Letting the Utility Generate Short Aliases for Table Names

You can allow the `be-storedeploy` utility to generate short aliases for long names. You can also edit those names and rerun the utility. For details see Configuring Aliases File and Project Schema Script.

Note that alias file entries are also generated for another reason. See Ontology Identifiers that Use Database Key Words.

## Specifying Short Table Names in the CDD File

You can avoid the problem of long entity type names before you begin to configure the backing store by specifying short database identifiers using the CDD Table Name setting.

The advantage of this method is that you can choose meaningful names before running the `be-storedeploy` utility. The disadvantages are that you may not know ahead of time which entities require short names, and you must also ensure that the table names you specify are unique across all entities in the ontology.

If you do not specify table names, and entity names are repeated. On the other hand, the generated table names are appended with dollar (`$`) characters as necessary, for example, `D_ORDER`, `D_ORDER$`,`D_ORDER$$` and so on.

See Configuring CDD for Special Cases (As Needed) for details.

## Ontology Identifiers that Use Database Key Words

As well as database names that are too long, ontology terms that are key (reserved) words in your DBMS product must also be mapped to an alias. If errors occur when you run the SQL scripts due to key word clashes, examine the errors and add the appropriate words to the keyword mapping file.

A provided file (BE_HOME/bin/dbkeywordmap.xml) includes some basic mappings: `start`, `end`, `schema`, `mode`, and `index`. You can use it as a model.

Unlike the Aliases file, the keyword mapping file is not a project-specific file. It is intended to be generally useful across different projects. However, keyword mappings are also added to the aliases file when you run the SQL scripts, so you can also provide project-specific aliases for the generic mappings, if you want to.

The procedures are explained in the task sections within the section Initializing the Database and Generate Non-Project Tables.

## String Properties that Exceed the DBMS Maximum Column Length

The default column size for String type attributes is 255 characters. If you expect the data length of an entity property to exceed that value, then in the CDD file set the Max Length field for each entity’s properties. The utility changes the data type of string attributes with long lengths to CLOB, as appropriate.

See Configuring CDD for Special Cases (As Needed) for details.

## Excluding Entities from the Backing Store

You do not have to use the backing store for all entities. In the CDD file, you can specify entities for which you do not want to use the backing store by using the Has Backing Store domain object override setting.

Note: If later you want to include any excluded entities, you must change the setting and update the backing store setup as explained in Updating Existing Backing Store Schema.

See Configuring CDD for Special Cases (As Needed) 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.