System and method for an administration server

• US 6,393,477 B1
• Filed: 05/25/2001
• Issued: 05/21/2002
• Est. Priority Date: 08/17/1998
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Streifert, Kurt A., Paxhia, Frank V.
• Primary Examiner(s): Dinh, Dung C.
• Assistant Examiner(s): EDELMAN, BRADLEY E
• Application Number:
  US09/865,946
• Publication Number:
  US 20020065878A1
• Time in Patent Office: 361 Days
• Field of Search: 709/203, 709/219, 709/104, 709/107, 709/223, 709/227
• US Class Current: 709/223
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 9/40 Network security protocols

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

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.