prolingarepclient 1 prolingarepclient command line Repository network/SOAP client tool prolingarepclient --config config_file_name.xml --in input_RC_file_name.xml --out output_RC_file_name.xml prolingarepclient --version The prolingarepclient program parses the input Repository Command XML file and sends this as a request to the Repository Web Service. The response of this request is placed in the output XML file as specified as the 2nd argument. prolingarepclient will get the information as hostname and TCP portnumber of the Web Service from the configuration file etc/prolingarepcfg.xml. config_file_name.xml The name of the XML file containing the configuration. If no file is specified, the default will be used. input_RC_filename.xml The name of the XML file containing a Repository Command. output_RC_filename.xml The name of the XML file containing the result of a Repository Command. prolingarepcreate 1 prolingarepcreate command line Repository creation tool prolingarepcreate --config config_file_name.xml repository_name prolingarepcreate --version The prolingarepcreate program creates and initializes a new empty Repository. The physical file name of the Repository will be that of the argument used and the directory will be that as defined as SystemPath in the configuration file etc/prolingarepcfg.xml. If a Repository with the same name already exists in that directory, creation will be ignored so the current Repository will NOT be deleted or reset. config_file_name.xml The name of the XML file containing the configuration. If no file is specified, the default will be used. repository_name The physical file name of the repository to be created. prolingarepd 1 prolingarepd Repository Web Service daemon prolingarepd prolingarepd --version The prolingarepd 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 Repository Command requests to arrive. Since the process is a fork, the prompt will return. Programs like prolingarepclient can now be used to send requests to this Web Service. prolingarepd will get the information as hostname and TCP portnumber where the service needs to bind to from the configuration file etc/prolingarepcfg.xml. Before running the prolingarepd for the first time, a Repository needs to be present. A Repository can be created using prolingarepcreate. After running for the first time files starting with "__" will be created in the Repository database directory. You may need chown/chgrp on these files to allow prolingarepexec to access the Repository as a different user than the user starting up the Web Service (= most likely root). An example automatic Repository startup script for Linux is available as file prolingarepd.init. This file can be copied and renamed to /etc/rc.d/init.d/prolingarepd 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/prolingarepd 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. prolingarepexec 1 prolingarepexec command line Repository access tool prolingarepexec --config config_file_name.xml --in input_RC_file_name.xml --out output_RC_file_name.xml prolingarepexec --version The prolingarepclient program parses the input Repository Command XML file and presents this as a request to the Repository 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 Repository name and directory from the configuration file etc/prolingarepcfg.xml. config_file_name.xml The name of the XML file containing the configuration. If no file is specified, the default will be used. input_RC_filename.xml The name of the XML file containing a Repository Command. output_RC_filename.xml The name of the XML file containing the result of a Repository Command. Configuration File 1 Configuration File File containing settings for the Repository ProLinga-Repository 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-Repository will put the default configuration file prolingarepcfg.xml in the etc directory. A default configuration file looks like this: localhost 8001 6 ProLinga-Repository on localhost localhost 8001 /usr/local/var/prolinga/system 3 /tmp/prolingarep.log 5 6 ]]> 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. ClientHost The name or IP number of the host where to connect to, to present a Repository Command. ClientPort The TCP port of the host where to connect to, to present a Repository Command. ClientCompressionLevel Level of compression to be used on the Repository Command XML document before it is send off over the network to the Repository Web Service. 0=No Compression, 9=Best Compression. ServerHost The name or IP number of the host where to bind to when starting prolingarepd as a Web Service. ServerPort The TCP port of the host where to bind to when starting prolingarepd as a Web Service. SystemPath The path containing the physical XML database files. NumberOfThreads 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. LogFile Name of the file where logging and debug info will be written to. LogLevel The level of logging. 0=No Logging, 2= +Messages/Errors, 3= +Soap request/response info. ServerCompressionLevel Level of compression to be used on the Repository Command XML document before it is returned over the network to the Repository caller/client. 0=No Compression, 9=Best Compression.