Running the Healthcare: HL7 to HL7 DFDL pattern

This pattern can distribute incoming messages to any number of destinations, but for ease of development and management, each pattern instance contains a maximum of six destinations.

Before you start:

Read "Using patterns" in the IBM App Connect Enterprise documentation.

A diagram showing how destinations are divided between pattern instance projects.

The first instance of the pattern determines the number of sources, the number of transforms, the total number of destinations, and configures all the parameters, except those that are specific to a particular destination.

For every group of six destinations that you want to use, you must create a new pattern instance. For example, to create a pattern with 16 destinations, you must have three pattern instances.

For ease of monitoring, append a number to the end of each pattern instance name. Increment the number by one each time you create a new pattern instance and ensure that the value of the Part parameter matches the number of the pattern instance. For example, if the pattern instance has the number 3, the pattern instance name is PatternInstance3, and the value in the Part parameter should also be 3.

From the second pattern instance onwards, no sources exist and you can have only a single TransformAndRoute flow.

Configuring your pattern

Configuring a pattern with a maximum of six destinations

To configure a pattern that contains a maximum of six destinations, complete the following steps:

  1. In the Pattern Specification tab, click Create New Instance to open the New Pattern Instance window.
  2. Enter your pattern instance name for the first pattern instance. For ease of monitoring, include a 1 at the end of the name (for example, PatternInstance1). Click OK. The Configure Pattern Parameters tab opens.
  3. Ensure that the Part parameter is set to 1, and enter the number of destinations that you want to use (for example, 6). A Destination n parameters section is created automatically for each destination, where n is the number of the destination.
  4. Optional: Review the parameters for each destination and edit any that you want to configure for that destination.
  5. Click Generate.
  6. You can now deploy your flows.

Configuring a pattern with more than six destinations

To configure a pattern that contains more than six destinations, complete the following steps:

  1. In the Pattern Specification tab, click Create New Instance to open the New Pattern Instance window.
  2. Enter your pattern instance name for the first pattern instance. For ease of monitoring, include a 1 at the end of the name (for example, PatternInstance1). Click OK. The Configure Pattern Parameters tab opens.
  3. Ensure that the Part parameter is set to 1, and enter the total number of destinations that you want to use (for example, 16). A Destination n parameters section is created automatically, where n is the number of the destination, for each of the first group of six destinations.
  4. Optional: Review the parameters for each destination and edit any that you want to configure for that destination.
  5. Click Generate.
  6. Return to the Pattern Specification tab and click Create New Instance to open the New Pattern Instance window.
  7. Enter your pattern instance name for the next pattern instance, remembering to increment the number at the end of the name by one (for example, PatternInstance2). Click OK. The Configure Pattern Parameters tab opens.
  8. Import the configuration file from the first pattern instance by clicking the Open existing configuration folder icon at the top of the Pattern Parameters table. This action ensures that all the parameters that are set in the first pattern instance are available to correctly configure the next group of destinations.
  9. Set the Part parameter to 2. A Destination n parameters section is created automatically, where n is the number of the destination, for each of the second group of six destinations; each destination has its own identifying number 7 - 12.
  10. Optional: Review the parameters for each destination and edit any that you want to configure for that destination. If a pattern parameter inherits its configuration from the first pattern instance, the parameter is disabled.
  11. Click Generate.
  12. Repeat steps 6 - 11 for each pattern instance that you need to create, replacing the pattern instance number and the Part parameter value as appropriate until you have a pattern instance for each of your destinations.
  13. You can now deploy your flows.

Queue and flow names

The names of the flows and queues are created automatically when you generate the pattern:

  1. Each Receiver flow is named to reflect its source number. For example, if the source number is 3, the flow name also contains the number 3 (except the flow for the first source).
  2. Each Sender flow and Destination subflow is named to reflect its destination number. Each TransformAndRoute flow is also named with a unique number. For example, if the destination number is 8, the flow names also contain the number 8.
  3. Each TransformAndRoute flow contains a unique name based on the number that is selected when generating the pattern.
  4. The queue name for the TransformAndRoute flow reflects the value of the Part parameter and the Transforms parameter. For example, the queue name for the second transformation in the pattern instance that contains the first group of destinations is QueuePrefix.RXF1.2.
  5. The queue name for each Sender flow also contains the number of the destination.
  6. Other queues are shared between the pattern instance projects.

Deploying your pattern instance

To deploy your pattern instance, complete the following steps:

  1. In the Application Development view, for Part 1 of the pattern, drag the generated HL7toHL7DFDL application onto the integration server in the Integration Nodes view.
  2. For every other part of the pattern, drag the corresponding generated HL7toHL7DFDL application onto the integration server in the Integration Nodes view.

If you selected the Generate as Integration Projects parameter, complete the following steps to deploy your pattern instance:

  1. In the Application Development view, for Part 1 of the pattern, drag all the Receiver flows, all the TransformAndRoute flows, and all of the Sender flows onto the integration server in the Integration Nodes view.
  2. For every other part of the pattern, drag the TransformAndRoute flow and each of the Sender flows onto the integration server in the Integration Nodes view.

The pattern is now running, and messages can be sent.

Back to the Healthcare: HL7 to HL7 DFDL pattern specification