webtransactions v7.0 web frontend for web services and...

WebTransactions V7.0

Web Frontend for Web Services and Business Objects

Edition: June 2005

Copyright © Fujitsu Siemens Computers GmbH, 2005.All rights reserved. Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

This manual was produced bycognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

http://www.cognitas.de


Contents1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Product characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Architecture of the web frontend for web services and business objects . . . . . . . . . . . . 71.3 WebTransactions documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 Structure and target group of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.5 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Concept of the web frontend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Creating a base directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Creating a base directory with WebLab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Structure of a base directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.1 java subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.2 wsdl subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 Generating templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.1 BizTransactions with Java integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.2 BizTransactions with SOAP integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.3 General web services with SOAP integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Testing the web frontend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.1 Testing the web frontend for business objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.1.1 Prerequisites for Java business objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265.1.2 Prerequisites for business objects as web services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.1.3 General start template for business objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.1.4 Web frontends for business objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.2 Testing the web frontend for general web services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.2.1 General start template for web services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.2.2 Web frontend for a web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6 Editing templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356.1 Accessing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.1.1 Integration via Java (BizTransactions business objects) . . . . . . . . . . . . . . . . . . . . . . . . . 366.1.2 Integration via SOAP (BizTransactions business objects and web services) . . . . . . . . . 396.1.3 Example of a simple data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.1.4 Example of a complex data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


Contents

6.2 Master templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.3 Generated templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.3.1 Business object integration via Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466.3.2 Business object integration via SOAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556.3.3 Using general web services via SOAP integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

7 Communication sharing of Java business objects and WebTransactions . . . . . . . . 737.1 Defining Java business object properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747.2 Calling Java business objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757.3 Defining the communication mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767.4 Example for a host application with communication sharing . . . . . . . . . . . . . . . . . . . . . 77

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Web Frontend for Web Services and Business Objects 5

1 PrefaceOver the past few years, more and more IT users have found themselves working in heterogeneous system and application environments, with mainframes standing next to UNIX and Windows systems and PCs operating alongside terminals. Different hardware, operating systems, networks, databases and applications are operated in parallel. Highly complex, powerful applications are found on mainframe systems, as well as on UNIX and Windows servers. Most of these have been developed with considerable investment and generally represent central business processes which cannot be replaced by new software without a certain amount of thought.

The ability to integrate existing heterogeneous applications in a uniform, transparent IT concept is a key requirement for modern information technology. Flexibility, investment protection, and openness to new technologies are thus of crucial importance.

1.1 Product characteristics

With WebTransactions, Fujitsu Siemens Computers offers a best-of-breed web integration server which will make a wide range of business applications ready for use with browsers and portals in the shortest possible time. WebTransactions enables rapid, cost-effective access via standard PCs and mobile devices such as tablet PCs, PDAs (Personal Digital Assistant) and mobile phones.

WebTransactions covers all the factors typically involved in web integration projects. These factors range from the automatic preparation of legacy interfaces, the graphic preparation and matching of workflows and right through to the comprehensive frontend integration of multiple applications. WebTransactions provides a highly scaleable runtime environment and an easy-to-use graphic development environment.

6 Web Frontend for Web Services and Business Objects

Product characteristics Preface

On the first integration level, you can use WebTransactions to integrate and link the following applications and content directly to the Web so that they can be easily accessed by users in the internet and intranet:

– Dialog applications in BS2000/OSD– UNIX applications– AS400 applications– MVS or z/OS applications– System-wide transaction applications based on openUTM – Dynamic web content

Users access the host application in the internet or intranet using a web browser of their choice.

Thanks to the use of state-of-the-art technology, WebTransactions provides a second integration level which allows you to replace or extend the typically alphanumeric user inter-faces of the existing host application with an attractive graphical user interface and also permits functional extensions to the host application without the need for any intervention on the host (dialog reengineering).

On a third integration level, you can use the uniform browser interface to link different host applications together. For instance, you can link any number of previously heterogeneous host applications (e.g. MVS or OSD applications) with each other or combine them with dynamic Web contents. The source that originally provided the data is now invisible to the user.

In addition, you can extend the performance range and functionality of the WebTransactions application through dedicated clients. For this purpose, WebTransactions offers an open protocol and special interfaces (APIs).

Furthermore, the object-oriented access to OSD, MVS and. openUTM host applications via business objects – previously provided in the BizTransactions supply unit – is now also inte-grated in WebTransactions. For more detailed information on business objects (BOs) and the BizTransactions functionality, see the “Application Integration with Business Objects” manu-al.

Host applications and dynamic Web content can be accessed not only via WebTransactions but also by “ordinary” terminals or clients. This allows for the step-by-step connection of a host application to the Web, while taking account of the wishes and requirements of different user groups.


Preface Architecture of the web frontend

1.2 Architecture of the web frontend for web services and business objects

The figure below shows the architecture of the web frontend for web services and business objects:

Figure 1: Architecture of the web frontend for web services and business objects

WebTransactions uses this web frontend for web services and business objects to access general web services and business objects.

Browser

frontend

Java BO

BO as web service

Web service

Generated template

WSDLfile

Javaarchive

Kernelwith

Java

SOAP

SOAP

WebTransactionsw

eb s

erve

r

WT_SOAP

WT_JAVA


WebTransactions documentation Preface

1.3 WebTransactions documentation

The WebTransactions documentation consists of the following documents:

● An introductory manual which applies to all supply units:

Concepts and Functions

This manual describes the key concepts behind WebTransactions:

– The various possible uses of WebTransactions.

– The concept behind WebTransactions and the meanings of the objects in WebTransactions, their main characteristics and methods, their interaction and life cycle.

– The dynamic runtime of a WebTransactions application.

– The administration of WebTransactions.

– The WebLab development environment.

● A Reference Manual which also applies to all supply units and which describes the WebTransactions template language WTML. This manual describes the following:

Template Language

After an overview of WTML, information is provided about:

– The lexical components used in WTML.

– The class-independent global functions, e.g. escape() or eval().

– The integrated classes and methods, e.g. array or Boolean classes.

– The WTML tags which contain functions specific to WebTransactions.

– The WTScript statements that you can use in the WTScript areas.

– The class templates which you can use to automatically evaluate objects of the same type.

– The master templates used by WebTransactions as templates to ensure a uniform layout.

– A description of Java integration, showing how you can instantiate your own Java classes in WebTransactions and a description of user exits, which you can use to integrate your own C/C++ functions.


Preface WebTransactions documentation

– The ready-to-use user exits shipped together with WebTransaction.

– The XML conversion for the portable representation of data used for communication with external applications via XML messages and the conversion of WTScript data structures into XML documents.

● A User Guide for each type of host adapter with special information about the type of data source:

Connection to AS400 applications

Connection to openUTM applications via UPIC

Connection to OSD applications

Connection to MVS applications

Connection to UNIX applications

All the host adapter guides contain a comprehensive example session. The manuals describe:

– The installation of WebTransactions with each type of host adapter.

– The setup and starting of a WebTransactions application.

– The conversion templates for the dynamic conversion of formats on the web browser interface.

– The editing of templates.

– The control of communications between WebTransactions and the host applications via various system object attributes.

– The handling of asynchronous messages and the print functions of WebTransactions.

● A User Guide that applies to all the supply units and describes the possibilities of the HTTP host adapter:

Access to Dynamic Web Contents

This manual describes:

– How you can use WebTransactions to access a HTTP server and use its resources.

– The integration of SOAP (Simple Object Access Protocol) protocols in WebTransactions and the connection of web services via SOAP.


WebTransactions documentation Preface

● A User Guide valid for all the supply units which describes the open protocol, and the interfaces for the client development for WebTransactions:

Client APIs for WebTransactions

This manual describes:

– The concept of the client-server interface in WebTransactions.

– The WT_RPC class and the WT_REMOTE interface. An object of the WT_RPC class represents a connection to a remote WebTransactions application which is run on the server side via the WT_REMOTE interface.

– The Java package com.siemens.webta for communication with WebTransactions supplied with the product.

● A User Guide which describes the BizTransactions components:

Application Integration With Business Objects

This manual describes the concept behind BizTransactions together with its mode of op-eration and its components. It explains all the steps involved in creating business ob-jects and web services.

The manual is intended for all users who want to create business objects for accessing host applications in order to:

– develop graphical user interfaces for host applications (e.g. via GUIs created using WebTransactions, Visual Basic, Visual C++, Microfocus NetExpress or Java).

– provide the host application as a web service, for example in the internet.

– integrate interactions with host applications in Microsoft Office products (e.g. the current data of an openUTM mainframe application in Excel tables).


Structure and target group of this manual

1.4 Structure and target group of this manual

This manual is intended for anyone who wishes to integrate business objects and general web services in WebTransactions, and describes the procedures involved in detail.

It is designed to supplement the introductory WebTransactions manual “Concepts and Func-tions” and the reference guide “Template Language” to provide all the information you need in order to integrate business objects and general web services in WebTransactions.

Scope of the manual

The web frontend for web services and business objects runs on Solaris, Linux, Windows and BS2000/OSD. The information provided in this manual applies for all of these system platforms, unless indicated otherwise.

1.5 Notational conventions

The following notational conventions are used in this documentation:

typewriter font Fixed components which are input or output in precisely this form, such as keywords, URLs, file names

italic font Variable components which you must replace with real speci-fications; also used for menu items

bold font Items shown exactly as displayed on your screen or on the graphical user interface; also used for menu items

[ ] Optional specifications; do not enter the square brackets them-selves

{alternative1 | alternative2 } Alternative specifications. You must select one of the expres-sions inside the braces. The individual expressions are sepa-rated from one another by a vertical bar. Do not enter the brac-es (curly brackets) and vertical bars themselves.

... Optional repetition or multiple repetition of the preceding com-ponents

Important notes and further information

Ê Prompt telling you to do something.

i

Eine Dokuschablone von Frank Flacheneckerby f.f. 1992


2 Concept of the web frontendWorking with WebTransactions you can incorporate in your WebTransactions application any Java object via the WT_JAVA interface and any web service via the WT_SOAP interface. The Java interface is described in the WebTransactions manual “Template Language”. Informa-tion on integrating the SOAP protocol in WebTransactions is provided in the WebTransactions manual “Access to Dynamic Web Contents”.

In addition to the functions of the WT_SOAP and WT_JAVA interfaces WebTransactions offers a basic interface, or web frontend, for the following cases:

● Integration of Java business objects created with BizTransactions

● Integration of business objects created as web services with BizTransactions

The SOAP protocol is stateless. Therefore operations must not be bound to a certain object, but they have to be kept independent of the instance, just like class methods. To obtain this, select the Method value for the business object property Connection when creating the business object (see BizTransactions manual „Application Integration with Business Objects“).

● Integration of web services which are freely available in the WWW

The web frontend is implemented in a template, that you can generate with WebLab. It con-trols the display on the browser and the communication with the web service and the Java business object. WebLab requires for the generation of this template a description file in WSDL format ( Web Service Description Language), that describes the operations of the web service and the methods of the Java business object. For Java business objects you receive the WSDL file by selecting the Web Service and WSDL file option when generating the object.

Via the web frontend you can provide users with the functionality of the web service and the business object. Alternatively you profit from it by obtaining an overview of their functionality, and adapting the generated template to suit your needs.

i


Concept of the web frontend

Figure 2: Flowchart for the web frontend

At runtime, WebTransactions uses the template to generate an HTML page for the browser, as well as a WT_JAVA object for each of the Java components or an instance of the WT_SOAP class for web services. It then uses these objects to communicate with the relevant compo-nents. It is possible for you to influence the communication process and to subsequently edit the template to suit your needs.

To connect a component to WebTransactions via a web frontend, proceed as follows:

Ê Using WebLab, create a base directory.

Ê Create or supply the WSDL file.

Ê Generate the template for the web frontend.

Ê Run the template.

Ê Edit the template to suit your needs.

These steps are described in the following chapters.

Browser

frontend

Java BO

BO as web service

Web service

WSDLfile

Javaarchive

Kernelwith

Java

SOAP

SOAP

WebTransactions

web

ser

ver

WT_SOAP

WT_JAVA

Generated template


3 Creating a base directoryOnce you have installed WebTransactions on the WebTransactions server and WebLab on your Windows PC, you can use WebLab to create one or more base directories. A base directory includes all the files which configure WebTransactions for a specific application scenario.

If you de-install WebTransactions or install a new product version, the individual configura-tions are therefore retained.

3.1 Creating a base directory with WebLab

Before you can create a base directory for a WebTransactions application, the WebTransactions administrator must have created a user ID for you and then subsequently released one or more pools for this user ID in which you can create a base directory.

Before you create a base directory, it is recommended that you first create a project to store most important data required by WebLab when working with the WebTransactions applica-tion. When creating a project, you are automatically offered the opportunity to create a base directory.

To do this, proceed as follows:

Ê Call WebLab, e.g. via Start/Programs/WebTransactions 7.0/WebLab

Ê There are two possibilities for starting to create a base directory:

Ê Select the Project/New... command and when asked whether you want to create a base directory, answer Yes .

or

Ê Choose the Generate/Basedir... command and specify that a new project is to be created when the relevant query appears.

In both instances, the Connect dialog box is opened.

Ê In the Connect dialog box, enter the connection parameters and confirm with OK.

Ê In the next dialog box, enter your user ID and password and click OK.


Structure of a base directory Creating a base directory

Ê In the Create Basedir dialog box, make the following entries:– Select the directory under which your base directory is to be created.– Enter a name for the new base directory.– In the openSEAS area, check the openSEAS support box.– Click OK.

