The socket2bod application

1. Introduction
2. Requirements
3. How to obtain the software
4. The SOCKET Software Modules

1. Introduction

The socket2bod.jar forms the link between the Bodington VLE and SOCKET. In the Full Monty deployment involving the console and UDDI registry, Bodington obtains a list of available SOCKET resources from a class in socket2bod.jar which in turn interrogates the console using a remote HTTP interface.

To demonstrate a socketized Bodington with access to a fixed set of resources, the socket2bod Java application can be used to generate a socket2bod.jar with a fixed, user-defined list of SOCKET resources.

2. Requirements

tbi

3. How to obtain the software

The source code can be downloaded in a zip file from the downloads page of the SOCKET web site.

4. How to install the software

Unzip the socket2bod.zip file. There is a build

5. How to edit the socket2bod source code

tbi

6. How to create the socket2bod.jar

tbi

7. How to deploy the socket2bod.jar in Bodington

The socket2bod.jar should be placed in the lib directory of the deployed Bodington VLE. The application has to be re-started in order for the new socket2bod.jar to be detected.

(Note that with the Full Monty SOCKET deployment with the UDDI registry and the console, no re-start is required because the socket2bod.jar does not change as new resources become available. It obtains a list of SOCKET services using a remote HTTP interface with the SOCKET console.)

SOCKET, A JISC ELF Toolkit Project

b.p.clark@leeds.ac.uk, August 2006

Document last modified 23 September 2006