Copyright © Cloud Software Group, Inc. All Rights Reserved

Configuring Storage for TIBCO ActiveMatrix BusinessWorks Processes

You can use TIBCO Administrator to configure the location where TIBCO ActiveMatrix BusinessWorks process engines store internal information.

Most of the information a process engine stores is information about each service’s state when a checkpoint is taken. There is, however, some other internal information stored by the engine. You can specify that this information is stored in the file system (the default) or in a database.

For some systems, using a file system for storage may be sufficient. However, some functionality is only available when you use a database for storing information about service state:

•	When configured properly, shared variables can be used to pass information across multiple process engines when a database is used for storage.

•	Duplicate detection of messages across multiple engines after a recovery from a checkpoint requires a database for process engine state storage.

•	Using critical section groups across multiple engines requires a database for storage.

•	With a database for storage, Wait/Notify activities can be used to pass data between services running on different machines.

Specifying a Database for Storage

To configure a database for storage, follow these steps:

1.	In TIBCO Designer, be sure to specify a JDBC Connection resource for the database you wish to use, and then build the EAR file.

2.	After you have uploaded the EAR file and created the application in the TIBCO Administrator GUI, select Application Management then select the application in the Configuration Builder pane of the Configuration console.

3.	Select the service (.par) in the Configuration Builder pane and choose the Advanced tab.

4.	In the TIBCO ActiveMatrix BusinessWorks Checkpoint Data Repository pane, select the Database pane.

Database Table Names

When you specify a database for TIBCO ActiveMatrix BusinessWorks storage, tables are created in your database. The administration domain name and deployment ID (assigned by TIBCO ActiveMatrix BusinessWorks) are used to name the tables to ensure uniqueness of the tables for each domain and each deployment.

Because some databases limit the number and kinds of characters for table names, the domain name can altered before being used in the table name. The first eight characters and the last eight characters of the domain name are taken and any non-legal characters (such as spaces or dashes) are converted to underscores. This creates a sixteen-character unique ID for each domain, provided that the first and last eight characters of all of your domain names are unique.

For example, the following illustrates conversion of domain names. Notice the second and third domain names convert to the same ID. You should avoid this by creating domain names so that the combination of the first and last eight characters are unique.

 

Domain Name	Converts To Domain ID
TIBCO_domain_Accounting	TIBCO_docounting
TIBCO_domain_Marketing	TIBCO_doarketing
TIBCO_domain_Direct_Marketing	TIBCO_doarketing

All table names created by TIBCO ActiveMatrix BusinessWorks begin with T_<domain-id>_<deploymentID>_. You can alter the storage parameters for these tables if you desire, but the table names and column definitions must remain the same.

Manually Creating Database Tables

The process engine creates database tables used to store process engine information automatically. Some database administrators do not permit applications to automatically create tables. If you wish to manually create the database tables, TIBCO ActiveMatrix BusinessWorks provides template scripts for the supported databases in the <TIBCO_BW_HOME>/bin directory.

In these scripts <TABLE_NAME_PREFIX> and <ENGINE_NAME_MAX_LENGTH> are placed in the SQL code as placeholders. The <TABLE_NAME_PREFIX> is determined by default at deployment time (see Database Table Names for a description of how the table name prefix is determined). You can obtain this prefix by locating the Database.Tablename.Prefix property in the deployment configuration file and substituting its value where required in the template SQL script. <ENGINE_NAME_MAX_LENGTH> is 128, so supply that value instead of the placeholder in the SQL script.

To manually create the tables, perform the following procedure:

1.	Create a deployment configuration that specifies a database for process engine storage. See Specifying a Database for Storage.

2.	Before starting the process engine, examine the deployment configuration file (the <processEngine>.tra file) and locate the property Database.Tablename.Prefix.

3.	Edit the appropriate SQL script template for the database you are using and replace <TABLE_NAME_PREFIX> with the value of the Database.Tablename.Prefix property.

4.	Change <ENGINE_NAME_MAX_LENGTH> to 128.

5.	Save the changes to the SQL script.

6.	Run the SQL script against the database you wish to use.

7.	Start the process engine.

Copyright © Cloud Software Group, Inc. All Rights Reserved