WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

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 broker archive file

  • Scenario: An error is issued when you add a message set to a broker archive (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 broker, and can be used by the IBM® Support Center to diagnose problems.

You cannot drag a broker archive file to a broker

  • Scenario: You cannot drag a broker archive (BAR) file to a broker.
  • Explanation: BAR files can be deployed only on an execution group.
  • Solution: Select an execution group in the deploy dialog.

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

  • 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

  • Scenario: The compiled message flow file (.cmf) has not been generated. Therefore, it is not added to the broker archive file, and cannot be deployed.
  • Explanation: When you create files that define message flow resources in the WebSphere® Message Broker 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
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:37


Task topicTask topic | Version 8.0.0.7 | au16541_