Introduction

prolinga 1 prolinga ProLinga script to start the ProLinga run-time binary prolingarun. prolinga passes on all arguments as documented for prolingarun. Introduction The prolinga is a small wrapper script to enable any environment preparations before starting up the binary prolingarun. Environment settings as shared library paths can be set before starting the application. All arguments are passed on to prolingarun without any syntax or contents checking. Options Any options can be set and all options are passed on to the binary prolingarun. prolingarun 1 prolingarun ProLinga run-time environment. prolingarun prolingarun prolingarun Introduction The prolingarun program is a 4GL interpreter and contacts the prolinga network environment to access various data sources. prolingarun will get the information as hostname and TCP portnumber of the run environment from the configuration file etc/prolingaruncfg.xml . Options Name of 4GL application to start. Name of user to logon as. Suppress the connection dialog box. (Not applicable for stand-alone configurations.) Displays version information. Configuration file to be used. (Optional) prolingarund 1 prolingarund Run Web Service daemon. prolingarund prolingarund Introduction The prolingarund 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 Run Command requests to arrive. Since the process is a fork, the prompt will return. Projects like ProLinga-Web can now be used to send requests to this Web Service. prolingarund will get the information as hostname and TCP portnumber where the service needs to bind to from the configuration file etc/prolingaruncfg.xml. An example automatic Run startup script for Linux is available as file prolingarund.init. This file can be copied and renamed to /etc/rc.d/init.d/prolingarund 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/prolingarund 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. Options Configuration File 1 Configuration File File containing settings for the run environment. Introduction ProLinga-Run comes with a configuration file where various service endpoints can be entered. Default installation of ProLinga-Run will put the default service file prolingaruncfg.xml in the etc directory. A default configuration file looks like this: m3 8005 6 m3 8005 3 /tmp/run.log 5 6 m3 8001 m3 8003 m3 8007 glade-2 ]]> There is a section for the client and server part available. The setup of this configuration file is such that it can be combined with configuration files from other ProLinga projects. Configuration Client Options The name or IP number of the host where to connect to, to present a Web Command. The TCP port of the host where to connect to, to present a Web Command. Configuration Server Options The name or IP number to bind to when starting prolingarund as a Web Service. The port number to bind to when starting prolingarund as a Web Service. Number of threads when starting prolingarepd 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 Web Command XML document before it is returned over the network to the Run caller/client. 0=No Compression, 9=Best Compression. The name or IP number the Repository Web Service. The port number the Repository Web Service. The name or IP number the Validate Web Service. The port number the Validate Web Service. The name or IP number the Data Web Service. The port number the Data Web Service. The path and filename of the external screen painter to be used.