Browse Prior Art Database

Automatic Update of Binding Information

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

Publishing Venue

IBM

Related People

Grillo, P: AUTHOR [+3]

Abstract

Disclosed is an algorithm to automatically update the binding information for dynamic routing and data conversion of client/server applications in a truly heterogeneous environment. This approach is very efficient and can be applied to remote call/return or send/receive interfaces, and it is extremely useful for applications generated by an application generator.

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

Automatic Update of Binding Information

      Disclosed is an algorithm to automatically update the binding
information for dynamic routing and data conversion of client/server
applications in a truly heterogeneous environment.  This approach is
very efficient and can be applied to remote call/return or
send/receive interfaces, and it is extremely useful for applications
generated by an application generator.

      For typical client/server applications, where hundreds or even
thousands of clients access the same server, it is painful and not
practical to modify every client's binding information if the server
is moved due to business or performance reasons.  The algorithm shows
an automatic way to update the necessary binding information so that
no change in the client side is needed even if the server is moved to
a dissimilar environment (with different system type or using
different code pages and linkage protocols).

      The Figure shows a scenario of two clients (residing on the
same machine), two servers, and a remote application database (RADB)
manager which control the access of a centralized database.  Each
client has its own local binding table (LBT) which can be accessed
via the conversion manager.  The algorithm works as follows:

1.  Keep the binding information of each registered remote
    application in a remote application database (RADB), which is
    controlled by the system administrator.  The database consists of
    the routing information such as application name, linkage
    protocols (e.g., APPC, TCP, NETBIOS, CICS, Namepipe, and SPX) and
    network addresses (e.g., SNA network address such as
    netID.LUName) and data conversion information such as machine
    type, code page, and language of the remote application (e.g.,
    COBOL or C) for each registered...