IBM WebSphere Business Integrati on A daptersAdapter for i2 User Gui deAdapter Version 1.0 .x
|In a syntax line, a pipe separates a set of options from whichyou must choose one and only one.[]In a syntax line, square brackets surround an option
Chapter 1. Overview of the connectorThis chapter describes the connector component of the IBM WebSphere BusinessIntegration Adapter for i2 and the rel
v CIS Back Bus--used by applications to create a bulk import/export interface fordata transfers.v CIS Single Sign-On--a standard set of Java interface
Component DescriptionCIS server Integration container which handles operation invocations. Integrationcontainer and CIS server are used interchangeabl
Status updatesNo status updates are made to the i2 applications. Typically, the event status, forexample, SUCCESS, FAIL, UNSUBSCRIBED, is written to t
metaobject (MO_Instance) and the input and output business objects as itschildren. The verb for the wrapper business object must be a valid operation
6 Adapter for i2 User Guide
Chapter 2. Installing and configuring the connectorThis chapter describes how to install and configure the connector component ofIBM WebSphere Busines
v Run the Installer utility for IBM WebSphere Business Integration Adapters fromthe product CD and select the IBM WebSphere Business Integration Adapt
Tip: Access this tool from the System Manager.v Connector Configurator--if WebSphere MQIntegrator is the integration brokerTip: Access this tool from
Property Description Possible valuesApplicationUserName User name for the i2 connection Not used in this releaseApplicationPassword Password for the i
Chapter 3. Understanding business objects for the connectorThis chapter describes the structure of i2 business objects, how the connectorprocesses the
objects. A hierarchical business object contains both simple attributes and childbusiness objects or arrays of child business objects that contain the
v The operation is set as the verb on the wrapper business object and is associatedwith a port. i2 does not have standard verbs. If multiple operation
I2MO_AddBidInstanceId=CA_InstanceWrapperBOName=IBM_Bidding_BOVerb=DummySpecifying business object attribute propertiesThe i2 connector has various pro
Attribute DescriptionAppSpecInfo For information on this property, see “Identifying business objectapplication-specific information” on page 15,Cardin
16 Adapter for i2 User Guide
Chapter 4. Generating business objects using i2 ODAThis chapter describes i2 ODA, an object discovery agent (ODA), which, workingwith XML schema ODA,
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 th
Working with error and trace message filesError and trace message files (the default is i2ODAAgent.txt) are located in\ODA\messages\, which is under t
IBM WebSphere Business Integrati on A daptersAdapter for i2 User Gui deAdapter Version 1.0 .x
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 f
RownumberProperty name Property type Description1 DefaultBOPrefix String Text that is prepended to the name of the business objectto make it unique.Ex
Metadata (Top tree node) (Expanding Metadata lists all the port types)PortType1(Child tree nodes)Operation1Input typeOutput typeOperation..nInput type
v Port informationv Instance IDv Dummy key (as the business object creation will fail without a key)v Two single cardinality attributes representing t
The following diagram shows the business object that the XML schemaODA generates for i2_order.xsd. The XML data handler uses thecombination of the ele
Create the metaobject for pollingOnce the business objects are created, you need to create the metaobjects forpolling using the CSM. These objects sha
26 Adapter for i2 User Guide
Chapter 5. Troubleshooting and error handlingThis chapter describes how the i2 connector for i2. handles errors. The connectorgenerates logging and tr
Polling-related error messagesThe following table describes polling-related error messages. These are logged inthe i2 Adapter log file.Notes:1. In som
Error description Error type Handling by i2 connectorFail to convert XML messageto IBM business objectError The error that the XML message has asyntax
Note!Before using this information and the product it supports, read the information in Appendix D, “Notices”, on page 77.18April2003This edition of t
Error description Error type Handling by i2 connectorNot able to convert the XMLmessage to the business object.Error The i2 connector logs the message
Tracing Level Tracing MessagesLevel 5v Messages that indicate connector initialization, for example,messages showing the value of each configuration p
32 Adapter for i2 User Guide
Appendix A. Standard configuration properties for connectorsConnectors have two types of configuration properties:v Standard configuration propertiesv
Listener PortCertificate LocationLogFileNameTraceFileNamejms.BrokerNameConfiguring standard connector properties for WebSphere InterChangeServerThis s
To determine the update semantics for a specific property, refer to the UpdateMethod column in the Connector Configurator window, or see the Update Me
Property Name PossiblevaluesDefaultvalueUpdatemethodNotesjms.NumConcurrentRequests positive integer 10 componentrestartJMS transportonlyjms.Password A
Property Name PossiblevaluesDefaultvalueUpdatemethodNotesSynchronousRequestQueue CONNECTORNAME/SYNCHRONOUSREQUESTQUEUEcomponentrestart“SynchronousResp
ApplicationNameName that uniquely identifies the connector’s application. This name is used bythe system administrator to monitor the WebSphere busine
multi-threaded, or be capable of using Connector Agent Parallelism and beconfigured for multiple processes (setting the Parallel Process Degreeconfigu
Integration broker compatibilitySupported on IBM WebSphere Business Integration Adapter Framework versions2.2.0, IBM WebSphere InterChange Server vers
DeliveryQueueThe queue that is used by the connector to send business objects to the integrationbroker.The default value is DELIVERYQUEUE.DeliveryTran
In this environment, you may experience difficulty starting the both the connectorcontroller (on the server side) and the connector (on the client sid
JvmMinHeapSizeThe minimum heap size for the agent (in megabytes). This property is applicableonly if the RepositoryDirectory value is <REMOTE>.T
TT a two-letter country or territory code (usually inupper case)codeset the name of the associated character code set; thisportion of the name is ofte
The default value is false.OADMaxNumRetrySpecifies the maximum number of times that the OAD automatically attempts torestart the application-specific
RepositoryDirectoryThe location of the repository from which the connector reads the XML schemadocuments that store the meta-data of business object d
SynchronousRequestTimeoutSpecifies the time in minutes that the connector waits for a response to asynchronous request. If the response is not receive
Name Possible values Default valueAdminInQueue valid JMS queue name CONNECTORNAME/ADMININQUEUEAdminOutQueue valid WebSphere MQqueue nameCONNECTORNAME/
Name Possible values Default valueSourceQueue valid WebSphere MQqueue nameCONNECTORNAME/SOURCEQUEUESynchronousRequestQueue valid WebSphere MQqueue nam
manually modify the \Data\Std\stdConnProps.xml file in the productdirectory. For more information, see the appendix on ConnectorConfigurator.Attention
iv Adapter for i2 User Guide
The default value is CONNECTORNAME/FAULTQUEUE.jms.FactoryClassNameSpecifies the class name to instantiate for a JMS provider.The default is CxCommon.M
Attention:v WebSphere MQ Integrator supports only one locale at a time. Ensure that everycomponent of the installation (for example, all adapters, app
example, C:\WebSphereAdapters\repository. The value must be a directory path.Do not use <REMOTE> as the RepositoryDirectory value for a connecto
WireFormatThe data format for messages exchanged by the connector. The default value CwXMLis the only valid value, and directs the connector to compos
54 Adapter for i2 User Guide
Appendix B. Connector ConfiguratorBefore you can use a connector, you must create a connector configuration file thatsets the properties for the conne
For example, to add the locale en_GB to the list of values for the Locale property,open the stdConnProps.xml file and add the line in boldface type be
Running Configurator independently of System ManagerWhen you run Connector Configurator without connecting to System Manager,you can save a connector
After you have completed the configuration file and set its properties, it will needto be deployed to the appropriate location for your connector.v If
Specifying general characteristicsThe Properties - Connector-Specific Property Template dialog appears. The dialoghas tabs for General characteristics
ContentsIntegration broker compatibility ...iiiAbout this document ...viiAudience ...
Setting dependenciesAfter you have finished making changes in both the General and the Value tabs,choose Next. The Dependencies dialog appears.A depen
display. When you select a name in the Template Name display, the PropertyTemplate Preview display shows the connector-specific properties that havebe
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
v All files (*.*)Choose this option if a *.txt file was delivered in the adapter package forthe connector, or if a definition file is available under
default values and some do not; you can modify some of the default values. Theinstallation and configuration chapter of each adapter guide describes t
Encryption for connector properties (ICS)Application-specific properties can be encrypted by clicking the Encrypt check boxin the Edit Property window
4. In the File menu of the Connector Configurator window, choose Save to Project.The revised connector definition, including designated support for th
If you are using maps that are uniquely defined for specific source and destinationbusiness objects, the maps will already be associated with their ap
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 o
Important: Connector Configurator accepts property values in either English ornon-English character sets. However, the names of both standard andconne
Service call request handling features ...73General features ...74Appendix D. Notices ...
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 Conne
4. When you add business objects to the configuration, you must load theirmessage set files. If you attempt to load a message set that contains a busi
For connector-specific properties, however, you will need to both define theproperties and set their values. Connector Configurator provides the inter
Appendix C. Connector feature listThis appendix details the features supported by the i2 connector. For descriptionsof these features, see “Appendix A
Category Feature Support NotesLogical delete N/AExist Exist verb NoMisc Attribute names Partial MO_Instance is the standard used torepresent the metao
Category Feature Support NotesConnector properties ApplicationPassword NoApplicationUserName NoUseDefaults No There is no validation of the business o
76 Adapter for i2 User Guide
Appendix D. NoticesIBM may not offer the products, services, or features discussed in this document inall countries. Consult your local IBM representa
Raleigh, NC 27709-2195U.S.ASuch information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.Th
IBMthe IBM logoAIXCrossWorldsDB2DB2 Universal DatabaseMQIntegratorMQSeriesTivoliWebSphereLotus, Domino, Lotus Notes, and Notes Mail are trademarks of
About this documentIBM(R) WebSphere(R) Business Integration Adapters supply integrationconnectivity for leading e-business technologies and enterprise
80 Adapter for i2 User Guide
Printed in U.S.A.
Commenti su questo manuale