IBM WebSphere Business Integration Adapter manual Appendix B. Connector Configurator

Page 65

Appendix B. Connector Configurator

Before you can use a connector, you must create a connector configuration file that sets the properties for the connector, designates the business objects and any meta-objects that it supports, and sets logging and tracing values that the connector will use at runtime. The configuration file may also contain properties for the use of messaging and data handlers required by your connector.

Use Connector Configurator to create and modify the configuration file for your connector. If a configuration file has previously been created for your connector, you can use Connector Configurator to open the file and modify its settings. If no configuration file has yet been created for your connector, you can use Connector Configurator to both create the file and set its properties.

When you complete a connector configuration file, the file is saved as an XML document. You will save the XML document either as a project in System Manager (if ICS is your broker) or as a file with a *.cfg extension in a directory folder (if WebSphere MQ Integrator Broker is your broker, or if you are using the file as a local configuration file for ICS).

This appendix describes how to use Connector Configurator to:

vCreate a connector-specific property template for configuring your connector

vCreate a configuration file

vSet properties in a configuration file

Connector Configurator runs only in a Windows environment. If you are running the connector itself in a UNIX environment, use Connector Configurator in the Windows system in the network to modify the configuration file. Then copy the file to your UNIX environment.

Note: Some properties in the connector configuration file use directory paths, and these paths default to the Windows convention for directory paths. If you use the connector configuration file in a UNIX environment, revise any directory path constructs in the configuration properties to match the UNIX convention for directory paths.

Using Connector Configurator in an internationalized environment

Connector Configurator is internationalized and handles character conversion between the configuration file and the integration broker. Connector Configurator uses native encoding. When it writes to the configuration file, it uses UTF-8 encoding.

Connector Configurator supports non-English characters in:

vAll value fields

vLog file and trace file path (specified in the Trace/Log files tab)

The drop list for the CharacterEncoding and Locale standard configuration properties displays only a subset of supported values. To add other values to the drop list, you must manually modify the \Data\Std\stdConnProps.xml file in the product directory.

© Copyright IBM Corp. 2002, 2003

55

Page 64 Page 66
Image 65
Page 64 Page 66
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 APIEvent detection and notification How the connector worksProcessing subscriptions 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 DescriptionOverview 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 Installing i2 ODA Generating business objects using i2 ODASteps for installing i2 ODA Overview of 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 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 ConcurrentEventTriggeredFlowsControllerTraceLevel ContainerManagedEventsControllerStoreAndForwardMode WebSphere MQ and IDL DeliveryQueueDeliveryTransport DuplicateEventElimination FaultQueueJvmMaxHeapSize JvmMaxNativeStackSizeJvmMinHeapSize Jms.PasswordJms.FactoryClassName Jms.MessageBrokerNameMaxEventCapacity LogAtInterchangeEndMessageFileName OADAutoRestartAgentOADRetryTimeInterval OADMaxNumRetryPollEndTime PollFrequencyResponseQueue RepositoryDirectoryRestartRetryCount RestartRetryIntervalTraceFileName SynchronousRequestTimeoutWireFormat 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 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 ICSUpdate method ICS Encryption for connector properties ICSSpecifying supported business object definitions ICS Business object nameMaximum 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 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.
Top Page Image Contents