Browse Prior Art Database

Long Running Request for Topology Database Requests

IP.com Disclosure Number: IPCOM000114954D
Original Publication Date: 1995-Feb-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 73K

Publishing Venue

IBM

Related People

Holt, VS: AUTHOR [+4]

Abstract

A user can submit a request to Topology Integration Services database for data on discovered nodes. An XMP API call, called an Action is used to retrieve data from Topology Integration Services. However, because of the architecture of XMP and the framework, when a request is made, the requestor and the responder begin an association that is marked by the issuance of invoke ids. The invoke id is a way of denoting the association for each of the parties as well as the framework. Once a request has been fulfilled, the invoke ids are deleted and the association is closed.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Long Running Request for Topology Database Requests

      A user can submit a request to Topology Integration Services
database for data on discovered nodes.  An XMP API call, called an
Action is used to retrieve data from Topology Integration Services.
However, because of the architecture of XMP and the framework, when a
request is made, the requestor and the responder begin an association
that is marked by the issuance of invoke ids.  The invoke id is a way
of denoting the association for each of the parties as well as the
framework.  Once a request has been fulfilled, the invoke ids are
deleted and the association is closed.

      An aspect the user is greatly interested in is the ability to
ask for information on a group or a specific node, and also be
contacted for any changes to that group or single node as well as the
appearance of new nodes.  This way the user can keep abreast of the
dynamics of the managed environment.  The problem is that in order to
supply information about changes or additions to the environment,
Topology Integration Services must have the ability to leave a
request open.  Then, when the user no longer wants updates, close the
open request.  A solution must be found to keep the
request/association from closing, and to be able to close it when the
user no longer wants the request.

      The solution to the problem is called a long running request.
A user can now have the option of requesting current data in one
call, or they can ask for an open request that will give them changes
and additions as they happen.

      In order to achieve this, Topology Integration Services will
receive an action from the requester that will have a flag that
specifies that a long running request is requested.  Topology
Integration Services (TOPIS) will respond with it's invoke id it
received on the action back to the req...