CASL: Web Service: Administration Guide.
DocumentId:GradSof-CASL-Web-e-AG-22.04.2002-1.0.0

Introduction

Configuration

CASL Web Services framework have just one parameter in common configuration file: name of Web Service config file ;). Why - becouse view of configuration as set of pairs $(name,value)$ is quite limited in usage.

So, CASL Web Services Config file is 'plain' XML file, does not binded to some DTD - DTD-s are extensible and interpretation of Web Service XML Config is the work of application programmer: he receive SDOM node as configuration for servlet.

Format of Web Service configuration file.

It's XML file with main node WebService, which must consists from subnodes of type Service.

i. e.

<?xml version="1.0">
<!-- configuration file for our web service -->
<WebService>
  <Servlet Name="QQQ" Library="libexec/CASL/Web/libQQQ.so" >
    .... (Some XML fragment, passed to servlet 'QQQ' as SDOM node) ...
  </Servlet>
  <Servlet Name="Xxx" Library="libexec/CASL/Web/libXxx.so">
    .... (Some XML fragment, passed to servlet 'Xxx' as SDOM node) ...
  </Servlet>
</WebService>

As you see, Servlet nodes must have 2 attributes: Name and Library. Name, as you know, is a name of servlet, library - location of shared library in which this servlet is implemented.

Configuration of related services

• CORBA: CASL Web service is based on ModCbroker [] framework, so you must include CORBA Service before Web Service in CASL config file and initialize one [CORBA Service] as server. (i. e. ClientOnly property must be setted ti false).

• Session: CASL Web service use Session Service, so it olso must be loaded into CASL before Web Service.

List of changes

1. 29.08.2002 - first english translation.

Bibliography