System and method for an administration server

Abstract

An administration server system and method which is capable of managing multiple copies or instances of servers includes an administration server; an administration server instance file; an administration server read-only configuration file for storing configuration directives; an administration server read-write configuration file for storing configuration directives; a services table; a rules list; and a worker thread pool. The administration server starts a main administration thread with any override parameters read from the administration server instance file; builds the rules list from configuration files directives; and for all server attributes in the configuration files, sets up any required threads; connects to a socket specified in the configuration or attributes file, or services table; upon receiving a browser request, passes a socket descriptor to a worker thread; reads the browser request and applies the rules list to the browser request and, upon a first match, selectively processes an applicable rule; returns the output to the browser; closes the connection to the socket; and returns the worker thread to the worker thread pool.

Claims

We claim:

1. Method for operating an administration server, comprising the steps of:

starting said administration server;

reading and parsing an administration server instance file;

starting a main administration thread with any override parameters read from said server instance file;

reading and parsing administration server read-only and read-write configuration files;

building a rules list from configuration files directives;

for all server attributes in said configuration files, setting up any required error, logging and alarm threads; and setting up worker threads;

connecting to a socket specified in configuration files, override parameters from attributes file, or services table;

waiting in an accept loop for a next browser request at said socket;

upon receiving a browser request, passing a socket descriptor to a worker thread;

reading said browser request and applying said rules list to said browser request and, upon a first match, selectively processing an applicable protect, pass, fail, execute or map rule to generate an output;

returning said output to said browser;

closing the connection to said socket; and

returning said worker thread to a worker thread pool.

2. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for operating an administration server, said method steps comprising:

starting said administration server;

reading and parsing an administration server instance file;

starting a main administration thread with any override parameters read from said server instance file;

reading and parsing administration server read-only and read-write configuration files;

building a rules list from configuration files directives;

for all server attributes in said configuration files, setting up any required error, logging and alarm threads; and setting up worker threads;

connecting to a socket specified in configuration files, override parameters from attributes file, or services table;

waiting in an accept loop for a next browser request at said socket;

upon receiving a browser request, passing a socket descriptor to a worker thread;

reading said browser request and applying said rules list to said browser request and, upon a first match, selectively processing an applicable protect, pass, fail, execute or map rule to generate an output;

returning said output to said browser;

closing the connection to said socket; and

returning said worker thread to a worker thread pool.

3. A computer program product or computer program element for operating an administration server according to the steps of:

starting said administration server;

reading and parsing an administration server instance file;

starting a main administration thread with any override parameters read from said server instance file;

reading and parsing administration server read-only and read-write configuration files;

building a rules list from configuration files directives;

for all server attributes in said configuration files, setting up any required error, logging and alarm threads; and setting up worker threads;

connecting to a socket specified in configuration files, override parameters from attributes file, or services table;

waiting in an accept loop for a next browser request at said socket;

upon receiving a browser request, passing a socket descriptor to a worker thread;

reading said browser request and applying said rules list to said browser request and, upon a first match, selectively processing an applicable protect, pass, fail, execute or map rule to generate an output;

returning said output to said browser;

closing the connection to said socket; and

returning said worker thread to a worker thread pool.

4. An administration server system, comprising:

an administration server;

an administration server instance file;

an administration server read-only configuration file for storing configuration directives;

an administration server read-write configuration file for storing configuration directives;

a services table;

a rules list;

a worker thread pool;

said administration server for reading and parsing said administration server instance file; starting a main administration thread with any override parameters read from said administration server instance file; reading and parsing said administration server read-only and read-write configuration files; building said rules list from configuration files directives; for all server attributes in said configuration files, setting up any required error, logging and alarm threads, and setting up worker threads; connecting to a socket specified in said configuration files, override parameters from said attributes file, or said services table; waiting in an accept loop for a next browser request at said socket; upon receiving a browser request, passing a socket descriptor to a worker thread; reading said browser request and applying said rules list to said browser request and, upon a first match, selectively processing an applicable protect, pass, fail, execute or map rule to generate an output; returning said output to said browser; closing the connection to said socket; and returning said worker thread to said worker thread pool.

Description

U.S. patent applications Ser. No. 09/135,149 filed Aug. 17, 1998, entitled "SYSTEM AND METHOD FOR CONFIGURING AND ADMINISTERING MULTIPLE INSTANCES OF WEB SERVERS", and Ser. No. 09/135,253 filed Aug. 17, 1998, entitled "SYSTEM AND METHOD FOR PORTING A MULTITHREADED PROGRAM TO A JOB MODEL", are filed concurrently herewith and assigned to the same assignee. They contain related subject matter incorporated herein by this reference.

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention pertains to configuration and administration of system components using World Wide Web (WWW) technology. In particular, this invention provides a plurality of instances of web server, with one of them being preconfigured for this administration function to allow web browsers to configure web-configurable components.

2. Background Art

The IBM AS/400 system traditionally uses 5250 terminal protocol to configure and administer system components, such as start or stop a server, change functional attributes, authorize users, and so forth. This 5250 terminal protocol requires a 5250 terminal or 5250 emulator that is known as a green screen display. A graphical user interface (GUI) presents to a user a much more user-friendly interface than a green screen display, and there is a need in the art to provide a graphical user interface for system configuration and administration functions.

