IBM WebSphere Business Integration Adapter manual Using an existing file

Page 72

appropriate type for your broker--either ICS or WebSphere MQ Integrator Broker (for WMQI). If it does not, change the broker value before you configure the connector. To do so:

1.Under the Standard Properties tab, select the value field for the BrokerType property. In the drop-down menu, select the value WMQI or ICS.

2.The Standard Properties tab refreshes to display properties associated with the selected broker. When you save the file, you retain this broker selection. You can save the file now or proceed to complete the remaining configuration fields, as described in “Setting the configuration file properties (WebSphere MQ Integrator Broker)” on page 68.

3.When you have finished making entries in the configuration fields, choose File>Save>To Project or File>Save>To File.

If you are saving to file, choose *.cfg as the extension, choose the correct location for the file and choose Save.

If multiple connector configurations are open, choose Save All to File to save all of the configurations to file, or choose Save All to Project to save all ICS connector configurations to a System Manager project.

Before it saves the file, Connector Configurator validates that values have been set for all required Standard properties. If a required Standard property is missing a value, Connector Configurator displays a message that the validation failed. You must supply a value for the property in order to save the configuration file.

Using an existing file

You may have an existing file available in one or more of the following formats:

vA connector definition file. This is a text file that lists properties and applicable default values for a specific connector. Some connectors include such a file in a \repository directory in their delivery package (the file typically has the extension .txt; for example, CN_XML.txt for the XML connector).

vAn ICS repository file. Definitions used in a previous ICS implementation of the connector may be available to you in a repository file that was used in the configuration of that connector. Such a file typically has the extension .in or

.out.

vA previous configuration file for the connector. Such a file typically has the extension *.cfg.

Although any of these file sources may contain most or all of the connector-specific properties for your connector, the connector configuration file will not be complete until you have opened the file and set properties, as described later in this chapter.

To use an existing file to configure a connector, you must open the file in Connector Configurator, revise the configuration, and then save the file as a configuration file (*.cfg file).

Follow these steps to open a *.txt, *.cfg, or *.in file from a directory:

1.In Connector Configurator, choose File > Open > From File.

2.In the Open File Connector dialog, choose one of the following file types to see the available files:

v Configuration (*.cfg)

vICS Repository (*.in, *.out)

Choose this option if a repository file was used to configure the connector in an ICS environment. A repository file may include multiple connector definitions, all of which will display when you open the file.

62Adapter for i2 User Guide

Page 71 Page 73
Image 72
Page 71 Page 73
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 About this document AudienceRelated documents Typographic conventionsViii Adapter for i2 User Guide Overview of the connector Connector architectureXML DH Wbia API Component DescriptionHow the connector works Processing subscriptionsEvent detection and notification Processing service call requests Status updatesProcessing verbs operations Event retrievalStatus updates Adapter for i2 User Guide Installing and configuring the connector Prerequisites for installing the connectorInstalling the connector on a Windows or Unix system Step for installing the standard filesInstalled file structure Configuring the connectorStandard connector properties Connector-specific propertiesLogAtInterchangeEnd MessageFileNameStarting the connector Configuring starti2.bat for Windows or starti2.sh for UnixConfiguring DataHandler Property DescriptionUnderstanding business objects for the connector Defining connector metadataOverview of business object structure I2 business object structure Wrapper BOConfiguring metaobjects for polling Type=outputSpecifying business object attribute properties Attribute DescriptionSpecial attribute values Application-specific information at the attribute levelParameter Description Adapter for i2 User Guide Generating business objects using i2 ODA Installing i2 ODASteps for installing i2 ODA Overview of i2 ODAOther installation requirements Launching i2 ODAWorking with error and trace message files Using i2 ODA in Business Object DesignerTrace Level Description Steps for using i2ODA Configure agent propertiesSelect the Agent 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 Troubleshooting and error handling Logging error messagesStructure of error messages Polling-related error messages Error description Error type Handling by i2 connectorService call request processing error messages Tracing messages Tracing LevelTracing Messages 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 AdminInQueue AdminOutQueueAgentConnections AgentTraceLevelApplicationName BrokerTypeCharacterEncoding ConcurrentEventTriggeredFlowsContainerManagedEvents ControllerStoreAndForwardModeControllerTraceLevel DeliveryQueue DeliveryTransportWebSphere MQ and IDL FaultQueue DuplicateEventEliminationJvmMaxHeapSize JvmMaxNativeStackSizeJms.Password JvmMinHeapSizeJms.FactoryClassName Jms.MessageBrokerNameLogAtInterchangeEnd MaxEventCapacityMessageFileName OADAutoRestartAgentOADMaxNumRetry OADRetryTimeIntervalPollEndTime PollFrequencyRepositoryDirectory ResponseQueueRestartRetryCount RestartRetryIntervalSynchronousRequestTimeout WireFormatTraceFileName Name Possible values Default value Application nameAdminInQueue AdminOutQueueAgentTraceLevel ApplicationNameFaultQueue ContainerManagedEventsDeliveryQueue DeliveryTransportJms.Password Jms.FactoryClassNameJms.MessageBrokerName Jms.NumConcurrentRequestsPollEndTime PollFrequencyPollStartTime RepositoryDirectorySynchronousTimeout RequestQueueResponseQueue RestartRetryCountWireFormat Adapter for i2 User Guide Appendix B. Connector Configurator Starting Connector Configurator Running Configurator from System ManagerValueenGB/Value 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 ICSEncryption for connector properties ICS Update method ICSSpecifying supported business object definitions ICS Business object nameAssociated maps ICS Agent supportMaximum transaction level Setting trace/log file values ICS Resources ICSConfiguring messaging Data handlersSetting standard connector properties Setting application-configuration propertiesEncryption for connector properties Update methodSpecifying supported business object definitions Setting trace/log file values Configuring data handlersCompleting the configuration Appendix C. Connector feature list Event notification featuresService call request handling 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