Each of these naming modules validates identifiers for particular BW elements. Valid identifiers for a naming module are specified by its format property. The value of format is a regular expression for valid identifiers.
This is an example of a configuration of an activity within a Process Definition module to ensure that the name member identifiers begin with a lower case, followed by any combination of letters and digits.
analyzers.process.activity.name.pattern = ^[a-z][a-zA-Z0-9]*$
The list of issues that may be raised are explained hereafter and these are:
This issue is raised when an element of the TIBCO Business Works project doesn't conform to the specified naming convention.
Currently, the BW Project Analyzer is capable of applying naming conventions to the following elements:
| Activity Name |
Checks if the Activity Name abides to naming conventions. By default, the file raccoon.properties is
defined as follows for this check:
analyzers.process.activity.name.active = true analyzers.process.activity.name.pattern = ^[A-Z][a-zA-Z0-9]*(-[A-Z0-9]+[a-zA-Z0-9]*)*$ |
|---|---|
| Process Name |
Checks if the Process Name abides to naming conventions. By default, the file raccoon.properties is
defined as follows for this check:
analyzers.process.name.active = true analyzers.process.name.pattern = ^[A-Z][a-zA-Z0-9]*.process$ analyzers.process.name.root = /Process |
| Rendezvous Shared Configuration Name |
Checks if the Rendezvous Shared Configuration Name abides to naming conventions.
By default, the file raccoon.properties is defined as follows for this check:
analyzers.transports.rv.active = true analyzers.transports.rv.pattern = ^/Configuration(/[A-Z]+[a-zA-Z]*)*(/Rendezvous)(/[A-Z]+[a-zA-Z]*).rvtransport$ |
This issue is raised when the name of an element of the TIBCO Business Works project is too long. The rational behind this check is that the length of an element impacts the runtime performance. The longer the names of the activities (and process definitions) the more memory is consummed and the more I/O there are.
Currently, the BW Project Analyzer is capable of applying naming length conventions to the following elements:
| Activity Name |
Checks if the length of the activity name abides to naming conventions is valid.
By default, the file raccoon.properties is defined as follows for this check:
analyzers.process.activity.name.length = 50 |
|---|---|
| Process Name |
Checks if the length of the process name abides to naming conventions is valid.
By default, the file raccoon.properties is defined as follows for this check:
analyzers.process.name.length = 30 |