Resolving problems that occur when preparing to deploy message flows

Use the advice given here to help you to resolve common problems that can occur during preparations to deploy message flows or message sets.

An error is issued when you add a message set to a BAR file

Procedure

  • Scenario: An error is issued when you add a message set to a BAR file.
  • Explanation: After you create a BAR file and add a message set project to it, two files are created in the BAR file: messageset.user.txt and messageset.service.txt. The user.txt file contains user log information, such as warning message BIP0177W, which states that the dictionary that you have created is not compatible with earlier versions.
  • Solution: Use the information in the user.txt file to diagnose the error. The service.txt file contains detailed information that is used by the integration node, and can be used by the IBM® Support Center to diagnose problems.

You cannot drag a BAR file to an integration node

Procedure

  • Scenario: You cannot drag a BAR file to an integration node.
  • Explanation: BAR files can be deployed only on an integration server.
  • Solution: Select an integration server in the deploy dialog.

You cannot deploy a message flow that uses a user-defined message flow

Procedure

  • Scenario: You have created a message flow that contains an input node in a user-defined node project. However, you cannot deploy a message flow that uses this node.
  • Explanation: Validation, compilation, and deployment do not recognize that a user-defined message flow contains an input node.
  • Solution: To work around the problem, add a dummy input node to the flow that you intend to deploy.

The compiled message flow file (.cmf) has not been generated

Procedure

  • Scenario: The compiled message flow file (.cmf) has not been generated.
    Therefore, it is not added to the BAR file, and cannot be deployed.
  • Explanation: When you create files that define message flow resources in the IBM Integration Toolkit, the overall file path length of those files must not exceed 256 characters, because of a Windows file system limitation.

    If you have a message flow that includes resource files that have a path length that exceeds 256 characters, the message flow cannot be compiled when you try to add it to a BAR file, and therefore cannot be deployed.

    You might also be affected by this restriction when you use the Adapters Connection wizard; names discovered and returned by the EIS can be very long. The Adapters Connection wizard attempts to write these files to the message set on the local file system, but their path exceeds the operating system limit, and the files appear corrupted.

  • Solution: To ensure that the path length does not exceed 256 characters, use names that are as short as possible for all resources; for example:
    • The installation path
    • Project names and broker schema names
    • ESQL and mapping file names
    • Inbound and outbound adapter files

You cannot deploy a message flow that contains restricted resources

Procedure

  • Scenario: An error is issued when you deploy a BAR file containing resources that are not valid for your runtime operation mode.
  • Explanation: In express mode and scale mode, the integration node operates with a limited set of nodes. If a BAR file contains nodes that are restricted in the runtime operation mode, you cannot deploy the BAR file.
  • Solution: Rework your message flow to use resources that are valid for your runtime operation mode; see Restrictions that apply in each operation mode. Alternatively, contact your IBM representative to upgrade your license.