Browse Prior Art Database

Combined Interceptor for Activity Service and other Unit Of Work Services

IP.com Disclosure Number: IPCOM000013486D
Original Publication Date: 2001-Apr-16
Included in the Prior Art Database: 2003-Jun-18
Document File: 2 page(s) / 35K

Publishing Venue

IBM

Abstract

A program is disclosed that enables the efficient reconstruction after propagation of the hierarchy represented by the Activity Service ActivityContext in combination with the Object Transaction Service PropagationContext , avoiding the creation of temporary maps and difficulties relating to the unknown ordering of the contexts.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Combined Interceptor for Activity Service and other Unit Of Work Services

A program is disclosed that enables the efficient reconstruction
after propagation of the hierarchy represented by the Activity
Service ActivityContext
in combination with the Object
Transaction Service PropagationContext
, avoiding the creation of
temporary maps and difficulties relating to the unknown ordering
of the contexts.

Background

    An Activity Service has been proposed by IBM Corp (OMG
Document Number orbos/2000-06-19) in response to the Object
Management Group's request for proposals for Additional
Structuring Mechanisms for the OTS
. This is an object framework
for the support of more complex transactional semantics than the
simple ACID properties of the Object Transaction Service (OTS).
The purpose of the Activity Service is to provide support for
composing applications that require non-prescriptive, extended
transaction behaviour. Long-running applications, for example,
can be structured as many independent, short-duration units of
activity
to form a "logical" long-running transaction. Such
structuring allows an activity to acquire and use resources for
only the required duration of this long-running transactional
application.

    The Activity Service provides interfaces to specify
demarcation boundaries for units of activity, and provides a
distributed service context that is implicitly propagated, via an
ORB, on remote requests. Key components of the Activity Service
are:

Actions and SignalSets. Actions may be registered with a
ActivityCoordinator in order to be involved in the coordinated
completion of that Activity, via an application- or
vendor-provided SignalSet. A SignalSet encapsulates the rules
governing the behaviour of the Activity during completion.
PropertyGroups. PropertyGroups may be registered with the
Activity Service to provide a mechanism by which
application-specific data may be made available on a
distributed thread of execution, bounded by the encapsulating
Activity.

Problem

    The Activity Service defined in the OMG document defines a
service context that enables different vendor implementations to
interoperate. In particular, an ActivityContext structure is
specified that represents, using an ordered sequence of
ActivityIdentity structures, a nested hierarchy of Activities
and, possibly, Transactions.

    An ActivityIdentity may represent an Activity or
transaction. In the latter case, the ctxIdfield contain...