beautypg.com

Configuring metaobjects for polling – IBM WebSphere Business Integration Adapter User Manual

Page 23

background image

v

The operation is set as the verb on the wrapper business object and is associated
with a port. i2 does not have standard verbs. If multiple operations have the
same set of input and output types, but are supported on different ports, there
will be two different wrapper business objects for the different ports.

v

The types are business object attributes which represent data types for an
operation.

The following diagram illustrates a sample business object IBM_Bidding_BO,
which has three child business objects. In the diagram:

v

IBM_OptParams and IBM_OptimizationResults represent the top level business

object generated by the XML ODA.

v

The application-specific information for the business object is in the Port
(Bidding) and Types (input--IBM_OptParams and output--
IBM_OptimizationResults) attributes.

v

The operation is addBid.

v

The child business objects are:
– IBM_OptParams, which has two attributes--LaneId and Price
– IBM_OptimizationResults, which has one attribute--WinningBid
– MO_Instance, which has one attribute--InstanceId

Port=Bidding

IBM_Bidding_BO

MO_Instance

IBM_OptimizationResults

Type=input

IBM_OpParams

Type=output

Verb=addBid

IBM_OptParams

LaneId
Price

InstanceId

MO_Instance

IBM_OptimizationResults

WinningBid

Configuring metaobjects for polling

The connector uses i2 metaobjects to register its interest in specific operations with
the CIS agent so that polling can take place. You need to configure one metaobject
for each operation of interest.

The metaobject name always starts with i2MO. Each metaobject holds information
about the instance that supports the operation and the wrapper business object
name for the operation. You need to add a dummy verb to all the metaobjects.

The attributes (instance ID, wrapper business object name, and operation name)
within the metaobjects have a static default value. For registering the same
operation on a different instance, you either have to change the default value and
restart the i2 instance or configure another metaobject for the new instance.

In the following diagram, the metaobject named i2MO_AddBid is used to
configure the instance ID CA_Instance, for the Bidding operation addBid, which is
set on the wrapper business object named IBM_Bidding_BO. The values shown are
default values for the attributes.

Chapter 3. Understanding business objects for the connector

13