prolingavalclient1prolingavalclientcommand line Validate network/SOAP client toolprolingavalclientprolingavalclientIntroduction
The prolingavalclient program parses the input Validate Command XML file and
sends this as a request to the Validate Web Service. The response of
this request is placed in the output XML file as specified as the 2nd argument.
prolingavalclient will get the information as hostname
and TCP portnumber of the
Web Service from the configuration file etc/prolingavalcfg.xml.
Options
The name of the XML file containing the configuration. If no file is
specified, the default will be used.
The name of the XML file containing a Validate Command.
The name of the XML file containing the result of a Validate Command.
prolingavalparser1prolingavalparsercommand line Validate parser and debugging toolprolingavalparserprolingavalparserIntroduction
The prolingavalparser program parses a text file
4GL_text_file_name containing ProLinga 4GL code
and outputs the result to stdout (screen). The 4GL logic will get
validated against objects of the application_name.
The argument transform_only is optional and
only the Logic transformation step to a RunControl will performed without
validation of the objects.
Options
The name of the XML file containing the configuration. If no file is
specified, the default will be used.
Perform only the transformation step in case the object is Logic.
The name of the application in the Repository against which objects will
get validated.
The name of the text file containing ProLinga 4GL logic.
prolingavald1prolingavaldValidate Web Service daemonprolingavaldprolingavaldIntroduction
The prolingavald program can be called from the command line without any arguments.
The program will then initialize and run as a daemon in memory waiting for Validate
Command requests to arrive. Since the process
is a fork, the prompt will return. Programs like
prolingavalclient can
now be used to send requests to this Web Service. prolingavald will get the information
as hostname and TCP portnumber where the service needs to bind to
from the configuration file etc/prolingavalcfg.xml.An example automatic Validate startup script for Linux is available as
file prolingavald.init. This file can be copied and renamed to
/etc/rc.d/init.d/prolingavald and initialized using /sbin/chkconfig.
Make sure all paths are correct in this file.
The Web Service can then be started as /etc/rc.d/init.d/prolingavald
start. To stop the
argument stop can be used.
You need to have root access for this. The binary rpm installation will perform
all these steps automatically.Optionsprolingavalexec1prolingavalexeccommand line Validate access toolprolingavalexecprolingavalexecIntroduction
The prolingavalclient program parses the input Validate Command XML file and
presents this as a request to the Validate engine. The response of
this request is placed in the output XML file as specified as the 2nd argument.
prolingarepexec will get the information as Validate name and directory
from the configuration file etc/prolingavalcfg.xml.
Options
The name of the XML file containing the configuration. If no file is
specified, the default will be used.
The name of the XML file containing a Validate Command.
The name of the XML file containing the result of a Validate Command.
Configuration File1Configuration FileFile containing settings for the Validate environmentIntroduction
ProLinga-Validate comes with a configuration file where various variable settings
can be entered. Variables like the name of the Language Definition file and
the name of the host where the Repository Web Service is running for instance.
Default installation of ProLinga-Validate will put the default configuration file
prolingavalcfg.xml in the etc directory.A default configuration file looks like this:localhost80030localhost80033/tmp/prolingaval.log50/usr/share/prolinga/langvalid.xmllocalhost80010
]]>
There is a main section for the client program and for the local/stand alone
programs. The setup of this configuration file is such that it can be combined with
configuration files from other ProLinga projects.
Client Options
The name or IP number of the host where to connect to, to present
a Validation Command.
The TCP port of the host where to connect to, to present
a Validation Command.
Level of compression to be used on the Validate Command XML
document before it is send off over the network to the
Validate Web Service. 0=No Compression, 9=Best Compression.
Server Options
The name or IP number of the host where to bind to when
starting prolingavald as a Web Service.
The TCP port of the host where to bind to when starting
prolingavald as a Web Service.
Number of threads when starting prolingavald
as a Web Service. This means that up to NumberOfThreads
requests can be served simultanously, before they are queued.
Name of the file where logging and debug info will be written to.
The level of logging. 0=No Logging, 2= +Messages/Errors, 3= +Soap request/response info.
Level of compression to be used on the Validate Command XML
document before it is returned over the network to the
Validate caller/client. 0=No Compression, 9=Best Compression.
Name of the file that holds the 4GL grammar rules and syntax definitions.
The name or IP number of the host where to connect to
get/put Repository Objects.
The TCP port of the host where to connect to
get/put Repository Objects.
Level of compression to be used on the Repository Command XML
document before it is returned over the network to the
Validate caller/client. 0=No Compression, 9=Best Compression.