Migrating artifacts to IBM App Connect for Healthcare 6.0.1.0

Migrate resources to IBM® App Connect for Healthcare 6.0.1.0 by importing them into the IBM App Connect Enterprise 12.0 workspace, then running the Migrate Healthcare Resources wizard.

Before you begin

About this task

You can continue to use resources from IBM App Connect for Healthcare 5.0 or IBM Integration Bus Healthcare Pack Version 4.0 by importing them to IBM App Connect for Healthcare 6.0.1.0. Some resource types are different in IBM App Connect Enterprise 12.0. Therefore, you need to use the wizard to migrate resources from previous versions so that they work correctly in Version 12.0.

For example, to achieve isolation when you deploy resources, you can migrate integration projects that you used in IBM Integration Bus 10.0 to applications in IBM App Connect Enterprise 12.0. If you do not convert an integration project to an application, the integration project resources are grouped into the default application when you deploy your BAR file. Therefore, all resources in the same application are started, stopped, and deployed at the same time and share a scope in the server. To share artifacts between multiple applications, you can put those artifacts in shared libraries so that multiple applications can use the shared libraries.

Subflow user-defined nodes that are used in some Healthcare patterns were defined in subflow user-defined node projects in IBM Integration Bus 10.0 and IBM App Connect Enterprise 11.0. IBM App Connect Enterprise 12.0.2.0 introduces a new way to develop subflow user-defined nodes in a static library instead of a subflow user-defined node project. This enhancement means that you can now deploy the message flows that contain these nodes as source in a BAR file, with no need to compile them. As a result, you can use the test framework and visual debugger that are available in IBM App Connect Enterprise 12.0. To use these resources from previous versions in IBM App Connect for Healthcare 6.0.1.0, you can use the migration wizard to convert them to IBM App Connect Enterprise 12.0 resources.

Procedure

  1. In IBM Integration Bus 10.0 or IBM App Connect Enterprise 11.0, export the resources that you want to use in IBM App Connect Enterprise 12.0.
    1. Click File > Export, then IBM Integration > Project Interchange, then Next.
    2. Select the projects that you want to export.
    3. Specify a name and location for the compressed file that is created, then click Finish.
      The project interchange file is created in the specified location.
  2. Create an IBM App Connect Enterprise 12.0 workspace, or open an existing one.
  3. Import the project interchange file into the IBM App Connect Enterprise 12.0 workspace.
    1. Click File > Import, then IBM Integration > Project Interchange, then Next.
    2. Specify the location of the project interchange file that you created in IBM Integration Bus 10.0 or IBM App Connect Enterprise 11.0, and specify the open IBM App Connect Enterprise 12.0 workspace.
    3. Select the projects that you want to import into your IBM App Connect Enterprise 12.0 workspace, then click Finish.
  4. Wait until the IBM App Connect Enterprise 12.0 workspace finishes building before you run the migration wizard.
    Progress is indicated on the status bar.
  5. To migrate your imported resources, right-click a project in the Application Development view, then click Migrate Healthcare Resources.
    The Migrate Healthcare Resources wizard opens and lists your projects.
  6. Select the projects that you want to migrate, then click Next.
  7. Select the options that define how you migrate your resources, then click Next.
    1. To convert Healthcare nodes to the style of user-defined node that is supported in IBM App Connect Enterprise 12.0, select the option to search in projects for flows that contain Healthcare nodes.
    2. To be able to deploy subflows as source in IBM App Connect Enterprise 12.0, without the need to compile them, select the option to convert .msgflow subflow files to .subflow files.

      If you deploy .subflow files in this way, you can use IBM App Connect Enterprise 12.0 features like the Flow Exerciser that are not available to compiled files.

    3. To be able to deploy artifacts separately, choose the option to convert integration projects to applications.

      If you do not convert an integration project to an application, the integration project resources are grouped into the default application when you deploy your BAR file. Therefore, all resources in the same application are started, stopped, and deployed at the same time and share a scope in the server. Deploying all your resources at the same time in this way has an impact on BAR file size and deployment times. If you need to share artifacts between multiple applications, you can put those artifacts in shared libraries so that multiple applications can use the shared libraries.

    4. If you decide to store your HL7 DFDL model in a shared library, select the appropriate options for your HL7DFDLInput and HL7DFDLOutput nodes, and specify the names of shared libraries.
      In IBM Integration Bus 10.0, many integration projects can share same static library, and just one copy of that library is deployed. When you use applications and libraries, each application is deployed with its own copy of the library. To replicate the behavior of IBM Integration Bus 10.0, you must use a shared library. The name of the shared library that you specify in the migration wizard is used as the value of the Message model property on the HL7DFDLInput node or the Default message model property on the HL7DFDLOutput node. You must provide the shared library name in the following circumstances.
      • A message flow contains an input node or a ResetContentDescriptor node where the Domain is set to DFDL and the Message is an HL7 message.
      • A message flow contains ESQL, Java™, or a map that creates a DFDL HL7 message tree.
      • A message flow contains ESQL or Java that serializes a DFDL HL7 message tree into a bit stream. For example, code that is downstream from a HL7DFDLInput node builds and serializes an HL7 ACK message, then sends it by using TCPIP.
  8. Check the list of projects that are selected for migration, then click Finish.
    A message confirms when migration is successful, and a migration report is provided. The artifacts that you created in previous versions are available to use in IBM App Connect for Healthcare 6.0.1.0.

