IBM WebSphere Business Integration Adapter manual Polling-related error messages

Page 38

Polling-related error messages

The following table describes polling-related error messages. These are logged in the i2 Adapter log file.

Notes:

1.In some cases, the connector logs a fatal error (log message type of

XRD_FATAL) so that e-mail notification can be triggered. For logging this error with the integration broker, you need to set the connector property LogAtInterchangeEnd to true.

2.E-mail notification will be sent only if the e-mail connector is configured.

Error description

Error type

Handling by i2 connector

 

 

 

Connection lost while polling

Fatal error

The connector detects the connection

 

 

error at the time of a poll call. It logs a

 

 

fatal error (log message type of

 

 

XRD_FATAL) and dumps the XML

 

 

message. Fatal error can trigger e-mail

 

 

notification. For logging this error

 

 

with the integration broker, you need

 

 

to set the connector property

 

 

LogAtInterchange to true and

 

 

continue with polling on other

 

 

operations that might be running on

 

 

instances that are active.

 

 

 

Not able to register an

Fatal error

With subsequent poll calls, the i2

operation with the CIS Agent

 

connector tries to re-register the

 

 

operations that could not be registered

 

 

with the previous poll call. In case

 

 

registering all the operations fail, we

 

 

assume that the CIS agent is down;

 

 

the connector returns

 

 

APPRESPONSETIMEOUT which shuts

 

 

down the i2 connector.

 

 

 

No metaobjects configured for

Error

The i2 connector always returns a

polling

 

FAIL after logging that the metaobjects

 

 

are not configured for polling.

 

 

 

Default value for the metadata

Error

For details on the default value

object attributes not set

 

attribute property, see Chapter 3,

 

 

“Understanding business objects for

 

 

the connector”, on page 11. The error

 

 

″required information for polling was

 

 

not found for the specified metaobject″

 

 

is logged and the processing continues

 

 

for other messages.

 

 

 

Not able to fetch the message

Error/SUCCESS

In case the poll call to the i2

from CIS Agent

 

application returns a null, or there are

 

 

no events for the operation, the

 

 

connector continues to poll for other

 

 

operations. In case an exception is

 

 

caught from any CIS Client API , an

 

 

error message containing the word

 

 

ERROR_PROCESSING_EVENT is

 

 

logged. The connector continues to

 

 

poll for other operations.

 

 

 

28Adapter for i2 User Guide

Page 37 Page 39
Image 38
Page 37 Page 39
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 DescriptionEvent detection and notification How the connector worksProcessing subscriptions 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 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 Steps for installing i2 ODA Generating business objects using i2 ODAInstalling 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 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 ConcurrentEventTriggeredFlowsControllerTraceLevel ContainerManagedEventsControllerStoreAndForwardMode WebSphere MQ and IDL DeliveryQueueDeliveryTransport JvmMaxHeapSize FaultQueueDuplicateEventElimination JvmMaxNativeStackSizeJms.FactoryClassName Jms.PasswordJvmMinHeapSize Jms.MessageBrokerNameMessageFileName LogAtInterchangeEndMaxEventCapacity OADAutoRestartAgentPollEndTime OADMaxNumRetryOADRetryTimeInterval PollFrequencyRestartRetryCount RepositoryDirectoryResponseQueue RestartRetryIntervalTraceFileName SynchronousRequestTimeoutWireFormat 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 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 ICSSpecifying supported business object definitions ICS Encryption for connector properties ICSUpdate method 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 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