Advice for dealing with common
problems that can arise when you develop message flows that contain
CORBA nodes.
IBM® Integration Bus does
not currently support all CORBA operations and types. Ensure that
you are passing in a valid IDL file that contains supported operations
and types. For a full list of what is supported, see CORBA support. To ensure that the IDL file is valid,
run it through an IDL parser.
Error message BIP4891 is issued when you include
a CORBARequest node in
a message flow
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
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.
Error message BIP4910 is issued during deployment
when you are using an IDL file that contains includes
Scenario: You are deploying a message flow that
contains a CORBARequest node,
but error message BIP4910 is issued.
Explanation: This error is issued when you have
imported an IDL file that contains includes, but not all the included
IDL files have been added to the BAR file. For example, you might
have dragged only the message flow onto the integration server. If you
have imported an IDL file that contains includes, you must ensure
that all the included IDL files are added to the BAR file so that
all the relevant information is available to the message flow.
Solution: When you deploy a message flow that contains
a CORBARequest node and
an IDL file that contains includes, ensure that all included IDL files
are added to the BAR file.
If you are dragging a message
flow that uses a multifile IDL file onto an integration server in the Integration Development perspective, included IDL files are not
deployed. To deploy message flows that use multifile IDL files, you
must create a BAR file.
Last updated Friday, 21 July 2017