Ibm WebSphere Business Integration Adapter Manuel d'utilisateur

Naviguer en ligne ou télécharger Manuel d'utilisateur pour Matériel Ibm WebSphere Business Integration Adapter. IBM WebSphere Business Integration Adapter User Manual Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 92
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 0
IBM WebSphere Business Integrati on A dapters
Adapter for i2 User Gui de
Adapter Version 1.0 .x

Vue de la page 0
1 2 3 4 5 6 ... 91 92

Résumé du contenu

Page 1 - Adapter for i2 User Gui de

IBM WebSphere Business Integrati on A daptersAdapter for i2 User Gui deAdapter Version 1.0 .x

Page 2

|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

Page 3

Chapter 1. Overview of the connectorThis chapter describes the connector component of the IBM WebSphere BusinessIntegration Adapter for i2 and the rel

Page 4

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

Page 5

Component DescriptionCIS server Integration container which handles operation invocations. Integrationcontainer and CIS server are used interchangeabl

Page 6

Status updatesNo status updates are made to the i2 applications. Typically, the event status, forexample, SUCCESS, FAIL, UNSUBSCRIBED, is written to t

Page 7 - Contents

metaobject (MO_Instance) and the input and output business objects as itschildren. The verb for the wrapper business object must be a valid operation

Page 8

6 Adapter for i2 User Guide

Page 9

Chapter 2. Installing and configuring the connectorThis chapter describes how to install and configure the connector component ofIBM WebSphere Busines

Page 10 - Adapter for i2 User Guide

v Run the Installer utility for IBM WebSphere Business Integration Adapters fromthe product CD and select the IBM WebSphere Business Integration Adapt

Page 11

Tip: Access this tool from the System Manager.v Connector Configurator--if WebSphere MQIntegrator is the integration brokerTip: Access this tool from

Page 13 - Processing subscriptions

Property Description Possible valuesApplicationUserName User name for the i2 connection Not used in this releaseApplicationPassword Password for the i

Page 14 - Processing verbs (operations)

Chapter 3. Understanding business objects for the connectorThis chapter describes the structure of i2 business objects, how the connectorprocesses the

Page 15 - Status updates

objects. A hierarchical business object contains both simple attributes and childbusiness objects or arrays of child business objects that contain the

Page 16 - 6 Adapter for i2 User Guide

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

Page 17

I2MO_AddBidInstanceId=CA_InstanceWrapperBOName=IBM_Bidding_BOVerb=DummySpecifying business object attribute propertiesThe i2 connector has various pro

Page 18 - Installed file structure

Attribute DescriptionAppSpecInfo For information on this property, see “Identifying business objectapplication-specific information” on page 15,Cardin

Page 19 - Connector-specific properties

16 Adapter for i2 User Guide

Page 20 - Starting the connector

Chapter 4. Generating business objects using i2 ODAThis chapter describes i2 ODA, an object discovery agent (ODA), which, workingwith XML schema ODA,

Page 21 - Defining connector metadata

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

Page 22 - 12 Adapter for i2 User Guide

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

Page 23 - Type=output

IBM WebSphere Business Integrati on A daptersAdapter for i2 User Gui deAdapter Version 1.0 .x

Page 24 - 14 Adapter for i2 User Guide

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

Page 25 - Special attribute values

RownumberProperty name Property type Description1 DefaultBOPrefix String Text that is prepended to the name of the business objectto make it unique.Ex

Page 26 - 16 Adapter for i2 User Guide

Metadata (Top tree node) (Expanding Metadata lists all the port types)PortType1(Child tree nodes)Operation1Input typeOutput typeOperation..nInput type

Page 27 - Steps for installing i2 ODA

v Port informationv Instance IDv Dummy key (as the business object creation will fail without a key)v Two single cardinality attributes representing t

Page 28 - Launching i2 ODA

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

Page 29

Create the metaobject for pollingOnce the business objects are created, you need to create the metaobjects forpolling using the CSM. These objects sha

Page 30 - Steps for using i2ODA

26 Adapter for i2 User Guide

Page 31

