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.
- 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.
- Protocol Config MO During request processing, the HTTP-HTTPS
protocol handlers use a Protocol Config MO to determine the
destination. If during event processing you are exposing
collaborations, the connector uses the Protocol Config MO to convey message
header information from the HTTP or HTTPS protocol listener to the
collaboration.
- Top-Level Business Object A top-level business object contains
a Request, a Response (optional) and one or more Fault (optional) business
objects. A TLO is used by the connector for both event processing and
request processing.
