Overview

Installation: Genero Web Services Extension

Summary:

Package Installation Prerequisites

Genero Web Services are packaged as an add-on to the Genero Business Development Language. The appropriate version of the Genero Business Development Language package (same major and minor version numbers) must be installed before installing the Genero Web Services Extension.

If the appropriate version of the Genero Business Development Language is not installed on your system, you MUST install this package before installing the Genero Web Services Extension.

In a deployment environment the Genero Application Server package is required to manage your Web Services. It is not required for Web Services development unless you are interested in testing deployment issues.

Required package:

Additional package:

 

 

License Agreement:   This product includes software developed by the Apache Software Foundation (http://www.apache.org). Please check the LICENSES_WSE file for the complete legal notices concerning this product.

For further information regarding installation, please check the Genero Web Services Extension package release notes.

Creating a Runner including the Web Services Extension

Use the fglmkrws command. This command uses a syntax compatible with the fglmkrun command. Please check the fglmkrun help option for a complete description of the command options.

Examples of creating a runner named "fglrunws" including the Web Services extension:

  1. To create a runner without a database 
        fglmkrws -o fglrunws -d nodb
  1. To create a runner with an Informix database
       fglmkrws -o fglrunws -d ix914 -l esql

 

Important!  When using Web Services, you need to create a dynamic runner (do not specify the "-static" option in FGLCC or INFORMIXC).

Creating a Runner including the Web Services Extension and your own C extensions

To create a runner with both the Web Services extension and your own C extension, you must add two lines to your fglExt.c file, to include the Web Services function definitions (fglExtWse.h) and the additional entries in the usrFunctions array (fglExtWse.inc).

Example fglExt.c file:

01 #define FGL_IS_LIB
02 
03 #include "f2c/fglExt.h"
04 #include "f2c/r_c.h">
05
06 UsrData usrData[]={
07   { 0, 0 }
08 };
09
10 #include "f2c/fglExtWse.h"
11
12 int myFirstFct(int argc);
13 int mySecondFct(int argc);
14 
15 UsrFunction usrFunctions[]={
16 #include "f2c/fglExtWse.inc"
17   { "myFirstFct",myFirstFct,1,1},
18   { "mySecondFct",mySecondFct,2,0},
19   { 0, 0, 0, 0 }
20 };

To build the runner, use the fglmkrws command with the same options that you usually use for the fglmkrun command.

Examples of creating a runner including the Web Services Extension and your own C extensions:

1. To create a runner without a database 
 fglmkrws -d nodb -ext myExt.c -alb "mylib.lib"
2. To create a runner on Windows with an Informix database 
 fglmkrws -o fglrunws -d ix914 -l esql -ext myExt.c 
 -alb "mylib.lib"
3. To create a runner on Unix without a database 
 fglmkrws -d nodb -ext myExt.c -alb "mylib.a"