Chapter 5. Troubleshooting and error handlingThis chapter describes how the i2 connector for i2. handles errors. The connectorgenerates logging and tr

Page 32 - 22 Adapter for i2 User Guide

Polling-related error messagesThe following table describes polling-related error messages. These are logged inthe i2 Adapter log file.Notes:1. In som

Page 33

Error description Error type Handling by i2 connectorFail to convert XML messageto IBM business objectError The error that the XML message has asyntax

Page 34 - 24 Adapter for i2 User Guide

Note!Before using this information and the product it supports, read the information in Appendix D, “Notices”, on page 77.18April2003This edition of t

Page 35 - WrapperBOName

Error description Error type Handling by i2 connectorNot able to convert the XMLmessage to the business object.Error The i2 connector logs the message

Page 36 - 26 Adapter for i2 User Guide

Tracing Level Tracing MessagesLevel 5v Messages that indicate connector initialization, for example,messages showing the value of each configuration p

Page 37 - Structure of error messages

32 Adapter for i2 User Guide

Page 38 - 28 Adapter for i2 User Guide

Appendix A. Standard configuration properties for connectorsConnectors have two types of configuration properties:v Standard configuration propertiesv

Page 39

Listener PortCertificate LocationLogFileNameTraceFileNamejms.BrokerNameConfiguring standard connector properties for WebSphere InterChangeServerThis s

Page 40 - Tracing messages

To determine the update semantics for a specific property, refer to the UpdateMethod column in the Connector Configurator window, or see the Update Me

Page 41 - Tips for troubleshooting

Property Name PossiblevaluesDefaultvalueUpdatemethodNotesjms.NumConcurrentRequests positive integer 10 componentrestartJMS transportonlyjms.Password A

Page 42 - 32 Adapter for i2 User Guide

Property Name PossiblevaluesDefaultvalueUpdatemethodNotesSynchronousRequestQueue CONNECTORNAME/SYNCHRONOUSREQUESTQUEUEcomponentrestart“SynchronousResp

Page 43 - New and deleted properties

ApplicationNameName that uniquely identifies the connector’s application. This name is used bythe system administrator to monitor the WebSphere busine

Page 44 - 34 Adapter for i2 User Guide

