IBM WebSphere Business Integration Adapter Jms.FactoryClassName, Jms.MessageBrokerName, Locale

Page 60

The default value is CONNECTORNAME/FAULTQUEUE.

jms.FactoryClassName

Specifies the class name to instantiate for a JMS provider.

The default is CxCommon.Messaging.jms.IBMMQSeriesFactory.

jms.MessageBrokerName

Specifies the broker name to use for the JMS provider.

The default is crossworlds.queue.manager.

jms.NumConcurrentRequests

Specifies the maximum number of concurrent service call requests that can be sent to a connector at the same time. Once that maximum is reached, new service calls block and wait for another request to complete before proceeding.

The default value is 10.

jms.Password

Specifies the password for the JMS provider. A value for this property is optional.

There is no default.

jms.UserName

Specifies the user name for the JMS provider. A value for this property is optional.

There is no default.

Locale

Specifies the language code, country or territory, and, optionally, the associated character code set. The value of this property determines such cultural conventions as collation and sort order of data, date and time formats, and the symbols used in monetary specifications. For more information, see the overview chapter of the connector guide for an internationalized connector.

A locale name has the following format:

ll_TT.codeset

where:

 

ll

a two-character language code (usually in lower

 

case)

TT

a two-letter country or territory code (usually in

 

upper case)

codeset

the name of the associated character code set; this

 

portion of the name is often optional.

The default is en_US.

 

Important: By default only a subset of supported locales display in the drop list. To add other supported values to the drop list, you must manually modify the \Data\Std\stdConnProps.xml file in the product directory.

50Adapter for i2 User Guide

Page 59 Page 61
Image 60
Page 59 Page 61
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