Resolving other problems when developing message flows

Use the advice given here to deal with problems that can arise when developing message flows, and that are not covered in the specific categories listed in "Resolving problems when developing message flows"

About this task

The values of your promoted properties are lost after editing

Procedure

  • Scenario: You edited a message flow using the Message Flow editor, and the values of your promoted properties are lost.
  • Explanation: The values of promoted properties for nodes with more than a single subflow definition (that is, two identically named subflows in the same project reference path) are lost if the flow is edited and saved.
  • Solution: To avoid this problem, ensure that each subflow in your project has a different name.

The Message Flow editor experiences problems when opening a message flow, and opens in error mode

Procedure

  • Scenario: You attempt to open an existing message flow in the Message Flow editor and it opens in read-only error mode, displaying a list of parsing or loading errors. The message flow is not open and a message is displayed indicating that the message flow file is not valid.
  • Explanation: The message flow file is unreadable or is corrupted, and the Message Flow editor cannot render the model graphically.
  • Solution: Contact IBM® Customer Support for assistance with the corrupted file.

A message flow has subflows with the same user-defined property set to different values, but only one value is set at run time

Procedure

  • Scenario: You have a message flow that contains identical subflows. Each subflow has the same user-defined property (UDP), but with different values. At run time, only one of the values is set.
  • Explanation: A UDP has global scope and is not specific to a particular subflow. If you reuse a subflow in a message flow, and those subflows have identical UDPs, you cannot set the UDPs to different values.
  • Solution: If you need to set a different value for each subflow, use a different UDP for each subflow.

You want to move resources to a new broker schema that you have created but it is not visible in the Application Development view

Procedure

  • Scenario: You have created a new broker schema and you want to move a resource to it, but the schema is not visible in the Application Development view.
  • Explanation: If category mode is selected, you cannot see the broker schema in the Application Development view.
  • Solution: To move resources to a broker schema that you have created, take one of the following steps.
    • Click Hide Categories (The Hide Categories toolbar icon) on the Application Development view toolbar. The new broker schema appears in the Application Development view and you can drag resources onto it.
    • Right-click a resource, click Move, then select the schema that you have created. When you click OK, the resource is moved to the selected schema.

A selector exception is raised when you use WebSphere Adapters

Procedure

  • Scenario: You run the Adapter Connection wizard for an inbound IDOC, then you run the wizard again for an outbound IDOC. When the message set is generated, you see the following error message: 
    'Selector exception caught from generateEISFunctionname' , 
'commonj.connector.runtime.SelectorException: 
commonj.connector.runtime.SelectorException: For the IDoc type 
SapYwmspgi01, operation key=YWMSPGIWMS not found using the 
application-specific information {Create={MsgType=, MsgCode=, MsgFunction=}} 
verify apropriate combination of MsgType,MsgCode, MsgFunction is set in 
SapYwmspgi01, application-specific information.
--
  • Explanation: When you run the Adapter Connection wizard for an inbound IDOC, then you run the wizard again for an outbound IDOC, the outbound IDOC definition replaces the inbound IDOC definition. Information that is stored in the inbound definition is used to map MsgType, MsgCode, and MsgFunction to a method binding. The outbound definition does not contain these mappings, so processing of the inbound IDOC fails.
  • Solution: To avoid this error, ensure that inbound and outbound IDOCs have different names if they are stored in the same message set.