multi-threaded, or be capable of using Connector Agent Parallelism and beconfigured for multiple processes (setting the Parallel Process Degreeconfigu

Page 45

Integration broker compatibilitySupported on IBM WebSphere Business Integration Adapter Framework versions2.2.0, IBM WebSphere InterChange Server vers

Page 46 - 36 Adapter for i2 User Guide

DeliveryQueueThe queue that is used by the connector to send business objects to the integrationbroker.The default value is DELIVERYQUEUE.DeliveryTran

Page 47 - AgentTraceLevel

In this environment, you may experience difficulty starting the both the connectorcontroller (on the server side) and the connector (on the client sid

Page 48 - ConcurrentEventTriggeredFlows

JvmMinHeapSizeThe minimum heap size for the agent (in megabytes). This property is applicableonly if the RepositoryDirectory value is <REMOTE>.T

Page 49 - ControllerTraceLevel

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

Page 50 - DeliveryTransport

The default value is false.OADMaxNumRetrySpecifies the maximum number of times that the OAD automatically attempts torestart the application-specific

Page 51 - JvmMaxNativeStackSize

RepositoryDirectoryThe location of the repository from which the connector reads the XML schemadocuments that store the meta-data of business object d

Page 52 - 42 Adapter for i2 User Guide

SynchronousRequestTimeoutSpecifies the time in minutes that the connector waits for a response to asynchronous request. If the response is not receive

Page 53 - OADAutoRestartAgent

Name Possible values Default valueAdminInQueue valid JMS queue name CONNECTORNAME/ADMININQUEUEAdminOutQueue valid WebSphere MQqueue nameCONNECTORNAME/

Page 54 - 44 Adapter for i2 User Guide

Name Possible values Default valueSourceQueue valid WebSphere MQqueue nameCONNECTORNAME/SOURCEQUEUESynchronousRequestQueue valid WebSphere MQqueue nam

Page 55

manually modify the \Data\Std\stdConnProps.xml file in the productdirectory. For more information, see the appendix on ConnectorConfigurator.Attention

Page 56 - 46 Adapter for i2 User Guide

iv Adapter for i2 User Guide

Page 57

The default value is CONNECTORNAME/FAULTQUEUE.jms.FactoryClassNameSpecifies the class name to instantiate for a JMS provider.The default is CxCommon.M

Page 58 - 48 Adapter for i2 User Guide

Attention:v WebSphere MQ Integrator supports only one locale at a time. Ensure that everycomponent of the installation (for example, all adapters, app

Page 59

example, C:\WebSphereAdapters\repository. The value must be a directory path.Do not use <REMOTE> as the RepositoryDirectory value for a connecto

Page 60

WireFormatThe data format for messages exchanged by the connector. The default value CwXMLis the only valid value, and directs the connector to compos

Page 61 - RepositoryDirectory

54 Adapter for i2 User Guide

Page 62 - 52 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

Page 63 - WireFormat

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

Page 64 - 54 Adapter for i2 User Guide

Running Configurator independently of System ManagerWhen you run Connector Configurator without connecting to System Manager,you can save a connector

Page 65

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

Page 66 - 56 Adapter for i2 User Guide

Specifying general characteristicsThe Properties - Connector-Specific Property Template dialog appears. The dialoghas tabs for General characteristics

Page 67 - Choosing your broker

ContentsIntegration broker compatibility ...iiiAbout this document ...viiAudience ...

Page 68 - 58 Adapter for i2 User Guide

Setting dependenciesAfter you have finished making changes in both the General and the Value tabs,choose Next. The Dependencies dialog appears.A depen

Page 69 - Specifying values

display. When you select a name in the Template Name display, the PropertyTemplate Preview display shows the connector-specific properties that havebe

Page 70 - Setting dependencies

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

Page 71

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

Page 72 - Using an existing file

default values and some do not; you can modify some of the default values. Theinstallation and configuration chapter of each adapter guide describes t

Page 73

Encryption for connector properties (ICS)Application-specific properties can be encrypted by clicking the Encrypt check boxin the Edit Property window

Page 74 - 64 Adapter for i2 User Guide

4. In the File menu of the Connector Configurator window, choose Save to Project.The revised connector definition, including designated support for th

Page 75 - Business object name

If you are using maps that are uniquely defined for specific source and destinationbusiness objects, the maps will already be associated with their ap

Page 76 - Associated maps (ICS)

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

Page 77 - Resources (ICS)

Important: Connector Configurator accepts property values in either English ornon-English character sets. However, the names of both standard andconne

Page 78 - Data handlers

Service call request handling features ...73General features ...74Appendix D. Notices ...

Page 79

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

Page 80

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

Page 81 - Configurator

For connector-specific properties, however, you will need to both define theproperties and set their values. Connector Configurator provides the inter

Page 82 - Completing the configuration

Appendix C. Connector feature listThis appendix details the features supported by the i2 connector. For descriptionsof these features, see “Appendix A

Page 83 - Event notification features

Category Feature Support NotesLogical delete N/AExist Exist verb NoMisc Attribute names Partial MO_Instance is the standard used torepresent the metao

Page 84 - General features

Category Feature Support NotesConnector properties ApplicationPassword NoApplicationUserName NoUseDefaults No There is no validation of the business o

Page 85

76 Adapter for i2 User Guide

Page 86 - 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

Page 87 - Appendix D. Notices

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

Page 88 - Trademarks and service marks

IBMthe IBM logoAIXCrossWorldsDB2DB2 Universal DatabaseMQIntegratorMQSeriesTivoliWebSphereLotus, Domino, Lotus Notes, and Notes Mail are trademarks of

Page 89 - Appendix D. Notices 79

About this documentIBM(R) WebSphere(R) Business Integration Adapters supply integrationconnectivity for leading e-business technologies and enterprise

Page 90 - 80 Adapter for i2 User Guide

80 Adapter for i2 User Guide

Page 92 - Printed in U.S.A

Printed in U.S.A.

Commentaires sur ces manuels

Pas de commentaire