Web Services Strategies


Nov 3, 2013 (3 years and 2 days ago)


Web Services Strategies

Web Services White Paper

January 2004

Prepared by:

Jerry Waese & Ron Thompson


665 Hood Road,

Markham, ON. L3R 4E1

9000 Fax: 905
9009 1

Copyright © 2004
01 CAIL Systems Inc. (CAIL)

All rights reserved.

The information contained in this document is the exclusive property of CAIL This work is
protected under copyright law and international copyright treaties and conventions. No part of
this work may b
e reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording, or by any information storage or retrieval
system, except as expressly permitted in writing by CAIL. All requests should be sent to
ention: VP Business Development, CAIL 665 Hood Road, Markham, ON. L3R 4E1

The information contained in this document is subject to change without notice.


CAIL Web Services Strategies

White Paper



What is Web Services


CAIL Guardian Based W
eb Services (SOAP/AM)


CAIL Web Extensions for Screen Based Programs


CAIL Aggregation of Web Services


Additional Notes about Security




Section 1

What is Web Services

The internet has so many easy to find resources dealing with the subject
, that this section is
provided merely to review the most important features of Web Services.

The Web Services Description Language (WSDL) forms the basis for Web Services. The idea is
that two entities are related in Web Services

a service provider and
a service consumer

this relationship is described in the WSDL. The relationship is conducted through SOAP
messages. Generally the service consumer has a need of information, or need of information
processing, which is described in the WSDL, and the p
rovider has established the ability to
deliver the required service(s). SOAP/AM is Guardian Based software which automates the
development of industry standard SOAP service providers and SOAP service consumers,

The steps involved in providing and consumin
g any Web Service are:


A service provider describes its service using WSDL. This definition usually is published
to a directory of services. The directory could use Universal Description, Discovery, and
Integration (UDDI). Other forms of directories can al
so be used


Typically a service consumer issues one or more queries to the directory to locate a
service and determine how to communicate with that service.


Part of the WSDL provided by the service provider is passed to the service consumer.
This tells th
e service consumer what the requests and responses are for the service


The service consumer uses the WSDL to send a request to the service provider.


The service provider provides the expected response to the service consumer.

All the messages a
re sent using SOAP (originally an acronym for Simple Object Access
Protocol). SOAP essentially provides the envelope for sending the Web Services messages.
SOAP generally is transmitted over HTTP, but other means of connection may be used. HTTP is
the fami
liar connection we all use for the Internet. In fact, it is the pervasiveness of HTTP
connections that have helped drive the adoption of Web Services.

Fig 1a. The basic idea of Web Services involves the exchange of SOAP messages between
providers and co
nsumers of Services over standard HTTP (or HTTPs)


Clear benefits of using Web Services include interoperability guaranteed between all vendors,
and layered architecture support for standard Encryption and Authentication schemes. Typically
the use of stand
ard web servers facilitates the use of HTTP(s) which is the SSL secured version
of HTTP. CAIL introduces other schemes for additional or alternative data transport encryption
layers, such as SSH (with or without authentication), SSL and DES.


Section 2

CAIL Guardian Based Web Services (SOAP/AM)

For the NonStop Community, CAIL provides SOAP/AM so that access to NonStop servers can be
exposed to Web Service consumers.

NonStop Pathway applications can also access data as consumers from remote Web Servic
providers on any platform using SOAP/AM.

The SOAP/AM created providers have direct access to Pathway or named $RECEIVE
servers via IPMs. SOAP/AM Web Service providers are integrated with Guardian security and
TMF. OSS is not required. The facili
ty for creating a NonStop application as SOAP/AM Web
Service consumer is also available from CAIL.

Fig 2a. SOAP/AM is a full featured implementation of Web Service provider and consumer
functionality on NonStop Platforms without the requirement for


Section 3

CAIL Web Extensions for Screen Based Programs

A large proportion of existing NonStop applications have business rules enforced in the screen
applications, some even have application level security, as well as data access restrictions
posed in screen logic sequences. CAIL is actively integrating Web Services with these Screen
Based Programs. The first requirement for this was to repackage all screen communications into
HTML, which is already completed and is shown below.

Figure 3a
. Access to Screen based SCOBOL programs over telnet can be converted
through the CAIL XML Adapter into a format that can be viewed by any Web Browsers on
the internet without downloading any additional controls.

The CAIL XML Adapter is now a released p
roduct. It converts all conversational and block mode
screens into HTML web pages viewable on any browser including IPAQ, and subject to all
standard security (HTTPs). The CAIL XML Adapter actually converts screens to XML documents
and then uses a XSLT st
yle sheet to transform the XML documents into HTML documents.


Section 4

CAIL Aggregation of Web Services

CAIL has extended the web relay and translation process which started with the XML Adapter
into a fully fledged Integration Platform called CAIL

CAIL Studio has been conceived to leverage of NonStop screen applications to create:


Web Services (providers) in the form of CAIL Servlets or .Net based web server


components in new GUI’s in the form of CAIL Servlets or .Net based web

extensions or as stand alone GUI applications on the desktop.


components in new Web Services in the form of CAIL Servlets or .Net based web server

Fig 4a. CAIL Studio Combines Screen logic programs with SOAP/AM services (or Web
rvices from any provider) to create new Web Services for SOAP/AM on NonStop (or any



CAIL Studio has also been conceived to leverage Web Services, particularly SOAP/AM type
NonStop Web Services to create :


Components in New GUI’s in the
form of CAIL Servlets or .Net based web server
extensions or as stand alone GUI applications on the desktop.


Components in new Web Services in the form of CAIL Servlets or .Net based web server

Fig 4b. CAIL Studio Combines Screen logic pro
grams with SOAP/AM services (or Web
Services from any provider) to create new HTML GUI applications for viewing in any kind
of Web Browser by Users.


Section 5

Additional Notes about Security

The CAIL Studio proxy style architecture can provide an op
portunity to increase the secure
access and variety of encryption layers by introducing the CAIL SOAP Proxy Support is provided
for SSH, SSL and DES.

The modularity of the design supports the optional use of Firewalls at each point in the network.


5a. CAIL Web Services Integration includes the SOAP Proxy relay system which
effectively hides the Web Services Provider and permits extra security precautions to be


Section 6


There is a growing need for easy to deploy and mai
ntain Web applications and Web Services that
are natural extensions of well established application software.

CAIL Solutions fill this need with industry standard technology



SOAP and HTML over
HTTP and Secured HTTP.

As a result, you hav

tools to


the data

and process

the information

from Host


both at the screen logic




Pathway servers.

In addition,


Studio provides an authoring system that


application oriented
paradigms so that existi
ng screen apps and SOAP transactions can be blended into new
aggregate SOAP services and new aggregate Web accessible GUI applications.