Step 3 If Needed - Map Key (Reserved) Words to Aliases

This task is optional and performed in case there are errors in the previous steps.

Complete this task only if you saw errors after completing Step 2 Run the Project Schema Script (as BE_USER). Such errors are caused when your project ontology uses terms that are key words (reserved terms) in the DBMS you are using. You must map these terms to an alias in the keyword mapping file.

    Procedure
  1. Edit the keyword map file in either of the following ways:

    • Edit the BE_HOME/dbkeywordmap.xml file to add entries.
    • If you use a custom backing store, you can create your own .xml mapping file.
    • For Cassandra backing store, edit the BE_HOME/bin/cassandrakeywordmap.xml file at the location BE_HOME/bin.

    Below is the format for entries in the .xml mapping file:

    <keyword name=“dbKeyWord" mapname=“nonDbKeyWord"/>
   <keyword name="start" mapname="start_"/>

  2. (Optional) If you create a custom .xml keyword file or use the cassandrakeywordmap.xml file, edit the java.property.jdbcdeploy.bootstrap.keyword.file path in the be-engine.tra and be-storedeploy.tra files as follows:
    java.property.jdbcdeploy.bootstrap.keyword.file  path_to_your_file/your_file.xml
  3. Repeat Generating Deployment Scripts for a Store, and tasks following as needed.
  4. If desired, create project-specific aliases for the key word mappings as explained in Providing Project-Specific Keyword Aliases.