Monitoring and Auditing Problems

Problem

When naming items, such as SetTypes or Statuses, the field does not allow enough characters to be entered.

Resolution

This is an indication that data is stored to the BizTracker ASA database with multi-byte characters.

The default ASA database, which is used to store Status and SetType names for BizTracker, UTF-8 to store character data. UTF-8 results in a difference in how single-byte and multi-byte characters are stored in the ASA database. BizTracker Status and SetType names are limited to a specific number of characters if single-byte characters are used, or a specific number of bytes if multi-byte characters are used.

As a user enters a name for an item, such as SetType or Status, the BizTracker interface tracks how many bytes are used for each character and allows input of characters until the byte limit is reached. If multi-byte characters are used, the byte limit is reached sooner that with single-byte characters.

• A Status name is limited to 15 bytes of data; 15 characters if single-byte characters are used

• A SetType name is limited to 17 bytes of data; 17 characters if single-byte characters are used

• An Operation name is limited to 30 bytes of data

• A View name is limited to 25 bytes of data

• A Mapping Rules name is limited to 255 bytes of data

• A Transport name is limited to 35 bytes of data.

• An Alert Message name is limited to 30 bytes of data

For additional information, see Supported Encoded Character Sets and Locales and the BizTracker System Administration Guide.

Problem

A process probe added to a business process is not tracked by the object SetType.

Resolution

This can occur when you are tracking messages using an object SetType and the elements of the probe message used to update the object do not contain data. BizTracker receives and processes the probe message, however, the object SetType is not updated.

In BizTracker, empty elements are automatically created for probe messages with elements that do not have values.

When you add a probe to a business process, you define the elements to be included in the probe message. When the business process runs, the defined elements and their values are gathered and a probe message is created. The probe message is then sent to the BizTracker audit transport for tracking. If you define an element to be included in the probe message that does not contain data as its value, an empty element is automatically created when the probe message is created. Therefore, if you are using the empty element value to update the object SetType in BizTracker, the object cannot be updated because there is no value.

You can work around this issue in two ways:

• Redefine the object SetType to use a different field for updating the SetType object; choose a field that always contains data.

• Redesign the business process to use the assign activity to set default data for process probes. See the example, Setting Default Data for Process Probes.