IBM WebSphere Business Integration Adapter Using Connector Configurator with ICS as the broker

Page 71

display. When you select a name in the Template Name display, the Property Template Preview display shows the connector-specific properties that have been defined in that template.

After you have chosen the template you want to use, choose OK.

3.A configuration screen will display for the connector that you are configuring. The title bar of the configuration screen shows the broker that you are using and the name that you have given to the connector. You can fill in all the field values to complete the definition now, or you can save the file and complete the fields later.

When you are using the configuration screen, you can, if you wish, add additional connector-specific properties, as described under “Setting application-configuration properties (ICS)” on page 64. Any such additions become part of the configuration file that you are creating, but do not affect the template that you used in creating the file.

4.To save the file, choose File > Save > to File or File > Save > Save to the project. To save to a project, you must be using ICS as the broker, and System Manager must be running. If you save as a file, the Save File Connector dialog displays.

Choose *.cfg as the file type, verify in the File Name field that the name is spelled correctly and has the correct case, navigate to the directory where you want to locate the file, and choose Save. The status display in the message panel of Connector Configurator indicates that the configuration file was successfully created.

Important: The directory path and name that you establish here must match the connector configuration file path and name that you supply in the startup file for the connector.

5.To complete the connector definition, enter values in the fields for each of the tabs of the Connector Configurator window, as described for your broker later in this chapter.

Using Connector Configurator with ICS as the broker

To use Connector Configurator to configure a connector that will be used with ICS, first select ICS as the broker mode in which you are running Connector Configurator, as described under“Choosing your broker” on page 57.

In a typical ICS implementation, the configuration file that you create with Connector Configurator is not put into use until after you have deployed it to the ICS server. You will perform that deployment (described in the Implementation Guide for WebSphere InterChange Server) after you have finished using Connector Configurator to complete the connector configuration file.

Completing a configuration file

This topic assumes that you already have a starting point for your connector configuration, either from an existing file (a connector definitions file, a repository file, or a *.cfg file) or from an existing project in System Manager. If you do not, see “Creating a template of connector-specific properties” on page 58.

When you open a configuration file or a connector from a project, the Connector Configurator window displays the configuration screen, with the attributes and values that Connector Configurator finds in the connector definition file.

The title of the configuration screen displays the type of the broker and the name of the connector as specified in the file. Make sure the title indicates the

Appendix B. Connector Configurator 61

Page 70 Page 72
Image 71
Page 70 Page 72
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