Proline

Note : All the settings shown on the screenshots only stand for examples. You must adapt them to your needs.

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

A shortcut “Proline Admin” is available in the Windows Start Menu, under the Proline folder.

Execute the start.sh script located in the folder obtained after Proline Admin GUI archive file extraction.

The default configuration file config/application.conf is loaded. You can alternatively edit this file (see "Configuring ProlineAdmin" section below) or select another .conf file of the same format. To select a file, go to the “Select configuration files” menu. A dialog opens, offering you to chose 2 files:

• the first one is the ProlineAdmin configuration file, mandatory to use configure, setup and upgrade Proline, as well as create users and projects;
• the second one is the Proline server configuration file. This one is optional for the actions described above, but mandatory to edit Proline Server configuration (see section 'Configuring the mount-points'). Additionally, if this file is selected, it will be automatically synchronized with ProlineAdmin's configuration file.

To edit Proline configuration file(s), press the “Edit Proline configuration” button. You can now edit your file(s) in the newly opened window, and save it.

Do not confuse:

• 'Data directory' under 'Proline': indicates where to store Proline data (e.g. exports).
• 'PostgreSQL data directory' (Menu → Select PostgreSQL data directory): references the PostgreSQL data directory (PostgreSQL configuration files). This one is needed to configure your PostgreSQL instance through ProlineAdmin-GUI (see PostgreSQL optimization).

Finish the Datastore setup by clicking the newly available button “Set up Proline”.

Note: This functionality will be disabled if Proline is already set up or if Proline configuration is invalid.

The server program files are located in the “.\ws” sub-folder of the Proline installation directory.

Open the folder where you have unzipped the “Proline Server” archive. The Proline server 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.
As shown previously, use 'Menu → Select Proline configuration files' to select Proline Server configuration file.

Go back to 'Edit Poline configuration'. Note that the section named 'Mount points' should now be enable. The Proline Server configuration file will be synchronized with ProlineAdmin configuration when you press the 'Save' button. This allow Proline Server to use the datastore you previously defined with Proline Admin.

You can save it now, or wait for mount points to be configured (see next section).

Administrator must configure the target directory/ies in 'Mount points' section of the dialog 'Edit Proline configuration'.

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.

!! 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)

Input files should be set in the 'RAW files' sub-section; Mascot dat or OMSSA path should be configured in the 'Result files' sub-section; mzDB files path should be set in the 'mzDB_files' sub-section. Several alias/full_path pairs can be used or each.

Aliases can be any valid string chosen by the administrator to help the users identify a mount_point. If multiple repositories are defined, aliases must be different.

Go back to Installing the Porline suite: Running the server .