IBM WebSphere Business Integration Adapter manual AdminInQueue, AdminOutQueue, AgentTraceLevel

Page 58

Name

Possible values

Default value

SourceQueue

valid WebSphere MQ

CONNECTORNAME/SOURCEQUEUE

 

queue name

 

SynchronousRequestQueue

valid WebSphere MQ

 

 

queue name

 

SynchronousResponseQueue

valid WebSphere MQ

 

 

queue name

 

SynchronousTimeout

an appropriate integer

0

 

indicating the number of

 

 

minutes the connector

 

 

waits for a response to a

 

 

synchronous request

 

WireFormat

CwXML

CwXML

 

 

 

AdminInQueue

The queue that is used by the integration broker to send administrative messages to the connector.

The default value is CONNECTORNAME/ADMININQUEUE.

AdminOutQueue

The queue that is used by the connector to send administrative messages to the integration broker.

AgentTraceLevel

Level of trace messages for the connector’s application-specific component. The default is 0. The connector delivers all trace messages applicable at the tracing level set or lower.

ApplicationName

Name that uniquely identifies the connection to the application. This name is used by the system administrator to monitor the connector’s environment. When you create a new connector definition, this property defaults to the name of the connector; when you work with the definition for an IBM WebSphere-delivered connector, the property is also likely to be set to the name of the connector. Set the property to a value that suggests the program with which the connector is interfacing, such as the name of an application, or something that identifies a file system or website in the case of technology connectors.

BrokerType

This property is set to the value WMQI for connectors that are configured to use WebSphere MQ Integrator Broker as the integration broker.

CharacterEncoding

Specifies the character code set used to map from a character (such as a letter of the alphabet, a numeric representation, or a punctuation mark) to a numeric value.

Note: Java-based connectors do not use this property. A C++ connector currently uses the value ASCII for this property. If you previously configured the value of this property to ascii7 or ascii8, you must reconfigure the connector to use either ASCII or one of the other supported values. To determine whether a specific connector is written in Java or C++, see the installing and configuring chapter of its adapter guide.

Important: By default only a subset of supported character encodings display in the drop list. To add other supported values to the drop list, you must

48Adapter for i2 User Guide

Page 57 Page 59
Image 58
Page 57 Page 59
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 Related documents About this documentAudience Typographic conventionsViii Adapter for i2 User Guide Overview of the connector Connector architectureXML DH Wbia API Component DescriptionProcessing subscriptions How the connector worksEvent detection and notification Processing verbs operations Processing service call requestsStatus updates Event retrievalStatus updates Adapter for i2 User Guide Installing the connector on a Windows or Unix system Installing and configuring the connectorPrerequisites for installing the connector Step for installing the standard filesInstalled file structure Configuring the connectorLogAtInterchangeEnd Standard connector propertiesConnector-specific properties MessageFileNameConfiguring DataHandler Starting the connectorConfiguring starti2.bat for Windows or starti2.sh for Unix Property DescriptionDefining connector metadata Understanding business objects for the connectorOverview of business object structure I2 business object structure Wrapper BOConfiguring metaobjects for polling Type=outputSpecifying business object attribute properties Attribute DescriptionApplication-specific information at the attribute level Special attribute valuesParameter Description Adapter for i2 User Guide Steps for installing i2 ODA Generating business objects using i2 ODAInstalling i2 ODA Overview of i2 ODAOther installation requirements Launching i2 ODAUsing i2 ODA in Business Object Designer Working with error and trace message filesTrace Level Description Configure agent properties Steps for using i2ODASelect 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 Logging error messages Troubleshooting and error handlingStructure of error messages Polling-related error messages Error description Error type Handling by i2 connectorService call request processing error messages Tracing Messages Tracing messagesTracing Level 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 AgentConnections AdminInQueueAdminOutQueue AgentTraceLevelCharacterEncoding ApplicationNameBrokerType ConcurrentEventTriggeredFlowsControllerStoreAndForwardMode ContainerManagedEventsControllerTraceLevel DeliveryTransport DeliveryQueueWebSphere MQ and IDL JvmMaxHeapSize FaultQueueDuplicateEventElimination JvmMaxNativeStackSizeJms.FactoryClassName Jms.PasswordJvmMinHeapSize Jms.MessageBrokerNameMessageFileName LogAtInterchangeEndMaxEventCapacity OADAutoRestartAgentPollEndTime OADMaxNumRetryOADRetryTimeInterval PollFrequencyRestartRetryCount RepositoryDirectoryResponseQueue RestartRetryIntervalWireFormat SynchronousRequestTimeoutTraceFileName Name Possible values Default value Application nameAgentTraceLevel AdminInQueueAdminOutQueue ApplicationNameDeliveryQueue FaultQueueContainerManagedEvents DeliveryTransportJms.MessageBrokerName Jms.PasswordJms.FactoryClassName Jms.NumConcurrentRequestsPollStartTime PollEndTimePollFrequency RepositoryDirectoryResponseQueue SynchronousTimeoutRequestQueue RestartRetryCountWireFormat Adapter for i2 User Guide Appendix B. Connector Configurator Running Configurator from System Manager Starting Connector ConfiguratorValueenGB/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 ICSSpecifying supported business object definitions ICS Encryption for connector properties ICSUpdate method ICS Business object nameAgent support Associated maps ICSMaximum transaction level Setting trace/log file values ICS Resources ICSConfiguring messaging Data handlersSetting standard connector properties Setting application-configuration propertiesUpdate method Encryption for connector propertiesSpecifying supported business object definitions Setting trace/log file values Configuring data handlersCompleting the configuration Service call request handling features Appendix C. Connector feature listEvent notification 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