This page is an obsolete help file. Please see following description : Install and set up Proline
The Proline suite is based on (different components). The following documentation describes the installation procedure for each of this component:
Download the automated installer from the Proline website (http://proline.profiproteomics.fr/download/).
Warning: Be sure to run the executable file as “administrator” to be able to install third-party dependencies such as PostgreSQL.
The wizard will guide you through the installation process.
By default, the installer will unpack all components on the computer. However, it is possible to install the Proline components on distinct computers if it fits better your hardware architecture.
For users who prefer manual installation or without administrator privileges, an archive file of the distribution is also available. You can follow the installation procedure described in the next section.
There is no automated installer at the moment.
First check that all requirements are first installed on the computer.
Then download the zip archive containing Proline components from the dedicated website(http://proline.profiproteomics.fr/download/).
The Proline Server archive file contains three others archives corresponding to the (different components).
Unzip these components on the appropriated computer (Proline Server and Proline Admin is recommended to be on the same computer. Sequence Repository is recommended to be installed on the computer where fasta files are accessible)
Once Proline is installed you must initialize Proline datastores and settings.
On this purpose, the Proline-Admin software is provided with the Proline Suite. It is available as a command-line tool or as Graphical Interface called Proline-Admin GUI.
We will guide you through this process, step by step, using both these tools.
You can either use the graphical interface ProlineAdmin GUI ⇒ How to
or use the command-line tool ProlineAdmin ⇒ How to .
Administrator can change default amount of memory used by the server in the jetty-runner.bat /jetty-runner.sh file. If the server is configured with large amount of memory, it is recommanded to increase this value.
Change the value of -Xmx option: Xmx4g ⇒ -Xmx9g to pass from default 4 GO to 8GO.
Run jetty-runner.bat (or jetty-runner.sh on linux system) to start the jetty server. You should now be able to access ProlineWeb-Core by typing http://localhost:8080/proline or http://<host>:8080/proline in your favorite browser. The following message must appear:
ProlineWeb-Core working ! Number of IVersion services : <X> fr.proline.core.wsl.Version Module: ProlineWeb-Core Version: <XXX> fr.proline.module.parser.omssa.Version Module: PM-OmssaParser Version: <YYY> fr.proline.module.parser.mascot.Version Module: PM-MascotParser Version:<XYZ> fr.proline.admin.Version Module: Proline-Admin Version: <ZYW> fr.proline.util.ScalaVersion Module: ProFI-Commons-Scala Version: <YZX> fr.proline.util.JavaVersion Module: ProFI-Commons-Java Version: <YXZ> fr.proline.core.service.Version Module: Proline-OMP Version: <WYZ>
Even if this is an optional module it is recommended to install it, mostly if you want to view the proteins sequences in the user interfaces!
It can be installed on the same machine running the Proline Server. However as this module will parse the mascot fasta files to extract sequence and description from it, it will be more efficient if installed on the computer executing your Mascot Server. In any case, you should also be able to access to the PostgreSQL server from the computer where Sequence Repository is installed.
Select this component from the wizard of the automated installer. The corresponding program files will be located in the “.\seqrepo” sub-folder of the Proline installation directory.
This module is distributed as an archive file (embedded in Proline Server archive) and need to be extracted in your preferred folder to be installed.
Configuration files are located under the “<seqrepo_folder>/config”.
Datastore description
pg_uds.properties file define datastore description to access to the UDS database (for postgresql database):
javax.persistence.jdbc.driver=org.postgresql.Driver javax.persistence.jdbc.url=jdbc:postgresql://<host>:<port>/<uds_db> javax.persistence.jdbc.user=<user_proline> javax.persistence.jdbc.password=<proline_user_password>
note:
javax.persistence.jdbc.url=jdbc:postgresql://<host>:5432/uds_db
application.conf for Proline Admin or Proline WebCoreProtein description parsing rule
As this module is used to extract Protein Sequence, description from a fasta file for a specific protein accession, it is necessary to configure the rule used to parse the protein ACC, from fasta description line. This is similar to the rules specified in Mascot Server. To do this, retrieve-service.properties file should be edited. In this file it is necessary to escape (this means prefix with '\') some characters: '\' , ':' and '='
# Name of the UDS Db configuration file (Java properties format)
fr.proline.module.seq.udsDbConfigurationFile=pg_uds.properties
# Paths must exist (regular file or directory) and multiple paths must be separated by ';' character
fr.proline.module.seq.localFASTAPaths=Y\:\\sequence;D\:\\Temp\\Admin\\FASTAs
# Java Regex with capturing group for SEDbInstance release version string (CASE_INSENSITIVE)
fr.proline.module.seq.defaultReleaseRegex=_(?:D|(?:Decoy))_(.*)\\.fasta
# UniProt style SEDb (FASTA file name must contain this Java Regex CASE_INSENSITIVE) multiple Regex separated by ';' character
fr.proline.module.seq.uniProtSEDbNames=\\AUP_;ISA_D
# Java Regex with capturing group for SEDbIdentifier value (without double quote)
# UniProt EntryName ">\\w{2}\\|[^\\|]*\\|(\\S+)"
# UniProt UniqueIdentifier (primary accession number) ">\\w{2}\\|([^\\|]+)\\|"
# GENERIC Regex ">(\\S+)"
fr.proline.module.seq.uniProtSEDbIdentifierRegex=>\\w{2}\\|[^\\|]*\\|(\\S+)
Note:
For other fasta files the protein accession will be extracted by using the string before the first blank space.