IBM WebSphere Business Integration Adapter How the connector works, Processing subscriptions

Page 13

Component

Description

 

 

CIS server

Integration container which handles operation invocations. Integration

 

container and CIS server are used interchangeably in this document.

 

 

How the connector works

The i2 connector is a CIS (Common Integration Services) client. It connects to the CIS client API in a non-managed environment, that is, it connects to the CIS adapter directly without an application server. No authentication is necessary (no user name or password is required). At present, the CIS client API does not support any connection pooling mechanism. Hence, connections are created for every transaction. For information on configuration properties, see “Configuring the connector” on page 8.

The i2 connector is bi-directional. It can process events originating from i2 applications, as well as requests sent by the broker to the application.

For event subscriptions, the i2 connector uses the information in the i2 metaobjects. It registers the operations on the types specified in these metaobjects with i2’s CIS agent. CIS agent listens to the registered operations and detects event messages only for registered operations. The i2 connector obtains these messages with the poll call.

For request processing, the i2 connector processes the requests coming from the integration broker by transforming incoming business objects into CIS records and using the appropriate CIS Client API calls to execute the operation on the i2 application modules.

The i2 connector follows the metadata design principles outlined in the IBM Connector Developer’s Guidelines. This means new IBM business objects can be defined without additional coding or customization at the i2 connector code level. For more information, see Chapter 3, “Understanding business objects for the connector”, on page 11.

Processing subscriptions

The following sections describe how the connector processes application events.

Event detection and notification

Events for the purpose of this document are the CIS messages published from the i2 application modules. The i2 application notifies the connector of all the events occurring in the modules for which corresponding operations have been registered with the CIS agent.

The onus of registering the operations of interest lies with the i2 connector.

Example: If the i2 connector is interested in the Bidding type operation addBid, any new Bidding additions to the i2 application module will be queued in the CIS server once the i2 connector registers for the addBid operation.

The i2 connector uses the information in the i2 metaobjects. It registers its intent to listen to some of the operations with the poll call. Effectively, this tells the CIS agent that the i2 connector wants to check for the output of the registered operations.

Chapter 1. Overview of the connector 3

Image 13
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 Audience About this documentRelated documents Typographic conventionsViii Adapter for i2 User Guide Connector architecture Overview of the connectorComponent Description XML DH Wbia APIProcessing subscriptions How the connector worksEvent detection and notification Status updates Processing service call requestsProcessing verbs operations Event retrievalStatus updates Adapter for i2 User Guide Prerequisites for installing the connector Installing and configuring the connectorInstalling the connector on a Windows or Unix system Step for installing the standard filesConfiguring the connector Installed file structureConnector-specific properties Standard connector propertiesLogAtInterchangeEnd MessageFileNameConfiguring starti2.bat for Windows or starti2.sh for Unix Starting the connectorConfiguring DataHandler Property DescriptionDefining connector metadata Understanding business objects for the connectorOverview of business object structure Wrapper BO I2 business object structureType=output Configuring metaobjects for pollingAttribute Description Specifying business object attribute propertiesApplication-specific information at the attribute level Special attribute valuesParameter Description Adapter for i2 User Guide Installing i2 ODA Generating business objects using i2 ODASteps for installing i2 ODA Overview of i2 ODALaunching i2 ODA Other installation requirementsUsing i2 ODA in Business Object Designer Working with error and trace message filesTrace Level Description Configure agent properties Steps for using i2ODASelect the Agent 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 Logging error messages Troubleshooting and error handlingStructure of error messages Error description Error type Handling by i2 connector Polling-related error messagesService call request processing error messages Tracing Level Tracing messagesTracing Messages ExampleTips 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 AdminOutQueue AdminInQueueAgentConnections AgentTraceLevelBrokerType ApplicationNameCharacterEncoding ConcurrentEventTriggeredFlowsControllerStoreAndForwardMode ContainerManagedEventsControllerTraceLevel DeliveryTransport DeliveryQueueWebSphere MQ and IDL DuplicateEventElimination FaultQueueJvmMaxHeapSize JvmMaxNativeStackSizeJvmMinHeapSize Jms.PasswordJms.FactoryClassName Jms.MessageBrokerNameMaxEventCapacity LogAtInterchangeEndMessageFileName OADAutoRestartAgentOADRetryTimeInterval OADMaxNumRetryPollEndTime PollFrequencyResponseQueue RepositoryDirectoryRestartRetryCount RestartRetryIntervalWireFormat SynchronousRequestTimeoutTraceFileName Application name Name Possible values Default valueAdminOutQueue AdminInQueueAgentTraceLevel ApplicationNameContainerManagedEvents FaultQueueDeliveryQueue DeliveryTransportJms.FactoryClassName Jms.PasswordJms.MessageBrokerName Jms.NumConcurrentRequestsPollFrequency PollEndTimePollStartTime RepositoryDirectoryRequestQueue SynchronousTimeoutResponseQueue RestartRetryCountWireFormat Adapter for i2 User Guide Appendix B. Connector Configurator Running Configurator from System Manager Starting Connector ConfiguratorValueenGB/Value 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 ICSUpdate method ICS Encryption for connector properties ICSSpecifying supported business object definitions ICS Business object nameAgent support Associated maps ICSMaximum transaction level Resources ICS Setting trace/log file values ICSData handlers Configuring messagingSetting application-configuration properties Setting standard connector propertiesUpdate method Encryption for connector propertiesSpecifying supported business object definitions Configuring data handlers Setting trace/log file valuesCompleting the configuration Event notification features Appendix C. Connector feature listService call request handling features Category Feature SupportGeneral 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.