Resolving problems when you use CORBA nodes
Advice for dealing with common problems that can arise when you develop message flows that contain CORBA nodes.
Before you begin
About this task
Error message BIP4891 is issued when you include a CORBARequest node in a message flow
Procedure
- Scenario: You have created a message flow that contains a CORBARequest node, but error message BIP4891 is issued, indicating that the node did not receive a valid body.
- Explanation: This error message indicates that the CORBARequest node is trying to call an operation but cannot find the required input parameters in the incoming tree. IBM Integration Bus uses the DataObject parser to read and write message from CORBA applications. If you use an input node to pass XML into the CORBARequest node, ensure that it uses the DataObject domain.
- Solution: Ensure that the incoming message has the correct structure. If you are using an input node to pass XML into the CORBARequest node, set the Message domain property on the Input Message Parsing tab of the input node to DataObject.
A CORBA IDL file drop error is issued when you are using an IDL file that contains includes
Procedure
- Scenario: You have dragged a CORBA IDL file onto the canvas but a CORBA IDL file drop error is issued.
- Explanation: If you have imported an IDL file that contains includes, you must drag the top-level IDL file onto the canvas so that the CORBARequest node has all the relevant information. Similarly, when setting properties on the CORBARequest node, if you have imported an IDL file that contains includes, you must select the top-level IDL file in the IDL file property.
- Solution: Drag the top-level IDL file onto the canvas, or set the IDL file property on the CORBARequest node to the top-level IDL file.