WebSphere MQ Application Properties

There is no shared resource representing the application properties for a message in BusinessWorks 6. Instead, a generic schema is used and mapped onto the operation.

The following field types are supported:
  • boolean
  • byte
  • bytes
  • short
  • int
  • long
  • float
  • double
  • string

The node represented by this schema is present on the input schema of the Put activity and in the output schema of the Get and Listener activities. Fields which contain values are mapped onto sent messages. When processing a received message, all fields in the schema which have corresponding named counterparts in the message are mapped onto the output schema. If a type mismatch occurs when mapping fields onto the output schema, the field is skipped. If fields that are required by the schema are missing from the message, it causes the activity to fail. If there is no sync-point in place for the activity and an error occurs while extracting the properties which causes the activity to fail, then the message is effectively lost. If there is any chance of this happening in your application, you are required to force a sync-point. See the Explicit Commit check box from the Multi-Message tab.

To create a WebSphere MQ Application Properties Schema, right-click the Schemas folder in the Project Explorer view, click New > XML Schema File, and configure the schema and then select it from all the activities that use it.

Note: If the application properties are used on a message, the properties are included in an MQRFH2 header. This header is visible to and must be handled by non-Java applications in order for those applications to access the properties.