Structure and contents of a base directory are described in the WebTransactions manual “Concepts and Functions” and in section “Structure of a base directory” on page 16.

Converting a base directory to a new version

Ê Select Generate/Update Base Directory. This opens the Update Base Directory dialog box.

Ê If you only want to change the links from the base directory to the new installation directory, select the Update all links option. Select this option when you have updated the files that are supplied or generated by WebTransactions.

Ê If all files which are copied or generated on creation of the base directory need to be recreated, select the Overwrite all files option.

3.2 Structure of a base directory

This section only describes the specifics of the base directory of the web frontend for web services and business objects.

For general information on the structure of base directories see WebTransactions manual “Concepts and Functions”.

3.2.1 java subdirectory

This subdirectory is created not with the base directory, but when you use Java business objects. The Jar archives of the Java business objects used, as well as the Jar archives re-quired by these business objects at runtime are stored in java.

3.2.2 wsdl subdirectory

This subdirectory is created not with the base directory, but when you use web services. The WSDL files of the web services used, which are required by WebTransactions at runtime are stored in wsdl.

i


4 Generating templatesOnce you have created a base directory for business objects or web services or you are connected to such a base directory, you can use WebLab to generate a template with the following commands:

– Generate/Templates/for Business Objects ...

– Generate/Templates/for WebServices ...

With these commands you can generate templates for integrating business objects and general web services in WebTransactions.

To generate the required templates, you also need the following:

– a description file (WSDL file)

– the corresponding master template

WSDL file

In the course of the generation process, you specify one or more description files, known as WSDL files (WebService Description Language). Each WSDL file will contain a descrip-tion of precisely one component. If you specify several WSDL files, a template will be gen-erated for each of the associated components. WSDL files can be stored locally on your own system or under the base directory.

The WSDL file for a business object is generated using BizTransactions. Most web services are already described in WSDL, which means that a WSDL file for the respective service will be readily available on the web.


Generating templates

Master templates

A template is generated for each WSDL file on the basis of a special master template:

These master templates are stored in the subdirectory weblab under the WebLab installa-tion directory, and can be customized to suit your needs. The master template tags are de-scribed in the WebTransactions manual “Template Language”.

Figure 3: Generating templates for openSEAS or web services

The templates generated on the basis of WSDL files and a master template have pre-defined names:

– wtOpenSEAS_componentname.htm for templates generated for business objects (BOs)

– wtWebService_componentname.htm for templates generated for general web services

where componentname is dependent on the name of the WSDL file. They are stored in the base directory under config/forms, unless specified otherwise. If you wish to use another target directory, this must be located under basedir/config.

The generated templates can then be used as is or as the basis for more sophisticated vi-sual layouts.

Java business objects JAVA_BO.wmt

business objects as web service WSDL.wmt

web services WSDL.wmt

Generated templatesfor openSEAS or

Master template

WSDL files

web services


Generating templates BizTransactions with Java integration

4.1 BizTransactions with Java integration

Before generating a template, make sure that the following files are available:

– the WSDL file

– the master template JAVA_BO.wmt

– the Java business object (generated as a Java bean)

The business object must be available in the form of a Java package in a JAR archive con-taining all user-defined classes (i.e. non-standard classes).

Procedure

To generate a template for Java business objects, proceed as follows:

Ê In WebLab, choose Generate/Templates/for Business Objects to open the Create Templates for Business Objects dialog box.


BizTransactions with Java integration Generating templates

Ê At the bottom of the dialog box, click the JAVA radio button next to Integration via to display the Java options.

Ê Specify the directory containing the WSDL files to be used as the basis for generating the template, either by entering the directory path directly or by clicking Browse and making the appropriate selection. The WSDL documents for Generation list will then display all files in the specified directory.

Ê In WSDL documents for Generation, select the WSDL files to be used as the basis for generating the template.

Ê Check that the master template is set correctly (JAVA_BO.wmt).

Ê In WTML Directory, enter the subdirectory under the base directory in which the gen-erated template is to be stored.

Ê Enter the absolute path name of the JAR archive directly, or click Browse and make the appropriate selection.

Ê Enter a package name for the business object.

Ê In Object name, specify a unique name for the business object.

Ê Click Generate to generate a template for integrating the Java business object in accor-dance with your specifications. In the process, the subdirectory java will be created un-der the base directory and the specified JAR archive will be copied to this subdirectory.


Generating templates BizTransactions with SOAP integration

4.2 BizTransactions with SOAP integration


– the WSDL file

– the master template WSDL.wmt

Procedure

To generate a template for business objects for which you have generated a web service, proceed as follows:

Ê In WebLab, choose Generate/Templates/for Business Objects to open the Create Templates for Business Objects dialog box.



Ê Check that the master template is set correctly (WSDL.wmt).


BizTransactions with SOAP integration Generating templates


Ê Click the SOAP radio button next to Integration via.

Ê Click Generate to generate a template for integrating the business object in accordance with your specifications. In the process, the subdirectory wsdl will be created under the base directory and the specified WSDL file will be copied to this subdirectory.


Generating templates General web services with SOAP integration

4.3 General web services with SOAP integration


– the WSDL file

– the master template WSDL.wmt

Procedure

To generate a template for web services, proceed as follows:

Ê In WebLab, choose Generate/Templates/for WebServices to open the Create Templates for WebServices dialog box.



Ê Check that the master template is set correctly (WSDL.wmt).



General web services with SOAP integration Generating templates

Ê Click Generate to generate a template for integrating the web service in accordance with your specifications. In the process, the subdirectory wsdl will be created under the base directory and the specified WSDL file will be copied to this subdirectory.


5 Testing the web frontendOnce you have generated the templates for integrating a business object or a web service, you are ready to test the web frontend. The generated templates can be used as is and form a modifiable web frontend.

This chapter covers the following topics for both business objects and web services:

– the prerequisites for use– the general start template– the web frontend

5.1 Testing the web frontend for business objects

When it comes to testing the various business objects, different prerequisites and flow-charts apply. These are described below.


Testing the web frontend for business objects Testing the web frontend

5.1.1 Prerequisites for Java business objects

Once you have generated the template for integrating a Java business object, make sure the java subdirectory under the base directory contains the Jar archive for the business ob-ject.

If the BizTransactions Object Builder is not installed on the computer on which WebLab is running, the archive bizta.jar must also be copied into the java subdirectory. You find these file on the WebTransactions server in the following directory:

C:\Programme\Gemeinsame Dateien\FujitsuSiemensComputers\BizTransactions70\bin

This Jar archive contains special classes for the business object, which will be accessed by WebTransactions at runtime.

The flowchart for a Java business object frontend can thus be represented as follows:

Figure 4: Flowchart for testing a Java business object

Browser

frontend Java business

Generated template

Kernelwith

WebTransactions

web

ser

ver

WT_JAVA

Java archives

object


Testing the web frontend Testing the web frontend for business objects

5.1.2 Prerequisites for business objects as web services

The SOAP protocol is stateless. Therefore operations must not be bound to a cer-tain object, but they have to be kept independent of the instance, just like class methods. To obtain this, select the Method value for the business object property Connection when creating the business object (see BizTransactions manual “Appli-cation Integration with Business Objects”).

Once you have generated the template for integrating a business object, make sure the wsdl subdirectory contains the WSDL file for the business object. This file must also be checked to ensure that the web service’s URL is entered correctly.

Ê In WebLab, connect to the base directory by selecting File/Connect.

Ê In the template tree, double-click on the WSDL file to open it for editing.

Ê Check if you can access the web service’s destination URL from the web. This URL is the value of the location attribute of the soap:address tag under the service port sec-tion of the WSDL file.

Example:

<service name="TravelBo"><port name="TravelBoWSIFPort" binding="tns:TravelBoWSIFBinding">

<soap:address xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"location="http://localhost:8080/TravelBo/TravelBo"/>

</port></service>

Ê If necessary replace localhost by the name of the host on which the web service is running.

Ê Save and then close the WSDL file.

The flowchart of a frontend for a business object used as web service can thus be repre-sented as follows:

i



Figure 5: Flowchart for testing a business object as web service

Browser

frontend Business object

Generated template

Kernelwith

WebTransactions

web

ser

ver

WT_SOAP

listener

WSDL file



5.1.3 General start template for business objects

Ê In WebLab, open a session by selecting File/Start Session.

Ê In the Start Session dialog box, enter the required data on the WebTransactions host and the base directory.

Ê Set the start template to wtstart and confirm with OK. The start template will then be displayed in the predefined browser.

Ê Click openSEAS. This opens the start template for openSEAS components in the browser.

The openSEAS component list will include all templates

– whose names begin with wtOpenSEAS_

– which are located in the directory defined by the system object’s STYLE and LANGUAGE attributes

Ê Choose an openSEAS component and confirm with access openSEAS.



5.1.4 Web frontends for business objects

Each business object is represented by a WebTransactions template. The interface itself is designed with the help of the WTBean wtcTabs. It includes a tab sheet for the respective object, which is named after the object in question. Here you can define general settings, such as the proxy settings for integration via SOAP or the dynamic extension of the JAVA_CLASSPATH for integration via Java. Each method also has its own tab sheet contain-ing the following information:

– the output or return value– the last parameters entered– the prescribed input parameters

A method is called by clicking the execute button.

Web frontend for BizTransactions via Java

Figure 6: Tab sheet containing the methods of the Java business object



Web frontend for BizTransactions via SOAP

Figure 7: Tab sheet containing the methods of the business object used as web service


Testing the web frontend for general web services Testing the web frontend

5.2 Testing the web frontend for general web services

Once you have generated the template for integrating a web service, make sure the wsdl subdirectory contains the WSDL file for the web service. If the web service is modified in some way since the generation of the template, it is recommended that you regenerate the template with the new WSDL file.

The flowchart for a web service frontend can thus be represented as follows:

Figure 8: Flowchart for testing a web service

Browser

frontend web service

Kernelwith

WebTransactions

web

ser

ver

WT_SOAP

Generated template

WSDL file


Testing the web frontend Testing the web frontend for general web services

5.2.1 General start template for web services

To start a web service frontend, proceed as follows:

Ê In WebLab, open a session by selecting File/Start Session.

Ê In the Start Session dialog box, enter the required data on the WebTransactions host and the base directory.

Ê Set the start template to wtstart and confirm with OK. The start template will then be displayed in the predefined browser.

Ê Click WebService. This opens the start template for the web service in the browser.

The web service access list will include all templates

– whose names begin with wtWebService_

– which are located in the directory defined by the system object’s STYLE and LANGUAGE attributes

Ê Choose a web service and confirm with access Webservice.


Testing the web frontend for general web services Testing the web frontend

5.2.2 Web frontend for a web service

A web service is represented by a WebTransactions template. The interface itself is designed with the help of the WTBean wtcTabs. It includes a tab sheet for the web service, which is named after the web service in question. Here you can define general settings, such as the proxy settings for integration via SOAP. Each method also has its own tab sheet containing the following information:

– the output or return value– the last parameters entered– the prescribed input parameters

A method is called by clicking the execute button.

Figure 9: Tab sheet containing the web service BabelFish method


6 Editing templatesAs a template programmer, you can feel free to edit the generated templates in WebLab, e.g. in order to make the resulting interface more attractive to the eye.

When working with WebLab, WebTransactions offers a considerable degree of support, par-ticularly when it comes to things like using objects to transfer parameters, for example. For this purpose, WebTransactions generates an object for each structure used. Once the tem-plate is run, these objects are created and displayed in the WebLab object tree, from where they can be easily incorporated in the code using the normal WebLab utilities.

This chapter contains information on the following:

– accessing objects– enhancing the layout of the generated interfaces– master templates

At the end of the chapter, you will find a commented listing of the generated templates.


Accessing objects Editing templates

6.1 Accessing objects

BizTransactions integrations in WebTransactions are implemented using WebTransactions ob-jects.

6.1.1 Integration via Java (BizTransactions business objects)

In the case of integration via Java each BizTransactions business object is mapped to a WT_JAVA object.

WT_JAVA class

The WT_JAVA class is built into the WebTransactions kernel. With the WT_JAVA class objects of any JAVA class can be created in WTScript. Its methods and attributes can be accessed directly at the Java object.

Representation of a BizTransactions business object by a WT_JAVA object

For each business object a java object is created in WT_Script by means of the WT_JAVA class. This object gets the name Java_serial_number. The methods of the business object are called directly at these objects. For the web frontend, a method call including all the nec-essary parameters is generated at these objects for each method of the business object.

Example:

Calling the method GetAllGolfCourses_jb()

Java_0.GetAllGolfCourses_jb();


Editing templates Accessing objects

Mapping Java data types to WTScript data types

The table below shows how WTScript data types are mapped to Java data types in the pa-rameters of the generated method calls.

WTScript type Conversion to Java type

Boolean objects Boolean

String objects Default: java.lang.String

If the string consists of only one character, an attempt will also be made to convert this to type char.

Number objects Default: double

If the object cannot be converted to the default type, an attempt will be made to convert it to all other nu-meric types until a suitable conversion is found, provided the conversion does not result in a loss of accuracy.

Java objects Default: Type used when creating the object

If the object cannot be converted to the default type, an attempt will be made to convert it to all superclass-es and implemented interfaces until a suitable con-version is found.

Java primitives Default: Corresponding primitive Java type

If the object cannot be converted to the default type, an attempt will be made to convert it to all types for which the object value is valid until a suitable conver-sion is found. char values are not handled as numeric values.

Other WTScript objects Not permitted as arguments



Objects for complex data types

If a method uses complex data structures as parameters, these will be supported as follows when the web frontend is generated:

– An object of the WT_JAVA class is automatically created for each complex parameter used when the constructor calls are generated. In the process, WebTransactions assumes that all complex data types used correspond to objects available in the Java archives.

– The generation of constructor calls is initiated by the master template tag %%ObjectCreate%. Pregenerated Java objects can be used in the template as is or adapted to suit your needs.

The name of a pregenerated Java object consists of:

– the name of the method used

– the structure name

– possibly a serial number, if the structure is used more than once within the method call

For examples of how objects are used in the generated templates, see section “Generated templates” on page 45.



6.1.2 Integration via SOAP (BizTransactions business objects and web services)

In the case of integration via SOAP, each web service or business object (BO) is mapped to a WT_SOAP object when generating the web frontend.

WT_SOAP class

The WT_ SOAP class is implemented in the template wtSOAP.htm and provides an access to web services via the SOAP protocol:

An instance of this class represents a web service which must be described in a WSDL file. WT_SOAP analyzes the WSDL file and provides the operations of a web service as methods (proxy methods) of the WT_SOAP class.

You will find a detailed description of the WT_SOAP class and corresponding methods in the WebTransactions manual “Access to Dynamic Web Contents”.

Representation of a web service by a WT_SOAP object

A web service is represented by an object of the WT_SOAP class. For each web service or each business object which you want to access as web service an instance of the WT_SOAP class is created. This instance is labeled WSDL_serial_number.

Calling web service operations and business object methods

It is possible to call proxy methods at a WT_SOAP object. In WebLab, a method call is inserted simply by dragging it from the object tree into the actual template.

As the SOAP protocol is stateless, operations must be kept independent of objects, just like class methods. This must be taken into consideration when designing busi-ness objects that are to be made available as web services.

i



Mapping SOAP data types to WTScript data types

During generation, a method call including all the necessary parameters is generated for each web service operation. The table below shows how the parameter data types are mapped:

SOAP data type WTScript data type

string string

boolean boolean

float number

double number

int number

short number

long number

decimal number

struct (complexType) Object

array Array



6.1.3 Example of a simple data type

An entry field and an associated value is generated on the web frontend for each method parameter. If the parameter has a simple data type, the user input will be forwarded directly to the method.

Example of a web frontend for a web service

The purpose of the following web service is to translate a piece of text. The first param-eter specifies the direction of the translation process, while the second contains the ac-tual text to be translated.

Generating the entry fields

Two entry fields are generated:

<TABLE BGCOLOR="#99CCCC"> <TR> <TD>translationmode:</TD> <TD><INPUT TYPE="TEXT" CLASS="BOX" NAME="translationmode_Translate" SIZE=32></TD> </TR> <TR> <TD>sourcedata:</TD> <TD><INPUT TYPE="TEXT" CLASS="BOX" NAME="sourcedata_Translate" SIZE=32></TD> </TR> </TABLE>

Calling the web service

WSDL_0.service.Translate.port.TranslatePort.operation.Translate( WT_POSTED.translationmode_Translate, WT_POSTED.sourcedata_Translate);

If you wish, you can change the graphical layout of the interface, e.g. by replacing one of the entry fields with a pick list:

<TR> <TD>translationmode:</TD> <TD> <SELECT NAME="translationmode_Translate"> <OPTION VALUE="de_en" >German->English</OPTION> <OPTION VALUE="en_de" >English->German</OPTION> </SELECT> </TR>

Since this pick list has the same name as the entry field, the operation call remains un-changed.



6.1.4 Example of a complex data type

If you wish to incorporate more complex data structures in the interface, you must ensure that the user has some means of entering individual values for the various elements within the data structure at the interface. This is because only one entry field will initially be gen-erated for each complex data type. Proceed as follows:

Ê At the appropriate location in the template, replace the INPUT tag generated for the en-tire structure with several INPUT tags for each attribute of the structure.

Ê After sending, copy this posted data to the object attributes in the Receive script before the method call.

Example of a web frontend for a business object with integration via SOAP

The following is generated:

<wtOnCreateScript>p0_BusinessObject_getTest = new Object(); //Objekt für die komplexe

//Datenstruktur </wtOnCreateScript>

<input type="text" name="p0_BusinessObject_getTest" value=""/>

<wtOnReceiveScript>

/* Methodenaufruf; als Parameter wird das Objekt für die komplexe Datenstruktur übergeben */

...getTest( proxyObjects.getTest_p0, ...);

</wtOnReceiveScript>



Extend the script as follows:

Ê Specify a separate INPUT tag for each attribute:

...

<input type="text" name="p0_BusinessObject_getTest_minutes" value=""/>

...

Ê For each attribute, add the following lines to the receive script before the method call (this example applies for the minutes attribute):

...

proxyObjects.getTest_p0.minutes = WT_POSTED.p0_BusinessObject_getTest_minutes;

...

<input type="text" name="p0_BusinessObject_getTest" value=""/>

This procedure allows you to generate the attribute and assign it the value entered by the user at the interface.

Other substitutions that must be carried out include:

<input type="text" name="p0_BusinessObject_getTest.minutes" value=""><input type="text" name="p0_BusinessObject_getTest.seconds" value=""><input type="text" name="p0_BusinessObject_getTest.hours" value=""><input type="text" name="p0_BusinessObject_getTest.date" value=""><input type="text" name="p0_BusinessObject_getTest.month" value=""><input type="text" name="p0_BusinessObject_getTest.year" value="">


Master templates Editing templates

6.2 Master templates

The following master templates are supplied:

– WSDL.wmt

– JAVA_BO.wmt

The supplied master templates are installed under installdir/Weblab.

The table below lists a number of new master template tags (MT tags), which have been introduced for the JAVA and WSDL protocol options only:

The following MT tags may not be used for the generation of web frontends for business objects and web services in the master template:

– %%Lines...%– %%ReceiveCopies%

MT tag Explanation

%%SOURCE% Replaced by the name of the copied WSDL file in the base directory (e.g. WSDL/BO1.wsdl)

%%ObjectName% Replaced by the name of the Java business object

%%PackageName% Replaced by the name of the Java package containing the object

%%ArchiveName% Replaced by the name of the Java archive

%%ObjectCreate% Initiates the generation of objects for complex structures

%%MethodInterface% Initiates the generation of the interface and further processing of individual methods


Editing templates Generated templates

6.3 Generated templates

This section describes the generated templates and the presentation of the associated interfaces for the following scenarios:

● Support for the business objects created with BizTransactions via Java integration

● Support for the business objects created with BizTransactions via SOAP integration

● Support for general web services via SOAP integration

Generated templates Editing templates

6.3.1 Business object integration via Java

The text below shows the wtOpenSEAS_STOCKINFO.htm template, generated in section “BizTransactions with Java integration” on page 19.

Generation options

<html><wtrem>************************************************************************</wtrem><wtrem>** WTML document: de.siemens.bizta.beans.STOCKINFO.STOCKINFO **</wtrem><wtrem>************************************************************************</wtrem><wtrem>** **</wtrem><wtrem>** Document generation based on Master Template : **</wtrem><wtrem>** C:\Programme\WebTransactionsV7\weblab\JAVA_BO.wmt **</wtrem><wtrem>** **</wtrem><wtrem>** Generated at Mon Jan 10 15:05:38 2005 **</wtrem><wtrem>** **</wtrem><wtrem>** Options used by the generator : **</wtrem><wtrem>** - %OPTIONS: **</wtrem><wtrem>** CommObj = Java_0 **</wtrem><wtrem>** Source = wsdl/STOCKINFO.wsdl - ObjectName = STOCKINFO **</wtrem><wtrem>** BO_RTS = de.siemens.bizta.runtime - JavaUtil = java.util **</wtrem><wtrem>************************************************************************</wtrem><wtrem>** WebTransactions V7.0 Fujitsu Siemens Computers GmbH, 2005 **</wtrem><wtrem>************************************************************************</wtrem>

Extending the system object attribute JAVA-CLASSPATH to include all .jar files in the java sub-directory

<wtoncreatescript><!--//create list of all available jar files in /javavar systemExits = new WT_Userexit("WTSystemExits");var dir = WT_SYSTEM.BASEDIR + "/java";var jarFiles = ( systemExits.Getdir(dir, "*.jar").split('\n')).sort();

if ( typeof WT_SYSTEM.JAVA_CLASSPATH == 'undefined' ){ WT_SYSTEM.JAVA_CLASSPATH = "";}

for( i in jarFiles ){ if ( ( jarFiles[i] != "" ) && ( WT_SYSTEM.JAVA_CLASSPATH.indexOf(WT_SYSTEM.BASEDIR + "/java/" + jarFiles[i]) == -1 ) ) WT_SYSTEM.JAVA_CLASSPATH += WT_SYSTEM.BASEDIR + "/java/" + jarFiles[i] + (WT_SYSTEM.PLATFORM == "NT" ? ";" : ":");}if (WT_SYSTEM.PLATFORM == "NT")



JAVA_CLASSPATH_OUT = WT_SYSTEM.JAVA_CLASSPATH.replace(/;/g, '; ');else JAVA_CLASSPATH_OUT = WT_SYSTEM.JAVA_CLASSPATH.replace(/:/g, ': ');