It is quite common today for any system to have a web server that hosts some site or sites. Such sites provide web content that is made available to web browsers. In general the goals of an enterprise with such a site are typical business goals that pertain to return on investment or customer satisfaction. Typically, such an enterprise has system sites that deal with business applications (such as an electronic shopping mall), or information sites (such as the company's product specifications, or employee benefit plans). These sites share in common the protocols that make web browsing possible. These include use of the HyperText Transfer Protocol (HTTP) and HyperText Markup Language (HTML), a Common Gateway Interface (CGI) that allows system administrators to write dynamic web applications, and the content itself, that is the HTML files, images, java applets, wave (audio) files, or other multimedia resources known to (that is, accessible by) browsers.

Some servers have the ability to manage other servers. However, systems today do not have multiple copies of those servers, and there is a need in the art for an administration server capable of managing multiple copies or instances of servers.

Further, there is a need in the art for an administration Internet connection server (ICS) that is a web (HTTP) server for serving a specialized set of applications that provide for configuration and administration of web enabled system components. These system components can be anything on an enterprise or site system that have an application written for and served by an administration server for the purpose of being configured by a web browser.

However, for security purposes, this administration Internet connection server must not share commonality with other ICS HTTP server(s) serving the web content that is made available by the site system to web browsers. Such an administration server preferably allows a user to configure certain aspects of the server, such as access and error logging, or the ability to run secure HTTP transactions (also referred to as HTTPs). However, this administration server must be controlled with respect to serving its content to browsers irrespective of such configuration by the user.

Further, there exists the need in the art to provide an administration Internet connection server (also referred to as an administration server) which is isolated from and therefore does not detract in any way from other, or "normal", HTTP server(s) at the site, and does not impose any requirements that the system use its "normal" web server(s) for what is considered system administration and configuration. It is particularly important that any changes the site makes to configuration of its "normal" HTTP server(s) (good or bad) cannot affect the configuration of the administration server. Furthermore, it is a requirement that any heavily loaded "normal" web server(s) at a site will not affect performance of the administration server, and conversely, the act of using the administration server, that is configuring and administering some system component, will not have any effect of the performance of other HTTP server(s) at the site.

It is an object of the invention to provide an improved administration server.

It is a further object of the invention to provide an administration server which serves administration and configuration applications to a browser's graphical user interface.

It is a further object of the invention to provide an administration server which serves to a browser capability for administering and configuring web enabled system components.

It is a further object of the invention to provide an improved administration server which is isolated from other servers at the site.

It is a further object of the invention to provide an improved administration server which is isolated from other servers at the site such that loading of either does not adversely impact the other.

It is a further object of the invention to provide an improved administration server which enables the management of multiple copies or instances of servers.

It is a further object of the invention to provide an administration server implemented as a browser.

SUMMARY OF THE INVENTION

In accordance with the invention, a system and a method are provided for serving HTML pages to web browsers for the purpose of administration and configuration. A plurality of instances of WWW servers is provided, with one such instance including a configuration file which is restricted in usage and not alterable by way of any HTML configuration or administration forms.

Other features and advantages of this invention will become apparent from the following detailed description of the presently preferred embodiment of the invention, taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high level system diagram of the administration server of the invention.

FIG. 2 is a high level system diagram illustrating the administration server of the invention as one instance of multiple server instances.

FIG. 3 is a diagrammatic representation of the configuration and server instance forms presented by the administration server of the invention at a graphical user interface.

FIG. 4 is a high level system diagram illustrating the main components of the system of the invention.

FIG. 5 is a flow diagram of the method of the invention.

FIG. 6 is a flow diagram of the *ADMIN site of the preferred embodiment of the invention.

FIG. 7 is a diagram illustrating the AS/400 tasks page.

FIG. 8 is a diagram illustrating the front page, or first page for configuration and administration of ICS in accordance with a preferred embodiment of the invention.

FIG. 9 is a diagram illustrating the general configuration and administration page for adding a new ICS server instance or to manage an existing one in accordance with the preferred embodiment of the invention.

FIG. 10 is a diagram illustrating a server instance page in accordance with the preferred embodiment of the invention.

FIG. 11 is a diagram illustrating a representation of instance parameters in accordance with the preferred embodiment of the invention.

FIG. 12 is a diagram illustrating a representation of configuration and administration in accordance with the preferred embodiment of the invention.

FIG. 13 is a diagram illustrating a basic page.

FIG. 14 is a diagram illustrating a confirmation page.

FIG. 15 is a diagram illustrating secure server instance management files and formats.

FIG. 16 is a diagram illustrating the format of the start server command.

FIG. 17 is a diagram illustrating the format of the end server command.

FIG. 18 is a high level system diagram illustrating server threading.

FIG. 19 is a high level flow diagram illustrating server threading flow.

FIG. 20 illustrates the job structure of the HTTP server of the preferred embodiment of the invention.

BEST MODE FOR CARRYING OUT THE INVENTION

In accordance the preferred embodiment of the invention, an hypertext transfer protocol (HTTP) web server is provided for serving browsers. A web server that supports the industry standard HTTP protocol is given a hardened (e.g., read only) configuration. A task page is provided that provides links to any application that can be configured via a browser. This one task page is served by this administration HTTP server. Upon selecting a link to a configurable application, the selected pages which are also served by the administration HTTP server, are used to complete the configuration task. The user interface throughout this process is the browser.

The pages, and forms contained therein, are accessed by a series of links from the tasks page, and provide the graphical user interface (GUI) for configuring and administering those applications. Examples of such applications include internet connection secure server, firewall, net.data, digital certificate manager, net.commerce and net.question. These become a link off of the tasks page and each provides a series of web pages which are traversed to achieve the desired configuration.

In accordance with the invention, forms are designed and implemented so that an internet connection server can be configured. A configuration file for an Internet connection server is built by selecting and entering values upon these forms. One or more copies or instances of the Internet connection server are provided, and these forms are used to manage these multiple instances. The administration server of this invention enables creation, selection and modification of other server instances by leading an authorized user at a browser through a series of GUI forms to accomplish the change, addition, start, stop, or other action.

For example, a plurality of instances of Internet connection servers (ICSs) exist at a site and need to be managed. A form is presented by the administration server listing this plurality of other servers, and the user selects the instance (that is, the other server) he needs to administer (start, stop, change, add, delete). Upon selecting a server and an action, a page is presented or displayed at the browser by the administration server which will allow further configuration, the content of that page depending upon the action selected.

In accordance with the preferred embodiment of the invention, there is provided an administration server that is accessed via a web browser.

Referring to FIGS. 1 and 2, ADMIN server 310 represents an instance of an HTTP server. In this preferred embodiment, there are provided an instance file 318 with one member and a configuration file with one member pair 314, 316 called ADMIN for installation separate and distinct from another instance 311 and configuration file 317 that are also provided for installation, but for a system administrator's use. A global attributes file 325 is provided. Instance file 317 overrides the contents of the config file(s) 314, 316, which overrides the contents of the attributes file 325. Attributes file 325 is referred to as the global attributes file because there is only one file member, used by all server instances; whereas each instance uses a unique instance file member 318 and a particular configuration (config) file member 314 (except admin server 310, which uses 2 config file members 314, 316).

In accordance with a preferred embodiment of the invention, an Internet connection secure server has a default setup that includes two HTTP server instances 310, 311. One instance is the ADMIN server 310 that is required for configuration and the other is DEFAULT server 311. Default server 311 can be started as-is with all of its default settings 317, 319, 321, 323. The server administrator can customize the default server 311 for his own environment and add additional servers as desired.

Referring to FIG. 2 in connection with FIG. 7, in accordance with a preferred embodiment, ADMIN server 310 serves an AS/400 configuration home page 350 that links to other browser configurable products, such as is represented by link 352. In operation, when the user (that is, the system administrator) points his browser (this is analogous to saying http://as400hostname.domain:2001) to the system administration home page, the browser is presented with a page 350 asking what is to be administered or configured, including a hot link 352 to HTTP server configuration pages, or alternatively a different page showing configuration screens for the other products.

Upon selecting link 352, the user is presented initial page 360. Upon selecting configure HTTP servers 362 on initial page 360, the system administrator is presented a general configuration and administration form 370 (also referred to as the server instance form or instance manager page). The system administrator is in this manner allowed to select either an instance 371 to work with, add a new instance, or change the default attributes that potentially affect all HTTP servers. Additionally, a user may choose the other hotlinks 364, 366, 368 on this initial page 360 to see some sample home pages, some URLs for help, or to return to initial page 350.

Referring to FIG. 3, instance manager page 370 provides various choices for working with an instance 371, including CHANGE 376, DELETE 378, START 380, STOP 382 and RESTART 384. Appropriate messages for these commands are shown after the command has executed. Help text is provided to guide a user through the steps. These selections are then turned into appropriate control commands in the case of START 380, STOP 382 or RESTART 384, or will delete an instance 371 in the instance file 318 if DELETE 378 is selected.

In accordance with a preferred embodiment of the invention, an interface for configuring the AS/400 Secure Web Server includes web pages and CGI scripts and a configuration file validation program. However, the web-based configuration function of the preferred embodiment of the invention does not use a separate validation program. Rather, validation of user entries in the configuration pages 316 is built into the CGI programs. Which CGI program gets invoked depends on which button (Apply, Change, . . . ) is pushed or which link (i.e., Global Attribute Values) is clicked, regardless of the rest of the page content. These CGI programs produce the code set forth in Tables 4-9.

The CGI scripts read current settings from the configuration file and build configuration pages filled in with those settings. CGI scripts are also used to read the values contained in the configuration pages and write those values out to the configuration file. These scripts may be modified to read or write from or to a configuration file 314 or an instance file 318, as appropriate. As will be apparent to those skilled in the art, this is common cgi usage, and need not be further described.

In accordance with a preferred embodiment of the invention, secure server configuration proceeds as follows:

1. The user opens the "Internet Connection Server for AS/400" page.

2. As each general configuration and administration form 370 (FIG. 3, a specific example of which is illustrated in FIG. 9 as form 370) is accessed, the "in" CGI script 391 obtains the appropriate values from the configuration file 316, instance file 318, global attributes file 325 and builds, for example, a page 400 (FIG. 10), which is filled in with those values and displayed to the user at the browser.

3. If the user clicks on the "Apply" button 412 (FIG. 10), an "out" CGI script 391 calls a validation routine. If valid; the configuration directives are written to the instance file 318 and a confirmation page is returned. Otherwise, an error page is returned.

4. If the user clicks on "Reset" button 414 (FIG. 10), the web browser 304 resets the input fields.

Referring to FIG. 4, another view of the main components characterizing the environment of the administration and configuration system *ADMIN 310 of the invention includes system 300 and web browser 304 in communication over a network 302. In accordance with the preferred embodiment of the invention, web browser 304, any industry compliant web browser, is the user interface required to use this *ADMIN server 310. (An alterntive user interface is described hereafter in connection with start TCP server command 540 and end TCP server command 550, FIGS. 16 and 17, respectively.) Web browser 304 communicates through network 302 using HTTP protocols to the Administration (HTTP) Internet Connection Server (ICS) 310, also referred to as *ADMIN server 310.

* ADMIN server 310 is started, and it's functionality is controlled, via administration instance file 318, read-only administration configuration file 314, read-write administration configuration file 316, and global attributes file 325. The system administrator can change configuration file 316 in order to maintain system compatibility; however, read-only administration configuration file 314 contains those parameters which are required to be served by *ADMIN server 310 to browser 304, and cannot be altered by the system administrator. That is, read-only configuration file 314 is hardened: while all directives can be put in read-write configuration file 316, they will not override all of the directives that are in read-only file 314. The contents of file 314 are shown in Table 3. Server 310 provides a Common Gateway Interface (CGI) 308 for the purpose of executing CGI applications 306. These applications 306 are described later.

It is quite common today for any system to have a web server that hosts some site or sites. Such sites provide web content 312 that is made available to web browsers 304, such as information sites (for example, the company's product specifications, or employee benefit plans). These sites share in common the protocols that make web browsing possible, that is the HyperText Transfer Protocol (HTTP) and HyperText Markup Language (HTML), a Common Gateway Interface (CGI) 308 that allows system administrators to write dynamic web applications 306, and content files 312 such as HTML files, images, java applets, wave (audio) files, or other multimedia resources known to browsers.

Administration (HTTP) Internet Connection Server (*ADMIN server) 310 is a web (HTTP) server, however it serves a specialized set of applications 306, namely those that deal with the configuration and administration of web enabled system components. These system components 306 can be anything on the system that has been web enabled. By web enabled is meant that an application 306 has been written and served via the *ADMIN server 310 for the purpose of being configured via a web browser 304.

*ADMIN server 310 is unique (from other servers) in that it does not share any commonality with the System administrator's ICS (HTTP) server(s) 311--that is it is a separate instance of the ICS server, with separate configuration and instance files 316 and 318, and a specific URL (Uniform Resource Locator). *ADMIN server 310 also has a special "read-only" configuration file 314 that is shipped and installed with the *ADMIN server 310 so the operation of the *ADMIN server 310 can be controlled with regards to serving its content, irrespective of what the system administrator may want to configure from browser 304. In accordance with this preferred embodiment, the system administrator is allowed to configure certain aspects of the server such as access and error logging, or the ability to run secure HTTP (HTTPS) transactions.

Read-only configuration file 314 is read by the web server before read-write configuration file 316. There are some directives which affect web serving in such a way that the first directive encountered that covers a particular web activity is the directive that will be used to control that activity. In effect, these directives cannot be overridden. They include Protect, Map, Pass, and Exec. Thus, much of the usage of the server that is controlled by the contents of the read-only file 314 will not be overridden by the contents of the read-write file 316. Instance parameters 318 would override the contents of the read-only file 314, but are limited in number, and are shown in FIG. 11. For example, the contents of the read-only file 314 allows the tasks page to be served, and this behavior cannot be overridden.

Thus, *ADMIN server 310 does not detract in any way from the system administrator's "normal" HTTP server(s) 311, and does not impose any requirements that the system administrator use his "normal" web server(s) 311 for what is considered system administration and configuration. The web-site (content) the system administrator wants to host is separate and distinct from *ADMIN server 310, and any changes the system administrator at browser 304 makes to his "normal" HTTP server(s) 311 configurations 317 (good or bad) cannot affect the configuration 314, 316 of *ADMIN servers 310. Furthermore, any heavily loaded system administrator's "normal" web server(s) 311 will not affect performance of *ADMIN server 310, and conversely, the act of using *ADMIN server 310, that is configuring and administering some system component 306, will not have any effect on the performance of the system administrator's other HTTP server(s) 311.

In order to keep the content of *ADMIN server 310 separate and distinct from the "normal" HTTP server(s) 311, it is necessary to provide a unique URL (Uniform Resource Locator) so browser 304 can access the home page of *ADMIN server 310. There are two different approaches to achieving this unique URL. The first is to provide a unique host address, and the URL would be: http://some_unique_address. However, the system administrator would have to configure this, thereby implying a multi-homed host 300, and obtain a separate IP address which may prove to be difficult. The second approach is to "port qualify" the URL so that instead of using the well known port for HTTP (which is port 80 ), and the well known port for HTTPs (which is port 443), a different port 303, 305 is chosen for each protocol, namely port 2001 for HTTP, and 2010 for HTTPs. Since it is possible to have a conflict with other socket applications, these ports are configurable. The URL for *ADMIN server 310 then becomes http://your_host_name:2001--this is what the system administrator would enter at browser 304 to access the home page 350 (FIG. 7) of *ADMIN server 310.

In accordance with this preferred embodiment, implementation of *ADMIN server 310 includes the following: an industry standard HTTP server 310 that has a CGI interface 308; the ability to have (execute) multiple copies of an HTTP--ICS server,,including *ADMIN server 310 and at least one other server 311; control of this *ADMIN server 310 by means of a configuration file 314, 316, instance file 318 and global attributes file 325; separate and distinct configuration and instance files 317 for the other ICS server(s) 311; a "read-only" configuration file 314 that guarantees operation of the *ADMIN server 310 (this file 314 is shipped by the manufacturer to the customer whose system 301 this is); a "read-write" configuration file 316 giving the system administrator the ability to configure some aspects of *ADMIN server 310; the ability to configure *ADMIN server 310 to bind to ports 303, 305 different than the well known HTTP and HTTPs ports. CGI interface 308 provides connection between the configuration pages and the CGIs.

In operation, referring to FIG. 5, after a start command 320 is received, in step 322 *ADMIN instance file 318 is read and appropriate parameters are passed to the main thread of the program. In step 324, the main thread then reads the configuration files 314, 316, builds a rules list from them, and then connects to the HTTP (and perhaps HTTPs) ports. In steps 326 and 328, the main thread of server 310 listens (waits) on the HTTP port, and the SSL listener thread listens (waits) on the HTTPs port for work to arrive (that is, requests from browser 304), and then passes these requests to a non-busy worker thread 330 from a managed pool of worker threads. Worker thread 330 is so named since it does all the work, reading, parsing and comparing the request against the rules list, and then acting on the rules that are encountered. When processing by worker thread 330 is complete, it returns information of some kind to browser 304, which may be the resource 312 requested, output of a CGI application 306, or an error message.

The threads model used for executing ADMIN server 310 is further described in copending U.S. patent applications Ser. No. 09/135,149, filed Aug. 17, 1998, entitled "SYSTEM AND METHOD FOR CONFIGURING AND ADMINISTERING MULTIPLE INSTANCES OF WEB SERVERS", and Ser. No. 09/135,253, filed Aug. 17, 1998, entitled "SYSTEM AND METHOD FOR PORTING A MULTITHREADED PROGRAM TO A JOB MODEL", the teachings of which are herein incorporated by this reference.

In Table 1, a further elaboration on the operation of of *ADMIN server 310 is set forth in pseudo code. In Table 1, comment lines are preceded by //.

                                      TABLE 1
                                   *ADMIN Server
    1     // pseudo code for Server 310
    2     // error handling is not shown here but is required for
    3     // product level implementations
    4           START TCP SERVER COMMAND 320 RECEIVED INDICATING START
    5           *ADMIN SERVER 310 OR START TCP COMMAND RECEIVED AND
    6           AUTOSTART=*YES
    7           READ AND PARSE *ADMIN SERVER INSTANCE FILE 318
    8           START MAIN *ADMIN THREAD WTTH ANY OVERRIDE PARAMETERS
    9     //main thread processing
    10
    11          SETUP SIGNAL HANDLERS
    12    // useful for such things as realizing the end tcp server
    13    // command has been issued. This way polling is avoided
    14    // for the end command, and the main loop can do real work
    15          READ AND PARSE CONFIGURATION FILES 314, 316
    16          BUILD RULES LIST
    17    // this rules list is what governs the behavior of the
    18    // server
    19          FOR ALL SERVER ATTRIBUTES IN CONFIGURATION FILE 314,
    20          316
    21    // server attributes include such things as number of worker
    22    // threads code pages for translations, access and error
    23    // logging if turned on
    24    // additional listener thread 328 if running HTTPS also
    25          SETUP APPROPRIATE ERROR, LOGGING, ALARM THREADS
    26          SETUP WORKER THREADS 330
    27
    28    // if all goes well, bind to specified socket and wait
    29    // for work
    30    // usually 2001 for *ADMIN HTTP
    31    // usually 2010 for *ADMIN HTTPs (secure HTTP transactions)
    32          CONNECT TO SOCKET SPECIFIED IN CONFIG OR OVERRIDE PARMS
    33          OR SERVICES TABLE
    34          WAIT IN ACCEPT LOOP FOR BROWSER REQUESTS
    35          WHEN REQUEST ARRIVES, PASS THE SOCKET DESCRIPTOR TO A
    36          WORKER THREAD 330
    37          BACK TO WAIT IN ACCEPT LOOP
    38    // a worker thread that is not busy is selected from the
    39    // pool 330 of worker threads.
    40    now worker thread has the socket descriptor
    41
    42          READ HTTP REQUEST FROM SOCKET
    43          APPLY RULES LIST TO HTTP REOUEST
    44          IF A MATCH OCCURS
    45    // there may be more than one, but first match wins
    46                PROCESS RULE WITH "THIS" HTTP REQUEST
    47    // CASE statement as long as number of rules in rules list
    48    // rule is applied to path part of URL
    49                SELECT RULE
    50                CASE: PROTECT
    51                     DETERMINE PROTECTION SETUP SUB-DIRECTIVES
    52                     APPLY SUB-DIRECTIVE POLICIES
    53                     CHECK CREDENTIALS AND AUTHENTICATE USER
    54                     IF USER IS AUTHENTICATED
    55                           CONTINUE PROCESSING THROUGH RULES LIST
    56                     ELSE, SEND BACK AUTHENTICATION FAILURE
    57                CASE: PASS
    58                     LOCATE RESOURCE SPECIFIED IN THE PATH PART OF
    59                     THE URL, GET READY TO SEND RESOURCE
    60
    61                CASE: FAIL
    62
    63                     GENERATE FORBIDDEN BY RULE MESSAGE
    64                CASE: EXEC
    65                     LOCATE PROGRAM TO RUN (IN THE URL)
    66                     PREP ENVIRONMENT BY SETTING UP STDIN,
    67                     ENVIRONMENT VARIABLES AND STDOUT
    68                     RUN PROGRAM
    69                     WHEN PROGRAM RETURNS, DATA IS IN STDOUT
    70                CASE: MAP
    71
    72                     FOR MATCHED ITEM IN TEMPLATE FIELD
    73                     REPLACE MATCHED ITEM WITH REPLACEMENT
    74                     FIELD
    75                CONTINUE PROCESSING THROUGH RULES LIST
    76    // end of processing through rules list, resource requested
    77    // should be buffered and present, therefore get ready to
    78    // send it to the browser
    79    // must be HTTP like before returning data to browser
    80    // that includes things such as choosing correct MIME types,
    81    // counting output bytes, time of day, server response
    82    // headers
    83          APPLY THE CCRRECT HTTP RESPONSE HEADERS
    84          RETURN OUTPUT TO BROWSER
    85          CLOSE THIS CONNECTION
    86    // note, socket options allow the application to close the
    87    // connection without worrying about how much data was sent
    88    // (since this is TCP)
    89          RETURN THIS THREAD 330 TO WORKER THREAD POOL
    90          WAIT FOR MORE WORK
    91
    92    // end of pseudo code for Server 310

                             TABLE 2
                        Instance File 318
    1   // Sample of instance file that drives the admin server 310
    2
    3   -r /QSYS.LIB/QTCP.LIB/QATMHTTPI.FILE/DEFAULT.MBR
    4   -r /QSYS.LIB/QUSRSYS.LIB/QATMHTTPA.FILE/ADMIN.MBR
    5   -AutoStartN

        UserID ANYBODY
        Protection DEF-PROT
            UserID  BUSYBODY
            AuthType Basic
            ServerID restricted
            PasswdFile QUSRSYS1/WWW/restrict
            GroupFile /docs/WWW/restrict.grp
            GetMask authors
        }
        Protect /secret/business/* DEF-PROT
        Protect /topsecret/* {
            AuthType Basic
            ServerID restricted
            PasswdFile QUSRSYS/TOPBRASS
            GroupFile /docs/WWW/restrict.grp
            GetMask topbrass
        }
    Pass        /secret/scoop/*   /WWW/restricted/*
    Pass        /secret/business/* /WWW/confidential/*
    Pass        /topsecret/*      /WWW/topsecret/*

    Protect /secret/* CustomerA-PROT webname
        204.146.167.72
    Protect /secret/* CustomerB-PROT webname 9.67.*
    Protect /topsecret/* webname 204.146.167.72 {
        AuthType Basic
        ServerID restricted
        PasswdFile QUSRSYS/WWW/CUSTOMERA
        GroupFile /docs/WWW/customer-A.grp
        GetMask A-brass
    }
    Protect /topsecret/* webname 9.67.*
        AuthType Basic
        ServerID restricted
        PasswdFile QUSRSYS/WWW/CUSTOMERB
        GroupFile /docs/WWW/customer-B.grp
        GetMask B-brass
    }

        Map     /stuff/*  /customerA/good/stuff/* 204.146.167.72
        Map     /stuff/*  /customerB/good/stuff/* 9.99*

    QDLS:         Pass    /doc/*    /QDLS/WEBTEST/*.HTM
    Root:         Pass    /root/*   /WEBSAMP/*.html
    QOpenSys:     Pass    /x/*      /QOpenSys/WEBSAMP/*.html
    QSYS:         Pass    /lib/*
              /QSYS.LIB/WEBSAMP.LIB/HTMLDOC.FILE/*.MBR

        Pass    /parts/*  /customerA/catalog/* 204.146.167.72
        Pass    /parts/*  /customerB/catalog/* 9.99.*

        /cgi-bin/mycgi         - The request arrives.
        /cgi-bin/mycgi.pgm     - The Map directive adds the .pgm.
        /QSYS.LIB/CGIBIN.LIB/* - The request changes to identify
                                   the path to the program
    (As/400                            library.)

        AddType       .ps application/postscript 8bit        1.0
        AddType       *.* application/binary   binary      0.3

                                     TABLE 3
                             Configuration File 314
    4       #     start sample of configuration file that drives #ADMIN    #
    5       #     server 310                                               #
    6       #     * * * * * * * * * * * * * * * * * * * * * * * * * * *    #
    7       #                                                              #
    8       #     HTTP Administration server configuration                 #
    9       #                                                              #
    10      #     * * * * * * * * * * * * * * * * * * * * * * * * * * *    #
    11      #                                                              #
    12      #     HostName                   your.full.host.name            #
    13      #     The default ports for the adminstration server are set   #
    14      #     in the services table.                                   #
    15      #     #
    16            DirAccess                  Off
    17      #
    18      #     ENABLE start
    19            Enable                     POST
    20            Enable                     GET
    21            Enable                     HEAD
    22      #     ENABLE end                                               #
    23      #                                                              #
    24      #     PROTECTION start - Force authentication and treat as     #
    25      #     AS/400 *USRPRF
    26            Protection      IBMDETP {
    27                AuthType    Basic
    28                ServerID    OS400ADM
    29                Userid      %%CLIENT%%
    30                PasswdFile  %%SYSTEM%%
    31                GetMask     All
    32                PostMask    All
    33                }
    34      #     PROTECTION end                                           #
    35      #                                                              #
    36      #     PROTECT start                                            #
    37            Protect         /QIBM/Firewall/*     IBMDFTP
    38            Protect         /QIBM/NetC/*         IBMDFTP
    39            Protect            /                          IBMDFTP
    40            Protect            /AS400TASKS                IBMDFTP
    41            Protect            /QIBM/OS400/*              IBMDFTP
    42            Protect            /QIBM/ICS/HTML/*           IBMDFTP
    43            Protect            /QSYS.LIB/QSYSCGI.LIB/*    IBMDFTP
    44            Protect            /QSYS.LIB/QTCPCGI.LIB/*    IBMDFTP
    45            Protect            /QIBM/ICSS/Cert/*          IBMDFTP
    46      #     PROTECT end                                              #
    47      #                                                              #
    48      #     MAP start                                                #
    49            Map     /QIBM/Firewall/Admin/*
    50      /QSYS.LIB/QSYSCGI.LIB/DB2WWW.PGM/QIBM
    51                    /ProdData/HTTP/Protect/Firewall/Macro/*
    52            Map     /QIBM/NetC/Admin/QSYS.LIB/QSYSCGI.LIB
    53                    /WEBCONFIG.PGM/loadmlt
    54            Map     /QIBM/NetC/Admin/webconfig/*
    55      /QSYS.LIB/QSYSCGI.LIB/WEBCONFIG.PGM/*
    56      Map           /QIBM/NetworkStation/Admin/QYTC/QYTCMAIN.PGM
    57      Map           /QIBM/ICSS/Cert/Admin/*
    58      /QSYS.LIB/QSYSCGI.LIB/DB2WWW.PGM
    59                    /QIBM/ProdData/HTTP/Protect/ICSS/Cert/Macro/*
    60            Map     /
    61                    /QSYS.LIB/QSYSCGI.LIB/DB2WWW.PGM
    62                    /QIBM/ProdData/HTTP/Protect
    63                    /OS400/Macro/qyunmain.ndm/main0
    64            Map     /AS400TASKS/QSYS.LIB/QSYSCGI.LIB/DB2WWW.PGM
    65                    /QIBM/ProdData/HTTP/Protect/OS400/Macro
    66                    /qyunmain.ndm/main0
    67            Map     /QIBM/ICS/HTML/MRI2924/rzag1mst.html
    68      /QSYS.LIB/QTCPCGI.LIB/QTMHFMIN.PGM/QUICKBGN
    69            Map     /QIBM/ICS/HTML/MRI2924/sample.html
    70      /QSYS.LIB/QTCPCGI.LIB/QTMHFMIN.PGM/SAMPLE
    71            Map     /QIBM/ICS/HTML/MRI2924/icswgmst.html
    72      /QSYS.LJB/QTCPCGI.LIB/QTMHFMIN.PGM/WEBMSTGD
    73      #     MAP end                                                  #
    74      #                                                              #
    75      #     PASS start                                               #
    76            Pass    /QIBM/OS400/*
    77      /QIBM/ProdData/HTTP/Protect/OS400/HTML/*
    78            Pass    /QIBM/Firewall/*
    79      /QIBM/ProdData/HTTP/Protect/Firewall/HTML/*
    80            Pass    /QIBM/NetC/*
    81                    /QIBM/ProdData/HTTP/Protect/NetC/*
    82            Pass    /QIBM/NetworkStation/*
    83      /QIBM/ProdData/HTTP/Protect/Networkstation/*
    84      #
    85      #     Pass statements for misplaced GIF files
    86      #
    87            Pass    /QIBM/ICS/HTML/MRI*/docmast.*
    88                    /QTBM/ProdData/HTTP/Protect/TC1/ICSS
    89                    /HTML/ICONS/docmast.gif
    90            Pass    /QIBM/ICS/HTML/MRI*/ics10s03.*
    91                    /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    92                    /HTML/ICONS/ics10s03.gif
    93            Pass    /QIBM/ICS/HTML/MRI*/ics10s04.*
    94                    /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    95                    /HTML/ICONS/ics10s04.gif
    96            Pass    /QIBM/ICS/HTML/MRI*/ics10s05.*
    97                    /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    98                    /HTML/ICONS/ics10s05.gif
    99            Pass    /QIBM/ICS/HTML/MRI*/ics.10s06.*
    100                   /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    101                   /HTML/ICONS/ics10s06.gif
    102           Pass    /QIBM/ICS/HTML/MRI*/ics10s07.*
    103     /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    104                   /HTML/ICONS/ics10s07.gif
    105           Pass    /QIBM/ICS/HTML/MRI*/ics10s08.*
    106     /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    107                   /HTML/ICONS/ics10s08.gif
    108           Pass    /QIBM/ICS/HTML/MRI*/ics10s14.*
    109                   /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    110                   /HTML/ICONS/ics10s14.gif
    111           Pass    /QIBM/ICS/HTML/MRI*/ICFICON.*
    112     /QIBM/ProdData/HTTP/Protect/TC1/ICSS
    113                  /HTML/ICONS/icficon.gif
    114     #
    115     #
    116           Pass    /QIBM/ICS/HTML/*
    117     /QIBM/ProdData/HTTP/Protect/TC1/ICSS/HTML/*
    118           Pass    /QIBM/ProdData/HTTP/Public/*
    119           Pass    /QIBM/ICSS/Cert/Download/*
    120     /QIBM/UserData/ICSS/Cert/Download/*
    121           Pass    /QIBM/ICSS/Cert/*
    122     /QIBM/ProdData/HTTP/Protect/ICSS/Cert/HTML/*
    123     #     PASS end                                                 #
    124     #                                                              #
    125     #     EXEC start                                               #
    126           Exec    /QSYS.LIB/QSYSCGI.LIB/*
    127           Exec    /QSYS.LIB/QTCPCGI.LIB/*
    128           Exec    /QYTC/* /QSYS.LIB/QYTC.LIB/*
    129     #     EXEC end                                                 #
    130     #                                                              #
    131     #     AddType start                                            #
    132           AddType .cacrt         application/x-x509-ca-cert 7bit 1.0
    133           AddType .usrcrt        application/x-x509-user-cert 7bit 1.0
    134           AddType .CACRT         application/x-x509-ca-cert 7bit 1.0
    135           AddType .USRCRT        application/x-x509-user-cert 7bit 1.0
    136     #     AddType end                                              #
    137     #     * * * * * * * * * * * * * * * * * * * * * * * * * * * *  #
    138     #     end Sample of configuration file that drives the admin
    139     #     server

                             TABLE 4
                      Tasks Page 150 (HTML)
    1     <HTML>
    2     <HEAD>
    3     <TITLE>AS/400 Tasks</TITLE>
    4     <P>
    5     <SCRIPT LANGUAGE="JavaScript">
    6     <!--
    7     function showHelpFunction( ) {
    8     window.open("/QSYS.LIB/QSYSCGI.LIB/DB2WWW.PGM/
          QIBM/ProdData/
    9     HTTP/Protect/OS400/Macro/qyunmain.ndm/help0","",
    10    "width=600,height=400,menubar=yes,scrollbars=yes,resizable=y
    11    es,status")
    12    //-->
    13    </SCRIPT>
    14    </HEAD>
    15    <BODY BGCOLOR="#FFFFFF">
    16    <CENTER>
    17    <TABLE WIDTH=80%>
    18    <TR>
    19    <TD>
    20    <FONT SIZE=5>
    21    <STRONG>
    22    <IMG SRC="/QIBM/QS400/Icons/ibmlogo.gif" ALIGN=LEFT
    23    ALT="IBM">
    24    </STRONG>
    25    </FONT>
    26    </td>
    27    <TD rowspan=2>
    28    <CENTER>
    29    <FONT SIZE=6>
    30    <STRONG>AS/400 Tasks
    31    </STRONG>
    32    </FONT>
    33    </CENTER>
    34    </TD>
    35    <TD ALIGN=CENTER>
    36    <IMG SRC="/QIBM/OS400/Icons/as400.gif" ALT="">
    37    </TD>
    38    </TR>
    39    <TR>
    40    <td>
    41    <FONT Size=1>(C) IBM Corporation 1997
    42    </FONT>
    43    </TD>
    44    <td>
    45    <center>
    46    <FoNT Size=2>RS008.ENDICOTT.IBM.COM
    47    </FONT>
    48    </center>
    49    </td>
    50    </TR>
    51    <TR>
    52    <TD colspan=3>
    53    <HR size=1>
    54    </td>
    55    </TR>
    56    <TR>
    57    <td colspan=3>
    58    <p>
    59    <BR>
    60
    61    <CENTER>
    62    <TABLE>
    63    <TR>
    64    <TD>
    65    <A HREF="/QSYS.LTB/QTCPCGI.LIB/QTMHICFP.PGM">
    66    <IMG SRC="/QIBM/ICS/HTML/ICONS/anchgrap.gif"
          border="0"
    67    ALT="* ">
    68    </A>
    69    </TD>
    70    <TD>
    71    <A HREF="/QSYS.LIB/QTCPCGI.LIB/QTMHICFP.PGM">
    72    <STRONG>Internet Connection Server for AS/400
    73    </STRONG>
    74    </A>
    75    <BR>
    76    <FONT SIZE=2>Configure the AS/400 HTTP Server and SSL
    77    </FONT>
    78    </TD>
    79    </TR>
    80    <TR>
    81    <TD>
    82    <A HREF="/QIBM/Firewall/Admin/qisafwl.ndm/main0">
    83    <IMG SRC="/QIBM/Firewall/Icons/qisafwl.gif" border="0"
    84    ALT="*">
    85    </A>
    86    </TD>
    87    <TD>
    88    <A HREF="/QIBM/Firewall/Admin/qisafwl.ndm/main0">
    89    <STRONG>IBM Firewall for AS/400
    90    </STRONG>
    91    </A>
    92    <BR>
    93    <FONT SIZE=2>Set up and monitor an Internet Firewall
    94    </FONT>
    95    </TD>
    96    </TR>
    97    <TR>
    98    <TD>
    99    <A HREF="/QIBM/NetC/Admin">
    100   <IMG SRC="/QIBM/NetC/Server/Icons/netcomm.gif" border="0"
    101   ALT="*">
    102   </A>
    103   </TD>
    104   <TD>
    105   <A HREF="/QIBM/NetC/Admin">
    106   <STRONG>IBM Net.Commerce for AS/400
    107   </STRONG>
    108   </A>
    109   <BR>
    110   <FONT SIZE=2>Configure the Net.Commerce Server
    111   </FONT>
    112   </TD>
    113   </TR>
    114   <TR>
    115   <TD>
    116   <A HREF="/QIBM/ICSS/Cert/Admin/qycucml.ndm/main0">
    117   <IMG SRC="/QIBM/ICSS/Cert/Icons/qycucml.gif" border="0"
    118   ALT="* ">
    119   </A>
    120   </TD>
    121   <TD>
    122   <A HREF="/QIBM/ICSS/Cert/Admin/qycucml.ndm/main0"
    123   <STRONG>Digital Certificate Manager
    124   </STRONG>
    125   </A>
    126   <BR>
    127   <FONT SIZE=2>Create, distribute, and manage Digital
    128   Certificates
    129   </FONT>
    130   </TD>
    131   </TR>
    132   </TABLE>
    133   </CENTER>
    124   <P><BR>
    135   </td>
    136   </TR>
    137   <TR>
    138   <td>
    139   <A
    140   href="http://www.as400.ibm.com/anchor/MRI2924/
          anchhome.htm">
    141   <font size="-1">Related task information
    142   </font>
    143   </a>
    144   </td>
    145   <td>
    146   </td>
    147   <td>
    148   <center>
    149   <a href="Javascript:showHelpFunction () ">
    150   <img src="/QIBM/OS400/Icons/help.gif" border="0" alt="">
    151   <BR>Help
    152   </a>
    153   <BR>
    154   <font size="-2">(Requires JavaScript)
    155   </font>
    156   </center>
    157   </td>
    158   </TR>
    159   </TABLE>
    160   </center>
    161   </BODY>
    162   </HTML>

                             TABLE 5
                        Front Page (HTML)
    1     ##Sample HTML representation of First Page of ICS
    2     ##configuration and Administration
    3     <html>
    4     <head>
    5     <title>Internet Connection Secure Server for
     AS/400</title>
    6
    7     </head>
    8     <frameset COLS="25,75">
    9     <frame SRC="/QIBM/ICS/HTML/MRI2924/ICSNAV.HTML"
    10    NAME="ICSNavFrame">
    11    <frameset ROWS="78, 22">
    12    <frame SRC="/QIBM/ICS/HTML/MRI2924/ICSSLOGO.HTML"
    13    NAME="ICSLogoFrame">
    14    <frame SRC="/QIBM/ICS/HTML/MRI2924/ICSBUTN.HTML"
    15    NAME="ICSButtonsFrame">
    16    </frameset>
    17    </frameset>
    18    <form NAME="icsframe" ACTION="" METHOD="POST">
    19    <center>
    20    </form>
    21    </center>
    22    </body>
    23    </html>

                                     TABLE 6
                 General Configuration and Administration (HTML)
    1     // Sample HTML representation of "Configuration and
    2     // Administration"
    3     <html>
    4     <head>
    5     <title>General Configuration and Administration</title>
    6     </head>
    7     <img src="/QIBM/ICS/HTML/ICONS/skycfg2.gif" align="middle"
    8     alt="">
    9     <strong>Configuration and Administration
    10    </strong>
    11    <p><hr>
    12    <body>
    13    <br>
    14    <hl>General Configuration and Administration</hl>
    15    <hr>Choose an existing server instance and an action to
    16    perform on it.
    17    <br>
    18    <form ACTION="/QSYS.LIB/QTCPCGI.LIB/QTMHFMOU.PGM/instact"
    19    METHOD="POST">
    20    <INPUT TYPE=RADIO NAME="INSTANCE" VALUE="ADMIN"> ADMIN
    21    <BR>
    22    <INPUT TYPE=RADIO NAME="INSTANCE" VALUE="DEFAULT">DEFAULT
    23    <BR>
    24    <input type="submit" name="pushbutton" value="Change">
    25    <input type="submit" name="pushbutton" value="Delete">
    26    <input type="submit" name="pushbutton" value="Start">
    27    <input type="submit" name="pushbutton" value="Stop">
    28    <input type="submit" name="pushbutton" value="Restart">
    29    </form>
    30    <hr>To generate a new server instance, specify an instance
    31    name and select the "Add" button..
    32    <br>
    33    <form ACTION="/QSYS.LIB/QTCPCGI.LIB/QTMHFMOU.PGM/instact"
    34    METHOD="POST">
    35    Instance name <input TYPE="text" NAME="instance" SIZE=10
    36    MAXLENGTH=10> <input type="submit" name="pushbutton"
    37    value="Add">
    38    </form>
    39    <hr>Change the
    40    <aHREF="/QSYS.LIB/QTCPCGI.LIB/QTMHFMIN.PGM/glblattr">
    41    Global Attribute Values</a>.
    42    <pre>
    43    <hr>
    44    <a href="/QSYS.LIB/QTCPCGI.LTB/QTMHICFP.PGM"><img
    45    align=middle src="/QIBM/ICS/HTML/ICONS/go2first.gif"
    46    alt="Front Page .vertline. "></a> <a
    47    href="/QIBM/ICS/HTML/MRI2924/HLPAS4IM.HTML"><img
    48    align=middle src="/QIBM/ICS/HTML/ICONS/skyhelp.gif"
    49    alt="Help"></a>
    50    </pre>
    51    </body>
    52    </html>

                                     TABLE 7
                               Link CHANGE (HTML)
    1         // Sample HTML representation of link "CHANGE"
    2         <html>
    3         <head>
    4         <title>Server Instance "DEFAULT "</title>
    5         </head>
    6         <img src="/QIBM/ICS/HTML/ICONS/skycfg2.gif" align="middle"
    7         alt=""> <strong>Configuration and
     Administration</strong>
    8         <p><hr>
    9         <body>
    10        <br>
    11        <hl>Server Instance "TEAM42 "</h1>
    12        <hr>
    13        <form ACTION="/QSYS.LIB/QTCPCGI.LIB/QTMHFMOU.PGN/assccfg"
    14        METHOD="POST">
    15        <h2>Associated Configuration</h2>
    16        This server instance uses the configuration named
    17        <strong>CONFIG</strong>. To use a different one,
    18        you choose the name of an existing configuration, specify
    19        the name of a new configuration, or do both. Then, choose
    20        the action you want to take.
    21        <p>
    22        <pre>
    23        Existing configuration
    24        <select NAME="assccfg"> <OPTION SELECTED>CONFIG
    25        <OPTION>CONFIG_BK <OPTION>CONFIGSAVE
    26        </select>
    27        New configuration
    28        <input TYPE="text" NAME="newcfg" maxlength=10 SIZE=10>
    29        </pre>
    30        <input TYPE=RADIO NAME="action" VALUE="1" Checked>
    31        Use existing configuration <br>
    32        <input TYPE=RADIO NAME="action" VALUE="2">
    33        Create new configuration <br>
    34        <input TYPE=RADIO NAME="action" VALUE="3">
    35        Create new configuration based on existing one
    36        <pre>
    37        <input type="submit" name="pushbutton" value="Apply">
    38        <input name="pushbutton" type="reset" value="Reset">
    39        </pre>
    40        <hr>
    41        <a HREF="/QSYS.LIB/QTCPCGI.LIB/QTMHFMIN.PGM/cfgact=CONFIG
    42        ">
    43        <h2>Configuration and Administration Forms</h2>
    44        </a>
    45        Change the configuration named
    46        <strong>CONFIG </strong>.
    47        <hr>
    48        <a HREF="/QSYS.LIB/QTCPCGI.LIB/QTMHFMIN.PGM/instparm=DEFAULT
    49
    50        ">
    51        <h2>Instance Parameters</h2>
    52        </a>
    53        Specify parameter values to be used by server instance
    54        <strong>DEFAULT </strong>.
    55        <INPUT TYPE=HIDDEN NAME="INSTANCE" VALUE="DEFAULT ">
    56        <pre>
    57        <hr>
    58        <a href="/QSYS.LIB/QTCPCGI.LIB/QTMHICFP.PGM"><img
    59        align=middle src="/QIBM/ICS/HTML/ICONS/go2first.gif"
    60        alt="Front Page .vertline."></a>  <a
    61        href="/QIBM/ICS/HTML/MRI2924/HLPAS4CF.HTML"><img
    62        align=middle src="/QIBM/ICS/HTML/ICONS/skyhelp.gif"
    63        alt="Help"></a>
    64        </pre>
    65        </form>
    66        </body>
    67        </html>

                                     TABLE 8
                           Instance Parameters (HTML)
    1       // Sample HTML Representation of link "INSTANCE PARAMETERS"
    2       <html>
    3       <head>
    4       <title>Instance Parameters</title>
    5       </head>
    6       <img src="/QIBM/ICS/HTML/ICONS/skycfg2.gif" align="middle"
    7       alt=""><strong>Configuration and
     Administration</strong>
    8       <p><hr>
    9       <body>
    10      <br>
    11      <h1>Instance Parameters</h1>
    12      Server instance: <STRONG>TEAM42</STRONG>
    13      <hr>
    14      <form
    15      ACTION="/QSYS.LIB/QTCPCGI.LIB/QTMHFNOU.PGM/instparm=DEFAULT"
    16      METHOD="POST">
    17      Specify parameter values to be used by this server instance.
    18      <p>
    19      <pre>
    20      Autostart
    21      <select NAME="auto"><option>NO <OPTION>YES
     <OPTION
    22      SELECTED>*GLOBAL </SELECT>
    23      Number of server jobs:
    24      Minimum
    25      <input TYPE="text"
    26                NAME="min"
    27                VALUE= "*CFG"
    28                maxlength=4
    29                SIZE=4>
    30      Maximum
    31      <input TYPE="text"
    32                NAME= "max"
    33                VALUE="*CFG"
    34                maxlength=6
    35                SIZE=6>
    36      Coded character set identifier
    37      <input TYPE="text"
    38                NAME="ccsid"
    39                VALUE-"*GLOBAL"
    40                maxlength=7
    41                SIZE=7>
    42      Server mapping tables:
    43      Outgoing EBCDIC/ASCII table
    44      <input TYPE="text"
    45                NAME="outtbl"
    46                VALUE="*GLOBAL"
    47                maxlength=10
    48                SIZE=19>
    49      Library
    50      <input TYPE="text"
    51                NAME="outlib"
    52                VALUE=""
    53                maxlength=10
    54                SIZE=10>
    55      Incoming ASCII/EBCDIC table
    56      <input TYPE="text"
    57                NAME="intbl"
    58                VALUE="*GLOBAL"
    59                maxlength=10
    60                SIZE=10>
    61      Library
    62      <input TYPE="text"
    63                NAME="inlib"
    64                VALUE=""
    65                maxlength=10
    66                SIZE=10>
    67      ACCESS log file name
    68      <input TYPE="text"
    69                NAME="accfil"
    70                VALUE="*CFG"
    71                max length=512
    72                SIZE=50>
    73      ERROR log file name
    74      <input TYPE="text"
    75                NAME="errfil"
    76                VALUE="*CFG"
    77                maxlength=512
    78                SIZE=50>
    79      Non-secure port
    80      <input TYPE="text"
    81                NAME="prt"
    82                VALUE="*CFG"
    83                maxlength=5 SIZE=5>
    84      Secure port
    85      <input TYPE="text"
    86                NAME="secprt"
    87                VALUE="*CFG"
    88                maxlength=5
    89                SIZE=5>
    90      </pre>
    91      <pre>
    92      <input type="submit" name="pushbutton" value="Apply">
    93      <input type="reset" name="pushbutton" value="Reset">
    94      <hr>
    95      <a href="/QSYS.LIB/QTCPCGI.LIB/QTMHICFP.PGM">
    96      <img align=middle src="/QIBM/ICS/HTML/ICONS/go2first.gif"
    97      alt="Front Page .vertline.">
    98      </a>
    99      <a href="/QTBM/ICS/HTML/MRI2924/HLPAS4JN.HTML">
    100     <img align=middle src="/QIBM/ICS/HTML/ICONS/skyhelp.gif"
    101     alt="Help">
    102     </a>
    103     </pre>
    104     </form>
    105     </body>
    106     </html>

                                     TABLE 9
                     Configuration and Administration (HTML)
    1         // Sample representation of link "Configuration and
    2         // Administration Forms"
    3         <html>
    4         <head>
    5         <title>Configuration and Administration Forms</title>
    6         </head>
    7         <body>
    8         <img src="/QIBM/ICS/HTML/ICONS/skycfg2.gif" align="middle"
    9         alt="">
    10        <strong>Configuration and Administration</strong>
    11        <p><hr>
    12        <hl>Configuration and Administration Forms</h1>
    13        Configuration: <strong>TEAM42</strong>
    14        <p>
    15        <hr>
    16        You can customize this server configuration by modifying the
    17        forms below:
    18        <p>
    19        <ul>
    20        <li>
    21        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/basic=CONFIG">
    22        Basic
    23        </a> - Specify required settings
    24        <li>
    25        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/useradm=CONFIG">
    26        User Administration </a>
    27                - Manage user ID and passwords
    28        <ul>
    29        <li>
    30        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/adduser=CONFIG">
    31                Add User </a>
    32                - Add a new user ID to a validation list and group file
    33        <li>
    34        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/deluser=CONFIG">
    35                Delete User </a>
    36                Delete a user from a validation list
    37        <li>
    38        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/chkuser=CQNFIG">
    39                Check User</a>
    40                - Determine if a user exists in a validation list
    41        <li>
    42
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/chpasswd=CONFIG">
    43                Change Password</a>
    44                - Change a user password in a validation list
    45        </ul>
    46        <li>
    47        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/dirappr=CONFIG">
    48        Directories and Welcome Page</a>
    49                - Set viewing options
    50        <ul>
    51        <li>
    52
     <ahref="/QSYS.LIB/QTCPCGT.LIB/QTMHCFIN.PGM/initpage=CONFIG">
    53                Initial Page</a>
    54                - Specify welcome pages and directory lists
    55        <li>
    56
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/listcnts=CONFIG">
    57                Directory List Contents</a>
    58                - Specify list columns
    59        <li>
    60
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/dirreadm=CONFIG">
    61                Readme Text</a>
    62                - Provide informative directory list text
    63        </ul>
    64
     <li><ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHLRIN.PGM/logging=CONFI
    65        G">
    66        Logging</a>
    67                - Customize access log and error log
    68        <ul>
    69        <li>
    70
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHLRIN.PGM/logfiles=CONFIG">
    71                Global Log File Configuration Settings</a>
    72                - Specify log formats
    73        <li>
    74        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHLRIN.PGM/accconf=CONFIG">
    75                Access Log File Configuration</a>
    76                - Specify access log location
    77        <li>
    78        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHLRIN.PGM/errconf=CONFIG">
    79                Error Log File Configuration</a>
    80                - Specify error log location
    81        </ul>
    82        <li>
    83        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/access=CONFIG">
    84                Access Control</a>
    85                - Set up access control for the server:
    86        <ul>
    87        <li>
    88
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/docautos=CONFIG">
    89                Document Protection</a>
    90                - Specify file directories to protect
    91        <li>
    92
     <ahret="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/prtclist=CONFIG">
    93                Protection Setups</a>
    94                - Specify file protection settings
    95        <li>
    96        <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/acldir=CONFIG">
    97                Access Control Lists</a>
    98                - Define user access files
    99        </ul>
    100       <li>
    101
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHSCIN.PGM/security=CONFIG">
    102               Security</a>
    103               - Set up security for the server:
    104       <ul>
    105       <li>
    106       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHSCIN.PGM/secconf=CONFIG">
    107               Security Configuration</a>
    108               - Define basic parameters for security
    109       <li>
    110       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHSCIN.PGM/key=CONFIG">
    111               Create Keys</a>
    112               - Create keys and request certificates
    113       <li>
    114       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHSCIN.PGM/reccert=CONFIG">
    115               Receive Certificate</a>
    116               - Receive a certificate into the key ring
    117       <li>
    118
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHSCIN.PGM/pwprompt=CONFIG">
    119               Key Management</a>
    120               - Work with keys, root keys, and certificates
    121       </ul>
    122       <li>
    123       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/resmap=CONFIG">
    124               Resource Mapping</a>
    125               - Redirect URLs and define file extensions
    126       <ul>
    127       <li>
    128       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/mpfrule=CONFIG">
    129               Request Routing</a>
    130               - Route URL requests to server files
    131       <li>
    132
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/addencod=CONFIG">
    133               MIME Encodings</a>
    134               - Define encodings and extensions
    135       <li>
    136       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/addtype=CONFIG">
    137               MIME Types</a>
    138               - Define file types and extensions
    139       <li>
    140       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/addlang=CONFIG">
    141               Languages</a>
    142               - Associate language encodings and extensions
    143       <ul>
    144       <li>
    145       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/timeout=CONFIG">
    146       TimeCuts</a>
    147               - Close connections automaticaliy
    148       <li>
    149
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/methenab=CONFIG">
    150       Methods</a>
    151               - Set method acceptance
    152       <li>
    153       <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/accscr=CONFIG">
    154       Accessory Scripts</a>
    155               - Specify custom method scripts
    156       <li>Performance Settings</a>- Define performance
     settings:
    157       <ul>
    158       <li>
    159
     <ahref="/QSYS.LIB/QTCPCGI.LIB/QTMHCFIN.PGM/performa=CONFIG">
    160               Jobs</a>
    161               - Configure jobs
    162       </ul>
    163       </ul>
    164       <hr>
    165       <a hret="/QSYS.LIB/QTCPCGI.LIB/QTMHICFP.PGM">
    166       <img src="/QIBM/ICS/HTML/ICONS/go2first.gif"
    167       alt="Front Page .vertline."></a>
    168       <img src="/QIBM/ICS/HTML/ICONS/greycfg.gif"
    169       alt="Configuration and Administration Forms .vertline.">
    170       <a href="/QIBM/ICS/HTML/MRI2924/sample.html">
    171       <img src="/QIBM/ICS/HTML/ICONS/skyhome.gif"
    172       alt="Sample Home Page .vertline."></a>
    173       <a href="http://www.ics.raleigh.ibm.com/">
    174       <img src="/QIBM/ICS/HTML/ICONS/skyres.gif"
    175       alt="Resource List .vertline."></a>
    176       <a href="/QIBM/ICS/HTML/MRI2924/rzaglmst.html">
    177       <img src="/QIBM/TCS/HTML/ICONS/skydoc.gif"
    178       alt="Documentation"></a>
    179       </body>
    180       </html>

    STRTCPSVR field 542: STRTCPSVR
    SERVER( ) field 544:
     SERVER(.vertline.*ALL.parallel.*SNMP.vertline.*ROUTD.vertline.*TELNET.vert
    line.
     *FTP.vertline.*SMTP.vertline.*LPD.vertline.*WSG.vertline.*POP.vertline.*HT
    TP.vertline. . . .
                         .vertline.)
    RESTART field 546:   RESTART(.vertline.*NONE.vertline.*HTTP.vertline.)
    HTTPSVR( ) field 548: HTTPSVR(.vertline.*ALL.parallel.server-instance-name
     .vertline.*ADMIN.parallel.*NONE.vertline.instance-startup-
                         values.vertline.)

    ENDTCPSVR field 552:   ENDTCPSVR
    SERVER( ) field 554:
     SERVER(.vertline.*SNMP.vertline.*ROUTED.vertline.*TELNET.vertline.
     *FTP.vertline.*SMTP.vertline.*LPD.vertline.*HTTP.vertline.*WSG
                           *POP.vertline. . . . .vertline.*ALL.vertline.
    HTTPSVR( ) field 556:  HTTPSVR(.vertline.*ALL.vertline.SERVER-INSTANCE-
                           NAME.vertline.*ADM.vertline.N.vertline.)