Differences

This shows you the differences between two versions of the page.

--- public_namespace:neurolog_middleware_prototype [2008/03/12 17:15] – montagnat
+++ public_namespace:neurolog_middleware_prototype [2009/01/09 14:35] (current) – gaignard
@@ Line 2: / Line 2: @@
 This page describes the current status of the NeuroLOG middleware prototype. It gives installation and configuration instructions.
@@ Line 8: / Line 9: @@
 The software is distributed in the following archive:
-  * [[http://egee1.unice.fr/NeuroLOG_Middleware-0.1.0.tgz|NeuroLOG middleware v0.1.0 archive]]
+  * [[http://egee1.unice.fr/NeuroLOG_Middleware-0.1.1.tgz|NeuroLOG middleware v0.1.1 archive]]
 This version was tested under linux only.
@@ Line 29: / Line 30: @@
   * ''bin/nlog_client'' for the NeuroLOG client.
 Note that if the ''dist'' directory is not deployed in the HOME directory of the user, the ''nlog_*'' scripts need to be edited to change the second line (JAR variable containing the path to the main NeuroLOG jar file inside the dist directory). The first line (Java VM location may also need to be updated depending on your installation.
@@ Line 55: / Line 58: @@
   - port **63878**: Registry unsecured interfaced, only used for new site requests initialization
-The NeuroLOG registry includes two separate programs: a daemon server and a graphical interface for the administrator. Upon successful installation, both programs are started. The interface can be shut down through the ''File -> Exit'' menu while the daemon keeps running.
+The NeuroLOG registry includes two separate programs: a daemon server and a graphical interface for the administrator. Upon successful installation, both programs are started. The interface can be shut down through the ''Administration -> Exit'' menu while the daemon keeps running.
@@ Line 72: / Line 75: @@
 **Carefully check the fingerprint value of the certificate you are importing as the complete trust chain depends on it**. If you are connecting to the official NeuroLOG project Registry service, the finger print should exactly match:
-  ''6B:27:87:FE:13:3B:C2:66:A5:E7:17:07:68:AD:2C:A2:B9:42:8E:71''
+B:27:87:FE:13:3B:C2:66:A5:E7:17:07:68:AD:2C:A2:B9:42:8E:71
 If you are connecting to a different service, the fingerprint will be different. Check its value with your Registry administrator.
@@ Line 83: / Line 86: @@
   - port **63880**: Server unsecured interfaced, only used for new client requests initialization
-The NeuroLOG Site Server includes two separate programs: a daemon server and a graphical interface for the administrator. Upon successful installation, both programs are started. The interface can be shut down through the ''File -> Exit'' menu while the daemon keeps running.
+The NeuroLOG Site Server includes two separate programs: a daemon server and a graphical interface for the administrator. Upon successful installation, both programs are started. The interface can be shut down through the ''Administration -> Exit'' menu while the daemon keeps running.
 === If you are a user ===
@@ Line 92: / Line 95: @@
   * Unsecured interface port: 63880
-The installation procedure is a two steps process. On the first run, a user certificate request is generated and sent to the site CA administrator. The process then normally exits, waiting for the site administrator to sign the request. You will be notified by phone or email when your request is ready to be retrieved. You can then restart the program to proceed with the second step. During the second step, the signed user certificate is retrieved. The site CA certificate is then imported. You are requested to validate the site CA certificate fingerprint as follows:
+The installation procedure is a two steps process. On the first run, a user certificate request is generated and sent to the site CA administrator. The process then normally exits, waiting for the site administrator to sign the request. You will be notified by phone or email when your request is ready to be retrieved. You can then restart the program to proceed with the second step. During the second step, the signed user certificate is retrieved. The site CA certificate is then imported. You are requested to validate the site CA certificate fingerprint. **Carefully check the fingerprint value of the certificate you are importing as the complete trust chain depends on it**. Contact your site administrator to verify its value.
-{{public_namespace:registry-fingerprint.png}}
+On completion, the client graphical interface will start.
-**Carefully check the fingerprint value of the certificate you are importing as the complete trust chain depends on it**. Contact your site administrator to verify its value.
-On completion, the client graphical interface will start.
+===== Normal runs =====
+On the first run, the NeuroLOG Registry service and the NeuroLOG Site Server will fork a daemon process executing in background even if the administator interface is terminated. On subsequent runs, the program auto-detects if a daemon is running. If a daemon is found, only the administrator interface is started and it is reconnected to the daemon. If no daemon can be found, a new daemon is forked. The administrator interface can be used to terminate a running daemon through the ''Administration -> Kill daemon'' menu.
 ===== Configuration =====
+The services are normally self-configured during the installation process. If you need to change some configuration parameters later, the text configuration files can be edited. Configuration changes require an application restart to be taken into account.
+The default configuration files are located in ''~/.neurolog''. The default files are:
+  - ''registry.config'' for the NeuroLOG Registry service
+  - ''server.config'' for the NeuroLOG Site Server
+  - ''client.config'' for the NeuroLOG client
+Note that the default configuration file location can be overriden by the ''-c'' option.
 ===== Sources ======
+The source files are available through the [[http://nyx.unice.fr/svn/neurolog|NeuroLOG SVN repository]]. A [[http://nyx.unice.fr/projects/neurolog|TRAC server]] is also available for following the developments.
+===== Troubleshooting =====
+The services logs are written to a file. The exact file name is configured during the services installation phase. By default it is located in the ''~/log'' repository. If it was configured differently, the log file location can be found from the service configuration file. Also note that the ''-l'' command line option may be used to override the log file location.
 ===== TODO =====
+The prototype only provides basic distribution facilities and data importation capability currently. Most components still need to be integrated. The data importation prototype available is not secured in the sense that images are not anonymized and files are not encrypted.