Back to Contents
Topics
Genero Application Server is supported on a large brand of operating systems,
such as Linux, IBM AIX, HP-UX, SUN Solaris and Microsoft Windows.
Each Genero Application Server package is identified with an operating system
code (hpx1100, w32vc71). You must install the Genero Application server package
corresponding to the operating system that you use.
For the detailed list of supported operating systems, please refer to the
Four J's support web site.
DVM for Genero 2.00+ is required.
Any web server compliant with CGI (Common Gateway Interface) version 1.1 is
supported. For development platforms, we recommend Apache httpd. For more
information, refer to http://httpd.apache.org.
Any Genero Front End or a Web Services client.For the
Genero Web Client, the supported user agents include:
| User Agent Provider |
Version(s) Supported |
| Microsoft |
Internet Explorer (IE) 6.x
Internet Explorer (IE) 7.x |
| Mozilla |
FireFox 2.x |
| Opera Software |
Opera 9.x |
| Apple, Inc. |
Safari 3.x |
Any database accessible from the DVM or from the ODI. Refer to the Genero
Business Development Language Manual for details.
Back to the top
The software is provided as an auto-extractible installation program (i.e.
product files and installation program are provided in the same file).
The name of the package includes the operating system type and version.
Ensure the package name corresponds to your operating system before starting the installation
program.
You should also know what type of installation to choose when prompted.
You do not need to be superuser to install Genero Application Server. However, some parts of
the Genero Application Server need to be installed with special rights.
For example, installation of the connector assumes that you have the rights to install the product in the web server directories.
The installation type you select depends on whether you are installing the
software on the application server host, the web server host, or a host that
will contain both the application server and web server.
- Type 1: Install the Application Server - choose for the
application server host.
- Type 2: Install the Connector - choose for the web server host.
- Type 3: Install both the Application Server and Connector.
The installation procedure differs between UNIX and Windows platforms:
The installation program provides options that allow you to specify
configuration options from the command line . You can display the installation program options using the
-h option:
$ /bin/sh fjs-gas-wersion-hpx1100.sh -h
The installation program identifies the operating system and checks that
all the system requirements are met before starting to copy the product
files to your disk.
To perform the installation, run the auto-extractible shell script with
the -i option:
$ /bin/sh fjs-gas-version-hpx1100.sh -i
Your application server and web server may reside on separate machines. As
such,
you are presented with three installation choices:
1 --- Application Server (Application server - gasd)
2 --- Web Server (CGI Connector)
3 --- Full installation (Application server and CGI Connector)
Installation type 1 installs the GAS engine on your
application server. Only
this part is needed for development purpose.
Installation type 2 installs the GAS Connector on your web server.
Installation type 3 assumes that your application server and web server
are the same machine.
After you select an installation type, the installation program copies the product files to
the relevant directories on disk.
Once the files are copied to disk, follow the instructions displayed.
Note: You can install the package as root using -r or --root
option.
On Microsoft Windows, GAS is provided as a standard Windows setup program.
Distribution files and installation program are provided in the same file.
fjs-gas-version-windows.exe
When you execute the setup program, a wizard guides you through the
installation process. At one point, you will be asked to select the type
of installation: Application Server, Web Server, Full Installation, or
Custom.
- If your Application Server and Web Server sit on separate hosts, you
would select Application Server or Web Server according to the host
machine's role. For development, you may bypass the Web Server and
connect directly to the Application Server for development and testing; in
this scenario, select Application Server.
- If your Application Server and Web Server reside on the same host, select
Full Installation.
On Microsoft Windows, GAS can be installed as a Windows service. If
installed as a Windows service, the
GAS daemon can be started automatically at the server startup.
With Microsoft Internet Information Services, the installed files may not have the right permissions. You
will need to update these files permissions to fit IIS permissions.
Back to the top
The following table lists those directories and files created by or
touched during the installation process.
| Directory |
File |
Description |
| <webserver> |
|
Web Server installation directory. |
| <webserver>/<script>/ |
fglccgi |
GAS connector. |
| |
fglcgienv |
Tool to check Web Server environment. |
| |
connector.xcf |
Connector configuration file. |
| $FGLASDIR |
|
GAS installation directory. |
| |
envas |
Script for setting environment variables. |
| $FGLASDIR/app |
|
GWC applications external configuration
files. |
| $FGLASDIR/bin |
gasd |
GAS daemon. |
| $FGLASDIR/etc |
as.xcf |
GAS configuration file. |
| $FGLASDIR/log |
|
By default, GAS log files are written to
this directory. |
| $FGLASDIR/tmp |
|
Default file transfer directory. |
| $FGLASDIR/tpl/ |
generodefault.html |
Template directory containing the default
template file for the built-in rendering engine.
Note: The generodefault.html template is not used for the
snippet-based rendering engine. |
$FGLASDIR/tpl/set1
$FGLASDIR/tpl/set2
$FGLASDIR/tpl/set3 |
main.xhtml |
Snippet-based rendering engine template
subdirectories. Each sub-directory contains a template file (main.xhtml)
and a set of .xhtml snippets that define how the snippet-based rendering
engine displays the objects in the UI. |
| $FGLASDIR/web |
demos.html |
Root directory for direct communication to
the application server.
Demonstrations listing. |
| $FGLASDIR/web/fjs |
gwccore.js
gwccomponents.js
gwccomponents.css |
JavaScript handling the application behavior.
Default cascading style sheet for Set1.
|
| $FGLASDIR/web/fjs/asapi |
application.js |
JavaScript handling communication with Genero Web Client. |
| |
wrappers.js |
JavaScript handling widgets behavior. |
| $FGLASDIR/web/fjs/uaapi |
webBrowser.js |
JavaScript handling user agents specifics. |
| $FGLASDIR/web/fjs/defaultTheme |
genero.css |
Default cascading style sheet for legacy engine. |
| |
genero.js |
JavaScript handling the application design. |
<script> is the script directory of your web server (example "cgi-bin" for Apache and "scripts" for Internet Information Services).
See also Genero Web Client Application Directory Structure.
Back to the top
Application Server
Note: If you installed the GAS daemon as a service on Windows and have
started the service, skip to step 3.
- Set the GAS environment using the script $FGLASDIR/envas
- Launch the GAS daemon gasd
- Check the connection to the GAS with a direct connection by
launching a demo application.
For the GDCAX, use Internet Explorer to access to the demo application ( http://myApplicationServer:6394/wa/r/gdc-demo
), replacing myApplicationServer with the name of the server
hosting the GAS. The first time you access to the demo application, the
ActiveX will install by itself. For more information, refer to the
Genero Desktop Client Manual.
For the GDC, you need to create a shortcut pointing to the demo
application (http://myApplicationServer:6394/wa/r/gdc-demo)
To create the shortcut, you must start the GDC in administrative mode
using the --admin or -a option. Refer to the Genero
Desktop Client Manual for more information on creating shortcuts.
To create the shortcut required for this test, once you have started the
New Shortcut wizard, select the By HTTP option:
In the HTTP connection information page, you provide the application
URL. On most systems, you can replace the "myApplicationServer" with
"localhost" for this test.
http://localhost:6394/wa/r/gdc-demo
Tips:
On Windows platforms, if an application does not start you can debug
the problem by manually launching the program. For example, use the command:
gasd -E res.dvm.wa="cmd /K start cmd". The GAS opens a DOS command window
when it accesses the application. In the DOS window, the environment for the application
is set; you can now manually run the program and check step-by-step what went
wrong.
Web Server
- Perform the Application Server checkup first
- Ensure that your webserver is correctly configured by accessing
a static page like index.html
- Check your connector.xcf file, figure out if you access the right GAS
- Launch a demonstration program through the web server
http://myWebServer/cgi-bin/fglccgi/wa/r/myApp
Back to the top
Important! After you upgrade your GAS,
you must refresh the css and js downloaded in the browser cache by clearing the
browser cache. For many browsers, you can accomplish this by pressing CTRL + F5.
Application Server
Note: If you installed the GAS daemon as a service on Windows and have
started the service, skip to step 3.
- Set the Genero Web
Client environment using the script
$FGLASDIR/envas.
- Launch the
GAS daemon gasd with the
gasd command.
To have the gasd reload
template and snippet files each time a new page is created, start the GAS
daemon with the --development flag. This is useful if you are
making changes to either the template or snippet files, and wish to see the
results without having to restart the GAS daemon. For more information on
starting the Genero Application Server daemon and the various command
options, please refer to the chapter Startup and Command
Options
.
- Check the connection to the application server using a URI providing a
direct connection. A variety of demonstration applications are provided with
the installation of Genero Web Client:
http://<myApplicationServer>:6394/wa/r/Edit
http://<myApplicationServer>:6394/demos.html
The latter URI displays a list of the available demonstration
programs.The Demos application is provided with the installation files, and is
pre-configured and ready to run.
Web Server
- Check the installation of your application server (as stated in the
previous paragraph).
- Ensure that your web server is correctly configured by accessing a static page
(such as index.html)
- Launch a demonstration program using a URI inclusive of the Web server
connector.
http://<myWebServer>/cgi-bin/fglccgi/wa/r/myApp
Note: On Windows platforms, when connecting via a Web server, you must include the extension when calling fglccgi.exe, as shown in the following URL:
http://<web_server>/cgi-bin/fglccgi.exe/demos.html
Back to the top
With IIS 6.x, running cgi or isapi is disabled by default. To use fglccgi.exe or fglcgisapi, you need to enable their execution.
- In the IIS manager console, go to the "Web Service Extension".
- Select "CGI Extensions".
- Click on "Allow".
- Repeat this process with "ISAPI Extensions".
Back to the top