Summary of the content on the page No. 1
IBM WebSphere Business Integration Adapters
Adapter for i2 User Guide
Adapter Version 1.0.x
Summary of the content on the page No. 2
Summary of the content on the page No. 3
IBM WebSphere Business Integration Adapters Adapter for i2 User Guide Adapter Version 1.0.x
Summary of the content on the page No. 4
Note! Before using this information and the product it supports, read the information in AppendixD, “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. When you send in
Summary of the content on the page No. 5
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. 2002, 2003 iii
Summary of the content on the page No. 6
iv Adapter for i2 User Guide
Summary of the content on the page No. 7
Contents Integration broker compatibility.........................iii About this document .............................vii Audience....................................vii Related documents.................................vii Typographic conventions...............................vii Chapter1. Overview of the connector.......................1 Connector architecture................................1 How the connector works...............................3 Chapter2. Installing and configuring the conn
Summary of the content on the page No. 8
Service call request handling features...........................73 General features..................................74 AppendixD. Notices..............................77 Programming interface information ...........................78 Trademarks and service marks.............................78 vi Adapter for i2 User Guide
Summary of the content on the page No. 9
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. Audience This document is fo
Summary of the content on the page No. 10
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. Angle brackets surround individual elements of a name to <> distinguish them from each other, as in tmp.log. In this document, backslashe
Summary of the content on the page No. 11
Chapter1. 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. The i2 connector is metadata driven, has object discovery capability
Summary of the content on the page No. 12
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 vario
Summary of the content on the page No. 13
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). At present, the CIS clien
Summary of the content on the page No. 14
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 Chapter5, “Troubleshooting and error handling”, on page 27. Event retrieval For the i2 connector, polling is single threa
Summary of the content on the page No. 15
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. The input child business object is first conv
Summary of the content on the page No. 16
6 Adapter for i2 User Guide
Summary of the content on the page No. 17
Chapter2. 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. It contains the following sections: v “Prerequisites for installing the connector” on page 7 v “Installing the connector on a Windows or UNIX system” on page 7 v “Configuring the connector”on page8 v “Starting the connector”on page10 Prerequisites for instal
Summary of the content on the page No. 18
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
Summary of the content on the page No. 19
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 AppendixB, “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. Changes to some connector
Summary of the content on the page No. 20
Property Description Possible values ApplicationUserName User name for the i2 connection Not used in this release ApplicationPassword Password for the i2 connection Not used in this release CISAgentHostName Used when the CIS agent is running on String host name a remote machine. If it is not set, the Example: any machine name current local host is assumed to have the like California CIS agent running. If it is set, the i2 connector establishes a connection with this remote host. ExecutionTimeout
