Web Connection User's Guide
To access a VisualAge Web Connection application, the client Web browser
sends an HTTP request. A user can generate such a request in any of
three ways:
- Directly specifying the Uniform Resource Locator (URL) for the servlet or
CGI program
- Selecting a link in an HTML document that specifies the URL for the
servlet or CGI program
- Selecting the "submit" button on an HTML fill-out form that specifies
the servlet or CGI program as the action to take
In any case, the request sent by the Web browser takes the form of a URL
containing the HTTP request and any data that goes along with it. The
complete URL to a VisualAge Web Connection application takes on various forms,
depending on the interface used.
For the Servlet interface, the URL is in the following form:
http://server/servletPath/servletName/VisualAgePartName
for example:
http://MyServer/servlets/com.ibm.abt.web.servlet.Router/myClass
where the parts of the URL are as follows:
- server
- The TCP/IP host name, and optionally the port, of the HTTP server.
- servletPath
- The path defined as the directory for servlets on the server
machine. This path is defined when you install a Web Server that
supports servlets, such as the IBM WebSphere Application Server.
- servletName
- The name of the servlet used to interface with the Web server. Web
Connection ships with the servlet
com.ibm.abt.web.servlet.Router.
- VisualAgePartName
- The name of the VisualAge part to open in response to this request.
Note: | Under WebSphere, the URL format example is:
http://MyServer/servlet/Router/myClass
|
For the Server Smalltalk interface, the URL is in the following
form:
server:port/AbtWebConnect/VisualAgePartName
for example:
MyServer:1332/AbtWebConnect/myClass
where the parts of the URL are as follows:
- server:port
- The TCP/IP host name and port of the HTTP server.
- AbtWebConnect
- The name of a class included with Server Smalltalk, needed to use Server
Smalltalk as a Web server with Web Connection.
- VisualAgePartName
- The name of the VisualAge part to open in response to this request.
For CGI, the URL is of the following form:
http://server/cgiPath/cgiName/VisualAgePartName
for example:
http://MyServer/cgi-bin/abtwsac.exe/MyClass
where the parts of the URL are as follows:
- server
- The TCP/IP host name, and optionally the port, of the HTTP server.
- cgiPath
- The path defined as the directory for CGI executables on the server
machine (typically cgi-bin).
- cgiName
- The name of the Web Server Interface CGI executable on the server (usually
abtwsac.exe or abtwsac).
- VisualAgePartName
- The name of the VisualAge part to open in response to this request.
For IBM ICAPI and Netscape NSAPI, the URL is of the following
form:
http://server/wsiMapping/VisualAgePartName
for example:
http://MyServer/abtwsi/MyClass
where the parts of the URL are as follows:
- server
- The TCP/IP host name, and optionally port, of the HTTP server.
- wsiMapping
- The mapping defined on the server machine for the WSI interfaces
(typically abtwsi).
- VisualAgePartName
- The name of the VisualAge part to open in response to this request.
For Microsoft ISAPI, the URL is of the following form:
http://server/cgipath/dllName/VisualAgePartName
for example:
http://MyServer/cgi-bin/abtwsi/MyClass
where the parts of the URL are as follows:
- server
- The TCP/IP host name, and optionally port, of the HTTP server.
- cgipath
- The path defined as the directory for CGI executables on the server
machine (typically cgi-bin).
- dllName
- The name of the Web Server Interface DLL on the server
(abtwsam.dll).
- VisualAgePartName
- The name of the VisualAge part to open in response to this request.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]