Ibm WebSphere Adapters Manuel d'utilisateur

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

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 226
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs

Résumé du contenu

Page 1 - WebSphere

WebSphere®AdaptersWebSphere Adapter Toolkit User GuideVersion 6 Release 2Version 6 Release 2

Page 2

WebSphere adapters utilize a format-independent data model for representing dataobjects. In a WebSphere Process Server or WebSphere Enterprise Service

Page 3

Callback event processing for event delivery with XA transactionTo provide data integrity and to make sure events are not delivered more thanonce, whi

Page 4

When the adapter signals that it has completed delivery, the transaction managerwill then call ″end″, ″prepare″, and ″commit″ to complete the requirem

Page 5 - Contents

Callback event processing for event recoveryWhen there is a failure in the event processing as part of system recovery, theadapter is able to recover

Page 6

When the container starts, it calls the getXAResources() method on the adapter toget all the associated XA resources. The adapter then instantiates th

Page 7 - WebSphere Adapter Toolkit

Application sign-onThe Adapter Foundation Classes can use either container-managed orcomponent-managed authentication or sign-on.The process of connec

Page 8 - IBM WebSphere Adapters

7. The ConnectionManager may call getConnection(Subject,ConnectionRequestInfo) on a ManagedConnection where the passedConnectionRequestInfo does not m

Page 9 - Business

public Object createConnectionFactory(ConnectionManager connMgr) throwsResourceException{return new TwineBallConnectionFactory(connMgr, this);}2. Mana

Page 10 - Architectural overview

Best practicesv Each ManagedConnection instance should encapsulate at most one connection tothe EIS.v Since there may be more than one Connection inst

Page 11 - JCA connector component

public Interaction createInteraction() throws ResourceException{return new TwineBallInteraction(this);}Note: If you want to provide your own implement

Page 12

this.connection.getResourceAdapter();ObjectNaming objectNaming = new ObjectNaming(resourceAdapter);factory = new TwineBallCommandFactory(objectNaming)

Page 13 - Metadata

processing performed by each component (and subcomponent) in the model isdescribed in sections that follow the illustration.The component model allows

Page 14

properties should not change the configuration of the EIS.javax.resource.cci.ConnectionMetadata:A javax.resource.cci.ConnectionMetadata instance provi

Page 15

3. Override method WBIManagedConnection.getLocalTransaction() and, if XAsupport is provided, method WBIManagedConnection.getXAResource().Wrap either o

Page 16

Adapters are responsible for creating, updating, retrieving, and deleting (CRUD)records in the EIS system based on the structure described by the inco

Page 17 - Operating system requirements

Consider the following scenario: Child B1 is in the EIS, but is not in the incomingstructure. Child B1, then, must be deleted. The Command Manager wil

Page 18 - Samples overview

Command Manager DeleteDelta objectsDelta processing is only relevant for service data objects (SDO).The Command Manager functions in a similar way whe

Page 19 - Developer

Suppose, as in the example below, that child B1 is created and is part of the changesummary. The resulting command structure will contain a Create com

Page 20

Command Manager CreateWhen it processes this structure, the interpreter will execute the No-op commandsas well as the Create command. In general, the

Page 21

Command Manager simplifies before and after comparisonsAs shown in the upper portion of the figure, the input to the Command Manageris a before image

Page 22

The Command Manager processes delta structures in a manner analogous to thatof after-image data. The difference is that, for delta objects, comparativ

Page 23

