The following terms are used in this Guide:
- ASI (Application-Specific Information) is code tailored to a
particular application or technology. ASI exists at both the attribute
level and business object level of a business object definition.
- ASBO (Application-Specific Business Object) A business object
that can have ASI.
- BO (Business Object) A set of attributes that represent a
business entity (such as Customer) and an action on the data (such as a create
or update operation). Components of the IBM WebSphere system use
business objects to exchange information and trigger actions.
- Content-Type The HTTP protocol header that includes the
type/subtype and optional parameters. For
example, in the Content-Type value
text/xml;charset=ISO-8859-1, text/xml is the
type/subtype and charset=ISO-8859-1 is the optional Charset
parameter.
- ContentType refers to the type/subtype
portion of the Content-Type header value only. For example, in the
Content-Type valuetext/xml;charset=ISO-8859-1,
text/xml is referred to in this document as the ContentType.
- MO_DataHandler_DefaultSOAPConfig Child data handler meta-object
specifically for the SOAP data handler.
- GBO (Generic Business Object) A business object with no ASI and
not tied to any application.
- MO_DataHandler_Default Data handler meta-object used by the
connector agent to determine which data handler to instantiate. This is
specified in the DataHandlerMetaObjectName configuration property of the
connector.
- Non-Top Level Business Object (Non-TLO)A non-TLO is any
business object that does not adhere to the web services TLO structure.
- Protocol Config MO During request processing, the SOAP/JMS,
SOAP/HTTP-HTTPS protocol handlers use a Protocol Config MO to determine the
destination of the target web service. If during event processing you
are exposing collaborations as SOAP/JMS web services, the connector uses the
Protocol Config MO to convey the JMS message header information from the
SOAP/JMS protocol listener to the collaboration.
- SOAP (Simple Object Access Protocol) defines a model of using
simple request and response messages, written in XML, as the basic protocol
for electronic communication. SOAP messaging is a platform-neutral
remote procedure call (RPC) mechanism, but it can be used for the exchange of
any kind of XML information (document exchange).
- SOAP Business Object A SOAP business object is a child of a TLO
and can be a SOAP Request, a SOAP Response or a SOAP Fault business
object. SOAP business objects contain information necessary for
processing by the SOAP data handler, including SOAP ConfigMOs, which are
children of SOAP business objects, and also contain SOAP header container
business objects.
- SOAP Config MO (Configuration Meta Object) The data handler
requires an object that contains configuration information about a single
transformation, for example, from a SOAP message to a SOAP business
object. This information is stored as meta-data in the child of a SOAP
business object. This child object is the SOAP Config MO
- SOAP Header Child Business Object A business object that
represents a single header element in a SOAP message. The header
element is an immediate child of the SOAP-Env:Header element of the SOAP
message. All attributes of a header container business object must be
of this type. These business objects may have an actor and a
mustUnderstand attribute. These attributes correspond to the actor and
mustUnderstand attributes of the SOAP header element.
- SOAP Header Container Business Object A business object that
contains information about the headers in a SOAP message. This business
object contains one or more child business objects. Each child business
object represents a header entry in the SOAP message. The SOAP data
handler business object may have an attribute, which is of type SOAP header
container business object. This attribute is also referred to as the
SOAP header attribute. Such an attribute has special
application-specific information requirements as described in SOAP data handler. This attribute must be an immediate child of a SOAP
business object.
- Top-Level Business Object A web services top-level business
object contains a SOAP Request, a SOAP Response (optional) and one or more
SOAP Fault (optional) business objects. A TLO is used by the connector
for both event processing and request processing.
- Web services are self-contained, modular, distributed, dynamic
applications that can be described, published, located, or invoked over the
network to create products, processes, and supply chains. They can be
local, distributed, or Web-based. Web services are built on top of open
standards such as TCP/IP, HTTP, Java, HTML, and XML. Web services use
new standard technologies such as SOAP (Simple Object Access Protocol) for
messaging, and UDDI (Universal Description, Discovery and Integration) and
WSDL (Web Service Description Language) for publishing.
- UDDI (Universal Description, Discovery and Integration) is a
specification that defines a way to publish and discover information about web
services. UDDI specification provides for XML-based interfaces (APIs)
that allow programmatic access to the UDDI registry information. SOAP
is the underlying RPC mechanism for these APIs.
- WSDL (Web Services Description Language) is an XML vocabulary
that defines the software interfaces for web services. It organizes all
of the web service technical details required for automatic integration at the
programming level, and is used to publish IBM WebSphere collaborations as web
services. WSDL is to web services as IDL is to CORBA objects.