if ( typeof WT_SYSTEM.Java_0 == 'undefined' ){ WT_SYSTEM.Java_0 = new Object();

Creating complex data structures as Java objects

//{{WebLab(object create)try {WT_SYSTEM.Java_0.BizTaEvent_STOCKINFO_fireEvent = newWT_JAVA.de.siemens.bizta.beans.STOCKINFO.BizTaEvent();} catch (_exc){WT_SYSTEM.Java_0.BizTaEvent_STOCKINFO_fireEvent = newWT_JAVA.de.siemens.bizta.runtime.BizTaEvent();}try {WT_SYSTEM.Java_0.BizTaEventListener_STOCKINFO_addBizTaEventListener = newWT_JAVA.de.siemens.bizta.beans.STOCKINFO.BizTaEventListener();} catch (_exc) {WT_SYSTEM.Java_0.BizTaEventListener_STOCKINFO_addBizTaEventListener = newWT_JAVA.de.siemens.bizta.runtime.BizTaEventListener();}try {WT_SYSTEM.Java_0.BizTaEventListener_STOCKINFO_removeBizTaEventListener = newWT_JAVA.de.siemens.bizta.beans.STOCKINFO.BizTaEventListener();} catch (_exc) {WT_SYSTEM.Java_0.BizTaEventListener_STOCKINFO_removeBizTaEventListener = newWT_JAVA.de.siemens.bizta.runtime.BizTaEventListener();}WT_SYSTEM.Java_0.StringHolder_STOCKINFO_readCompanyInfo = new WT_JAVA.de.siemens.bizta.runtime.StringHolder();WT_SYSTEM.Java_0.StringHolder_STOCKINFO_readCompanyInfo_1 = new WT_JAVA.de.siemens.bizta.runtime.StringHolder();WT_SYSTEM.Java_0.GregorianCalendar_STOCKINFO_format = new WT_JAVA.java.util.GregorianCalendar();

//}}}

Creating a Java object with WT_JAVA

if ( typeof WT_SYSTEM.Java_0.STOCKINFO == 'undefined' ) WT_SYSTEM.Java_0.STOCKINFO = new Object();if ( typeof WT_SYSTEM.Java_0.STOCKINFO.instance == 'undefined' ){ try { Java_0 = WT_SYSTEM.Java_0.STOCKINFO.instance = new WT_JAVA.de.siemens.bizta.beans.STOCKINFO.STOCKINFO(); } catch ( exc ) {

</style></wtif></head>

<body bgcolor="#336666" text="#000000"> <form webtransactions name="de.siemens.bizta.beans.STOCKINFO.STOCKINFO"> <table cellspacing="1" cellpadding="2"> <tr> <td colspan="3" align="right"> <img src="##WT_SYSTEM.CGI.SCRIPT_NAME#/logo" align="left"> </td> <td><font size="+3" color="#ffffff">WebTA is the web frontend for openSEAS</font></td> </tr> <tr> <td> <wtif (Java_0_system.FORMTPL)> <wtinclude Name="##Java_0_system.FORMTPL#"> </wtif> </td> </tr>

Button for general control

<TR BGCOLOR="#99CCCC"> <td colspan="3" align="center"> <h2>control</h2> </td> <td align="center"><h3>return to component selection</h3> </td> <td align="center"> <input type="submit" name="Control" value="back"/> </td> </tr> </table>

General control

   <wtonreceivescript> if (WT_POSTED.Control) { WT_SYSTEM.FORMAT = 'wtconnectOpenSEAS.htm'; exitReceiveProcessing(); } if (WT_POSTED.SetParameter) WT_SYSTEM.JAVA_CLASSPATH += WT_POSTED.WT_Java_ClassPath+ (WT_SYSTEM.PLATFORM == "NT" ? ";" : ":"); </wtonreceivescript>

Header for the Java business object

   <wtc name="wtcTabs" type="inline" version="7.0"><wtcTitle>Tab Control <wtcPar name="objectname">ComponentTabs</wtcPar></wtcTitle><script language="Javascript" src="##WT_SYSTEM.WWWDOCS_VIRTUAL#/javascript/wtcTabs_browserFunctions.js" type="text/javascript"></script><script><wtcPar name="objectname">ComponentTabs</wtcPar> = new wtcTabs(<wtcPar name="width">950</wtcPar>,<wtcPar name="tabHeight">20</wtcPar>,'<wtcPar name="ident">compTabs</wtcPar>',<wtcPar name="foregroundColor">'#333333'</wtcPar>,<wtcPar name="backgroundColor">'#DDDDDD'</wtcPar>,<wtcPar name="borderColor">'#FFFFFF'</wtcPar>,<wtcPar name="foregroundColorDimmed">'#999999'</wtcPar>,<wtcPar name="backgroundColorSelectedDimmed">'#CCCCCC'</wtcPar>,<wtcPar name="borderColorDimmed">'#DDDDDD'</wtcPar>);</script>

List of tab sheets, one for the business object and one for each method

<wtcList name="Tab-List" minLength="1"><wtcTitle>List of Tabs</wtcTitle>

Tab sheet for adding the Java classpath

  <wtcListItem> <script language="JavaScript" type="text/javascript"><wtcPar name="objectname">ComponentTabs</wtcPar>.addTab(<wtcPar name="titlename">'STOCKINFO'</wtcPar>, <wtcPar name="titlewidth">150</wtcPar>); </script><wtcBlock><wtcTitle><wtcPar name="titlename">'STOCKINFO'</wtcPar></wtcTitle> <table cellspacing="3" cellpadding="2"> <tr bgcolor="#669999"> <td> current JAVA_CLASSPATH: </td> <td> JAVA environment parameters: </td> </tr> <tr bgcolor="#99CCCC"> <td>##WT_SYSTEM.JAVA_CLASSPATH_OUT || ' '#</td> <td> <table> <tr> <td>JAVA_CLASSPATH:</td> <td><input type="text" name="WT_Java_ClassPath" size="32"/></td> </tr> </table> </td> <td> <input type="submit" name="SetParameter" value="set parameters"/> </td> </tr> </table> </wtcBlock> </div> </wtcListItem>

Blocks such as the one shown below for each method

<wtcListItem> <script language="JavaScript" type="text/javascript"> <wtcPar name="objectname">ComponentTabs</wtcPar>.addTab(<wtcPar name="titlename">'STOCKINFO_readCompanyInfo'</wtcPar>, <wtcPar name="titlewidth">120</wtcPar>); </script> <wtcBlock> <wtcTitle><wtcPar name="titlename">'STOCKINFO_readCompanyInfo'</wtcPar></wtcTitle>

User interface– displaying return information– displaying the last parameters specified– generating entry fields for the method input parameters– button for initiating the method

<table cellspacing="3" cellpadding="2"> <tr bgcolor="#669999"> <td> return value: </td> <td> previous parameters: </td> <td> input parameters: </td> <td>&nbsp</td> </tr>

Displaying return information<tr bgcolor="#99CCCC">

<td> <table> <tr><td>##WT_SYSTEM.Java_0["STOCKINFO"].ret_STOCKINFO_readCompanyInfo#</td</tr> </table> </td>



Displaying the last parameters specified

<td> <table bgcolor="#99CCCC"> <tr> <td> ##WT_POSTED.p0_STOCKINFO_readCompanyInfo || ' '# </td> </tr> <tr> <td> ##WT_POSTED.p1_STOCKINFO_readCompanyInfo || ' '# </td> </tr> <tr> <td> ##WT_POSTED.p2_STOCKINFO_readCompanyInfo || ' '# </td> </tr> </table> </td>

Generating entry fields for the method input parameters

<td> <table bgcolor="#99CCCC"> <tr> <td>p0:</td> <td><input type="text" name="p0_STOCKINFO_readCompanyInfo" size="32"/></td> </tr> <tr> <td>p1:</td> <td><input type="text" name="p1_STOCKINFO_readCompanyInfo" size="32"/></td> </tr> <tr> <td>p2:</td> <td><input type="text" name="p2_STOCKINFO_readCompanyInfo" size="32"/></td> </tr> </table> </td>

Button for initiating the method

<td> <input type="submit" name="STOCKINFO_readCompanyInfo" value="execute"/> </td> </tr> </table>

Calling the Java method with type-specific parameters (corresponding sections generated for each method)

<wtonreceivescript> if ( WT_POSTED.STOCKINFO_readCompanyInfo) { try { WT_SYSTEM.Java_0["STOCKINFO"].ret_STOCKINFO_readCompanyInfo = Java_0.readCompanyInfo( WT_POSTED.p0_STOCKINFO_readCompanyInfo, WT_SYSTEM.Java_0.StringHolder_STOCKINFO_readCompanyInfo, WT_SYSTEM.Java_0.StringHolder_STOCKINFO_readCompanyInfo_1); } catch ( exc ) { WT_System.Java_0["STOCKINFO"].ret_STOCKINFO_readCompanyInfo = exc;} exitReceiveProcessing(); } </wtonreceivescript> </wtcBlock> </div> </wtcListItem></wtcList>

End of the template: activating the tab sheets

</span><script language="JavaScript" type="text/javascript"><wtcPar name="objectname">ComponentTabs</wtcPar>.adjust();<wtcPar name="objectname">ComponentTabs</wtcPar>.redefineFocus();<wtcPar name="objectname">ComponentTabs</wtcPar>.activate(##WT_POSTED['wtcTabs_<wtcPar name="ident">compTabs</wtcPar>_ActiveTab']||0#);</script></wtc>

  

</form> </body> <wtif (Java_0_system.EPILOG)> <wtinclude Name="##Java_0_system.EPILOG#"> </wtif></html>

6.3.2 Business object integration via SOAP

The text below shows the wtOpenSEAS_k3_Datentypen.htm template, generated in section “BizTransactions with SOAP integration” on page 21.

Generation options

<html><wtrem>************************************************************************</wtrem><wtrem>** WTML document: de.siemens.bizta.beans.k3_Datentypen.k3_Datentypen **</wtrem><wtrem>************************************************************************</wtrem><wtrem>** **</wtrem><wtrem>** Document generation based on Master Template : **</wtrem><wtrem>** C:\Programme\WebTransactionsV7\weblab\WSDL.wmt **</wtrem><wtrem>** **</wtrem><wtrem>** Generated at Mon Jan 10 15:52:20 2005 **</wtrem><wtrem>** **</wtrem><wtrem>** Options used by the generator : **</wtrem><wtrem>** - %OPTIONS: **</wtrem><wtrem>** CommObj = WSDL_0 **</wtrem><wtrem>** Source = wsdl/k3_Datentypen.wsdl **</wtrem><wtrem>************************************************************************</wtrem><wtrem>** WebTransactions V7.0 Fujitsu Siemens Computers GmbH, 2005 **</wtrem><wtrem>************************************************************************</wtrem>

Creating a proxy object with WT_SOAP

<wtOnCreateScript><!--include ('wtSOAP');if ( typeof WT_SYSTEM.WSDL_0 == 'undefined' ) WT_SYSTEM.WSDL_0 = new Object();if ( typeof WT_SYSTEM.WSDL_0["k3_Datentypen"] == 'undefined' ) WT_SYSTEM.WSDL_0["k3_Datentypen"] = new Object();if ( typeof WT_SYSTEM.WSDL_0["k3_Datentypen"].instance == 'undefined' ){ try { WSDL_0 = WT_SYSTEM.WSDL_0["k3_Datentypen"].instance = new WT_SOAP('wsdl/k3_Datentypen.wsdl'); WSDL_0.proxyObjects = proxyObjects; } catch ( exc ) { document.writeln(exc); WT_SYSTEM.WSDL_0["k3_Datentypen"].ret_value = exc; }}else { WSDL_0 = WT_SYSTEM.WSDL_0["k3_Datentypen"].instance; proxyObjects = WSDL_0.proxyObjects;}



WSDL_0_system = WT_SYSTEM;


<wtif (WSDL_0_system.PROLOG)> <wtinclude Name="##WSDL_0_system.PROLOG#"></wtif>


<head><title>WebTransactions V7.0 - WebService de.siemens.bizta.beans.k3_Datentypen.k3_Datentypen</title>##WT_SYSTEM.CGI.HTTP_USER_AGENT.indexOf( 'MSIE' ) >= 0 ? '<meta http-equiv="Pragma" content="no-cache"/>' : '<meta http-equiv="Cache-Control" content="no-cache"/>'#<wtif (WT_BROWSER.acceptClass)> <style type="text/css"> input { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; } input.box { border: 0 solid; padding: 1px 0 1px 0; margin-left: -1px; margin-top: ##WT_BROWSER.marginTop#px; font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; color: #000000; background-color: #FFFFFF; } input.button { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; border-width: 1pt; margin-left: -1pt; } select { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; } pre { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; margin: 0; } </style></wtif></head>

<body bgcolor="#336666" text="#000000"> <form WebTransactions name="de.siemens.bizta.beans.k3_Datentypen.k3_Datentypen"> <table cellspacing="1" cellpadding="2"> <tr> <td colspan="3" align="right"> <img src="##WT_SYSTEM.CGI.SCRIPT_NAME#/logo" align="left"/> </td> </tr> <tr> <td> <wtif (WSDL_0_system.FORMTPL)> <wtinclude Name="##WSDL_0_system.FORMTPL#"> </wtif> </td>

</tr>


<tr bgcolor="#99CCCC"> <td colspan="3" align="center"> <h2>control</h2> </td> <td align="center"><h3>return to component selection</h3> </td> <td align="center"> <input type="submit" name="Control" value="back"/> </td> </tr> </table>

General control for accessing the web service

   <wtonreceivescript> if (WT_POSTED.Control) { WT_SYSTEM.FORMAT = WT_SYSTEM.PREVIOUS_CONTROL_FORMAT; delete WT_SYSTEM.PREVIOUS_CONTROL_FORMAT; exitReceiveProcessing(); } if (WT_POSTED.SetParameter) { if (WT_POSTED.Proxy) { if (WT_POSTED.ProxyPort) WSDL_0.setProxy(WT_POSTED.Proxy, WT_POSTED.ProxyPort); else WSDL_0.setProxy(WT_POSTED.Proxy); } if (WT_POSTED.ProxyUser)

{ if (WT_POSTED.ProxyPwd) WSDL_0.setProxyAuthorization(WT_POSTED.ProxyUser, WT_POSTED.ProxyPwd); else WSDL_0.setProxyAuthorization(WT_POSTED.ProxyUser); } } </wtonreceivescript>

Header for the WSDL service

   <wtc name="wtcTabs" type="inline" version="7.0"><wtcTitle>Tab Control <wtcPar name="objectname">ComponentTabs</wtcPar></wtcTitle><script language="Javascript" src="##WT_SYSTEM.WWWDOCS_VIRTUAL#/javascript/wtcTabs_browserFunctions.js" type="text/javascript"></script><script><wtcPar name="objectname">ComponentTabs</wtcPar> = new wtcTabs(<wtcPar name="width">950</wtcPar>,<wtcPar name="tabHeight">20</wtcPar>,'<wtcPar name="ident">compTabs</wtcPar>',<wtcPar name="foregroundColor">'#333333'</wtcPar>,<wtcPar name="backgroundColor">'#DDDDDD'</wtcPar>,<wtcPar name="borderColor">'#FFFFFF'</wtcPar>,<wtcPar name="foregroundColorDimmed">'#999999'</wtcPar>,<wtcPar name="backgroundColorSelectedDimmed">'#CCCCCC'</wtcPar>,<wtcPar name="borderColorDimmed">'#DDDDDD'</wtcPar>);</script><wtcList name="Tab-List" minLength="1"><wtcTitle>List of Tabs</wtcTitle>

Tab sheets for setting HTTP parameters for the service

   <wtcListItem> <script language="JavaScript" type="text/javascript"><wtcPar name="objectname">ComponentTabs</wtcPar>.addTab(<wtcPar name="titlename">'JavaService'</wtcPar>, <wtcPar name="titlewidth">150</wtcPar>); </script><wtcBlock><wtcTitle><wtcPar name="titlename">'JavaService'</wtcPar></wtcTitle> <table cellspacing="3" cellpadding="2"> <tr bgcolor="#669999">



<td> further parameters: </td> <td> HTTP parameters: </td> </tr> <tr bgcolor="#99CCCC"> <td> <table> <tr> <td>##WT_POSTED.Proxy || ' '#</td> <td> </td> </tr> <tr> <td>##WT_POSTED.ProxyPort || ' '#</td> <td> </td> </tr> <tr> <td>##WT_POSTED.ProxyUser || ' '#</td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> </TABLE> </td> <td> <TABLE> <tr> <td>Proxy:</td> <td><input type="text" name="Proxy" size="32"/></td> </tr> <tr> <td>Proxy-Port:</td> <td><input type="text" name="ProxyPort" size="6"/></td> </tr> <tr> <td>Proxy-User:</td> <td><input type="text" name="ProxyUser" size="32"/></td> </tr> <tr> <td>Proxy-Password:</td> <td><input type="password" name="ProxyPwd" size="32"/></td> </tr> </table> </td> <td> <input type="submit" name="SetParameter" value="set parameters"/> </td> </tr>

</table> </wtcBlock> </div> </wtcListItem>   

There are blocks such as the one shown below for all methods

<wtcListItem> <script language="JavaScript" type="text/javascript"> <wtcPar name="objectname">ComponentTabs</wtcPar>.addTab(<wtcPar name="titlename">'k3_Datentypen_methString'</wtcPar>, <wtcPar name="titlewidth">120</wtcPar>); </script> <wtcBlock> <wtcTitle><wtcPar name="titlename">'k3_Datentypen_methString'</wtcPar></wtcTitle>

User interface – displaying return information– displaying the last parameters specified– generating entry fields for the method input parameters– button for initiating the method


Displaying return information

<tr bgcolor="#99CCCC"> <td> <table> <tr><td>##WT_SYSTEM.WSDL_0["k3_Datentypen"].ret_k3_Datentypen_methString#</td</tr>



</table> </td>


<td> <table bgcolor="#99CCCC"> <tr> <td> ##WT_POSTED.p0_k3_Datentypen_methString || ' '# </td> </tr> <tr> <td> ##WT_POSTED.p1_k3_Datentypen_methString || ' '# </td> </tr> <tr> <td> ##WT_POSTED.p2_k3_Datentypen_methString || ' '# </td> </tr> <tr> <td> ##WT_POSTED.p3_k3_Datentypen_methString || ' '# </td> </tr> </table> </td>


<td> <table bgcolor="#99CCCC"> <tr> <td>p0:</td> <td><input type="text" name="p0_k3_Datentypen_methString" size="32"/></td> </tr> <tr> <td>p1:</td> <td><input type="text" name="p1_k3_Datentypen_methString" size="32"/></td> </tr> <tr> <td>p2:</td> <td><input type="text" name="p2_k3_Datentypen_methString" size="32"/></td> </tr> <tr> <td>p3:</td>

<td><input type="text" name="p3_k3_Datentypen_methString" size="32"/></td> </tr> </table> </td>


<td> <input type="submit" name="k3_Datentypen_methString" value="execute"/> </td> </tr> </table>

Calling the proxy method with type-specific parameters (corresponding sections generated for all methods)

<wtonreceivescript> if ( WT_POSTED.k3_Datentypen_methString) { try { WT_SYSTEM.WSDL_0["k3_Datentypen"].ret_k3_Datentypen_methString = WSDL_0.service.JavaService.port.k3_Datentypen.operation.methString( WT_POSTED.p0_k3_Datentypen_methString, proxyObjects.k3_Datentypen_methString_Request_p1, proxyObjects.k3_Datentypen_methString_Request_p2, proxyObjects.k3_Datentypen_methString_Request_p3); } catch ( exc ) { WT_System.WSDL_0["k3_Datentypen"].ret_k3_Datentypen_methString = exc;} exitReceiveProcessing(); } </wtonreceivescript> </wtcBlock> </div> </wtcListItem>

</wtcList></span><script language="JavaScript" type="text/javascript"><wtcPar name="objectname">ComponentTabs</wtcPar>.adjust();<wtcPar name="objectname">ComponentTabs</wtcPar>.redefineFocus();<wtcPar name="objectname">ComponentTabs</wtcPar>.activate(##WT_POSTED['wtcTabs_<wtcPar name="ident">compTabs</wtcPar>_ActiveTab']||0#);</script></wtc>


</form> </body> <wtif (WSDL_0_system.EPILOG)> <wtinclude Name="##WSDL_0_system.EPILOG#"> </wtif></html>

6.3.3 Using general web services via SOAP integration

The text below shows the wtWebService_BabelFishService.htm template, generated in section “General web services with SOAP integration” on page 23.

Generation options

<html><wtrem>************************************************************************</wtrem><wtrem>** WTML document: BabelFishService **</wtrem><wtrem>************************************************************************</wtrem><wtrem>** **</wtrem><wtrem>** Document generation based on Master Template : **</wtrem><wtrem>** C:\Programme\WebTransactionsV7\weblab\WSDL.wmt **</wtrem><wtrem>** **</wtrem><wtrem>** Generated at Mon Jan 10 11:06:12 2005 **</wtrem><wtrem>** **</wtrem><wtrem>** Options used by the generator : **</wtrem><wtrem>** - %OPTIONS: **</wtrem><wtrem>** CommObj = WSDL_0 **</wtrem><wtrem>** Source = wsdl/BabelFishService.wsdl **</wtrem><wtrem>************************************************************************</wtrem><wtrem>** WebTransactions V7.0 Fujitsu Siemens Computers GmbH, 2005 **</wtrem><wtrem>************************************************************************</wtrem>

Creating a proxy object with WT_SOAP

<wtOnCreateScript><!--include ('wtSOAP');if ( typeof WT_SYSTEM.WSDL_0 == 'undefined' ) WT_SYSTEM.WSDL_0 = new Object();if ( typeof WT_SYSTEM.WSDL_0["BabelFishService"] == 'undefined' ) WT_SYSTEM.WSDL_0["BabelFishService"] = new Object();if ( typeof WT_SYSTEM.WSDL_0["BabelFishService"].instance == 'undefined' ){ try { WSDL_0 = WT_SYSTEM.WSDL_0["BabelFishService"].instance = new WT_SOAP('wsdl/BabelFishService.wsdl'); WSDL_0.proxyObjects = proxyObjects; } catch ( exc ) { document.writeln(exc); WT_SYSTEM.WSDL_0["BabelFishService"].ret_value = exc; }}else { WSDL_0 = WT_SYSTEM.WSDL_0["BabelFishService"].instance; proxyObjects = WSDL_0.proxyObjects;



}WSDL_0_system = WT_SYSTEM;


<wtif (WSDL_0_system.PROLOG)> <wtinclude Name="##WSDL_0_system.PROLOG#"></wtif>


<head><title>WebTransactions V7.0 - WebService BabelFishService</title>##WT_SYSTEM.CGI.HTTP_USER_AGENT.indexOf( 'MSIE' ) >= 0 ? '<meta http-equiv="Pragma" content="no-cache"/>' : '<meta http-equiv="Cache-Control" content="no-cache"/>'#<wtif (WT_BROWSER.acceptClass)> <style type="text/css"> input { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; } input.box { border: 0 solid; padding: 1px 0 1px 0; margin-left: -1px; margin-top: ##WT_BROWSER.marginTop#px; font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; color: #000000; background-color: #FFFFFF; } input.button { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; border-width: 1pt; margin-left: -1pt; } select { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; } pre { font-size: ##WT_BROWSER.charSize#px; font-family: courier new, monospace; margin: 0; } </style></wtif></head> <body bgcolor="#336666" text="#000000">

<form WebTransactions name="BabelFishService"> <table cellspacing="1" cellpadding="2"> <tr> <td colspan="3" align="right"> <img src="##WT_SYSTEM.CGI.SCRIPT_NAME#/logo" align="left"/> </td> </tr> <tr> <td> <wtif (WSDL_0_system.FORMTPL)> <wtinclude Name="##WSDL_0_system.FORMTPL#"> </wtif> </td> </tr>


<tr bgcolor="#99CCCC"> <td colspan="3" align="center"> <h2>control</h2> </td> <td align="center"><h3>return to component selection</h3> </td> <td align="center"> <input type="submit" name="Control" value="back"/> </td> </tr> </table>

General control

   <wtonreceivescript> if (WT_POSTED.Control) { WT_SYSTEM.FORMAT = WT_SYSTEM.PREVIOUS_CONTROL_FORMAT; delete WT_SYSTEM.PREVIOUS_CONTROL_FORMAT; exitReceiveProcessing(); } if (WT_POSTED.SetParameter) { if (WT_POSTED.Proxy) { if (WT_POSTED.ProxyPort) WSDL_0.setProxy(WT_POSTED.Proxy, WT_POSTED.ProxyPort); else WSDL_0.setProxy(WT_POSTED.Proxy); } if (WT_POSTED.ProxyUser) {

if (WT_POSTED.ProxyPwd) WSDL_0.setProxyAuthorization(WT_POSTED.ProxyUser, WT_POSTED.ProxyPwd); else WSDL_0.setProxyAuthorization(WT_POSTED.ProxyUser); } } </wtonreceivescript>

web service header

   <wtc name="wtcTabs" type="inline" version="7.0"><wtcTitle>Tab Control <wtcPar name="objectname">ComponentTabs</wtcPar></wtcTitle><script language="Javascript" src="##WT_SYSTEM.WWWDOCS_VIRTUAL#/javascript/wtcTabs_browserFunctions.js" type="text/javascript"></script><script><wtcPar name="objectname">ComponentTabs</wtcPar> = new wtcTabs(<wtcPar name="width">950</wtcPar>,<wtcPar name="tabHeight">20</wtcPar>,'<wtcPar name="ident">compTabs</wtcPar>',<wtcPar name="foregroundColor">'#333333'</wtcPar>,<wtcPar name="backgroundColor">'#DDDDDD'</wtcPar>,<wtcPar name="borderColor">'#FFFFFF'</wtcPar>,<wtcPar name="foregroundColorDimmed">'#999999'</wtcPar>,<wtcPar name="backgroundColorSelectedDimmed">'#CCCCCC'</wtcPar>,<wtcPar name="borderColorDimmed">'#DDDDDD'</wtcPar>);</script><wtcList name="Tab-List" minLength="1"><wtcTitle>List of Tabs</wtcTitle>

Tab sheets for controlling access via HTTP

<wtcListItem> <script language="JavaScript" type="text/javascript"><wtcPar name="objectname">ComponentTabs</wtcPar>.addTab(<wtcPar name="titlename">'BabelFishService'</wtcPar>, <wtcPar name="titlewidth">150</wtcPar>); </script><wtcBlock><wtcTitle><wtcPar name="titlename">'BabelFishService'</wtcPar></wtcTitle> <table cellspacing="3" cellpadding="2"> <tr bgcolor="#669999"> <td> further parameters: </td> <td> HTTP parameters: </td> </tr> <tr bgcolor="#99CCCC"> <td> <table> <tr> <td>##WT_POSTED.Proxy || ' '#</td> <td> </td> </tr> <tr> <td>##WT_POSTED.ProxyPort || ' '#</td> <td> </td> </tr> <tr> <td>##WT_POSTED.ProxyUser || ' '#</td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> </TABLE> </td> <td> <TABLE> <tr> <td>Proxy:</td> <td><input type="text" name="Proxy" size="32"/></td> </tr> <tr> <td>Proxy-Port:</td> <td><input type="text" name="ProxyPort" size="6"/></td> </tr> <tr>

<td>Proxy-User:</td> <td><input type="text" name="ProxyUser" size="32"/></td> </tr> <tr> <td>Proxy-Password:</td> <td><input type="password" name="ProxyPwd" size="32"/></td> </tr> </table> </td> <td> <input type="submit" name="SetParameter" value="set parameters"/> </td> </tr> </table> </wtcBlock> </div> </wtcListItem>   

There are blocks such as the one shown below for each method

<wtcListItem> <script language="JavaScript" type="text/javascript"> <wtcPar name="objectname">ComponentTabs</wtcPar>.addTab(<wtcPar name="titlename">'BabelFishPortType_BabelFish'</wtcPar>, <wtcPar name="titlewidth">120</wtcPar>); </script> <wtcBlock> <wtcTitle><wtcPar name="titlename">'BabelFishPortType_BabelFish'</wtcPar></wtcTitle>



User interface – displaying return information– displaying the last parameters specified– generating entry fields for the method input parameters– button for initiating the method


Displaying return information

<tr bgcolor="#99CCCC"> <td> <table> <tr><td>##WT_SYSTEM.WSDL_0["BabelFishService"].ret_BabelFishPortType_BabelFish#</td></tr> </table> </td>


<td> <table bgcolor="#99CCCC"> <tr> <td> ##WT_POSTED.translationmode_BabelFishPortType_BabelFish || ' '# </td> </tr> <tr> <td> ##WT_POSTED.sourcedata_BabelFishPortType_BabelFish || ' '# </td> </tr> </table> </td>

<td> <table bgcolor="#99CCCC"> <tr> <td>translationmode:</td> <td><input type="text" name="translationmode_BabelFishPortType_BabelFish" size="32"/></td> </tr> <tr> <td>sourcedata:</td> <td><input type="text" name="sourcedata_BabelFishPortType_BabelFish" size="32"/></td> </tr> </table> </td>


<td> <input type="submit" name="BabelFishPortType_BabelFish" value="execute"/> </td> </tr> </table>

Calling the proxy method with type-specific parameters (corresponding sections generated for each method)

<wtOnReceiveScript> if ( WT_POSTED.BabelFishPortType_BabelFish) { try { WT_SYSTEM.WSDL_0["BabelFishService"].ret_BabelFishPortType_BabelFish = WSDL_0.service.BabelFishService.port.BabelFishPort.operation.BabelFish( WT_POSTED.translationmode_BabelFishPortType_BabelFish, WT_POSTED.sourcedata_BabelFishPortType_BabelFish); } catch ( exc ) { WT_System.WSDL_0["BabelFishService"].ret_BabelFishPortType_BabelFish = exc;} exitReceiveProcessing(); } </wtonreceivescript> </wtcBlock> </div> </wtcListItem>

</wtcList></span><script language="JavaScript" type="text/javascript"><wtcPar name="objectname">ComponentTabs</wtcPar>.adjust();<wtcPar name="objectname">ComponentTabs</wtcPar>.redefineFocus();<wtcPar name="objectname">ComponentTabs</wtcPar>.activate(##WT_POSTED['wtcTabs_<wtcPar name="ident">compTabs</wtcPar>_ActiveTab']||0#);</script></wtc>


</form> </body> <wtif (WSDL_0_system.EPILOG)> <wtinclude Name="##WSDL_0_system.EPILOG#"> </wtif></html>


7 Communication sharing of Java business objects and WebTransactions

An integration of Java business objects generated with BizTransactions, generally uses a se-parate connection between business object and host application. This procedure can cause problems, if only one user ID is available for each WebTransactions session: the host appli-cation can only be connected to either WebTransactions or the business object.

With WebTransactions you can run Java business objects via the WebTransactions commu-nication objects. You can assign the communication objects completely to the business ob-jects, or integrate business objects in the current connection during a running WebTransac-tions dialog.

WebTransactions offers this procedure for WebTransactions for OSD and WebTransactions for MVS.

In the sections below you find a description of

– the required business object properties for communication sharing

– how such a Java business object is called

– how a business object can utilize the WebTransactions communication object assigned to it.


Defining properties Communication Sharing

7.1 Defining Java business object properties

When creating a Java business object to be run via a WebTransactions communication oject, the followng points must be observed (see also the BizTransactions manual “Application In-tegration with Business Objects”):

Ê When creating a business object, select the value Business Object or Extern for the Connection property

Ê If you want to proceed the dialog with a host application, already started by WebTransactions, make sure the send and receive methods of WebTransactions and the business object interlock. Generally, business object methods must begin with send and end with receive.

This procedure is absolutely necessary if you are going to use WebTransactions and Biz-Transactions communication simultaneously. Use this procedure if, for example, you wish to provide additional functions for Automask via business objects during dialog mode.


Communication Sharing Calling business objects

7.2 Calling Java business objects

If you create a Java business object in WTScript, specify via the constant de.siemens.bizta.runtime.BizTaBasicCommunication.WebTa, that you want to apply a WebTransactions communication object for the communication with the host application:

Example

myBo=newWT_JAVA.fsc.App9750.MyBO.MyBO(WT_JAVA.de.siemens.bizta.runtime.BizTaBasicCommunication.WebTa);

If you want to open an new connection to the host application, you must create a commu-nication object.

Example

newComm = new WT_Communication ("BOCOMM");

If you want to proceed an existing dialog, apply the communication object used in this dia-log.

You must assign the communication object which is to be used to the Java business object before calling a business method. This is done with the method attachCommObject():

void attachCommObject (comObject [, mode])

comObject link to a communication object

mode mode for controlling the connection (see section “Defining the communication mode” on page 76)Default value: false

Example

myBO.attachCommObject (newComm , false);

Now you can call the business methods of Java business objects as usual.

If you have specified the Extern option for the Connection property with providing a business object, you have to indicate a communication server for the business ob-ject before calling the first method:

var objIO = new WT_JAVA.de.siemens.bizta.runtime.BizTaConnection();MyBO.setCommunicationServer (objIO);

i


Defining a communication mode Communication Sharing

7.3 Defining the communication mode

A Java business object can use the assigned WebTransactions communication object in two different ways:

– The business object itself executes open and close.

– The business object uses the current WebTransactions connection.

Executing open and close within the business object

This mode is activated if you omit the mode parameter or set it explicitly to false (default) on calling attachCommObject().

In this case the connection parameters defined in the business object are applied. Open connections on the assigned WebTransactions communication object are disconnected.

Using an open WebTransactions connection

This mode is activated, if the mode parameter is set to true on calling attachCommObject().

In this case every business object call of open or close is suppressed. The current WebTransactions connection is continued by the business object.


Communication Sharing Example

7.4 Example for a host application with communication sharing

A host application for the administration and display of order numbers will serve as an ex-ample. Every order number is displayed as a link. A click on the link opens a popup window with a brief description of the corresponding article.

A business object ON is used with the business method getInfoShort to display the brief description. This method has the order number as input parameter and the brief description as output parameter.

Every order number has the format A0123456. This requires the following link to be pro-grammed in the Automask template:

output = hostObject.HTMLValue.replace(/A0\d\d\d\d\d\d/gi,'<a href="javascript:void window.open(\''+ WT_SYSTEM.HREF_ASYNC+ '&WT_ASYNC_PAGE=show_oninfo&ON=$&\',\'ONINF\',\'width=400

height=70\')">$&</a>');


Example Communication Sharing

The business object is called in the template show_oninfo.htm:

<html><head><title>Info for ON ##WT_POSTED.ON#</Title>##WT_BROWSER.is_ie

'<META HTTP-EQUIV="Pragma" CONTENT="no-cache">' :'<META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">'#

</HEAD><body bgcolor="#400080" text="#ffffff" style="font-family: Arial"><wtOnCreateScript><!-////Java-BO was created with generated template as WT_SYSTEM.Java_0.ON.instance//try{

bo = WT_SYSTEM.Java_0.ON.instance;bo.attachCommObject (WT_HOST.active true);WT_SYSTEM.Java_0.ON.ret_ON_getInfoShort =

bo.getInfoShort( WT_POSTED.ON, WT_SYSTEM.Java_0.StringHolder_ON_getInfoShort);

document.writeln ('\n<b>',WT_POSTED.ON, ': ',WT_SYSTEM.Java_0.StringHolder_ON_getInfoShort.value,'</b>');

}catch ( exc ){

document.writeln (exc);}//--></wtOnCreateScript></BODY></HTML>


GlossaryA term in ->italic font means that it is explained somewhere else in the glossary.

active dialogIn the case of active dialogs, WebTransactions actively intervenes in the control of the dialog sequence, i.e. the next ->template to be processed is determined by the template programming. You can use the ->WTML language tools, for example, to combine multiple ->host formats in a single ->HTML page. In this case, when a host ->dialog step is terminated, no output is sent to the ->browser and the next step is immediately started. Equally, multiple interactions between the Web ->browser and WebTransactions are possible within one and the same host dialog step.

array->Data type which can contain a finite set of values of one data type. This data type can be:– ->scalar – a ->class – an arrayThe values in the array are addressed via a numerical index, starting at 0.

asynchronous messageIn WebTransactions, an asynchronous message is one sent to the terminal with-out having been explicitly requested by the user, i.e. without the user having pressed a key or clicked on an interface element.

attributeAttributes define the properties of ->objects.

● In WebTransactions, an attribute may be, for example, the color, size or position of an object or it can itself be an object. Attributes are also interpret-ed as ->variables and their values can be queried or modified.

● In BizTransactions, an attribute may be a ->property of a ->catalog object or ->catalog element.


Glossary

Automask templateA WebTransactions ->template created by WebLab either implicitly when generating a base directory or explicitly with the command Generate Automask. It is used whenever no format-specific template can be identified. An Automask template contains the statements required for dynamically mapping formats and for communication. Different variants of the Automask template can be generated and selected using the system object attribute AUTOMASK.

base directoryThe base directory is located on the WebTransactions server and forms the basis for a ->WebTransactions application. The base directory contains the ->templates and all the files and program references (links) which are necessary in order to run a WebTransactions application.

BCAM application nameCorresponds to the openUTM generation parameter BCAMAPPL and is the name of the −>openUTM application through which −>UPIC establishes the connec-tion.

BizTransactions applicationApplication, which integrates -> host applications for COM or Java access. A BizTransactions application consists of:– ->host adapters– ->business objects– a ->client, which addresses the business objects

BizTransactions catalogCentral database used and processed by the BizTransactions Studio during the development phase. For instance, the BizTransactions catalog contains a description of the ->host applications and of the messages (->services) exchanged with the host application.

browserProgram which is required to call and display ->HTML pages. Familiar browsers include, for example, Netscape Navigator or Microsoft Internet Explorer.

browser display printThe WebTransactions browser display print prints the information displayed in the ->browser.

browser platformOperating system of the host on which a ->browser runs as a client for WebTransactions.


Glossary

bufferDefinition of a record, which is transmitted from a ->service. The buffer is used for transmitting and receiving messages. In addition there is a specific buffer for storing the ->recognition criteria and for data for the representation on the screen.

business object (BO)Object-oriented view of a ->host application: Business Objects in BizTransactions combine a number of ->services of an application to form a logical object. A description of each business object is stored in the ->BizTransactions catalog. This description then forms the basis for generating an ActiveX component, .NET component or ->JavaBean which then represents the business object.

business object classJava, .NET or Visual Basic class generated by the BizTransactions Studio on the basis of a business object stored in the ->BizTransactions catalog.

capturingTo enable WebTransactions to identify the received ->formats at runtime, you can open a ->session in ->WebLab and select a specific area for each format and name the format. The format name and ->recognition criteria are stored in the ->capture database. A ->template of the same name is generated for the format. Capturing forms the basis for the processing of format-specific templates for the WebTransactions for OSD, MVS, As400 and UNIX product variants.

capture databaseThe WebTransactions capture database contains all the format names and the associated ->recognition criteria generated using the ->capturing technique. You can use ->WebLab to edit the sequence and recognition criteria of the formats.

catalog elementSubordinate ->catalog objects in BizTransactions, such as ->buffers, ->records or ->fields. The ->properties of catalog elements are ->attributes.

catalog objectDescriptions saved in the ->BizTransactions catalog for– ->Host applications– ->Services – ->Business objects – ->Classes – ->Functions ->Catalog-elements are subordinate to the catalog-objects. The ->properties of catalog objects and elements are ->attributes. A separate ->XML schema is assigned to each catalog object.


Glossary

CGI(Common Gateway Interface)Standardized interface for program calls on ->Web servers. In contrast to the static output of a previously defined->HTML page, this interface permits the dynamic construction of HTML pages.

classContains definitions of the ->properties and ->methods of an ->object. It provides the model for instantiating objects and defines their interfaces.

In BizTransactions the ->catalog object of the type class contains only properties which means that a class is also considered as a user-defined data structure. Access methods for the class properties are added through generation. A class can be used by the following catalog elements:– Properties of ->business objects– Properties of other classes– ->Method parameters– ->Function parameters

class directoryA directory in BizTransactions which contains the generated ->business object classes and ->service classes.

class templateIn WebTransactions, a class template contains valid, recurring statements for the entire object class (e.g. input or output fields). Class templates are processed when the ->evaluation operator or the toString method is applied to a ->host data object.

clientRequestors and users of services in a network. A BizTransactions client accesses ->business objects within a ->client application.

clusterSet of identical ->WebTransactions applications on different servers which are interconnected to form a load-sharing network.

COMComponent Object Model.The COM defines a standard governing the way in which software components can access the services or data provided by other software components.


Glossary

communication objectThis controls the connection to an ->host application and contains information about the current status of the connection, the last data to be received etc.

conversion toolsUtilities supplied with WebTransactions and BizTransactions. These tools are used to analyze the data structures of ->openUTM applications and store the information in files. These files can then be imported in the form of an object description into the ->BizTransactions catalog or used in WebLab as ->format description sources in order to generate WTML templates and ->FLD files.COBOL data structures or IFG format libraries form the basis for the conversion tools. The conversion tool for DRIVE programs is supplied with the product DRIVE.

daemon Name of a process type in UNIX/POSIX systems which runs in the background and performs no I/O operations at terminals.

data access controlMonitoring of the accesses to data and ->objects of an application.

data typeDefinition of the way in which the contents of a storage location are to be inter-preted. Each data type has a name, a set of permitted values (value range), and a defined number of operations which interpret and manipulate the values of that data type.

DCOMDistributed Component Object ModelThis is based on the ->COM standard and defines the way in which COM objects can provide their services or data outside system boundaries.


Glossary

dialog

● In WebTransactions, a dialog describes the entire communication between browser, WebTransactions and ->host application. It will usually comprise multiple ->dialog cycles. WebTransactions supports a number of different types of dialog.

– ->passive dialog– ->active dialog– ->synchronized dialog– ->non-synchronized dialog

● In BizTransactions a dialog is defined as a series of ->dialog steps. A method of a ->Business Object is the same as a dialog with the ->host application.

dialog cycleCycle that comprises the following steps when a ->WebTransactions application is executed:– construct an ->HTML page and send it to the ->browser – wait for a response from the browser– evaluate the response fields and possibly send them to the->host application

for further processingA number of dialog cycles are passed through while a ->WebTransactions appli-cation is executing.

dialog stepIn BizTransactions, a dialog step begins by sending a dialog message to the ->host application, and ends with a response from the host application.

distinguished nameThe Distinguished Name (DN) in ->LDAP is hierarchically organized and consists of a number of different components (e.g. “country, and below country: organization, and below organization: organizational unit, followed by: usual name”). Together, these components provide a unique identification of an object in the directory tree.Thanks to this hierarchy, the unique identification of objects is a simple matter even in a worldwide directory tree: – The DN "Country=DE/Name=Emil Person" reduces the problem of achiev-

ing a unique identification to the country DE (=Germany).– The DN "Organization=FSC/Name=Emil Person" reduces it to the organiza-

tion FSC.– The DN "Country=DE/Organization=FSC/Name=Emil Person" reduces it to

the organization FSC located in Germany (DE).


Glossary

document directory->Web server directory containing the documents that can be accessed via the network. WebTransactions stores files for download in this directory, e.g. the WebLab client or general start pages.

Domain Name Service (DNS) Procedure for the symbolic addressing of computers in networks. Certain computers in the network, the DNS or name server, maintain a database containing all the known host names and IP numbers in their environment.

dynamic dataIn WebTransactions, dynamic data is mapped using the WebTransactions object model, e.g. as a ->system object, host object or user input at the browser.

EHLLAPIEnhanced High-Level Language APIProgram interface, e.g. of terminal emulations for communication with the SNA world. Communication between the transit client and SNA computer, which is handled via the TRANSIT product, is based on this interface.

EJB (Enterprise JavaBean)This is a Java-based industry standard which makes it possible to use in-house or commercially available server components for the creation of distributed program systems within a distributed, object-oriented environment.

entry pageThe entry page is an ->HTML page which is required in order to start a ->WebTransactions application This page contains the call which starts WebTransactions with the first ->template, the so-called start template.

evaluation operator In WebTransactions the evaluation operator replaces the addressed ->expressions with their result (object attribute evaluation). The evaluation oper-ator is specified in the form ##expression#.

expressionA combination of ->literals, ->variables, operators and expressions which return a specific result when evaluated.

FHSFormat Handling SystemFormatting system for BS2000/OSD applications.


Glossary

fieldA field is the smallest component of a service and element of a ->record or ->buffer.

field file (*.fld file)In WebTransactions, this contains the structure of a ->format record (metadata).

filterProgram or program unit (e.g. a library) for converting a given ->format into another format (e.g. XML documents to ->WTScript data structures).

formatOptical presentation on alphanumeric screens (sometimes also referred to as screen form or mask).

In WebTransactions each format is represented by a ->field file and a ->template.

format type(only relevant in the case of ->FHS applications and communication via ->UPIC)Specifies the type of format: #format, +format, -format or *format.

format description sourcesDescription of multiple ->formats in one or more files which were generated from a format library (FHS/IFG) or are available directly at the ->host for the use of “expressive” names in formats.

functionA function is a user-defined code unit with a name and ->parameters. Functions can be called in ->methods by means of a description of the function interface (or signature).

holder task A process, a task or a thread in WebTransactions depending on the operating system platform being used. The number of tasks corresponds to the number of users. The task is terminated when the user logs off or when a time-out occurs. A holder task is identical to a ->WebTransactions session.

hostThe computer on which the- >host application is running.


Glossary

host adapterHost adapters are used to connect existing ->host applications to WebTransactions and BizTransactions. At runtime, for example, they have the task of establishing and terminating connections and converting all the exchanged data.

host applicationApplication that is integrated with WebTransactions or BizTransactions.

host control objectIn WebTransactions, host control objects contain information which relates not to individual fields but to the entire ->format. This includes, for example, the field in which the cursor is located, the current function key or global format attributes.

host data objectIn WebTransactions, this refers to an ->object of the data interface to the ->host application. It represents a field with all its field attributes. It is created by WebTransactions after the reception of host application data and exists until the next data is received or until termination of the ->session.

host data printDuring WebTransactions host data print, information is printed that was edited and sent by the ->host application, e.g. printout of host files.

host platformOperating system of the host on which the ->host applications runs.

HTML(Hypertext Markup Language) see ->Hypertext Markup Language

HTTP(Hypertext Transfer Protocol)This is the protocol used to transfer ->HTML pages and data.

HTTPS(Hypertext Transfer Protocol Secure)This is the protocol used for the secure transfer of ->HTML pages and data.

hypertextDocument with links to other locations in the same or another document. Users click the links to jump to these new locations.


Glossary

Hypertext Markup Language (Hypertext Markup Language) Standardized markup language for documents on the Web.

Java BeanJava programs (or ->classes) with precisely defined conventions for interfaces that allow them to be reused in different applications.

KDCDEFopenUTM tool for generating ->openUTM applications.

LDAP(Lightweight Directory Access Protocol)The X.500 standard defines DAP (Directory Access Protocol) as the access protocol. However, the Internet standard “LDAP” has proved successful specif-ically for accessing X.500 directory services from a PC. LDAP is a simplified DAP protocol that does not support all the options available with DAP and is not compatible with DAP. Practically all X.500 directory services support both DAP and LDAP. In practice, interpretation problems may arise since there are various dialects of LDAP. The differences between the dialects are generally small.

literalCharacter sequence that represents a fixed value. Literals are used in source programs to specify constant values (“literal” values).

master templateWebTransactions template used to generate the Automask and the format-specific templates.

message queuing (MQ)A form of communication in which messages are not exchanged directly, rather via intermediate queues. The sender and receiver can work at separate times and locations. Message transmission is guaranteed regardless of whether or not a network connection currently exists.

methodObject-oriented term for a ->function. A method is applied to the ->object in which it is defined.

In BizTransactions, the method of a ->business object conducts a ->dialog with the associated ->host application.


Glossary

module templateIn WebTransactions, a module template is used to define ->classes, ->functions and constants globally for a complete ->session. A module template is loaded using the import() function.

MT tag(Master Template tag)Special tags used in the dynamic sections of ->master templates.

multitier architectureAll client/server architectures are based on a subdivision into individual soft-ware components which are also known as layers or tiers. We speak of 1-tier, 2-tier, 3-tier and multitier models. This subdivision can be considered at the physical or logical level:– We speak of logical software tiers when the software is subdivided into

modular components with clear interfaces. – Physical tiers occur when the (logical) software components are distributed

across different computers in the network.

With WebTransactions and a host connection in BizTransactions, multitier models are possible both at the physical and logical level.

name/value pairIn the data sent by the ->browser, the combination, for example, of an ->HTML input field name and its value.

non-synchronized dialogNon-synchronized dialogs in WebTransactions permit the temporary deactiva-tion of the checking mechanism implemented in ->synchronized dialogs. In this way, ->dialogs that do not form part of the synchronized dialog and have no effect on the logical state of the ->host application can be incorporated. In this way, for example, you can display a button in an ->HTML page that allows users to call help information from the current host application and display it in a separate window.


Glossary

objectElementary unit in an object-oriented software system. Every object possesses a name via which it can be addressed, ->attributes, which define its status together with the ->methods that can be applied to the object.

In BizTransactions objects only exist as instances of ->classes during run time. However, for simplicity’s sake, the object definitions created during development are also referred to as objects. Thus, we speak of, for example, ->business objects stored in the ->BizTransactions catalog although these are actually only definitions. These definitions are used by BizTransactions to generate ->business object classes which serve to instantiate the “actual” business objects at runtime.

openUTM(Universal Transaction Monitor)Transaction monitor from Fujitsu Siemens Computers, which is available for BS2000/OSD and a variety of UNIX and Windows platforms.

openUTM applicationA ->host application which provides services that process jobs submitted by ->clients or other ->host applications. openUTM responsibilities include transac-tion management and the management of communication and system resources. Technically speaking, the UTM application is a group of processes which form a logical unit at runtime.

openUTM applications can communicate both via the client/server protocol ->UPIC and via the emulation interface (9750).

openUTM-Client (UPIC)The openUTM-Client (UPIC) is a product used to create client programs for openUTM. openUTM-Client (UPIC) is available, for example, for UNIX, BS2000/OSD and Windows platforms.

openUTM program unitThe services of an ->openUTM application are implemented by one or more openUTM program units. These can be addressed using transaction codes and contain special openUTM function calls (e.g. KDCS calls).

parameterData which is passed to a ->function or a ->method for processing (input param-eter) or data which is returned as a result of a function or method (output param-eter).


Glossary

passive dialogIn the case of passive dialogs in WebTransactions, the dialog sequence is controlled by the ->host application, i.e. the host application determines the next ->template which is to be processed. Users who access the host application via WebTransactions pass through the same dialog steps as if they were accessing it from a terminal. WebTransactions uses passive dialog control for the automatic conversion of the host application or when each host application format corre-sponds to precisely one individual template.

passwordString entered for a ->user id in an application which is used for user authenti-cation (->system access control).

pollingCyclical querying of a given event.

poolIn WebTransactions, this term refers to a shared directory in which WebLab can create and maintain ->base directories. You control access to this directory with the administration program.

postTo send data.

posted object (wt_Posted)List of the data returned by the ->browser. This ->object is created by WebTransactions and exists for the duration of a ->dialog cycle.

processThe term “process” is used as a generic term for process (in Solaris, Linux and Windows) and task (in BS2000/OSD).

projectIn the WebTransactions development environment, a project contains various settings for a ->WebTransactions application. These are saved in a project file (suffix .wtp). You should create a project for each WebTransactions application you develop, and always open this project for editing.

propertyProperties define the nature of an ->object, e.g. the object “Customer” could have a customer name and number as its properties. These properties can be set, queried, and modified within the program.


Glossary

protocolAgreements on the procedural rules and formats governing communications between remote partners of the same logical level.

protocol file

● BizTransactions: Messages about specific program status conditions are written during the program execution into a log file.

● openUTM-Client: File into which the openUTM error messages as are written in the case of abnormal termination of a conversation.

● In WebTransactions, protocol files are called trace files.

roaming session->WebTransactions sessions which are invoked simultaneously or one after another by different ->clients.

recordA record is the definition of a set of related data which is transferred to a ->buffer. It describes a part of the buffer which may occur one or more times.

recognition criteriaRecognition criteria are used to identify ->formats of a ->terminal application and can access the data of the format. The recognition criteria selected should be one or more areas of the format which uniquely identify the content of the format.

scalar->variable made up of a single value, unlike a ->class, an ->array or another complex data structure.


Glossary

service

In BizTransactions, services are messages exchanged with the ->host application. In the case of access via the terminal interface (9750/3270), they are ->formats. In program-to-program communication, they correspond to message structures. Services are created using the BizTransactions Studio. They are automatically entered in the ->BizTransactions catalog and can be used by the (COM) ->clients. Depending on the type of server application, a service may represent:

● a 9750 emulation screen

● a 3270 emulation screen

● an openUTM ->dialog step (in the case of interconnection via UPIC) which is distinguished by:

– the FHS format

– the data structure of a DRIVE procedure

– the data structure of a COBOL program (structure of the UPIC message buffer)

● a message sent or received by the ->host adapter

service (openUTM)In ->openUTM, this is the processing of a request using an ->openUTM applica-tion. There are dialog services and asynchronous services. The services are assigned their own storage areas by openUTM. A service is made up of one or more ->transactions.

service application->WebTransactions session which can be called by various different users in turn.

service datadescription of a ->service in the BizTransactions catalog. The service data contain a description of the structure of the service and either– a ->recognition criterion or– data for the presentation of the service while recording a ->dialog

service nodeInstance of a ->service. During development and runtime of a ->method a service can be instantiated several times. During modelling and code editing those instances are named service nodes.


Glossary

sessionWhen an end user starts to work with a ->WebTransactions application this opens a WebTransactions session for that user on the WebTransactions server. This session contains all the connections open for this user to the ->browsers, special ->clients and ->hosts.A session can be started as follows:– Input of a WebTransactions URL in the browser.– Using the START_SESSION method of the WT_REMOTE client/server interface.A session is terminated as follows:– The user makes the corresponding input in the output area of this

->WebTransactions application (not via the standard browser buttons).– Whenever the configured time that WebTransactions waits for a response

from the ->host application or from the ->browser is exceeded.– Termination from WebTransactions administration.– Using the EXIT_SESSION method of the WT_REMOTE client/server interface.A WebTransactions session is unique and is defined by a ->WebTransactions application and a session ID. During the life cycle of a session there is one ->holder task for each WebTransactions session on the WebTransactions server.

SOAP(originally Simple Object Access Protocol)The ->XML based SOAP protocol provides a simple, transparent mechanism for exchanging structured and typecast information between computers in a decentralized, distributed environment. SOAP provides a modular package model together with mechanisms for data encryption within modules. This enables the uncomplicated description of the internal interfaces of a ->Web-Service.

styleIn WebTransactions this produces a different layout for a ->template, e.g. with more or less graphic elements for different->browsers. The style can be changed at any time during a ->session.

synchronized dialogIn the case of synchronized dialogs (normal case), WebTransactions automati-cally checks whether the data received from the web browser is genuinely a response to the last ->HTML page to be sent to the ->browser. For example, if the user at the web browser uses the Back button or the History function to return to an “earlier” HTML page of the current ->session and then returns this, WebTransactions recognizes that the data does not correspond to the current ->dialog cycle and reacts with an error message. The last page to have been sent to the browser is then automatically sent to it again.


Glossary

system access controlCheck to establish whether a user under a particular ->user ID is authorized to work with the application.

system object (wt_System)The WebTransactions system object contains ->variables which continue to exist for the duration of an entire ->session and are not cleared until the end of the session or until they are explicitly deleted. The system object is always visible and is identical for all name spaces.

TACSee ->transaction code

tag->HTML, ->XML and ->WTML documents are all made up of tags and actual content. The tags are used to mark up the documents e.g. with header formats, text highlighting formats (bold, italics) or to give source information for graphics files.

TCP/IP (Transport Control Protocol/Internet Protocol)Collective name for a protocol family in computer networks used, for example, in the Internet.


Glossary

templateA template is used to generate specific code. A template contains fixed informa-tion parts which are adopted unchanged during generation, as well as variable information parts that can be replaced by the appropriate values during gener-ation.

● In WebTransactions, a ->WTML file is a file with special tags for controlling the dynamic generation of a ->HTML page and for the processing of the values entered at the ->browser. It is possible to maintain multiple template sets in parallel. These then represent different ->styles (e.g. many/few graphics, use of Java, etc.).

WebTransactions uses different types of template:– ->Automask templates for the automatic conversion of the ->formats of

AS400, MVS, OSD and UNIX applications.– Custom templates, written by the programmer, for example, to control

an ->active dialog. – Format-specific templates which are generated for subsequent post-

processing. – Include templates which are inserted in other templates.– ->Class templates– ->Master templates to ensure the uniform layout of fixed areas on the

generation of the Automask and format-specific templates.– Start template, this is the first template to be processed in a

WebTransactions application.

● In BizTransactions, templates are supplied files which contain code sections that can be used as patterns for the generation functions of BizTransactions.

template object->Variables are used to buffer values for a ->dialog cycle in WebTransactions.

terminal applicationApplication on a ->host computer which is accessed via a 9750 or 3270 inter-face.

terminal hardcopy printA terminal hardcopy print in WebTransactions prints the alphanumeric represen-tation of the ->format as displayed by a terminal or a terminal emulation.

transactionProcessing step between two synchronization points (in the current operation) which is characterized by the ACID conditions (Atomicity, Consistency, Isolation and Durability). The intentional changes to user information made within a transaction are accepted either in their entirety or not at all (all-or-nothing rule).


Glossary

transaction code/TACName under which an openUTM service or ->openUTM program unit can be called. The transaction code is assigned to the openUTM program unit during configuration. A program unit can be assigned several transaction codes.

UDDI(Universal Description, Discovery and Integration)Refers to directories containing descriptions of ->Web services. This information is available to web users in general.

UPIC(Universal Programming Interface for Communication)Carrier system for openUTM clients which uses the X/Open interface, which permity CPI-C client/server communication between a CPI-C-Client application and the openUTM application.

URI(Uniform Resource Identifier)Blanket term for all the names and addresses that reference objects on the Internet. The generally used URIs are->URLs.

URL (Uniform Resource Locator)Description of the location and access type of a resource in the ->Internet.

user exitFunctions implemented in C/C++ which the programmer calls from a ->template.

user IDUser identification which can be assigned a password (->system access control) and special access rights (->data access control).

UTMSee ->openUTM

variableMemory location for variable values which requires a name and a ->data type.

visibility of variables->Objects and ->variables of different dialog types are managed by WebTransactions in different address spaces. This means that variables belong-ing to a ->synchronized dialog are not visible and therefore not accessible in a ->asynchronous dialog or in a dialog with a remote application.


Glossary

web serverComputer and software for the provision of ->HTML pages and dynamic data via ->HTTP.

web serviceService provided on the Internet, for example a currency conversion program. The SOAP protocol can be used to access such a service. The interface of a web service is described in ->WSDL.

WebTransactions applicationThis is an application that is integrated with ->host applications for internet/intranet access. A WebTransactions application consists of: – a ->base directory– a start template – the ->templates that control conversion between the ->host and the

->browser.– protocol-specific configuration files.

WebTransactions platformOperating system of the host on which WebTransactions runs.

WebTransactions serverComputer on which WebTransactions runs.

WebTransactions sessionSee ->session

WSDL(Web Service Definition Language)Provides ->XML language rules for the description of ->web services. In this case, the web service is defined by means of the port selection.

WTBeanIn WebTransactions ->WTML components with a self-descriptive interface are referred to as WTBeans. A distinction is made between inline and standalone WTBeans:– An inline WTBean corresponds to a part of a WTML document– A standalone WTBean is an autonomous WTML document

A number of WTBeans are included in of the WebTransactions product, addition-al WTBeans can be downloaded from the WebTransactions homepage(www.Fujitsu-Siemens.com/WebTransactions).

www.Fujitsu-Siemens.com/WebTransactions


Glossary

WTML(WebTransactions Markup Language)Markup and programming language for WebTransactions ->templates. WTML uses additional ->WTML tags to extend ->HTML and the server programming language ->WTScript, e.g. for data exchange with ->host applications. WTML tags are executed by WebTransactions and not by the ->browser (serverside scripting).

WTML tag(WebTransactions Markup Language-Tag)Special WebTransactions tags for the generation of the dynamic sections of an ->HTML page using data from the->host application.

WTScriptServerside programming language of WebTransactions. WTScripts are similiar to client-side Java scripts in that they are contained in sections that are intro-duced and terminated with special tags. Instead of using ->HTML-SCRIPT tags you use ->WTML-Tags: wtOnCreateScript and wtOnReceiveScript. This indicates that these scripts are to be implemented by WebTransactions and not by the ->browser and also indicates the time of execution. OnCreate scripts are executed before the page is sent to the browser. OnReceive scripts are executed when the response has been received from the browser.

XML(eXtensible Markup Language)Defines a language for the logical structuring of documents with the aim of making these easy to exchange between various applications.

XML schemaAn XML schema basically defines the permissible elements and attributes of an XML description. XML schemas can have a range of different formats, e.g. DTD (Document Type Definition), XML Schema (W3C standard) or XDR (XML Data Reduced).

In BizTransactions, an XDR schema defines the permitted elements and attributes of a catalog object.


AbbreviationsBO Business Object

CGI Common Gateway Interface

DN Distinguished Name

DNS Domain Name Service

EJB Enterprise JavaBean

FHS Format Handling System

HTML Hypertext Markup Language

HTTP Hypertext Transfer Protocol

HTTPS Hypertext Transfer Protocol Secure

IFG Interactive Format Generator

ISAPI Internet Server Application Programming Interface

LDAP Lightweight Directory Access Protocol

MT tag Master Template tag

MVS Multiple Virtual Storage

OSD Open Systems Direction

SGML Standard Generalized Markup Language

SOAP Simple Object Access Protocol

SSL Secure Socket Layer


Abbreviations

TCP/IP Transport Control Protocol/Internet Protocol

Upic Universal Programming Interface for Communication

UDDI Universal Description, Discovery and Integration

URI Uniform Resource Identifier

URL Uniform Resource Locator

UTM Universal Transaction Monitor

WSDL Web Service Definition Language

WTML WebTransactions Markup Language

wtc WebTransactions Component

XML eXtensible Markup Language


Related publicationsYou can download all the WebTransactions manuals from the following Web address http://manuals.Fujitsu-Siemens.com/servers/man/man_us/appi_man/webta_hb.htm.

[1] WebTransactions Concepts and FunctionsIntroduction

Target groupUsers who want information on the functional scope and performance of WebTransactions.ContentsThe manual contains a general description of the concepts behind the product, as well as information on the object concept and the dynamic session procedure.

[2] WebTransactions Template LanguageReference Manual

Target groupUsers who wish to actively create WebTransactions applications. ContentsThe manual contains a description of all the language resources in the template language WTML. When you integrate host applications into the Web, this language allows you to adapt the results of automatic conversion to suit your requirements.

[3] WebTransactions Connection to OSD ApplicationsUser Guide

Target groupUsers who wish to use WebTransactions to connect OSD dialog applications to the Web.ContentsThe manual describes all the steps required for connecting OSD dialog applications to the Web. It supplements the introductory manual “Concepts and Functions“ and the Reference Manual “Template Language“ by providing all the information relating to OSD.

http://manuals.Fujitsu-Siemens.com/servers/man/man_us/appi_man/webta_hb.htm


Related Publications

[4] WebTransactions Connection to MVS ApplicationsUser Guide

Target groupUsers who wish to use WebTransactions to connect MVS dialog applications to the Web.ContentsThe manual describes all the steps required for connecting MVS dialog applications to the Web. It supplements the introductory manual “Concepts and Functions“ and the Reference Manual “Template Language“ by providing all the information relating to MVS.

[5] WebTransactions Connection to openUTM Applications via UPICUser Guide

Target groupUsers who wish to use WebTransactions to connect openUTM dialog applications to the Web.ContentsThe manual describes all the steps required for connecting openUTM dialog applications to the Web. It supplements the introductory manual “Concepts and Functions“ and the Refe-rence Manual “Template Language“ by providing all the information relating to openUTM.

[6] WebTransactions Connection to AS400 ApplicationsUser Guide

Target groupUsers who wish to use WebTransactions to connect AS400 dialog applications to the Web.ContentsThe manual describes all the steps required for connecting AS400 dialog applications to the Web via the 5250 protocol. This manual supplements the introductory manual “Concepts and Functions” and the reference manual “Template Language” and provides all the information relating to AS400.

[7] WebTransactions Connection to UNIX ApplicationsUser Guide

Target groupUsers who wish to use WebTransactions to connect UNIX dialog applications to the Web.ContentsThe manual describes all the steps required for connecting UNIX-dialog applications to the Web via Telnet or the rlogin protocol. This manual supplements the introductory manual “Concepts and Functions” and the reference manual “Template Language” and provides all the information relating to UNIX.


Related Publications

[8] WebTransactionsAccess to Dynamic Web ContentsUser Guide

Target groupUsers who wish to use WebTransactions to access dynamic Web contents.ContentsThe manual describes all the steps required for accessing dynamic web contents via the HTTP protocol. It supplements the introductory manual “Concepts and Functions“ and the Reference Manual “Template Language“ by providing all the information relating to HTTP.

[9] WebTransactionsClient APIs for WebTransactionsUser Guide

Target groupAnyone who wishes to implement Clients for WebTransactions.ContentsThe manual describes all the interfaces WebTransactions provides developing client pro-grams. You can develop not only your own Java clients with the suppiled classes, but alsoclients in any programming language which communicate with WebTransactions via the cli-ent protocol. WebTransactions itself can function as a client of a WebTransactions application.

[10] BizTransactionsApplication Integration with Business ObjectsUser Guide

Target group This manual addresses users wishing to create business objects for accessing host appli-cations in order to – develop graphical interfaces for host applications (e.g. via GUIs, created using

WebTransactions, Visual Basic, Visual C++, Microfocus NetExpress or Java).– make the host application available as a Web service, for example, on the Internet.– integrate interactions with host applications into Microsoft Office products (e.g. current

data of an openUTM mainframe application to Excel tables).ContentsThis manual describes the concept, functions and components of BizTransactions. It explains all steps required to create business objects and Web services.


Index

Aaccess

objects 35active dialog 79, 84architecture

web frontend 7array 79asynchronous message 79attribute 79automask template 80

Bbase data type 79base directory 80

converting to a new version 16creating 15

basic interfacegeneral web frontend 13

BCAM application name 80BCAMAPPL 80BizTransactions

web frontend 30, 31BizTransactions application 80BizTransactions catalog 80BO see business objectbrowser 80browser display print 80browser platform 80buffer 81business object 81

communication sharing 73generated as web service 13generated template via SOAP 45Java 13testing template 30

business object as web serviceflowchart for frontend 27generated template 18generating template 21master template 18prerequisites for testing 27web frontend 31

business object class 81

Ccapture database 81capturing 81catalog element 81catalog object 81CGI (Common Gateway Interface) 82class 82

business object 81directory 82templates 82WT_JAVA 36WT_SOAP 39

client 82cluster 82COM 82communication mode 76communication object 83communication sharing with Java business

objects 73complex data types, WT_JAVA 38concept of the web frontend 13conversion tools 83


Index

Ddaemon 83data

dynamic 85data access control 83data type 83

complex (WT_JAVA) 38WT_JAVA 37WT_SOAP 40

DCOM 83dialog 84

active 84non-synchronized 84, 89passive 84, 91synchronized 84, 94types 84

dialog cycle 84dialog step 84distinguished name 84document directory 85Domain Name Service (DNS) 85

Eedit

templates 35EHLLAPI 85EJB 85entry page 85evaluation operator 85expression 85

FFHS 85field 86field file 86filter 86fld file 86flowchart

frontend (business object as web service) 27frontend (Java business object) 26frontend (web service) 32

format 86#format 86*format 86+format 86-format 86

format description source 86format type 86function 86

Ggenerate

template for business objects as web service 21

template for Java business objects 19template for web services 23

generated template 44business object (via SOAP) 45Java business object 45web service 45

Hholder task 86host 86host adapter 87host application 87host control object 87host data object 87host data print 87host platform 87HTML 88HTTP 87HTTPS 87hypertext 87Hypertext Markup Language (HTML) 88

Iinline WTBean 98


Index

Jjava

subdirectory 16Java Bean 88Java business object 13

call 75communication sharing 73defining a communication mode 76flowchart for frontend 26generated template 18, 45generating template 19integration via communication objects 73master template 18prerequisites for testing 26web frontend 30

KKDCDEF 88

LLDAP 88literals 88

Mmaster template 18, 35, 88, 96

JAVA_BO.wmt 19tag 89WSDL.wmt 21

message queuing 88method 88module template 89MT tag 44, 89multitier architecture 89

Nname/value pair 89non-synchronized dialog 84, 89

Oobject 90

accessing 35generated as web service 13Java 13

openUTM 90application 90Client 90program unit 90service 93

operations 83

Pparameter 90passive dialog 84, 91password 91polling 91pool 91posted object 91posting 91prerequisites

testing (business object as web service) 27testing (Java business object) 26

process 91project 91property 91protocol 92protocol file 92

Rrecognition criteria 92record 92record structure 86

Sscalar 92service 93service (openUTM) 93service data 93service node 93session 94

WebTransactions 94SOAP 94SOAP protocol 13standalone WTBean 98start template 96

openSEAS 29web service 33

style 94


Index

subdirectoryjava 16wsdl 16

synchronized dialog 84, 94system access control 95system object 95

TTAC 97tag 95TCP/IP 95template 96

class 82edit 35generating for business objects as web

service 21generating for Java business objects 19generating for web services 23master 96object 96start 96testing for business object 30testing for web service 33

terminal application 96terminal hardcopy printing 96test

template for business object 30template for web service 33

Thread 86transaction 96transaction code/TAC 97

UUDDI 97UPIC 97URI 97URL 97user exits 97user ID 97UTM see openUTM

Vvalue range of a data type 83variable 97visibility 97

Wweb frontend

architecture 7basic interface 13business object as web service 31concept 13flowchart 14flowchart for business object as web

service 27flowchart for Java business object 26flowchart for web service 32Java business object 30testing (openSEAS) 25web service 34

web server 98web service 13, 98

flowchart for frontend 32generated template 18, 45generating template 23master template 18testing template 33web frontend 34

WebTransactions session 94WebTransactions application 98WebTransactions platform 98WebTransactions server 98WSDL 98wsdl

subdirectory 16WSDL file 13, 17WT_JAVA 36

complex data types 38data types 37

WT_SOAP 39data types 40

WTBean 98WTML 99WTML tag 99WTScript 99


Index

WWW browser 80WWW server 98

XXML 99XML schema 99

Comments on WebTransactions V7.0Web Frontend for Web Services and Business Objects


Fujitsu Siemens Computers GmbHUser Documentation81730 MunichGermany

Fax: (++49) 700 / 372 00001

e-mail: [email protected]://manuals.fujitsu-siemens.com

CommentsSuggestionsCorrections

✁

Submitted by

mailto:[email protected]

http://manuals.fujitsu-siemens.com

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.

This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.

Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.

Contact and support addresses will now be offered by Fujitsu Technology So-lutions and have the format …@ts.fujitsu.com.

The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-dem den Namen Fujitsu Technology Solutions.

Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.

Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.

Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.

Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009

webtransactions v7.0 web frontend for web services and...

Documents