fglgar

The fglgar is a tool for packaging applications for deployment as standalone on a server or on any Web server with Genero Application Server (GAS).

Syntax

fglgar command [options] [ argument [...] ]
  1. command is an fglgar command, it can be one of the following:
    • gar: To create a Genero Archive file (.gar).
    • war: To create a Java Web Archive file (.war).
    • run: To execute an application packaged in a .war (including a .gar).
  2. options are specific to each command as described below.
  3. argument is a parameter for command.
The fglgar tool supports the following commands:
  • fglgar gar [options]
    The gar command creates a .gar Genero Archive file. Options are described in Table 2.
  • fglgar war [options]
    The war command creates a .war Java Web Archive file embedding a Genero Archive and GAS in a jar file (JGAS). It also provides the option to add a customized Genero Browser Client (GBC). Options are described in Table 3.
  • fglgar run [options]
    The run command executes a Genero Archive application previously packaged as a .war file. Options are described in Table 4

Options

Table 1. fglgar options without command
Option Description
-V or --version Displays version information.
-h or --help Displays options for the tool.
Table 2. fglgar gar options
Option Description
-h

--help

Displays help for the gar command.
-v

--verbose

Displays the verbose output of additional information.
-q

--quiet

Operates in silent mode
-o output_file_path

--output output_file_path

The relative or absolute path to the archive file to create. If not specified, the archive defaults to the name of current directory where the command is run.
-s directory

--input-source directory

Directory to archive.
--resource directory Specifies the Genero Archive resource directory where the application's public images are found. (These are common or can be shared by all your applications.)
--trigger-component component_name Specifies Genero Archive application trigger execution component. (Optional).
--deploy-trigger command (Optional) Specifies the Genero Archive trigger command to deploy the application. Generates a MANIFEST file, if none exists. Raises errors if a MANIFEST already exists.

--undeploy-trigger command

(Optional) Specifies the Genero Archive trigger command to undeploy the application. Generates a MANIFEST file, if none exists. Raises errors if a MANIFEST already exists.
--application application_file Specifies the application configuration or executable file. If you specify executable (42r or 42m) files instead of xcf file, xcf files are created automatically based on default configuration defined in the GAS as.xcf file. Multiple applications may be specified. Generates a MANIFEST file, if none exists. Raises errors if a MANIFEST already exists.
--service application_file Specifies the service configuration file or executable.If you specify executable (42r or 42m) files instead of xcf file, xcf files are created automatically based on default configuration defined in the GAS as.xcf file. Multiple applications may be specified. Generates a MANIFEST file, if none exists. Raises errors if a MANIFEST already exists.
Table 3. fglgar war options
Option Description
-h

--help

Displays help for the war command.
-v

--verbose

Displays the verbose output of additional information.
-q

--quiet

Operates in silent mode
-o output_file_path

--output output_file_path

Specifies the relative or absolute path to the war file to create. If not specified, the war defaults to the name of the current directory where the command is run.
-g gar-file

--input-gar gar-file

Specifies the Genero Archive (gar) file you want to use to create the war. This option is mandatory.
-w directory

--web-content directory

Specifies Java Web content directory. This is optional but it allows you specify a different Java Servlet content directory if needed to package some additional Java applications or files. See the Java documentation.
-c directory

--gbc directory

Specifies your customized Genero Browser Client (GBC). By default, the gbc installed with the FGLGWS package is embedded in the war file.
Table 4. fglgar run options
Option Description
-h

--help

Displays help for the run command.
-w war-file

--war war-file

Specifies the war file for input.
-p server_port

--http-port server_port

Specifies the port where the GAS is accessible. If not set, the default is 8080.
-P server_port

--https-port server_port

Specifies the port for secure connections (HTTPS) on the server where the GAS is accessible. If not set, the default is 443.
-E directory

--resource-overwrite directory

Specifies the GAS resources you want to overwrite, such as the directory of the logs. For example,
-E log.file.path=`pwd`

Usage

The fglgar command line tool is used to create Genero archive (gar), or Java Web archive (war) files. You can use it for the following methods of application deployment:
  • You can deploy Web applications or services in a gar file on any Web server where the GAS is installed.
  • You can deploy Genero applications and services on a Java EE server like Apache Tomcat®, or Glassfish (via war) and then with the browser you can access your applications and services.
  • You can also run Web applications or services in a Java servlet (war) as standalone on a machine (without any Java EE Web server) and access your applications and services via a browser.
In other words, the fglgar tool allows you to develop, package, and test your Web application or service on a browser without GAS being installed on the server.
Important:
  • FGLGWS needs to be installed on the server to interpret the Genero 4GL applications and services.
  • You need a Java Runtime Environment (JRE) version that is at least version 1.8 or greater.
For usage options, run the command fglgar without any other parameters or with the help ( -h ) option.
Tip: For help with using a specific command, for example gar, running fglgar gar, is the same as running fglgar gar --help.