Browse Prior Art Database

Service to Enable Common Gateway Interface Programs within Tivoli Management Environment Netfinity Based Internet Applications

IP.com Disclosure Number: IPCOM000118771D
Original Publication Date: 1997-Jul-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 4 page(s) / 205K

Publishing Venue

IBM

Related People

Barbieri, S: AUTHOR [+4]

Abstract

Disclosed is a Tivoli Management Environment (TME) Netfinity service to allow industry standard Common Gateway Interface (CGI) programs to operate within the TME environment. The industry standard states that CGI programs accept data from the server from either 1) standard input (stdin), 2) command line arguments, or 3) the environment variable QUERY_STRING. The CGI program performs program logic in response to the input and provides results using Hyper Text Markup Language (HTML) redirected to standard output (stdout).

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

Service to Enable Common Gateway Interface Programs within Tivoli
Management Environment Netfinity Based Internet Applications

      Disclosed is a Tivoli Management Environment (TME) Netfinity
service to allow industry standard Common Gateway Interface (CGI)
programs to operate within the TME environment.  The industry
standard states that CGI programs accept data from the server from
either 1) standard input (stdin), 2) command line arguments, or 3)
the environment variable QUERY_STRING.  The CGI program performs
program logic in response to the input and provides results using
Hyper Text Markup Language (HTML) redirected to standard output
(stdout).

      Within a proprietary environment such as NetFinity, an
application must create a "plug-in" using the NetFinity Application
Programming Interface (API) toolkit in order to be integrated.  While
NetFinity provides HTML-based remote interface, applications wishing
to integrate within the NetFinity environment must use NetFinity's
APIs.

      For existing applications already utilizing CGI programs in an
HTML environment with an HTTP Server, this requires that the
application be rewritten to accept the NetFinity API set for
integration within NetFinity, while maintaining the existing CGI API.

      Integrating existing web functionality into an application
that provides internet enablement to services through a proprietary
toolkit results in one of two choices:
  o  Rewrite each CGI based service to conform to the
      application's internet toolkit
  o  Create a single application service that acts like
      a server calling the existing CGI programs

      The option to rewrite each CGI based service would mean that
the service was only usable by that application and not generically
usable by standard Internet Servers (which typically provide CGI
support).  This option would create two different code bases, each
requiring maintenance and testing.  On the positive side, rewriting
the CGI based services would enable the original CGI service to make
use of new specialty services, provided by the application toolkit,
to increase function.

      The option to create a single application service that acted
like the server would allow the same service to be run in either
environment, Internet server or Netfinity application.  The ability
to have the same code base executing in two different environments
allows for the integration of an application in a more timely
fashion.  The detailed logic behind the reusable Service follows.

      The Figure illustrates how, with a CGI Enabler, an application
can inter-operate within NetFinity or a standard Internet server to
access the same CGI program.  This reusable CGI Enabler service is
provided as a "mapping" layer between NetFinity and the existing CGI
program.

Registration of New Service within Application

      The NetFinity internet toolkit treats the location part of a
Uniform Resource L...