What to do next

  1. When migration is complete, check for any errors on the Problems tab.
    • If you see the message The application X cannot be referenced from the project Y, project X was converted into an application instead of a static library. To fix this problem, right-click the message in the Problems tab, then click Quick Fix. Check the selected file, then click Finish. Application X is converted to a static library.
    • If you are converting integration projects that share a Java project to an application, you must include the shared project in a static library.

      For example, you might be converting multiple integration projects that contain flows that each have a JavaCompute node that uses the same Java project. The converted application cannot share the Java project and you see an error. To fix this error, open one of the applications, right-click the Java project, then click Include project in a new library. A new static library is created with the same name as the Java project, and a library is created that contains a library descriptor and a reference to the original Java project. All the applications are updated to refer to the library.

    • If you use the FHIRValidate node in your flows, be aware that validation is improved in the version of IBM FHIR (4.10.2) that is included in IBM App Connect for Healthcare 6.0.1.0. Validation is more compliant with the HL7 FHIR v4.0.1 specification; therefore, you might see new FHIR validation errors or warnings.
  2. Rework message flows.

    Some message flow nodes that were available in IBM Integration Bus Healthcare Pack Version 4.0 are no longer in IBM App Connect for Healthcare 6.0.1.0. If your message flows contain nodes that are no longer available, you must rework them to use only those nodes that are available with IBM App Connect for Healthcare 6.0.1.0. For a list of resources that are not available with IBM App Connect for Healthcare 6.0.1.0, see Coexistence and migration of IBM App Connect for Healthcare.

  3. Migrate DICOM configurable services in IBM Integration Bus Healthcare Pack Version 4.0 to policies in IBM App Connect for Healthcare 6.0.1.0.

    Policies replace configurable services in IBM App Connect Enterprise 11.0. If you have a DICOM healthcare pattern that contains a configurable service, migrate the configurable service to a policy by using the wizard.

    1. In the Application Development view, double-click the .configurableservice file to open the New DICOM Policy wizard.
    2. Create or select a policy project to contain the policy. (By default, the policy name is the name of the configurable service.)
    3. Select the option to delete the configurable service, then click Finish.
    4. The DICOM Input Node policy is opened so that you can edit it. You can find the policy, with a file extension of .policy.xml, in the policy project in the Application Development view.
  4. If you created Resequence, ATNA, AssigningAuthority, or any other configurable services, you must create the equivalent policy in a policy project at this stage. For more information, see Creating policies with the IBM App Connect Enterprise Toolkit in the IBM App Connect Enterprise product documentation.
  5. Rebuild the broker archive (BAR) files that contain your healthcare solutions by using the BAR file editor. If you created any policies, you can add them to existing BAR files or deploy them in a separate BAR file.

    For more information, see Adding resources to a BAR file in the IBM App Connect Enterprise product documentation.

  6. Redeploy the BAR file.

    For more information, see Deploying integration solutions to a production environment in the IBM App Connect Enterprise product documentation.