IBM WebSphere Business Integration Adapter manual Configuring metaobjects for polling, Type=output

Page 23

vThe 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.

vThe 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:

vIBM_OptParams and IBM_OptimizationResults represent the top level business object generated by the XML ODA.

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

vThe operation is addBid.

vThe 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

IBM_Bidding_BO

Port=Bidding

IBM_OpParams

Type=input

IBM_OptimizationResults

Type=output

MO_Instance

Verb=addBid

IBM_OptParams

LaneId

Price

IBM_OptimizationResults

WinningBid

MO_Instance

InstanceId

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

Page 22 Page 24
Image 23
Page 22 Page 24
Contents Adapter for i2 User Guide Page Adapter for i2 User Guide 18April2003 Integration broker compatibility Iv Adapter for i2 User Guide Contents Appendix D. Notices Typographic conventions About this documentAudience Related documentsViii Adapter for i2 User Guide Connector architecture Overview of the connectorComponent Description XML DH Wbia APIEvent detection and notification How the connector worksProcessing subscriptions Event retrieval Processing service call requestsStatus updates Processing verbs operationsStatus updates Adapter for i2 User Guide Step for installing the standard files Installing and configuring the connectorPrerequisites for installing the connector Installing the connector on a Windows or Unix systemConfiguring the connector Installed file structureMessageFileName Standard connector propertiesConnector-specific properties LogAtInterchangeEndProperty Description Starting the connectorConfiguring starti2.bat for Windows or starti2.sh for Unix Configuring DataHandlerOverview of business object structure Understanding business objects for the connectorDefining connector metadata Wrapper BO I2 business object structureType=output Configuring metaobjects for pollingAttribute Description Specifying business object attribute propertiesParameter Description Special attribute valuesApplication-specific information at the attribute level Adapter for i2 User Guide Overview of i2 ODA Generating business objects using i2 ODAInstalling i2 ODA Steps for installing i2 ODALaunching i2 ODA Other installation requirementsTrace Level Description Working with error and trace message filesUsing i2 ODA in Business Object Designer Select the Agent Steps for using i2ODAConfigure agent properties Example i2BO Row Property name Property type Description NumberAdapter for i2 User Guide Generating business objects using i2 ODA Property Value Save the business object filesCreate the metaobject for polling I2MOOperation InstanceId DefaultValue= WrapperBONameAdapter for i2 User Guide Structure of error messages Troubleshooting and error handlingLogging error messages Error description Error type Handling by i2 connector Polling-related error messagesService call request processing error messages Example Tracing messagesTracing Level Tracing MessagesTips for troubleshooting Adapter for i2 User Guide New and deleted properties Appendix A. Standard configuration properties for connectorsAdapter for i2 User Guide Property Name Possible Default Update Values Method CONNECTORNAME/REQUESTQUEUE AgentTraceLevel AdminInQueueAdminOutQueue AgentConnectionsConcurrentEventTriggeredFlows ApplicationNameBrokerType CharacterEncodingControllerTraceLevel ContainerManagedEventsControllerStoreAndForwardMode WebSphere MQ and IDL DeliveryQueueDeliveryTransport JvmMaxNativeStackSize FaultQueueDuplicateEventElimination JvmMaxHeapSizeJms.MessageBrokerName Jms.PasswordJvmMinHeapSize Jms.FactoryClassNameOADAutoRestartAgent LogAtInterchangeEndMaxEventCapacity MessageFileNamePollFrequency OADMaxNumRetryOADRetryTimeInterval PollEndTimeRestartRetryInterval RepositoryDirectoryResponseQueue RestartRetryCountTraceFileName SynchronousRequestTimeoutWireFormat Application name Name Possible values Default valueApplicationName AdminInQueueAdminOutQueue AgentTraceLevelDeliveryTransport FaultQueueContainerManagedEvents DeliveryQueueJms.NumConcurrentRequests Jms.PasswordJms.FactoryClassName Jms.MessageBrokerNameRepositoryDirectory PollEndTimePollFrequency PollStartTimeRestartRetryCount SynchronousTimeoutRequestQueue ResponseQueueWireFormat Adapter for i2 User Guide Appendix B. Connector Configurator ValueenGB/Value Starting Connector ConfiguratorRunning Configurator from System Manager Choosing your broker Running Configurator independently of System ManagerCreating a template of connector-specific properties Using a connector-specific property templateSpecifying values Specifying general characteristicsSetting dependencies Completing a configuration file Using Connector Configurator with ICS as the brokerUsing an existing file Setting the configuration file properties ICS Using an existing System Manager projectSetting application-configuration properties ICS Setting standard connector properties ICSBusiness object name Encryption for connector properties ICSUpdate method ICS Specifying supported business object definitions ICSMaximum transaction level Associated maps ICSAgent support Resources ICS Setting trace/log file values ICSData handlers Configuring messagingSetting application-configuration properties Setting standard connector propertiesSpecifying supported business object definitions Encryption for connector propertiesUpdate method Configuring data handlers Setting trace/log file valuesCompleting the configuration Category Feature Support Appendix C. Connector feature listEvent notification features Service call request handling featuresGeneral features Appendix C. Connector feature list Adapter for i2 User Guide Appendix D. Notices Programming interface information Trademarks and service marksIBM Adapter for i2 User Guide

WebSphere Business Integration Adapter specifications

IBM WebSphere Business Integration Adapter is an essential component of IBM's integration solutions, providing organizations with a robust framework to connect various systems, applications, and data sources. This versatile solution is particularly designed to streamline the integration of enterprise applications and enhance their interactions.

One of the main features of the WebSphere Business Integration Adapter is its wide range of pre-built adapters. These adapters facilitate seamless connectivity with diverse applications, such as ERP systems, CRM software, databases, and legacy systems. This wide compatibility ensures that organizations can automate processes and share data effortlessly, reducing the time and overhead typically associated with manual integrations.

Another notable feature of the integration adapter is its support for various messaging protocols, including JMS, MQ, and HTTP. This multi-protocol support enables organizations to easily implement message-driven architectures by facilitating reliable and asynchronous communication between disparate systems. As a result, businesses can achieve greater scalability and responsiveness in their operations.

The technology stack behind IBM WebSphere Business Integration Adapter also incorporates standards-based protocols, such as Web Services (SOAP, REST) and XML messaging. This adherence to industry standards ensures that the adapter can easily integrate with modern cloud-based applications and services, providing organizations with the flexibility to adapt to evolving technological landscapes.

In addition to its core integration capabilities, the WebSphere Business Integration Adapter supports comprehensive monitoring and management features. Administrators can easily track the performance of integration flows, monitor message processing, and manage exceptions through an intuitive dashboard. This visibility enables organizations to proactively address issues before they escalate, ensuring smooth and uninterrupted operations.

Another significant characteristic of the IBM WebSphere Business Integration Adapter is its scalability. Organizations can deploy the adapter in various environments, from on-premise data centers to cloud infrastructures. This flexibility allows businesses to scale their integration solutions as needed, accommodating growing data volumes and increasing transaction demands with ease.

Moreover, the adapter's modular architecture makes it easy to customize and extend. Businesses can enhance existing functionalities or integrate additional capabilities to meet specific requirements, ensuring that their integration solutions remain relevant and effective in an ever-changing business landscape.

In conclusion, the IBM WebSphere Business Integration Adapter is a powerful tool for organizations looking to enhance their system integrations. With its extensive features, support for multiple technologies, and capacity for customization, it positions businesses for success in an increasingly interconnected world. By leveraging this adapter, organizations can achieve greater efficiency, agility, and operational excellence in their integration efforts.
Top Page Image Contents