prolingadatclient 1 prolingadatclient command line Data network/SOAP client tool prolingadatclient --config config_file_name.xml --in input_DC_file_name.xml --out output_DC_file_name.xml prolingadatclient --version The prolingadatclient program parses the input Data Command XML file and sends this as a request to the Data Web Service. The response of this request is placed in the output XML file as specified as the 2nd argument. prolingadatclient will get the information as hostname and TCP portnumber of the Web Service from the configuration file etc/prolingadatcfg.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_DC_filename.xml The name of the XML file containing a Data Command. output_DC_filename.xml The name of the XML file containing the result of a Data Command. prolingadatd 1 prolingadatd Data Web Service daemon prolingadatd prolingadatd --version The prolingadatd 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 Data Command requests to arrive. Since the process is a fork, the prompt will return. Programs like prolingadatclient can now be used to send requests to this Web Service. prolingadatd will get the information as hostname and TCP portnumber where the service needs to bind to from the configuration file etc/prolingadatcfg.xml. An example automatic Data startup script for Linux is available as file prolingadatd.init. This file can be copied and renamed to /etc/rc.d/init.d/prolingadatd 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/prolingadatd 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. Configuration File 1 Configuration File File containing settings for the Data environment ProLinga-Data comes with a configuration file where various variable settings can be entered. Variables like the name of the host where the Data Web Service is running for instance. Default installation of ProLinga-Data will put the default configuration file prolingadatcfg.xml in the etc directory. A default configuration file looks like this: localhost 8007 0 localhost 8007 3 /tmp/prolingadat.log 5 0 ]]> 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 Validation Command. ClientPort The TCP port of the host where to connect to, to present a Validation Command. ClientCompressionLevel Level of compression to be used on the Data Command XML document before it is send off over the network to the Data Web Service. 0=No Compression, 9=Best Compression. ServerHost The name or IP number of the host where to bind to when starting prolingavald as a Web Service. ServerPort The TCP port of the host where to bind to when starting prolingavald as a Web Service. NumberOfThreads Number of threads when starting prolingadatd 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 Data Command XML document before it is returned over the network to the Data caller/client. 0=No Compression, 9=Best Compression. Data Source Configuration File 1 Data Source Configuration File File containing (access) settings for the data providers. One of the problem LibGDA solves is the naming of data sources. Every database system has it's own way of defining names for it's databases. For example MySQL uses the hostname, port number, and the name of the database. Other databases, like Solid use the hostname and port number only. Because the client does not need all these details, the libgda configuration defines all the properties of such a data source, so that the correct data base server can be contacted. This information is accessed by the client library and sent to the provider, which in turn will parse the string to decide which database must be connected to. An example data source configuration looks like this:

]]> This example shows two different data sources. The first one connects to a MySQL database and the second one to a PostgreSQL database. LibGDA requires that the name of this file is config and lives as either an user file ~/.libgda/config or as a global file in [libgdainstalldir]/etc/libgda/config. Since it is advised to run the ProLinga-Data Web Service as the root user and if you want to configure as a user file for Linux the path and name of this file is then /root/.libgda/config. Future releases will include more help and possibly an utility to configure data sources. To configure data sources other than the examples given, please look at the LibGDA configuration documentation for more information. Alternatively, the product libgnomedb can be build. This product comes with a binary called gnome-database-properties that can be used for configuration. libgnomedb is available at the GNOME DB website. DSN This is the most important entry. The value of this entry is the string sent to the provider so that it knows which datasource to access. How this entry is interpreted by the providers is provider dependent. Description The value of this entry is a short description of the datasource. It is here for convenience only and it is not used for any purpose. Password The password to be used when connecting to (=not logging on to) the database. This is stored in plain text, so be sure you restrict access to the configuration file (~/.libgda/config) to any "dangerous" users. Provider The value of this entry is used as the object ID for the plug-in activation. Username The user name to be used when connecting to (=not logging on to) the database. Provider Notes 1 Provider Notes Provider dependent notes. This section contains some provider dependent notes. Default configuration files live in /var/lib/pgsql/data on Linux Edit file postgresql.conf and search for the setting tcpip_socket and set this to true. tcpip_socket = true Edit file pg_hba.conf and add a line similar as this: host all all 127.0.0.1/32 trust Edit file postgresql.conf and add a line like this: client_min_messages = warning Messages of the type "NOTICE" must be avoided.