Creating Custom Header Schemas for Dynamic Message Type Discovery
In most scenarios, you should specify the default SWIFT header schema (Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas.HeaderSchema) for the SWIFT Header Schema configuration property of the SWIFT disassembler. The SWIFT disassembler uses the default SWIFT header schema to parse message headers that conform to the SWIFT standard specification, and has the necessary promoted properties to facilitate dynamic schema resolution (and sub-type resolution for "dual type" SWIFT messages like MT574_IRSLST and MT574_W8BENO). For more information about the default SWIFT header schema and to understand how the SWIFT disassembler performs schema resolution, see Dynamic Message Type Discovery and Schema Resolution.
For other scenarios where messages contain non-SWIFT standard header data, you can use a custom header schema for header parsing and dynamic message type discovery. To create and use a custom header schema for dynamic schema resolution, do the following:
Create a custom schema that the SWIFT disassembler can use to structurally parse the expected header data format.
Identify which fields in the schema will hold the value(s) indicating message type.
Add the A4SWIFT Property Schema (Microsoft.Solutions.A4SWIFT.Property.PropertySchema) to the "Property schemas list" of the custom header schema and promote the appropriate fields that indicate message type using the following A4SWIFT properties:
A4SWIFT_MessageType
A4SWIFT_MessageType2 (optional if A4SWIFT_MessageTypes is used)
A4SWIFT_SecondaryMessageType (optional)
Build and deploy the custom header schema.
Set the SWIFT Header Schema configuration property of the SWIFT disassembler (in your receive pipeline project) to the custom header schema.
For more information about these and other promoted properties, see A4SWIFT_* Promoted Properties. For more information about using BizTalk Editor to create and edit schemas, promote properties using a property schema, and build and deploy schema projects, see BizTalk Server Help.