IBM WebSphere Business Integration Adapter Tracing messages, Tracing Level, Tracing Messages

Page 40

Error description

Error type

Handling by i2 connector

 

 

 

Not able to convert the XML

Error

The i2 connector logs the message to

message to the business object.

 

the adapter log and sets the status on

 

 

the exception to FAIL. It also dumps

 

 

the XML message to the log file along

 

 

with the error message.

 

 

 

Execute method returns null

Error/Success

In case the operation does not have an

output

 

output type, the execute method

 

 

execution is considered a SUCCESS. If

 

 

an output is expected, the execute

 

 

method issues an exception which is

 

 

caught by the connector.

 

 

 

Tracing messages

Tracing is an optional debugging feature you can turn on to closely follow a connector’s behavior. Tracing messages are configurable and can be changed dynamically. You set various levels depending on the desired detail. Trace messages, by default, are written to STDOUT (screen). You can also configure tracing to write to a file.

Recommendation: Tracing should be turned off on a production system or set to the lowest possible level to improve performance and decrease file size.

The following table describes the types of tracing messages that the i2 connector outputs at each trace level. All the trace messages appear in the file specified by the connector property TraceFileName. These messages are in addition to any tracing messages output by the IBM WebSphere Business Integration Adapter architecture.

Tracing Level

Level 0

Level 1

Level 2

Level 3

Level 4

Tracing Messages

Message that identifies the connector version. No other tracing is done at this level. This message is always displayed.

Example:

’2002/07/10 15:01:46.812: This is version 1.0 of the i2 Adapter’. Messages delivered each time the pollForEvents method is executed.

vMessages logged each time a business object is posted to the integration broker from gotApplEvent.

vMessages that indicate each time a business object request is received.

Not applicable

vApplication-specific information messages, for example, messages showing the values returned by the functions that parse the business object’s application-specific information fields

vMessages that identify when the connector enters or exits a function, which helps trace the process flow of the connector.

30Adapter for i2 User Guide

Page 39 Page 41
Image 40
Page 39 Page 41
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 DescriptionProcessing subscriptions How the connector worksEvent 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 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 Generating business objects using i2 ODA Installing i2 ODASteps for installing 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 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 ConcurrentEventTriggeredFlowsControllerStoreAndForwardMode ContainerManagedEventsControllerTraceLevel DeliveryTransport DeliveryQueueWebSphere MQ and IDL FaultQueue DuplicateEventEliminationJvmMaxHeapSize JvmMaxNativeStackSizeJms.Password JvmMinHeapSizeJms.FactoryClassName Jms.MessageBrokerNameLogAtInterchangeEnd MaxEventCapacityMessageFileName OADAutoRestartAgentOADMaxNumRetry OADRetryTimeIntervalPollEndTime PollFrequencyRepositoryDirectory ResponseQueueRestartRetryCount RestartRetryIntervalWireFormat SynchronousRequestTimeoutTraceFileName 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 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 ICSEncryption for connector properties ICS Update method ICSSpecifying supported business object definitions 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 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