IBM WebSphere Adapters - Manual (Page 140)

Outbound Function Description
The following information has to be filled in by the discovery service
implementations:
v Name - e.g. createCustomer, applyChangesCustomer
v InteractionSpec - Instance of interaction spec which has function name specified
that represents this method description. E.g. for createCustomer the function
name would be ’Create’.
v Input - input data description representing the object that is input to the method
v Output - output data description representing the object that is returned by the
method.
v MetadataImportConfiguration - Handle to the metadata import configuration or
the object that was selected by the user which lead to creation of this method
description.
See ″Outbound Operation Signatures″ in Standard operations for descriptions of
the outbound operation signature and scenarios for their use.
Data descriptions:
The data description implementation enables the adapter to create valid data
objects for EIS requests and to interpret the objects returned as responses. You
must implement DataDescription, InboundServiceDescription, and
OutboundServiceDescription
.
DataDescription
The data description is common to inbound and outbound service. It includes a
definition of the structure and content of adapter business objects that will be
passed between the client and adapter at run time. Each DataDescription instance
should have a unique namespace. The convention followed by IBM is to use a base
namespace concatenated by the name of the corresponding object.
InboundServiceDescription
The InboundServiceDescription must have a default name and associated function
descriptions. The standard top-level operations are described in Inbound Operation
Signatures. InboundFunctionDescription should use the same functionName and
EISFunctionName.
Note: If needed, the default FunctionSelector can be overridden.
OutboundServiceDescription
The OutboundServiceDescription must have a default name, along with associated
function descriptions. The supported, standard top-level operations are described
in the Outbound operation signatures table in Standard operations.
Adapters that can provide functionality above and beyond these standard
operations can opt to expose unique, EIS-specific operations. giving customers
access to more functionality of the EIS. Define names and behavior on a
case-by-cases basis to most accurately reflect the functionality of the underlying
EIS.
134 WebSphere Adapters: WebSphere Adapter Toolkit User Guide