IBM WebSphere Business Integration Adapter manual Processing verbs operations, Status updates

Page 14

Status updates

No status updates are made to the i2 applications. Typically, the event status, for example, SUCCESS, FAIL, UNSUBSCRIBED, is written to the application’s event store. Since no event store is maintained for i2, the status update strategy is not relevant for the i2 connector. Error messages, if any, are logged to the i2 adapter log file. For more information, see Chapter 5, “Troubleshooting and error handling”, on page 27.

Event retrieval

For the i2 connector, polling is single threaded. The connector uses i2 metaobjects to register the operations of interest with the CIS agent for polling. These metaobject names have the i2MO prefix and store information about the operation and the corresponding IBM wrapper business object name for the specified operation and type. The attributes for the metaobject are specified as static default values. Default value is an attribute property, which can be set at the business object design time. For information on the wrapper business object structure and attribute properties, see Chapter 3, “Understanding business objects for the connector”, on page 11 and Chapter 4, “Generating business objects using i2 ODA”, on page 17.

The steps involved in retrieving a subscription message are as follows:

1.The i2 connector registers the operations with the CIS agent after reading the i2MO metaobject information. The information in the metaobjects is cached by the i2 connector with the first poll call.

2.Each poll call is issued from the integration broker based on the connector property PollFrequency. In case there were any registration failures in the first poll call, the i2 connector tries to register the same operation with the subsequent poll calls.

3.With all the poll calls, the i2 connector checks on the output of the operations that it has registered with the CIS agent. If there is any output from any of the operations, it retrieves the output in the form of a CIS record. The i2 connector retrieves the PollQuantity (connector property) number of messages for each poll call for each registered operation.

Example: If the PollQuantity is set to 5 and there are 5 registered operations, each poll call will result in checking the output 25 times. If the PollQuantity is not set, a default of 1 message is retrieved for each poll call for each operation.

4.The retrieved XML message is converted to a business object. The business object is set as the child attribute in the wrapper business object for the operation. The instance ID from which this output was retrieved is set as the instance ID in the metaobject attribute of the wrapper. For more information, see Chapter 3, “Understanding business objects for the connector”, on page 11.

5.The connector sends the wrapper business object to the integration broker for further processing.

Processing verbs (operations)

Operations are i2’s equivalent for verbs and are defined by the XML structure provided by i2 for each port. For more information, see Chapter 3, “Understanding business objects for the connector”, on page 11, and Chapter 4, “Generating business objects using i2 ODA”, on page 17.

Processing service call requests

When the i2 connector receives a service call request from an integration broker to perform an operation in an application, the request takes the form of a wrapper business object. The wrapper business object encompasses the instance ID

4Adapter for i2 User Guide

Page 13 Page 15
Image 14
Page 13 Page 15
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 Related documents About this documentAudience Typographic conventionsViii Adapter for i2 User Guide Overview of the connector Connector architectureXML DH Wbia API Component DescriptionEvent detection and notification How the connector worksProcessing subscriptions Processing verbs operations Processing service call requestsStatus updates Event retrievalStatus updates Adapter for i2 User Guide Installing the connector on a Windows or Unix system Installing and configuring the connectorPrerequisites for installing the connector Step for installing the standard filesInstalled file structure Configuring the connectorLogAtInterchangeEnd Standard connector propertiesConnector-specific properties MessageFileNameConfiguring DataHandler Starting the connectorConfiguring starti2.bat for Windows or starti2.sh for Unix Property DescriptionOverview of business object structure Understanding business objects for the connectorDefining connector metadata I2 business object structure Wrapper BOConfiguring metaobjects for polling Type=outputSpecifying business object attribute properties Attribute DescriptionParameter Description Special attribute valuesApplication-specific information at the attribute level Adapter for i2 User Guide Steps for installing i2 ODA Generating business objects using i2 ODAInstalling i2 ODA Overview of i2 ODAOther installation requirements Launching i2 ODATrace Level Description Working with error and trace message filesUsing i2 ODA in Business Object Designer Select the Agent Steps for using i2ODAConfigure agent properties Row Property name Property type Description Number Example i2BOAdapter for i2 User Guide Generating business objects using i2 ODA Save the business object files Property ValueI2MOOperation InstanceId DefaultValue= WrapperBOName Create the metaobject for pollingAdapter for i2 User Guide Structure of error messages Troubleshooting and error handlingLogging error messages Polling-related error messages Error description Error type Handling by i2 connectorService call request processing error messages Tracing Messages Tracing messagesTracing Level ExampleTips for troubleshooting Adapter for i2 User Guide Appendix A. Standard configuration properties for connectors New and deleted propertiesAdapter for i2 User Guide Property Name Possible Default Update Values Method CONNECTORNAME/REQUESTQUEUE AgentConnections AdminInQueueAdminOutQueue AgentTraceLevelCharacterEncoding ApplicationNameBrokerType ConcurrentEventTriggeredFlowsControllerTraceLevel ContainerManagedEventsControllerStoreAndForwardMode WebSphere MQ and IDL DeliveryQueueDeliveryTransport JvmMaxHeapSize FaultQueueDuplicateEventElimination JvmMaxNativeStackSizeJms.FactoryClassName Jms.PasswordJvmMinHeapSize Jms.MessageBrokerNameMessageFileName LogAtInterchangeEndMaxEventCapacity OADAutoRestartAgentPollEndTime OADMaxNumRetryOADRetryTimeInterval PollFrequencyRestartRetryCount RepositoryDirectoryResponseQueue RestartRetryIntervalTraceFileName SynchronousRequestTimeoutWireFormat Name Possible values Default value Application nameAgentTraceLevel AdminInQueueAdminOutQueue ApplicationNameDeliveryQueue FaultQueueContainerManagedEvents DeliveryTransportJms.MessageBrokerName Jms.PasswordJms.FactoryClassName Jms.NumConcurrentRequestsPollStartTime PollEndTimePollFrequency RepositoryDirectoryResponseQueue SynchronousTimeoutRequestQueue RestartRetryCountWireFormat Adapter for i2 User Guide Appendix B. Connector Configurator ValueenGB/Value Starting Connector ConfiguratorRunning Configurator from System Manager Running Configurator independently of System Manager Choosing your brokerUsing a connector-specific property template Creating a template of connector-specific propertiesSpecifying general characteristics Specifying valuesSetting dependencies Using Connector Configurator with ICS as the broker Completing a configuration fileUsing an existing file Using an existing System Manager project Setting the configuration file properties ICSSetting standard connector properties ICS Setting application-configuration properties ICSSpecifying supported business object definitions ICS Encryption for connector properties ICSUpdate method ICS Business object nameMaximum transaction level Associated maps ICSAgent support Setting trace/log file values ICS Resources ICSConfiguring messaging Data handlersSetting standard connector properties Setting application-configuration propertiesSpecifying supported business object definitions Encryption for connector propertiesUpdate method Setting trace/log file values Configuring data handlersCompleting the configuration Service call request handling features Appendix C. Connector feature listEvent notification features Category Feature SupportGeneral features Appendix C. Connector feature list Adapter for i2 User Guide Appendix D. Notices Trademarks and service marks Programming interface informationIBM 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