You will need to implement the following:1. Command implementations for each command type (″Retrieve″, ″RetrieveAll″,″Create″, ″Update″, ″Delete″, and

Page 24

The connectivity subcomponent interacts with the target enterprise informationsystem’s specific libraries and functionality. The subcomponent is expos

Page 25

if (functionName.equals(NodeLevelOperations.CREATE_NODE)) {command = new TwineBallCreateCommand();} else if (functionName.equals(NodeLevelOperations.D

Page 26

Data and metadataAdapter Foundation Classes (AFC) implement DESPI APIs and support two dataformats, service data objects (SDO) and JavaBeans.The data

Page 27

Table 2. Mapping between built-in XSD schema and JavaBean properties (continued)Header HeaderanySimpleType StringAny StringThere are cases in which a

Page 28

The notion of whether or not a property is set is critical to processing null valuesor values that have not been set in the adapter. If a property has

Page 29

As defined in the sapBAPIBusinessObjectTypeMetadata schema ″Operation″ is ann-cardinality complex type. The ″MethodName″ element of the operation type

Page 30 - Modify the module

objectAnnotationsMapObjectName WBI_CUSTOMER_CIOperation operationsListcreateOperationsMapName CreateMethodName MethodNameListoperationListupdateOperat

Page 31 - Test the sample

These interfaces may contain more helper methods than are listed here, please seethe Javadoc for the additional helpers.Factory classesClass TypeFacto

Page 32

Property getProperty(String propertyName)Returns the property object for this property name.Map getAnnotations(String source)Returns the object-level

Page 33

boolean isContainment()Returns whether or not the property contains a Type(complex object).boolean isMany()Returns whether or not the property contain

Page 34 - Troubleshooting the samples

Support for GeneratedRecords artifact type: WebSphere adapters may supportJavaBeanRecord data representation along with SDO 1.0 and SDO 2.0 data objec

Page 35

the appropriate programming model. It is responsible for mapping the specificinvocation to the invocation of the connector component through the JCA c

Page 36

The enterprise metadata discovery component is analogous to the Object DiscoveryAgent of WebSphere Business Integration Adapters. In addition to gener

Page 37 - Specify project properties

Business Object StructuresThese are the business objects used by JCA adapters. They describe the structureand content of arguments to functions on the

Page 38 - Specify project facets

Service metadataEnterprise metadata discovery architectureThe enterprise metadata discovery tooling includes runtime, discovery, and servicegeneration

Page 39

These interfaces extend the CCI interfaces defined in the JCA specification tosupport invocation of services discovered with enterprise metadata disco

Page 40 - Specify generation options

for multiple back-end EIS assets. IBM WebSphere recommends a singleadapterType for each enterprise metadata discovery implementation.The following inf

Page 41

copy matching properties from metadata connection to runtime connection. Formore information, see the WBIOutboundConnectionTypeImpl in the Javadocs.Th

Page 42

MetadataConnectionThe MetadataConnection object represents the connection to EIS or EIS repository.This interface is implemented by the Adapter Founda

Page 43

In addition to object selection, MetadataSelection also holds properties that areapplicable for the selected objects. Such properties include the foll

Page 44 - Data Binding classes

the import. The Adapter Foundation Classes provide an implementation forServiceDescription as abstract classes. Discovery service implementations shou

Page 45

You must provide EIS connection descriptions for the enterprise metadatadiscovery service. Adapter Foundation Classes contain interface implementation

Page 46

Version 1.1 of Enterprise Metadata Discovery includes enhancements forconfigurable data handlers, function selectors, and data bindings, and a way tob

Page 47

Outbound Function DescriptionThe following information has to be filled in by the discovery serviceimplementations:v Name - e.g. createCustomer, apply

Page 48

Note: To limit confusion, custom operation names should not conflict with thestandard operation names mentioned above.Note: In cases where the mapping

Page 49

v Name – For example, VENDORIDv Type – For example, stringv Cardinality – 1 or Nv Required – Booleanv ObjectTypeName – For cases where an attribute ma

Page 50

BootStrap:WebSphere Integration Developer performs a bootstrap step to identify a resourceadapter that has been enabled for enterprise metadata discov

Page 51

v PropertyGroup – A collection of properties including single and multi types andPropertyGroup itself. For example, OutboundConnectionConfiguration al

Page 52

A propertyChange() method should be implemented if a property needs to listenfor changes on some other property. Check the TwineBall sample forService

Page 53

public TwineBallMetadataDiscovery() throws MetadataException {super("com.ibm.j2ca.sample.twineball.emd");}The WBIAdapterTypeImpl constructor

Page 54

discovery and the one that used for run time. The copy is based on names. Forexample, if a property name Username exists in the configuration used for

Page 55

public TwineBallAdapterType()throws MetadataException{super(Constants.RESOURCE_ADAPTER_BEAN_NAME, 2, 1);setId(Constants.ADAPTER_NAME);setDisplayName(C

Page 56

the managed connection factory types that are supported by the adapter. Eachmanaged connection factory maps to an instance of outbound connection type

Page 57

– The New Connector Project Wizard - Prompts you to specify informationabout the resource adapter you wish to develop, and then generates code anda de

Page 58

setDescription(WBIMetadataDiscoveryImpl.getPropertyDescription("ConnectionType"));setId("TwineBall");setDisplayName(WBIMetadataDis

Page 59

TwineBallConfigurationProperties.getTwineBallConfigurationProperties();TwineBallResourceAdapter ra =new TwineBallResourceAdapter();WBIPropertyGroupImp

Page 60

This class is similar to WBIOutboundConnectionConfigurationImpl except insteadof ManagedConnectionFactory, WBIInboundConnectionConfigurationImpl handl

Page 61

ConstructorThe constructor takes MetadataConnection as an argument. The constructor canalso return properties from MetadataConnection that were used t

Page 62

(Constants.SERVICETYPE));propertyGroup.addProperty(typeProp);WBISingleValuedPropertyImpl nameSpaceProp =new WBISingleValuedPropertyImpl(Constants.NAME

Page 63

ArrayList objects = getTopLevelObjects();response.setObjects(objects);return response;}WBIMetadataObjectImpl samples:WBIMetadataObjectImpl represents

Page 64 - Using the Overview pane

createSelectionPropertiesThe createSelectionProperties() method returns a property group that is used tocapture inputs from users. These inputs includ

Page 65

The enterprise metadata discovery service uses WBIMetadataEditImpl to acquireconnectionTypes, which contains editable properties forResourceAdapter,Ma

Page 66

dataDesc.prepareChildSchemaFiles();WBIMetadataDiscoveryImpl.getLogUtils().trace(Level.FINER,CLASSNAME,"preparingChildSchemaFiles","Prep

Page 67

bometadata.setNameSpace(namespace);bometadata.setObjectNameSpace(Constants.BUS_OBJ_APPINFO_ASI_TYPE_TAG);bometadata.setASI(Constants.ASI_OBJECTNAME,th

Page 68

v Generate a resource adapter deployment descriptorYou can view and edit this deployment descriptor using the Resource AdapterDeployment Descriptor Ed

Page 69

WBIMetadataDiscoveryImpl.getLogUtils().traceMethodExit(CLASSNAME, "getImportNameSpaces");return list;}getNameSpacesThe getNameSpaces() metho

Page 70

getChildListThe getChildList() method returns the Iterator for the child objects of theDataDescription.public Iterator getChildList() throws MetadataE

Page 71

FunctionDescription[] funcArray =new FunctionDescription[functionDescriptions.size()];functionDescriptions.toArray(funcArray);super.setFunctionDescrip

Page 72

dataDescription.setMetadataObject(metadataObj);dataDescription.populateSchemaDefinitions();dataDescription.setRelativePath(location);dataDescription.s

Page 73 - Generated bean properties

Creating services that use technology-style adapters relies on being able toimplement the interfaces in the commonj.connector.metadata.build.* package

Page 74

processed. A custom function selector can use the information in theInboundInteractionSpec to generate a native function.For a custom adapter, you can

Page 75 - Data model

To access the binding configuration, docontext.get(BindingContext.BINDING_CONFIGURATION)To access the expected type, do context.get (BindingContext.EX

Page 76 - After-images versus deltas

v WBIMetadataBuildv WBIFunctionBuilderv WBIMetadataType (optional)When you extend WBIMetadataBuild, you will need to implement the followingmethods:v

Page 77 - Business object standards

Extend WBIMetadataType if your adapter needs a simple wrapper object around apayload object, similar to the IBM WebSphere Adapter for Flat Files and t

Page 78

Initialize input methodThis method resolves the type of the metadata if it’s a JavaBean or SDO type andinitializes the metadata interfaces appropriate

Page 79

IBM WebSphere Adapter Toolkit tasksThe tasks range from installing the toolkit, samples, and Adapter FoundationClasses (using the Eclipse Update Manag

Page 80

Set managed connection methodThis method passes the ManagedConnection handle to the record implementation,allowing the record to get access to the phy

Page 81

the retriveAll operation could return ″N″ records from the backend application,for each call to the getNext() method the implementation should fill in

Page 82

The method should first extract the value from backend object representationdefined through Xpath and use OutputCursor and OutputAccessor interfaces t

Page 83

For operations where getNext() should be invoked multiple times like RetrieveAll,the databinding should call getNext() multiple times add the built Bu

Page 84

v When WBIStructuredRecord is initialized with data that contains Bidiannotations, Cursors and accessors that are associated with that structuredrecor

Page 85 - Inbound event notification

How to support fault handling:Understand the following concepts for implementing fault handling into youradapter.Before you define faults, review adap

Page 86

//Added for Faults funcDesc.setName(operation.toLowerCase() + queryDataDesc.getBOName());getLogUtils().trace(LogLevel.FINEST,CLASSNAME, "getXMLLi

Page 87 - Application Requirements

public class JDEXMLListFaultDataDescription implementsFaultDataDescription {public JDEXMLListFaultDataDescription() {super();// TODO Auto-generated co

Page 88

fdesc2.setGenericDataBindingClassName("com.ibm.j2ca.extension.emd.runtime.WBIFaultDataBindingImpl");fdesc2.setFaultName(FaultBOUtil.MATCHES_

Page 89

Table 4. Fault name and configured fault binding (continued)Fault Name Configured Fault BindingINVALID_REQUEST com.ibm.j2ca.extension.emd.runtime.WBIF

Page 90

Operating system VersionsWindows 2000 Windows 2000 Professional (SP4)Windows 2000 Server (SP4)Windows 2000 Advanced Server (SP 4)Windows XP Windows XP

Page 91

You can use the FaultBOUtil to define the fault business object, as long as eitherno attributes or only simple attributes are added. This should amoun

Page 92

– They provide information on the state of the adapter for use by monitortooling– Represented as common base event data at run time, event messages ca

Page 93 - Transaction Support Methods

Writing a trace messageYou use the trace method of the LogUtils class to generate a trace message. Thismethod has two signatures. One of them is infor

Page 94

"getRecordForEvent()", "test");return null;}}Example of trace message for the outbound scenario with confidential tracingproperty

Page 95

Tracing assists developers and troubleshooters. Due to the significant performancecost incurred by tracing, however, many customers disable it in prod

Page 96 - One way callback events

Message typesThere are two message types for adapters, ADAPTER_RBUNDLE. The BASE_RBUNDLE isreserved for the Adapter Foundation Classes. The message ty

Page 97 - Callback event sender

translated text. Values that are language-independent, such as key values or objectnames, are appropriate as log message parameters.Similarly to trace

Page 98

Example of log message for the inbound scenario with confidential tracingproperty enabledpublic javax.resource.cci.Record getRecordForEvent(com.ibm.j2

Page 99

public interface EventSourceContext{/*** Returns an event source for a monitored element.* @param elementKind an artifact kind that can be monitored e

Page 100

* The client of an event point needs to know the payload of the fired events.*/public interface EventPoint{/***return the name of the event point*/Str

Page 101

This documentation describes how to run the Twine Ball sample only. However,you can apply the instructions for running and testing the Twine Ball samp

Page 102

<?xml version="1.0" encoding="UTF-8"?><EventNaturesSpec name="EventNatures" targetNamespace="http://www.ib

Page 103 - Outbound support

targetNamespace="http://www.ibm.com/xmlns/prod/websphere/scdl/eis/6.0.0:JCAAdapter"xmlns:er="http://www.ibm.com/xmlns/prod/websphere/re

Page 104 - Application sign-on

Purpose1. Monitorable Element Schema (.mes) file changesDefines the element type within an adapter where monitoring can be attached.The element type i

Page 105 - Implementing outbound support

d. If eventPoint is enabled, then fire event for Entry, Exit and Failure isinvoked.Entry event is fired in the beginning of the method call, exit even

Page 106

v Is a transaction (and the application) hung, or are transactions failing?v What is the response time?v Are service level commitments being met?v Who

Page 107

statistics and data for each ManagedConnection, which can be used to assess andtroubleshoot performance related problems.In order for resource adapter

Page 108

FFDC processing overviewInstead of explicitly instrumenting catch blocks by calling FFDC directly, eithermanually or by using a tool, you can write a

Page 109

If you use the FFDCSupport aspect, you can ensure a consistent FFDC policy foryour application by adding declare warning or error advice to your aspec

Page 110

When using FFDCSupport aspect you can control the data gathered. Two templatemethods getSourceId and getProbeId are provided to you for this purpose.

Page 111 - Using command patterns

Exception messagesException messages, like trace messages, convey information about problems. Thedifference is that exception messages are tailored mo

Page 113

This launches the Samples.c. From the Samples navigation pane, select Technology samples and expandJava and WebSphere Adapters so that the Twine Ball

Page 114

To test the enterprise metadata discovery (EMD) implementation for the developedresource adapter, complete the following steps:1. From the IBM WebSphe

Page 115

JUnit: an open source framework for unit testingJUnit is becoming the standard tool for unit testing in Java developmentenvironments. JUnit allows you

Page 116

Your adapter may or may not be dependant on ″live″ data inside the EIS. If so,you must either return the data to a known state after every test, or cr

Page 117

setUp()The setUp() method for inbound is very similar to that for outbound. You may,however, not need an outbound connection through the adapter. Acco

Page 118

For information on testing the adapter in managed mode in WebSphereApplication Server, see Validating code with Rational Application Developer /Websph

Page 119

Test module configuration3. Select the testing mode and click Finish to start the test. On the DeploymentLocation screen, select a WebSphere Process S

Page 120

Adding a value to the DatapoolThis adds the data to Datapool.When you want to use this input data again, select Use Value from Pool.Using an execution

Page 121 - Data and metadata

After you have created and exported an adapter EAR file with the service type setto Inbound, you can test inbound functionality.1. Edit your module us

Page 122

Selecting the Java packageg. Save the module.2. Publish the application to WebSphere Process Server.3. Open the administration console for the WebSphe

Page 123

Validating code with Rational Application Developer andWebSphere Application ServerTo test the adapter in the Websphere Application Server environment

Page 124

c. Optional: Deselect the Add project to an EAR check box.4. Click Finish.A dialog prompts you to open the J2EE perspective. Click Yes to finish thepr

Page 125 - The Metadata API

4. In the Resource Adapter deployment panel, choose how to deploy the adapter.You can deploy the adapter with the EAR or you can deploy the adapter as

Page 126 - Interfaces

7. Start UTC using the Run universal test client option.WebSphere Adapter development overview 205

Page 127 - Interface Type:

8. Once the UTC comes up, use the JNDI explorer to find your EJB. Look for yoursession EJB under EJB Beans.Now, you can test your adapter via the EJB

Page 128

Note: External service discovery is equivalent to enterprise metadata discovery.f. Select the appropriate external service.g. Specify the connection p

Page 129

ReferenceTerminologyThe terminology presented are of terms that are used frequently in thedocumentation.Adapter foundation classes (AFC)Sometimes refe

Page 130 - Types of enterprise metadata

EclipseAn open source infrastructure for building tools such as an IntegratedDevelopment Environment (IDE). The toolkit’s wizard and editor are Eclips

Page 131

OutboundOutbound is a description of the direction in which data and messages passfrom a J2EE client application to the EIS. Adapters support both inb

Page 132

NoticesThis information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed i

Page 133 - Metadata discovery

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently crea

Page 134 - OutboundConnectionType

this code are derived from IBM Corp. Sample Programs. (c) Copyright IBM Corp._enter the year or years_. All rights reserved.If you are viewing this in

Page 135 - InboundConnectionType

4. Click Next to launch the New External Service window.5. From the New External Service window, make sure that Unlisted Adapter isselected and click

Page 136 - MetadataConnection

214 WebSphere Adapters: WebSphere Adapter Toolkit User Guide

Page 137

IndexSpecial characters.WBIOutboundServiceDescriptionImpl 39(CCI), Common Client Interface 4(EAR) project, Enterprise ApplicationArchive 31(EAR), ente

Page 138

Ggeneration options 35Hhardware requirements 12Iimplementation overview 68Inboundcallback event notification 90, 91, 92,94callback event sender 91call

Page 139

Vverbsusagebusiness graph 71WWBIActivationSpec 37WBIAdapterTypeImpl 39, 141WBIConnection 35, 102WBIConnectionFactory 35, 101WBIConnectionRequestInfo 1

Page 140

218 WebSphere Adapters: WebSphere Adapter Toolkit User Guide

Page 142 - Namespace definition

Printed in USA

Page 143

7. From the Processing Direction window, select Outbound and click Next.8. From the Discovery Configuration window, click Next. No connectionpropertie

Page 144

10. From the Configure Composite Properties window, select Next.11. From the Service Generation and Deployment Configuration window, deselectSpecify a

Page 145

12. From the Service Location Properties window, click New. This launches theNew Integration Project window.13. From the New Integration Project windo

Page 146

15. Click Finish from the Service Location Properties window to add theoutbound interface to the module.16. You are prompted on whether you want to up

Page 147

4. Click Next to launch the New External Service window.5. From the New External Service window, make sure that Unlisted Adapter isselected and click

Page 148

7. From the Processing Direction window, select Inbound and click Next.8. From the Discovery Configuration window, click Next. No connectionproperties

Page 149

10. From the Configure Composite Properties window select Next.11. From the Service Generation and Deployment Configuration window, deselectSpecify a

Page 150

WebSphere®AdaptersWebSphere Adapter Toolkit User GuideVersion 6 Release 2Version 6 Release 2

Page 151

12. From the Service Location Properties window, click Finish to add the inboundinterface to the module.13. You are prompted on whether you want to up

Page 152

a. In the viewing pane of the Assembly diagram, right click and select Add →Java to add a Java component to the diagram2. Add a wire from the inbound

Page 153

4. Run the administrative console and verify the module is installed and running.5. Test the module by performing the following steps:a. Change to the

Page 154

6. In Java Creation and Deployment Configuration, make the followingselections:v Select create new project Name and enter a name for the project, fore

Page 155

6. On left side select EJBSessionBean1 and click CustomercreateCustomer(Customer) Enter input customer parametersTroubleshooting the samplesYou may ne

Page 156

Launching the New Connector Project wizardYou launch the wizard from IBM WebSphere Integration Developer.Make sure you have met all of the installatio

Page 157

Select a wizard dialog5. Start the wizard.Expand theJava EE folder, choose Connector Project, and click Next. This startsthe New Connector Project wiz

Page 158

Specify project propertiesYou name your connector project, optionally adding it to an Enterprise Applicationproject. You also specify the configuratio

Page 159

Specify project facetsAs part of the process of creating a project, you specify project facets. A project facetrepresents a unit of functionality in t

Page 160

2. Click Next to advance to the Resource adapter properties page.Now you are ready to set the properties for the resource adapter.Specify resource ada

Page 161

NoteBefore using this information and the product it supports, read the information in “Notices” on page 211.December 2008This edition applies to vers

Page 162

1. In Adapter Name, type the name of the adapter.2. In Adapter ShortName, type a one- to four-character short name for theadapter. The short name is u

Page 163

For information on the characteristics of an IBM WebSphere Resource Adapter anda J2C Resource Adapter, see Introduction to JCA.Generation Options dial

Page 164 - Implementing a data handler

You can select the following properties when generating outbound adapter classes:v Local transaction supportGenerating outbound adapter classes with l

Page 165 - Implementing a data binding

/*** Does the EIS support XA transaction?* Get the XAResource from your EIS and return the wrapper.** @return new instance of WBIXAResourceWrapper* @s

Page 166

When you choose the connection pooling component property the wizard willcreate the ActivationSpecWithXid class that extendsWBIActivationSpecForPoolin

Page 167

com.ibm.j2ca.extension.databinding.WBIDataBindingGeneratorFor information on how to generate data binding classes, see Generating DataBinding Classes.

Page 168 - Discovery-service.xml

v StringCaseChangerThis is a utility that you can use format the business object or attribute nameproperly.For information on how to generate Enterpri

Page 169 - Initialize output method

Generating outbound local transaction support methods:With local transaction support, the transaction is managed and performed by theEIS. LocalTransac

Page 170 - Get next method

Generating outbound XA transaction support methods:With XA transaction support, the transaction spans multiple heterogeneoussystems. It uses global or

Page 171 - Extract method

Review the section on command pattern classes in Generating an IBM WebSphereResource Adapter.The command pattern classes allow you to break down a hie

Page 172 - Data binding implementation

ContentsWebSphere Adapter Toolkit ...1IBM WebSphere Adapter Toolkit technologyoverviews ...2IBM WebSphere Adapters ...2Architectu

Page 173 - DataBinding generator

2. Review the available component property options associated with inboundadapter classes.Each of the component property options are described in the

Page 174 - Problem determination

2. Click Finish.Now, you can generate inbound event polling support.Generating inbound event polling support:Event polling refers to an adapter’s capa

Page 175

2. When you are finished choosing generation options, click Finish.Now, you can generate inbound callback event classes.Generating inbound callback ev

Page 176

2. When you are finished choosing generation options, click Finish.Now you can generate enterprise metadata discovery classes.Generating enterprise me

Page 177

2. When you are finished choosing generation options, click Finish.Generate data binding classes.Generating data binding classesYou can generate data

Page 178

2. When you are finished choosing generation options, click Finish.Learn how to generate a JCA resource adapter.Generating a JCA resource adapterYou u

Page 179

v ManagedConnectionFactory implementsjavax.resource.spi.ResourceAdapterAssociation,javax.ValidatingManagedConnectionFactory, ManagedConnectionFactoryv

Page 180 - Logging and tracing messages

v EditableType implements commonj.connector.discoveryEditableTypev MetadataDiscovery implementscommonj.connector.discovery.MetadataDiscoveryv Metadata

Page 181

implements javax.resource.runtime.SingleTypedProperty andjavax.resource.runtime.PropertyDescriptorv SingleValuedProperty implements javax.resource.run

Page 182

2. When you are finished choosing generation options, click Finish.Generate inbound JCA adapter classes.Generating inbound JCA adapter classesThe inbo

Page 183

iv WebSphere Adapters: WebSphere Adapter Toolkit User Guide

Page 184

2. When you are finished choosing generation options, click Finish.Generate JCA enterprise metadata discovery classes.Generating JCA enterprise metada

Page 185

2. When you are finished choosing generation options, click Finish.Generated code and deployment descriptorThe generated artifacts reflect the adapter

Page 186

Using the Resource Adapter Deployment Descriptor editorThe Resource Adapter Deployment Descriptor editor provides an easy andconvenient way to configu

Page 187

Deployment descriptor Overview paneAlternatively, you can view the deployment descriptor in the editor byhighlighting the file in the Project Explorer

Page 188

Using the Overview paneThe Overview pane provides access to general information about your resourceadapter. You can display it at any time by clicking

Page 189

Add component dialogThe Icons section of the overview pane allows you to associate icons with theresource adapter. You can specify a large or small ic

Page 190

Resource adapter paneThe General Information section allows you to specify deployment descriptorvalues for the entire resource adapter. This section d

Page 191

Add Config property dialogWhen you add, modify, or delete user-defined properties in this section, the editorcreates (or removes) the corresponding Ja

Page 192

The sections of the Outbound Adapter pane are described below.Outbound resource adapter paneThe General Information section allows you to specify depl

Page 193

Add Connection Definition dialogA Connection Definition requires the following information:v ConnectionFactory Interfacev ConnecitonFactory Implementa

Page 194

WebSphere Adapter ToolkitThe IBM®WebSphere®Adapter Toolkit provides the development tools, librariesand sample code to assist you in creating JCA reso

Page 195

Add Config property dialogWhen you add, modify, or delete user-defined properties in this section, the editorcreates (or removes) the corresponding Ja

Page 196

class. Clicking the Add button under the list of Message Listeners on the left sideof the editor displays the following dialog box.Add Message Listene

Page 197

Add Required Config Property dialogWhen you add, modify, or delete user-defined properties in this section, the editorcreates (or removes) the corresp

Page 198

Generated bean propertiesThe editor maps resource adapter properties to class code. When you modify theresource adapter, the editor performs automatic

Page 199 - Validating the code

You can now view or modify the raw ra.xml file using the default editor providedby WebSphere Integration Developer. When you use this editor to save t

Page 200

b. Identify configuration properties suitable for use by a client for a specificoutbound connection instance (for example, username, password, languag

Page 201 - Developing JUnit tests

v A full, working implementation, as opposed to the CCI Record model thatsimply defines interfaces that must be implemented by the adapter developer.v

Page 202

changes. For outbound requests, the adapter must interpret the change summary,making all applicable changes to the data. For example, if an ORDER_LINE

Page 203

Convert business object names from EIS-assigned formats to a camel case format(remove separators such as spaces or underscores and capitalize first le

Page 204 - Installing the test client

Outbound Operation Signatures NotesapplyChanges<BOType>create<BOType>update<BOType>delete<BOType>These operations can handle d

Page 205 - Saving business object data

The development process using the IBM WebSphere Adapter Toolkit includes thefollowing as shown in the illustration:1. Run the New JCA Resource Adapter

Page 206 - Testing inbound functionality

v Adapters should follow strict conventions in processing business objects. Thisincludes failing if an entity is marked as updated in the input busine

Page 207

2. If the EIS does not generate its own primary key (or keys), insert the keyvalues from the input business object into the appropriate key column (or

Page 208

Operation return valueNote: When writing the output values to the output cursor, be sure to include anygenerated keys or other side effects.Error hand

Page 209 - WebSphere Application Server

The InvalidRequestException exception is thrown if input to the operation is notsupported.The EISSystemException exception is thrown if the EIS report

Page 210

CCI clients of resource adapters that support batch results must be capable ofrecognizing a top-level container and iterating through the child object

Page 211

Note: The RetrieveAll operation always returns a result set regardless of howmany (if any) matches are found.Processing overviewRetrieveAll processing

Page 212

EIS applications. Depending on the underlying EIS, the business events an adaptergenerates may span the set of changes that have occurred to a given e

Page 213

Event Store Requirements1. Event data must be persistent. Once detected in the event store, an eventshould remain available there until deleted by the

Page 214 - Terminology

During recovery, WebSphere Application Server calls the resource adapter, queriesit for XAResources, and then performs transaction recovery as follows

Page 215

generate a timestamp to identify an event, producing an identifier such asMyAdapterName_06139833001005.Object KeyEach event should contain enough key

Page 216

Inbound event notification complements outbound request processing, enablingadapters to provide bidirectional communication between business processes

Page 217

StatusThe event status is used to track the state of an event. It allows the FoundationClasses to distinguish among events that are new from those in

Page 218

Field DescriptioneventType Corresponds to the Business Object Namefield of the event recordtimeStamp Corresponds to the Timestamp field of theevent re

Page 219 - Trademarks and service marks

5. Set the name of the WebSphere business object complexType that correspondsto this application entity6. Set the event status to New.Implementing eve

Page 220

Method DescriptionArrayList getEvents(int quantity, inteventStatus, String[] typeFilter)This method enables the adapter todetermine if there are any n

Page 221

EventStore transaction control methodsMethod Descriptionboolean isTransactional() Is the event store transactional? If so, thismethod should return tr

Page 222

Function selector:Function selectors map resource adapter events to corresponding SCA exportfunction names.The WebSphere Adapter component that expose

Page 223

When you enable inbound callback event notification, business processes arealerted to changes in, or new information about, an EIS. The phrase callbac

Page 224

Using the IBM WebSphere adapter foundation classes forinbound callback event processingThe adapter foundation classes can automatically track endpoint

Page 225

The sendWithReturn methods invoke onMessage on the InboundListener. Thismethod delivers the Record it received from the listener thread. Here the diff

Page 226 - Printed in USA

public EndpointPair(MessageEndpointFactory mef, ActivationSpec activationSpec) {this.mef = mef;this.activationSpec = activationSpec;}public boolean eq

Commentaires sur ces manuels

Pas de commentaire