IBM WebSphere Business Integration Adapter manual Using a connector-specific property template

Page 68

After you have completed the configuration file and set its properties, it will need to be deployed to the appropriate location for your connector.

vIf you are using ICS as your broker, save the configuration in a System Manager project, and use System Manager to load the file into InterChange Server.

vIf you are using WebSphere MQ Integrator Broker as your broker, manually copy the configuration file to its appropriate location, which must match exactly the configuration file location specified in the startup file for your connector.

For further information about deployment, see the Implementation Guide for WebSphere InterChange Server (for using the connector with ICS as the broker), or the Implementation Guide for WebSphere MQ Integrator Broker (for using the connector with MQ Integrator as the broker).

Using a connector-specific property template

To create a configuration file for your connector, you can start with a previously created connector configuration file (*.cfg), a connector definition file (*.txt) or a repository file (*.in or *.out), if any of these already exists for your connector. For instructions on using such existing files, see “Using an existing file” on page 62.

If none of those files exist, or if they are too dissimilar to the configuration requirements of your connector, you can start instead by creating a template for the connector-specific properties of your connector. You’ll create properties in the template, define general characteristics and values for those properties, and specify any dependencies between the properties. Then you’ll save the template and use it as the base for creating a new connector configuration file.

Creating a template of connector-specific properties

To create a template:

1.Choose File>New>Connector-Specific Property Template.

2.The Connector-Specific Property Template dialog appears, with the following fields

v Name

Enter a unique name that identifies the connector, or type of connector, for which this template will be used. You will see this name again when you open the dialog for creating a new configuration file from a template.

vFind Template, and Template Name

The names of all currently available templates are displayed in the Template Name display. Look for an existing template that would make a good starting point for your new connector template (such as a template whose property definitions are a subset of the properties used by your connector).

To see the connector-specific property definitions that are contained in any template, select that template’s name in the Template Name display. A list of the property definitions contained in that template will appear in the Template Preview display.

If you do not see any template that displays the connector-specific properties that are used by your connector, you will need to create one. Connector Configurator provides a template named None, containing no property definitions, as a default choice.

Choose a template from the Template Name display, enter that template name in the Find Name field (or highlight your choice in Template Name), and choose Next.

58Adapter for i2 User Guide

Page 67 Page 69
Image 68
Page 67 Page 69
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 DescriptionEvent detection and notification How the connector worksProcessing subscriptions 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 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 Generating business objects using i2 ODA Installing i2 ODASteps for installing 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 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 ConcurrentEventTriggeredFlowsControllerTraceLevel ContainerManagedEventsControllerStoreAndForwardMode WebSphere MQ and IDL DeliveryQueueDeliveryTransport FaultQueue DuplicateEventEliminationJvmMaxHeapSize JvmMaxNativeStackSizeJms.Password JvmMinHeapSizeJms.FactoryClassName Jms.MessageBrokerNameLogAtInterchangeEnd MaxEventCapacityMessageFileName OADAutoRestartAgentOADMaxNumRetry OADRetryTimeIntervalPollEndTime PollFrequencyRepositoryDirectory ResponseQueueRestartRetryCount RestartRetryIntervalTraceFileName SynchronousRequestTimeoutWireFormat 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 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 ICSEncryption for connector properties ICS Update method ICSSpecifying supported business object definitions 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 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