IBM WebSphere Business Integration Adapter LogAtInterchangeEnd, MaxEventCapacity, MessageFileName

Page 53

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. For more information, see the appendix on Connector Configurator.

Attention: If the connector has not been internationalized, the only valid value for this property is en_US. Do not run a non-internationalized C++ connector against InterChange Server version 4.1.1 if you cannot guarantee that only ISO Latin-1 data will be processed. To determine whether a specific connector has been internationalized, see the installing and configuring chapter of its connector guide.

LogAtInterchangeEnd

Specifies whether to log errors to InterChange Server’s log destination, in addition to the location specified in the LogFileName property. Logging to the server’s log destination also turns on email notification, which generates email messages for the MESSAGE_RECIPIENT specified in the InterchangeSystem.cfg file when errors or fatal errors occur. As an example, when a connector loses its connection to its application, if LogAtInterChangeEnd is set to true, an email message is sent to the specified message recipient. The default is false.

MaxEventCapacity

The maximum number of events in the controller buffer. This property is used by flow control and is applicable only if the value of the RepositoryDirectory property is <REMOTE>.

The value can be a positive integer between 1 and 2147483647. The default value is 2147483647.

MessageFileName

The name of the connector message file. The standard location for the message file is \connectors\messages. Specify the message filename in an absolute path if the message file is not located in the standard location.

If a connector message file does not exist, the connector uses InterchangeSystem.txt as the message file. This file is located in the product directory.

Important: To determine whether a specific connector has its own message file, see the installing and configuring chapter of its adapter guide.

OADAutoRestartAgent

Specifies whether the Object Activation Daemon (OAD) automatically attempts to restart the application-specific component after an abnormal shutdown. The properties “OADMaxNumRetry” on page 44 and “OADRetryTimeInterval” on page 44 are related to this property. This property is required for automatic restart.

Appendix A. Standard configuration properties for connectors 43

Page 52 Page 54
Image 53
Page 52 Page 54
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