Browse Prior Art Database

Web Transport Gateway

IP.com Disclosure Number: IPCOM000123021D
Original Publication Date: 1998-Apr-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 3 page(s) / 120K

Publishing Venue

IBM

Related People

Morris, RP: AUTHOR

Abstract

There is a rush today to make data available on legacy systems available to users on the web. These legacy systems include data on OS/390, Novell servers, NetBIOS LAN servers, UNIX systems to name just a few. The problem is that much of the data on these systems is not directly accessible through standard web protocols such as TCP/IP and HTTP. Even if the data were available using web protocols, security concerns would prevent much of the data from being made available.

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

Web Transport Gateway

      There is a rush today to make data available on legacy systems
available to users on the web.  These legacy systems include data on
OS/390, Novell servers, NetBIOS LAN servers, UNIX systems to name
just a few.  The problem is that much of the data on these systems is
not directly accessible through standard web protocols such as TCP/IP
and HTTP.  Even if the data were available using web protocols,
security concerns would prevent much of the data from being made
available.

      The standard method for making this data available today is
through what is commonly known as a 3-tier solution.  A user using a
browser loads a web page from a web server.  Through the use of forms
and/or Java applets, requests are routed through a web server to
either a servlet or cgi-bin where the request is parsed and performed
by establishing communications with the appropriate legacy data
server.  The legacy system's response is then sent back to the
servlet/cgi-bin where it is converted into a format that the client
applet or web browser can handle and thus respond to the user.

      The proposed solution provides a single servlet that can allow
clients to communicate with any number of legacy servers without the
need for a special second tier servlet/cgi-bin for each type of
legacy server.  The aim is to provide basic transport layer services
between client and a legacy server using only the standard web
protocols available through any web browser or JVM.  For example, to
establish a connection between a client and a legacy server the
client would issue an HTTP request to a web server using the
following URL depending on the protocol used by the legacy server.
  http://webservername/servlet/webgateway?
  protocol=TCP&address=legacy.
  ibm.com:1476
  http://webservername/servlet/webgateway?
  protocol=SPX&address=0a9ed13.
  23fc21:2047
  http:webservername/servlet/webgateway?
   protocol=APPC&address=LEGACY_LU
  NAME:LEGACY_TPNAME
  http://webservername.servlet/webgateway?
   protocol=NetBIOS&address=lanServe
  rNetBIOSNAME

      The web server upon receiving the command would handle access
control for access to the servlet.  It passes the request to the
servlet which receives and parses the request, and establishes a
connection to the address specified using the protocol specified.
Note that a connection supporting basic stream connections and record
connections can be established that requires no private protocol
between either tier 1 & 2 or tier 2 & 3.  The web server provides
access control, authentication, and encryption when necessary.

      Transport gateways exist today with the MTPN gateway being the
best example.  MPTN gateways
  o  use non-native protocols
  o  require special configuration such as DNS setup for address
      mapping
  o  are not integrated with web servers (i.e., don't provide
      security, au
  o  connect only like applications to lik...