IBM WebSphere Business Integration Adapter manual Setting trace/log file values

Page 81

4.When you add business objects to the configuration, you must load their message set files. If you attempt to load a message set that contains a business object name that already exists in the configuration, or if you attempt to load a message set file that contains a duplicate business object name, Connector Configurator detects the duplicate and displays the Load Results dialog. The dialog shows the business object name or names for which there are duplicates. For each duplicate name shown, click in the Message Set ID field, and choose the Message Set ID that you wish to use.

Setting trace/log file values

When you open a connector configuration file or a connector definition file, Connector Configurator uses the logging and tracing values of that file as default values. You can change those values in Connector Configurator.

To change the logging and tracing values:

1.Choose the Trace/Log Files tab.

2.For either logging or tracing, you can choose to write messages to one or both of the following:

vTo console (STDOUT): Writes logging or tracing messages to the STDOUT display.

vTo File: Writes logging or tracing messages to a file that you specify. To specify the file, choose the directory button (ellipsis), navigate to the preferred location, provide a file name, and choose Save. Logging or tracing message are written to the file and location that you specify.

Note: Both logging and tracing files are simple text files. You can use the file extension that you prefer when you set their file names. For tracing files, however, it is advisable to use the extension .trace rather than

.trc, to avoid confusion with other files that might reside on the system. For logging files, .log and .txt are typical file extensions.

Configuring data handlers

The data handlers section is available for configuration only if you have designated a value of JMS for DeliveryTransport and a value of JMS for ContainerManagedEvents. See the descriptions under ContainerManagedEvents in Appendix A, Standard Properties, for values to use for these properties. For additional details, see the Connector Development Guide for C++ or the Connector Development Guide for Java

Using standard and connector-specific properties with Connector Configurator

Connector configuration properties include both standard configuration properties (the properties that all connectors have) and connector-specific properties (properties that are needed by the connector for a specific application or technology).

Because standard properties are used by all connectors, you do not need to define those properties within your configuration file; Connector Configurator already has those definitions, and it incorporates them into your configuration file as soon as you create the file. For standard properties, your only task is to use Connector Configurator to set the values of the properties.

Appendix B. Connector Configurator 71

Page 80 Page 82
Image 81
Page 80 Page 82
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 APIHow the connector works Processing subscriptionsEvent detection and notification 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 DescriptionUnderstanding 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 Installing i2 ODA Generating business objects using i2 ODASteps for installing i2 ODA Overview of 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 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 ConcurrentEventTriggeredFlowsContainerManagedEvents ControllerStoreAndForwardModeControllerTraceLevel DeliveryQueue DeliveryTransportWebSphere MQ and IDL DuplicateEventElimination FaultQueueJvmMaxHeapSize JvmMaxNativeStackSizeJvmMinHeapSize Jms.PasswordJms.FactoryClassName Jms.MessageBrokerNameMaxEventCapacity LogAtInterchangeEndMessageFileName OADAutoRestartAgentOADRetryTimeInterval OADMaxNumRetryPollEndTime PollFrequencyResponseQueue RepositoryDirectoryRestartRetryCount RestartRetryIntervalSynchronousRequestTimeout WireFormatTraceFileName 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 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 ICSUpdate method ICS Encryption for connector properties ICSSpecifying supported business object definitions ICS Business object nameAssociated 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 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