Browse Prior Art Database

JEPN for distributed environment test automation

IP.com Disclosure Number: IPCOM000022385D
Original Publication Date: 2004-Mar-12
Included in the Prior Art Database: 2004-Mar-12
Document File: 4 page(s) / 90K

Publishing Venue

IBM

Abstract

JEPN (Java End Point Network) is an xml based tool for distributed environment test automation. The architecture is composed of a light java end point to install on each cpu and capable to execute only four basic actions: 1) Command execution and output sending, 2) File download, 3) File upload and 4) File customization. The end points can be commanded in a centralized way, first defining cpus and tasks in an xml text file, than using a java gui or a command line capable to open the file and to launch the defined tasks on a cpu or on a group of cpus. The xml commands are sent to remote cpus and their command outputs and exit values are collected and sent back to user.

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 53% of the total text.

Page 1 of 4

JEPN for distributed environment test automation

Distributed test environment requires a lot of time and effort
for disk space checking, application installing, cpu
configuring and above all distributed application tests
performing. The most famous tool to solve this problems is
STAF. It is very powerfull, it is a complex job executing and
monitor system, requires a STAF administrator to manage
services and a great effort to learn how to use it.
Tipically testers have no time to increase their STAF skill,
no time to manage a complex distributed test system, but have
great UNIX skill and a lot of test scenarios to do!!!
A faster and less expensive solution is required, testers want
to launch in an immediate way a set of commands and want to
see the command outputs immediatly and as they are generated
on the machine (not a representation of it).

    JEPN is an xml based tool for distributed environment test
automation.
The network cpus and their tasks can be defined in an xml
centralized file. The xml file virtualizes all the network
resources and all the network functionalities.
Two different type of task can be defined: Cpu-Task and
Global-Task.

    The first type is the implementation for a single cpu of
a generic task, it can be launched only on the cpu on wich is
defined simply calling it by its external name.
The Cpu-Task has an external name and an implementation that
can call one of the following four actions:
1) Command execution and output sending (the command specified
is local and os dependent)
2) File download
3) File upload
4) File customization

    The second type is the Global-Task. It defines a sequence
of task external name to call and a list of cpu that have to
execute them.

    The end points can be commanded in a centralized way,
first defining tasks in an xml text file, than using a java
gui or a command line capable to open the file and to launch
the defined tasks.

Here an example of cpu and Cpu-Task implementation:

      < cpu name = "lab151047_...