Browse Prior Art Database

Remote Service Loader Disclosure Number: IPCOM000168262D
Original Publication Date: 2008-Mar-04
Included in the Prior Art Database: 2008-Mar-04
Document File: 5 page(s) / 38K

Publishing Venue



A software approach that one may rely on for installing, loading and/or updating the modules (components) of Geographically Distributed Software.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 5

Remote Service Loader

1.0. Approach for Installing, Loading or Updating Modules of
Geographically Distributed Software

The article discloses a software approach that one may rely on
for installing, loading and/or updating the modules (components)
of Geographically Distributed Software (GDS). A prototype has
been implemented to prove the applicability of the particular
concept of installing, loading and/or updating the modules in GDS
in the field of Automated Software Quality Assurance, where
geographically-distributed software-test-frameworks are
developed. This article presents the use-case, design and
implementation of the particular prototype in details.

1.1. Automated Software Quality Assurance

Automated software quality assurance has been widely adopted in
the Software Development Industry. A wide range of technologies
and frameworks are being used in the particular field for
developing automated test infrastructures, and the Software
Testing Automation Framework (STAF*) is one of the frontrunners.
The STAF is designed as a collection of software modules, which
are referred to as services. The STAF services are designed to
provide enhancements to the original framework, which are loaded
to the framework by a component referred to as the STAF Service
Loader. There is a STAF Service Loader that comes with the
framework by default. However, the particular Service Loader is
only capable of loading services installed on the host machine
and therefore, causes the following usability concerns towards
the field of automated software quality assurance.


Page 2 of 5

1.2. Use case

In the STAF paradigm, an automated test infrastructure is
typically implemented as a collection of services. The particular
services composing an automated test infrastructure must be
manually installed on all the hardware and virtual resources used
in the automation setup, which are referred to as automation
units throughout the document from here for simplicity. The
corresponding automation related services are often updated or
enhanced during their lifecycle, and such an updated or enhanced
service must be manually reinstalled on all the associated
automation units. This particular approach has been proven to be
extremely user unfriendly and also to cause a considerable
overhead from the maintenance perspective. The prototype Web
Server Service Loader
has been implemented to demonstrate how to
address the corresponding usability concerns caused by the
default STAF Service Loader.

1.3. Web Server Service Loader

The Web Server Service Loader provides STAF with the ability of
loading services installed on the web servers. As a result of
this enhanced functionality, the automated test framework
developers are no longer requ...