IBM WebSphere Business Integration Adapter DuplicateEventElimination, FaultQueue, JvmMaxHeapSize

Page 51

In this environment, you may experience difficulty starting the both the connector controller (on the server side) and the connector (on the client side) due to memory use within the WebSphere MQ client. If your installation uses less than 768M of process heap size, IBM recommends that you set:

vThe LDR_CNTRL environment variable in the CWSharedEnv.sh script.

This script resides in the \bin directory below the product directory. With a text editor, add the following line as the first line in the CWSharedEnv.sh script:

export LDR_CNTRL=MAXDATA=0x30000000

This line restricts heap memory usage to a maximum of 768 MB (3 segments * 256 MB). If the process memory grows more than this limit, page swapping can occur, which can adversely affect the performance of your system.

vThe IPCCBaseAddress property to a value of 11 or 12. For more information on this property, see the System Installation Guide for UNIX.

Notes:

vIf your installation uses more than 768M of process heap size, this resolution would adversely affect product performance.

vIf you run on AIX 4.3.3, you do not need to set the LDR_CNTRL environment variable. However, you must set IPCCBaseAddress to a value of 11 or 12.

DuplicateEventElimination

Setting this property to true enables a JMS-enabled connector with a non-JMS event store to ensure that duplicate events are not delivered to the delivery queue. To make use of this feature, during connector development a unique event identifier must be set as the business object’s ObjectEventId attribute in the application specific code.

This property can also be set to false.

Note: When DuplicateEventElimination is set to true, you must also configure the MonitorQueue property to enable guaranteed event delivery.

FaultQueue

If the connector experiences an error while processing a message then the connector moves the message to the queue specified in this property, along with a status indicator and a description of the problem.

The default value is CONNECTORNAME/FAULTQUEUE.

JvmMaxHeapSize

The maximum heap size for the agent (in megabytes). This property is applicable only if the RepositoryDirectory value is <REMOTE>.

The default value is 128m.

JvmMaxNativeStackSize

The maximum native stack size for the agent (in kilobytes). This property is applicable only if the RepositoryDirectory value is <REMOTE>.

The default value is 128k.

Appendix A. Standard configuration properties for connectors 41

Page 50 Page 52
Image 51
Page 50 Page 52
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 Typographic conventions About this documentAudience Related documentsViii Adapter for i2 User Guide Connector architecture Overview of the connectorComponent Description XML DH Wbia APIHow the connector works Processing subscriptionsEvent detection and notification Event retrieval Processing service call requestsStatus updates Processing verbs operationsStatus updates Adapter for i2 User Guide Step for installing the standard files Installing and configuring the connectorPrerequisites for installing the connector Installing the connector on a Windows or Unix systemConfiguring the connector Installed file structureMessageFileName Standard connector propertiesConnector-specific properties LogAtInterchangeEndProperty Description Starting the connectorConfiguring starti2.bat for Windows or starti2.sh for Unix Configuring DataHandlerUnderstanding business objects for the connector Defining connector metadataOverview of business object structure Wrapper BO I2 business object structureType=output Configuring metaobjects for pollingAttribute Description Specifying business object attribute propertiesSpecial attribute values Application-specific information at the attribute levelParameter Description Adapter for i2 User Guide Overview of i2 ODA Generating business objects using i2 ODAInstalling i2 ODA Steps for installing i2 ODALaunching i2 ODA Other installation requirementsWorking with error and trace message files Using i2 ODA in Business Object DesignerTrace Level Description Steps for using i2ODA Configure agent propertiesSelect the Agent 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 Troubleshooting and error handling Logging error messagesStructure of error messages Error description Error type Handling by i2 connector Polling-related error messagesService call request processing error messages Example Tracing messagesTracing Level Tracing MessagesTips 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 AgentTraceLevel AdminInQueueAdminOutQueue AgentConnectionsConcurrentEventTriggeredFlows ApplicationNameBrokerType CharacterEncodingContainerManagedEvents ControllerStoreAndForwardModeControllerTraceLevel DeliveryQueue DeliveryTransportWebSphere MQ and IDL JvmMaxNativeStackSize FaultQueueDuplicateEventElimination JvmMaxHeapSizeJms.MessageBrokerName Jms.PasswordJvmMinHeapSize Jms.FactoryClassNameOADAutoRestartAgent LogAtInterchangeEndMaxEventCapacity MessageFileNamePollFrequency OADMaxNumRetryOADRetryTimeInterval PollEndTimeRestartRetryInterval RepositoryDirectoryResponseQueue RestartRetryCountSynchronousRequestTimeout WireFormatTraceFileName Application name Name Possible values Default valueApplicationName AdminInQueueAdminOutQueue AgentTraceLevelDeliveryTransport FaultQueueContainerManagedEvents DeliveryQueueJms.NumConcurrentRequests Jms.PasswordJms.FactoryClassName Jms.MessageBrokerNameRepositoryDirectory PollEndTimePollFrequency PollStartTimeRestartRetryCount SynchronousTimeoutRequestQueue ResponseQueueWireFormat Adapter for i2 User Guide Appendix B. Connector Configurator Starting Connector Configurator Running Configurator from System ManagerValueenGB/Value 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 ICSBusiness object name Encryption for connector properties ICSUpdate method ICS Specifying supported business object definitions ICSAssociated maps ICS Agent supportMaximum transaction level Resources ICS Setting trace/log file values ICSData handlers Configuring messagingSetting application-configuration properties Setting standard connector propertiesEncryption for connector properties Update methodSpecifying supported business object definitions Configuring data handlers Setting trace/log file valuesCompleting the configuration Category Feature Support Appendix C. Connector feature listEvent notification features Service call request handling featuresGeneral 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