IBM WebSphere Business Integration Adapters Adapter for i2 User Guide Adapter Version 1.0.
IBM WebSphere Business Integration Adapters Adapter for i2 User Guide Adapter Version 1.0.
Note! Before using this information and the product it supports, read the information in Appendix D, “Notices”, on page 77. 18April2003 This edition of this document applies to IBM WebSphere InterChange Server, version 4.2, WebSphere Business Integration Adapters, version 2.2.0, and to all subsequent releases and modification until otherwise indicated in new editions. To send us your comments about this document, email doc-comments@us.ibm.com. We look forward to hearing from you.
Integration broker compatibility Supported on IBM WebSphere Business Integration Adapter Framework versions 2.2.0, IBM WebSphere InterChange Server versions 4.1.1 and 4.2, WebSphere MQ Integrator version 2.1.0, and WebSphere MQ Integrator Broker, version 2.1.0. See Release Notes for any exceptions. © Copyright IBM Corp.
iv Adapter for i2 User Guide
Contents Integration broker compatibility . . . . . . . . . . . . . . . . . . . . . . . . . iii About this document Audience . . . . . . Related documents . . . Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii . vii . vii Chapter 1. Overview of the connector . .
Service call request handling features . General features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 . 74 Appendix D. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Programming interface information . Trademarks and service marks . . . vi Adapter for i2 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this document IBM(R) WebSphere(R) Business Integration Adapters supply integration connectivity for leading e-business technologies and enterprise applications.This document describes the installation, configuration, and business object development for the adapter for i2.. This document describes the installation, configuration, troubleshooting, and business object development for the connector component of the IBM WebSphere Business Integration Adapter for i2.
| [ ] ... < > /, \ %text% and $text viii Adapter for i2 User Guide In a syntax line, a pipe separates a set of options from which you must choose one and only one. In a syntax line, square brackets surround an optional parameter. In a syntax line, ellipses indicate a repetition of the previous parameter. For example, option[,...] means that you can enter multiple, comma-separated options.
Chapter 1. Overview of the connector This chapter describes the connector component of the IBM WebSphere Business Integration Adapter for i2 and the relevant business integration system architecture. The i2 connector integrates with i2 application modules through i2’s Common Integration Services (CIS) API. CIS API from i2 is an implementation of JCA Common Client Interface. i2 has a suite of application modules that support CIS.
v CIS Back Bus--used by applications to create a bulk import/export interface for data transfers. v CIS Single Sign-On--a standard set of Java interfaces used by Web applications to authenticate users against a central authentication. store. The i2 connector interacts with the CIS Front Bus using the CIS Client API provided by i2 along with its CIS adapters. CIS Client API is the implementation of JCA Common Client Interface. CIS adapters operate based on CIS metadata information using the various bindings.
Component Description CIS server Integration container which handles operation invocations. Integration container and CIS server are used interchangeably in this document. How the connector works The i2 connector is a CIS (Common Integration Services) client. It connects to the CIS client API in a non-managed environment, that is, it connects to the CIS adapter directly without an application server. No authentication is necessary (no user name or password is required).
Status updates No status updates are made to the i2 applications. Typically, the event status, for example, SUCCESS, FAIL, UNSUBSCRIBED, is written to the application’s event store. Since no event store is maintained for i2, the status update strategy is not relevant for the i2 connector. Error messages, if any, are logged to the i2 adapter log file. For more information, see Chapter 5, “Troubleshooting and error handling”, on page 27. Event retrieval For the i2 connector, polling is single threaded.
metaobject (MO_Instance) and the input and output business objects as its children. The verb for the wrapper business object must be a valid operation for the specified instance. The information about the child business object, whether it is an input or output type, is obtained from the Application Specific Information (ASI) of the wrapper business object’s attributes. Example: ASI Type=input indicates that the child business object is of input type.
6 Adapter for i2 User Guide
Chapter 2. Installing and configuring the connector This chapter describes how to install and configure the connector component of IBM WebSphere Business Integration Adapter for i2 and how to configure applications to work with the connector.
v Run the Installer utility for IBM WebSphere Business Integration Adapters from the product CD and select the IBM WebSphere Business Integration Adapter for i2. The utility allows you to browse and select the directory into which it will install the connector subdirectories and files. You must install to the %ProductDir% product directory that you used for your installation of the IBM WebSphere InterChange Server system. Use the browse button in the Installer to locate the directory and select it.
Tip: Access this tool from the System Manager. v Connector Configurator--if WebSphere MQIntegrator is the integration broker Tip: Access this tool from the IBM WebSphere Business Integration Adapter program folder. For more information about Connector Configurator, see Appendix B, “Connector Configurator”, on page 55. A connector obtains its configuration values at startup. During a run-time session, you may want to change the values of one or more connector properties.
Property Description Possible values ApplicationUserName ApplicationPassword CISAgentHostName User name for the i2 connection Password for the i2 connection Used when the CIS agent is running on a remote machine. If it is not set, the current local host is assumed to have the CIS agent running. If it is set, the i2 connector establishes a connection with this remote host. Time in milliseconds before the call to i2 application terminates.
Chapter 3. Understanding business objects for the connector This chapter describes the structure of i2 business objects, how the connector processes the business objects, and the assumptions the connector makes about them. Use this information as a guide to modifying existing business objects for i2 or as suggestions for implementing new business objects.
objects. A hierarchical business object contains both simple attributes and child business objects or arrays of child business objects that contain the values. A cardinality 1 container object, or single-cardinality relationship, occurs when an attribute in a parent business object contains a single child business object. In this case, the child business object represents a collection that can contain only one record. The type of the attribute is the same as that of the child business object.
v The operation is set as the verb on the wrapper business object and is associated with a port. i2 does not have standard verbs. If multiple operations have the same set of input and output types, but are supported on different ports, there will be two different wrapper business objects for the different ports. v The types are business object attributes which represent data types for an operation.
I2MO_AddBid InstanceId=CA_Instance WrapperBOName=IBM_Bidding_BO Verb=Dummy Specifying business object attribute properties The i2 connector has various properties that you can set on its business object attributes. This section describes how the connector interprets several of these properties and describes how to set them when modifying a business object. The following table shows the properties for simple attributes.
Attribute Description AppSpecInfo For information on this property, see “Identifying business object application-specific information” on page 15, Cardinality For relationship details between XML elements and cardinality, see Chapter 3, ″XML data handler,″ in IBM WebSphere Business Integration Adapters Data Handler Guide. Special attribute values Simple attributes in business objects can have the special value, CxIgnore.
16 Adapter for i2 User Guide
Chapter 4. Generating business objects using i2 ODA This chapter describes i2 ODA, an object discovery agent (ODA), which, working with XML schema ODA, generates business objects for the IBM WebSphere Business Integration Adapter for i2.
v ODA\i2\start_i2ODA.bat (Windows only) v ODA/i2/start_i2ODA.sh (UNIX only) Notes: 1. Except as otherwise noted, this document uses backslashes (\) as the convention for directory paths. For UNIX installations, substitute slashes (/) for backslashes. 2. All product path names are relative to the directory where the product is installed on your system. Other installation requirements v i2 provides the MetadataService adapter to obtain the metadata information from the registry.
Working with error and trace message files Error and trace message files (the default is i2ODAAgent.txt) are located in \ODA\messages\, which is under the product directory. These files use the following naming convention: AgentNameAgent.txt Example: If the AGENTNAME variable specifies i2ODA1, the tool assumes that the name of the associated message file is i2ODA1Agent.txt You can have a message file for each ODA instance or have differently named ODAs use the same message file.
5. Complete the business object and generate the business objects for the types. 6. Save the business object files. Details for each step follow. Steps for using i2ODA Before you begin: You need to start the i2 Business Object Designer wizard. 1. Open Business Object Designer. 2. From the File menu, select New Using ODA.... Result: Business Object Designer displays the first window in the wizard, named Select Agent. Perform the following steps: Select the Agent To select the ODA: 1.
Row number Property name Property type Description 1 DefaultBOPrefix String 2 SchemaFileLocation String 3 MessageFile String 4 CISAgentHostName String Text that is prepended to the name of the business object to make it unique. Example: i2_BO Path where the generated.xsd files are stored. This is mandatory; you must specify the path to store the schema files. Path to the error and message file. If the file is not specified, the error messages from the ODA are not displayed.
Metadata (Top tree node) (Expanding Metadata lists all the port types) PortType1(Child tree nodes) Operation1 Input type Output type Operation..n Input type Output type PortType2 Operation Input type v Select the port, operation, and type for generating the business object. Each operation has an input and output type on a port, and each of these types needs to have a corresponding business object. Result: i2 ODA will create the schema file for the chosen type.
v v v v Port information Instance ID Dummy key (as the business object creation will fail without a key) Two single cardinality attributes representing the input and output types for the operation. The attributes are named as BOPrefix_in_operation_type and BOPrefix_out_operation_type. Example: The wrapper BO for the operation persistOrder is i2BO_persistOrder.
The following diagram shows the business object that the XML schema ODA generates for i2_order.xsd. The XML data handler uses the combination of the element next to CISDocument and BOPrefix to get the business object name. I2BO_order XMLDeclaration I2BO_TLO_CISDocument_Order (1 card) CISDocument I2BO_CISDocument_Order OrderId SystemId Save the business object files Now that all the required business objects are generated, you need to save them to the InterChange server for use by the collaborations.
Create the metaobject for polling Once the business objects are created, you need to create the metaobjects for polling using the CSM. These objects shall have the i2MO prefix followed by the operation. The attributes need to have a default value. This information is used during polling to register the specific operation and check the output from i2 applications for the registered operation. The following diagram shows the structure of the i2 metaobject for i2 MO_Operation.
26 Adapter for i2 User Guide
Chapter 5. Troubleshooting and error handling This chapter describes how the i2 connector for i2. handles errors. The connector generates logging and tracing messages. The chapter contains the following sections: v “Logging error messages” on page 27 v “Tracing messages” on page 30 v “Tips for troubleshooting” on page 31 Logging error messages The connector logs an error message whenever it encounters an abnormal condition during processing, regardless of the trace level.
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 Fail to convert XML message to IBM business object Error The error that the XML message has a syntax error is logged for the message, The XML message gets dumped to the log file, and the processing continues for other messages. Any error when posting event to the broker Error The error is logged with the status of ERROR_POSTING_EVENT for the business object, and the polling continues for the other messages.
Error description Error type Handling by i2 connector Not able to convert the XML Error message to the business object. The i2 connector logs the message to 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 output In case the operation does not have an output type, the execute method execution is considered a SUCCESS.
Tracing Level Tracing Messages Level 5 v Messages that indicate connector initialization, for example, messages showing the value of each configuration property retrieved from the integration broker. v Messages that comprise a business object dump.
32 Adapter for i2 User Guide
Appendix A. Standard configuration properties for connectors Connectors have two types of configuration properties: v Standard configuration properties v Connector-specific configuration properties This chapter describes standard configuration properties, applicable to all connectors. For information about properties specific to the connector, see the installing and configuring chapter of its adapter guide.
Listener Port Certificate Location LogFileName TraceFileName jms.BrokerName Configuring standard connector properties for WebSphere InterChange Server This section describes standard configuration properties applicable to connectors whose integration broker is WebSphere InterChange Server (ICS). Standard configuration properties provide information that is used by a configurable component of InterChange Server called the connector controller.
To determine the update semantics for a specific property, refer to the Update Method column in the Connector Configurator window, or see the Update Method column of the table below. The following table provides a quick reference to the standard connector configuration properties. You must set the values of some of these properties before running the connector. See the sections that follow for explanations of the properties.
Property Name Possible values Default value Update method Notes jms.NumConcurrentRequests positive integer 10 jms.Password Any valid password component restart server restart jms.UserName Any valid name server restart JMS transport only JMS transport only JMS transport only Locale en_US component restart LogAtInterchangeEnd en_US , ja_JP, ko_KR, zh_C, zh_T, fr_F, de_D, it_I, es_E, pt_BR Note: These are only a subset of supported locales.
Property Name Possible values SynchronousRequestQueue “SynchronousResponseQueue” on page 52 SynchronousRequestTimeout “WireFormat” on page 53 CwXML, CwBO Default value Update method CONNECTORNAME/ SYNCHRONOUSREQUESTQUEUE CONNECTORNAME/ SYNCHRONOUSRESPONSEQUEUE 0 component restart component restart component restart agent restart cwxml Notes CwXML for non-ICS broker; CwBO if Repository Directory is AdminInQueue The queue that is used by the integration broker to send administrative messag
ApplicationName Name that uniquely identifies the connector’s application. This name is used by the system administrator to monitor the WebSphere business integration system environment. This property must have a value before you can run the connector. BrokerType Identifies the integration broker type that you are using. If you are using an ICS connector, this setting must be ICS.
multi-threaded, or be capable of using Connector Agent Parallelism and be configured for multiple processes (setting the Parallel Process Degree configuration property greater than 1). Important: To determine whether a specific connector is single- or multi-threaded, see the installing and configuring chapter of its adapter guide. The ConcurrentEventTriggeredFlows property has no effect on connector polling, which is single-threaded and performed serially.
DeliveryQueue The queue that is used by the connector to send business objects to the integration broker. The default value is DELIVERYQUEUE. DeliveryTransport Specifies the transport mechanism for the delivery of events. Possible values are MQ for WebSphere MQ, IDL for CORBA IIOP, or JMS for Java Messaging Service. If ICS is the broker type, the value of the DeliveryTransport property can be MQ, IDL, or JMS, and the default is IDL.
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: v The LDR_CNTRL environment variable in the CWSharedEnv.sh script. This script resides in the \bin directory below the product directory.
JvmMinHeapSize The minimum heap size for the agent (in megabytes). This property is applicable only if the RepositoryDirectory value is . The default value is 1m. jms.FactoryClassName Specifies the class name to instantiate for a JMS provider. You must set this connector property when you choose JMS as your delivery transport mechanism (DeliveryTransport). The default is CxCommon.Messaging.jms.IBMMQSeriesFactory. jms.MessageBrokerName Specifies the broker name to use for the JMS provider.
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.
The default value is false. OADMaxNumRetry Specifies the maximum number of times that the OAD automatically attempts to restart the application-specific component after an abnormal shutdown. The default value is 1000. OADRetryTimeInterval Specifies the number of minutes of the retry time interval that the OAD automatically attempts to restart the application-specific component after an abnormal shutdown.
RepositoryDirectory The location of the repository from which the connector reads the XML schema documents that store the meta-data of business object definitions. When the integration broker is ICS, this value must be set to because the connector uses the InterChange Server repository to obtain its connector-definition information ResponseQueue Designates the JMS response queue, which delivers a response message from the connector framework to the integration broker.
SynchronousRequestTimeout Specifies the time in minutes that the connector waits for a response to a synchronous request. If the response is not received within the specified time then the connector moves the original synchronous request message into the fault queue along with an error message. The default value is 0. TraceFileName The name of the file where the application-specific component writes trace messages. Specify the filename in an absolute path. The default is STDOUT.
Name Possible values Default value AdminInQueue AdminOutQueue valid JMS queue name valid WebSphere MQ queue name 0-5 application name WMQI ASCII, SJIS, Cp949, GBK, Big5, Cp297, Cp273, Cp280, Cp284, Cp037, Cp437 Note: These are only a subset of supported values.
Name Possible values Default value SourceQueue valid WebSphere MQ queue name valid WebSphere MQ queue name valid WebSphere MQ queue name an appropriate integer indicating the number of minutes the connector waits for a response to a synchronous request CwXML CONNECTORNAME/SOURCEQUEUE SynchronousRequestQueue SynchronousResponseQueue SynchronousTimeout WireFormat 0 CwXML AdminInQueue The queue that is used by the integration broker to send administrative messages to the connector.
manually modify the \Data\Std\stdConnProps.xml file in the product directory. For more information, see the appendix on Connector Configurator. Attention: Do not run a non-internationalized connector against InterChange Server version 4.1.1 if you cannot guarantee that only ISO Latin-1 data will be processed. The default value is ascii.
The default value is CONNECTORNAME/FAULTQUEUE. jms.FactoryClassName Specifies the class name to instantiate for a JMS provider. The default is CxCommon.Messaging.jms.IBMMQSeriesFactory. jms.MessageBrokerName Specifies the broker name to use for the JMS provider. The default is crossworlds.queue.manager. jms.NumConcurrentRequests Specifies the maximum number of concurrent service call requests that can be sent to a connector at the same time.
Attention: v WebSphere MQ Integrator supports only one locale at a time. Ensure that every component of the installation (for example, all adapters, applications, and the integration broker itself) is set to the same locale. v 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.
example, C:\WebSphereAdapters\repository. The value must be a directory path. Do not use as the RepositoryDirectory value for a connector that is not using ICS as the broker. RequestQueue The queue that is used by the integration broker to send business objects to the connector. The default value is CONNECTORNAME/REQUESTQUEUE. ResponseQueue Designates the JMS response queue, which delivers a response message from the connector framework to the integration broker.
WireFormat The data format for messages exchanged by the connector. The default value CwXML is the only valid value, and directs the connector to compose the messages in XML. Appendix A.
54 Adapter for i2 User Guide
Appendix B. Connector Configurator Before you can use a connector, you must create a connector configuration file that sets the properties for the connector, designates the business objects and any meta-objects that it supports, and sets logging and tracing values that the connector will use at runtime. The configuration file may also contain properties for the use of messaging and data handlers required by your connector.
For example, to add the locale en_GB to the list of values for the Locale property, open the stdConnProps.
Running Configurator independently of System Manager When you run Connector Configurator without connecting to System Manager, you can save a connector configuration file (an XML document with the extension *.cfg) to a directory that you specify, but you cannot save or open a System Manager project. When you are creating a connector for use with a broker other than ICS, you do not need to connect to System Manager at any point in order to use the file.
After you have completed the configuration file and set its properties, it will need to be deployed to the appropriate location for your connector. v If you are using ICS as your broker, save the configuration in a System Manager project, and use System Manager to load the file into InterChange Server.
Specifying general characteristics The Properties - Connector-Specific Property Template dialog appears. The dialog has tabs for General characteristics of the defined properties and for Value restrictions. The General display has the following fields: v Edit properties Use the buttons provided (or right-click within the Edit properties display) to add a new property to the template, to edit or delete an existing property, or to add a child property to an existing property.
Setting dependencies After you have finished making changes in both the General and the Value tabs, choose Next. The Dependencies dialog appears. A dependent property is a property that is included in the template and used in the configuration file only if the value of another property meets a specific condition. To designate a property as being dependent and set the condition upon which it depends, do this: 1. In the Available Properties display, select the property that will be made dependent. 2.
display. When you select a name in the Template Name display, the Property Template Preview display shows the connector-specific properties that have been defined in that template. After you have chosen the template you want to use, choose OK. 3. A configuration screen will display for the connector that you are configuring. The title bar of the configuration screen shows the broker that you are using and the name that you have given to the connector.
appropriate type for your broker--either ICS or WebSphere MQ Integrator Broker (for WMQI). If it does not, change the broker value before you configure the connector. To do so: 1. Under the Standard Properties tab, select the value field for the BrokerType property. In the drop-down menu, select the value WMQI or ICS. 2. The Standard Properties tab refreshes to display properties associated with the selected broker. When you save the file, you retain this broker selection.
v All files (*.*) Choose this option if a *.txt file was delivered in the adapter package for the connector, or if a definition file is available under another extension. 3. In the directory display, navigate to the appropriate connector definition file, select it, and choose Open. Using an existing System Manager project Follow these steps to open a connector configuration from a System Manager project: 1. Start System Manager.
default values and some do not; you can modify some of the default values. The installation and configuration chapter of each adapter guide describes the application-specific properties and the recommended values. The fields for Standard Properties and Connector-Specific Properties are color-coded to show which are configurable: v A field with a grey background indicates a standard property. You can change the value but cannot change the name or remove the property.
Encryption for connector properties (ICS) Application-specific properties can be encrypted by clicking the Encrypt check box in the Edit Property window. To decrypt a value, click to clear the Encrypt check box, enter the correct value in the Verification dialog box, and choose OK. If the entered value is correct, the value is decrypted and displays. The adapter guide for each connector contains a list and description of each property and its default value.
4. In the File menu of the Connector Configurator window, choose Save to Project. The revised connector definition, including designated support for the added business object definition, is saved to the project in System Manager. To delete a business object from the supported list: 1. To select a business object field, click the number to the left of the business object 2. From the Edit menu of the Connector Configurator window, choose Delete Row. The business object is removed from the list display. 3.
If you are using maps that are uniquely defined for specific source and destination business objects, the maps will already be associated with their appropriate business objects when you open the display, and you will not need (or be able) to change them. If more than one map is available for use by a supported business object, you will need to explicitly bind the business object with the map that it should use.
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: v To console (STDOUT): Writes logging or tracing messages to the STDOUT display. v To 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.
Important: Connector Configurator accepts property values in either English or non-English character sets. However, the names of both standard and connector-specific properties, and the names of supported business objects, must use the English character set only. Standard properties differ from connector-specific properties as follows: v Standard properties of a connector are shared by both the application-specific component of a connector and its broker component.
2. Enter a name or value. 3. To encrypt a property, click the Encrypt box. 4. Choose to save or discard changes, as described for Setting Standard Connector Properties. The Update Method displayed for each property indicates whether a component or agent restart is necessary to activatechanged values. Important: Changing a preset application-specific connector property name may cause a connector to fail. Certain property names may be needed by the connector to connect to an application or to run properly.
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 connector-specific properties, however, you will need to both define the properties and set their values. Connector Configurator provides the interface for performing both of these tasks. Completing the configuration After you have created a configuration file for a connector and modified it, make sure that the connector can locate the configuration file when the connector starts up.
Appendix C. Connector feature list This appendix details the features supported by the i2 connector. For descriptions of these features, see “Appendix A: Connector feature checklist” in IBM WebSphere Business Integration Adapters Connector Development Guide. Event notification features The following table details the event notification features supported by the connector.
Category Feature Support Logical delete N/A Exist Exist verb No Misc Attribute names Partial Business object names Full Retrieve Ignore missing child object N/A RetrieveByContent Ignore missing child object N/A Update Verbs Notes MO_Instance is the standard used to represent the metaobject containing the instance ID in any wrapper business object. Multiple results N/A There is only one output type per operation.
Category Feature Support Connector properties ApplicationPassword No ApplicationUserName No UseDefaults No General messaging Full generateMsg() No Trace level 0 Full Trace level 1 Full Trace level 2 Full Trace level 3 N/A Trace level 4 Full Trace level 5 Full CDK method LogMsg Full Java Package Names Full Logging messages Full NT service compliance Full Transaction support N/A There is no transaction support in i2.
76 Adapter for i2 User Guide
Appendix D. Notices IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
Raleigh, NC 27709-2195 U.S.A Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment.
IBM the IBM logo AIX CrossWorlds DB2 DB2 Universal Database MQIntegrator MQSeries Tivoli WebSphere Lotus, Domino, Lotus Notes, and Notes Mail are trademarks of the Lotus Development Corporation in the United States, other countries, or both.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
80 Adapter for i2 User Guide
Printed in U.S.A.
