Parameterized Subject and Destination Name Restrictions
The following are restrictions on parameterized subject names and destination names:
| • | Length of parameterized subject and destination names |
| — | A TIBCO Rendezvous parameterized subject name can be at most 255 characters in length, with each component no more than127 characters. |
| — | A JMS parameterized destination name can be at most 249 characters in length, with each component no more than 127 characters. |
In the previous example, if the ORDER_DESCRIPTION column contains a description value that is longer than 127 characters, the parameter name $ORDER_DESCRIPTION is used as the subject or destination in place of the description value.
| • | Wildcard characters |
The asterisk (*) or greater than (>) characters, or empty strings cannot be used as attribute values (VARCHAR, CHAR) in a column that is part of a parameterized subject or destination. Doing so makes the subject or destination invalid.
For example, if the TIBCO.ORDER.$ORDER_ID.$ORDER_DESCRIPTION parameterized subject or destination name is defined and the following values are inserted into ORDER_TABLE:
insert into ORDER_TABLE values(111,'*',88.81);
and the following values are inserted into the ORDER_DESCRIPTION table:
insert into ORDER_DESCRIPTION TABLE values(112,'>',99.91);
the publisher would return an error.
| • | Data type restrictions |
| — | Do not use columns that contain Date types as part of a parameterized subject or destination. Date values are likely to contain characters such as dashes and spaces that can cause problems when used as part of a subject or destination. |
| — | Do not use columns that contain binary types as part of a parameterized subject or destination. |
| — | Do not insert Float-type data as an attribute value in a column that is part of a parameterized subject or destination. Doing so makes the subject or destination invalid. |
| • | Column name |
Each element cannot represent more than one column. For example, MYSUBJECT.$COLUMN1$COLUMN2 is an invalid parameterized subject name.
| • | Group messaging |
The group messaging feature is not supported with parameterized subjects or destinations. An error message will display and the adapter will automatically disable the group messaging feature for the publisher. For example, if the TIBCO Rendezvous transport type is used, the error message will be:
Cannot use parameterized subject with group Publishing. Disable group publishing.
| • | Pre-registration |
Pre-registration in the adapter cannot work when a parameterized subject or destination is used.