====== Setup Proline Suite with Proline-Admin (command-line)======


You must first configure Proline-Admin since this component is used to create the databases needed by Proline.

===== DataStore =====


Edit the configuration file ''config/application.conf'' located in the Proline-Admin folder. Then perform the datastore setup by running the dedicated script.

The ProlineAdmin program files are located in the ".\admin" sub-folder of the Proline installation directory if you used the Windows installer. Otherwise they should be in the folder obtained after Proline Admin GUI archive file extraction.

==== Configuration files ====

To allow Proline Admin to access to Proline DataStore, you should modify the application.cong file located under the config foler of your Proline Admin installation directory.

<code>
server-config-file = "" 
pwx-config-file = ""
postgresql-data-dir = ""

proline-config {
  driver-type = "postgresql" // valid values are: h2, postgresql or sqlite
  data-directory = "/Path/to/Proline/Data"  //Not used actually...
}

auth-config {
  user="<user-proline>"  //!! SET TO Database Proline user login
  password="<proline_user_password>" //!! SET TO Database Proline user password
}

host-config {
  host="your_postgresql_server_host"  //!! Do NOT put "localhost", but the real IP address or fully qualified name
  port="5432" //or other port used to access your DBMS
}
...
</code>

__Note__: 
  * default naming scheme of databases created by Proline can be modified by editing ''config/application-<dbtype>.conf'' file.
  * Other parameters shouldn't be modified unless specific usage. 
  * ''server-config-file'' and ''pwx-config-file'' may only be used when using [[setupguide:setup_with_prolineadmin_gui|Admin GUI]] configuration editor


** Do not confuse: **
  * 'data-directory' under 'proline-config': indicates where to store Proline data (e.g. exports).
  * 'postgresql-data-dir': references the PostgreSQL data directory (for ProlineAdmin purposes). \\

==== Setup ==== 

Once all configuration have been done, run from the Proline-Admin installation directory :

Under Windows
<code>
> setup_proline.bat
</code>

Under Linux
<code>
> setup_proline.sh
</code>


=====  Proline Server =====

When using command line configuration, you should manually edit and configure Proline Server file (application.conf)


The server folder is located in the ".\ws" sub-folder if Windows installer has been used or in the folder where you have unzipped the "Proline Server" archive. 
This folder should contain a sub-folder named ''ProlineWeb-Core-<x.y.z>''.

The configuration file is located at ''<proline_server_folder>\ProlineWeb-Core-<x.y.z>\Proline\WEB-INF\classes''. \\ 

==== Configure the datastore ====

Edit the ''application.conf'' file in the same way you did it for ProlineAdmin (see [[#Configuration files]]).
If your configuration is valid, the Proline Server will be able to use the datastore you've created using Proline Admin.

==== Configure the mount-points ====

Result identification files (Mascot dat,  OMSSA or X!Tandem) as well as mzDB files (for the XIC Quantitation process)  are only browsed from Proline Server side. 

Administrator must configure the target directory/ies in the entry ''mount_points'' in the ''application.conf'' file

!! Important: on a Windows server installation, please use UNC style to access remote disks instead of mounted disk on letters. Otherwise Proline won't be fully functional.
ex: use \\\\my_server\\disk\\folder 
instead of a mounted disk on Z: (Z: mounted as \\my_server\\disk\\folder)

Mascot dat or OMSSA path should be configured in ''result_files'' sub-entry, administrator can add one or more mappings as ''label = "<absolute/directory/path>"''.
mzDB files path should be set under ''mzdb_files'' sub-entry.

Label can be any valid string chosen by Administrator to help user identify mount_point. If multiple repositories are defined, labels must be different.

Configuration examples:
<code>
mount_points {

  result_files {
    mascot_data = "Z:/"  //under window environement
    omssa_data = "/local/omssa/data" //under linux environement
    xtandem_data = "U:/"
    ...
  }
  ...
  
  mzdb_files {
  }

}
</code>