• The Proline Web Extension is based on the use of MongoDB database engine. You need to download it and install it either on the computer which will host the Proline Web Extension server, or any other network-accessible computer. You will find the installation files on this page : http://www.mongodb.org/downloads
• Download and run the Proline Web Extension Installer

If you installed your MongoDB database on a different computer than the Proline Web Extension server, you'll need to edit the Proline Web Extension configuration file :

• Go to the installation directory of your Proline Web Extension server
• Go to the “config” folder and open the “pwx.conf” file with any text editor (like Window default Notepad)
• Setup the “mongo_db_config” “host” parameter with the right URL to your MongoDB server (ex: 'mongodb:185.532.02.33:27017' or 'mongodb:distant_computer_name:27017')
• There is a “mongo_db.bat” script file in your proline web installation directory. Right-click on it and click “Modify” in order to set up the right path to your MongoDB Installation. Replace the “C:\Program Files\mongodb-win32-x86_64-2008plus-2.4.6\bin\mongod.exe” -dbpath=“E:\mongodb” statement with the path to your mongod.exe executable, and the path to the directory where data will be stored in the “dbpath” param
• If you defined a specific user and password on your MongoDB server, you should add them as “user:“user_name” and “password:“your_password” parameters

If MongoDB is installed on the same computer as the Proline Web Extension server, you don't need to configure anything at this time.

• First, please make sure that MongoDB is running. If it's not, please start it manually. Check out the configuration procedure to make sure your “mongo_db.bat” script file is correct (you must set up the path to your mongodb server program and the directory where your data will be stored)
• In order to start the Proline Web Extension server components, go to its installation folder, and launch the “start.bat” script. This script will start the following programs :
  • The Gearman service : this is a program used to supervise and manage heavy tasks requests that will be executed by the PWX Daemon program.
  • The PWX Daemon, that handles :
    • the heavy works that need to be ran in a separated Perl process
    • the events listenning and dispatching.
  • The PWX “Mojolicious” Program that is the actual web server. It runs the Web Desktop and the Applications.

• The connection between the desktop and the proline core server is provided by the “proline” service. This service is included with the Proline Web Extension package, but it needs to be registered and configured as a service for your Web Desktop server. The following steps will explain how :
• To set it up, go to “Start”>“Administration”>“Services Manager”. On the “Services Directory Browser”, you should see the “proline” service appear in the the table. Click on its name to select it, and click the “Register” button. You should be notified when it has been registered properly.
• 
• Once the registration is done, click on the “Registered Services” tab, select “proline” in the Grid Table, and then click on “Configure”

• Here are some param values you can use :
  • ws_host is the adress of the Proline Web Core server. Use the name or the IP adress of the server to set the URL. Examples :
    • http://servername:8080/proline
    • http://localhost:8080/proline
    • http://198.0.13.37/proline (replace 198.0.13.37 by the right IP adress)

• uds_db_dsn is the UDS database connexion configuration (DSN stands for Data Source Name). It has the following format dbi: + name of the Driver (Pg for PostgreSQL, SQLite for SQLite) + :db_name= + name of the Postgre SQL database (uds_db or path to the SQLite file D:/path/to/uds_db.sqlite) + ;host= + Postgre SQL erver adress or name + ;port= + port of the Postgre SQL server. The host and port params are not needed if you use a SQLite database. Here are some config examples :
  • dbi:Pg:dbname=uds_db;host=localhost;port=5432
  • dbi:SQLite:dbname=D:/proline/data/uds_db.sqlite
• data_root is the directory where the user projects data will be stored. You can use something like D:/proline/data. Make sure this directory exists on your disk, Proline won't create it automatically if it doesn't.
• ps_db_dsn is equivalent to the uds_db_dsn param but points to the PS Database. Set up the connection config the same way you did it for the UDS Database.
• pwd_mascot_data_root is the Directory where the Proline Web Extension server will browse mascot result files. Set it up with a simple path like D:/proline/mascot/data or a network adresse like \\servername\mascot\data. Make sure this directory exists on your disk, Proline won't create it automatically if it doesn't.
• pwc_mascot_data_root is the path from which the Proline Web Core will access this directory. You can leave it blank if you configured it in the Proline Web Core config file. It can be useful if you installed Proline Web Extension and Proline Web Core on two different servers, and if one of them runs on Linux, for example
• db_username is the user name used by the PostgreSQL connection. not needed if you use SQLite. The default PostgreSQL user is ” *postgres* ”.
• db_password is the password you gave to the PostgreSQL user specified above.
• raw_files_root is the path to your .raw files root directory
• mzdb_files_root is the path to your .mzdb files root directory

• You must set up the right connexion informations and data directories in order to access the Proline Core Web services properly
• You must set up two path to the mascot data root folder : one for the desktop (pwd_mascot_data_root) and one for jetty (pwc_mascot_data_root). These to paths must point to the same folder. There are two of them because you need the Proline Web Extension server and the Proline Web Core server may not access it via the same way. Fill it the right way so the both servers can access the same directory. If they are on the same network and use the same OS (i.e Windows), you can set up the same path on both fields.
• Set up the SQL Server connection settings, and the path to the raw files and mzdb files root directory.
• Once it's done, simply click “Save Configuration”
• To make sure that the “admin” user is registered in the UDS DB, you need to logout and login, in order to make the Proline Service to check your status in the UDS DB, and create your account if you're not registered yet