postgresql/insertFKsCreatePostgreSQLAll.sql (for PostgreSQL) or
oracle/insertFKsCreateOracleAll.sql (for Oracle)
to create some tables
If you are using MySQL InnoDB must be now the default engine. The my.ini (Windows)/ my.cnf (Linux) must contain the following entry: default-storage-engine=INNODB
If not MASPECTRAS won't work properly (For AAS MyISAM is sufficient). To correct enter: default-storage-engine=INNODB. Stop the AAS; Restart MySQL; Start the AAS
7.2. Go to $JBOSS_HOME/bin
7.3. Start maspectras with
run-maspectras.bat (for Windows) or
run-maspectras.sh (for Linux or Solaris)
and wait until the JBoss started
7.4 Use from /database/initialize/maspectras/
mysql/sequestInitialValuesMySQL.sql (for MySQL) or
e.g. /usr/local/mysql/bin/mysql -u maspectras -p maspectras < /home/maspectras/maspectras/database/initialize/maspectras/mysql/sequestInitialValuesMySQL.sql
e.g. Enter password: maspectras
postgresql/sequestInitialValuesPostgreSQL.sql (for PostgreSQL) or
oracle/sequestInitialValues.sql (for Oracle)
to insert required data
8. Change the Maspectras settings and insert the path to the newly created DATAROOTDIRECTORY
8.1. Open http://localhost:8080
8.2. Click on JMX-Console
8.3. Click on service=ServerSettings
8.4. Use the method setProperty
p1 = DATAROOTDIRECTORY
p2 = /home/maspectras/maspectrasdata/
Be sure that there is a trailing '/' for Linux or a trailing '\' for Windows otherwise you will have problems with the file upload
8.5. Click on invoke
8.6. To check the properties use method „listProperties“
9. Install JClusterService on a UNIX/Linux system (it wont work under Windows and not tested under OSX)
9.1. Create a user under which the jclusterservice should execute the commands
and create a JCLUSTERSERVICEROOTDIRECTORY e.g. /home/maspectras/maspectrasjclusterservice where
the user has access right.
If not already done copy and unpack the maspectras.tar.gz again under the home directory
of the new user. This creates a maspectras directory with all the necessary files.
From there copy all files within maspectras/maspectrasjclusterservice to this directory and make sure that
the user can access the folder. e.g.
groupadd maspectras
useradd -d /home/maspectras -g maspectras maspectras
su - maspectras
mkdir -p /home/maspectras/maspectrasjclusterservice
tar -xzf maspectras.tar.gz
cp -r %extracted path%/maspectrasjclusterservice/* /home/maspectras/maspectrasjclusterservice
chown -R maspectras:maspectras /home/maspectras
# (just to be sure that every file is accessible for the service user execute this command as root)
If you have not already switched to maspectras user, then change to user maspectras (su - maspectras)
9.2. Edit jboss-4.2.2.GA/server/jclusterservice/deploy/JClusterWS.ear/JClusterWSWeb.war/WEB-INF/server-config.wsdd and change to:
<parameter name="attachments.Directory"
value="%installationpath%/jboss-4.2.2.GA/server/JClusterWS/./deploy/JClusterWS.ear/JClusterWS/./deploy/JClusterWS.ear/JClusterWSWeb.war/WEB-INF/attachments"/>
e.g.
/home/maspectras/maspectras/jboss-4.2.2.GA/server/jclusterservice/deploy/JClusterWS.ear/JClusterWSWeb.war/WEB-INF/attachments
If you change the server ports for jclusterservice in bindings.xml, change also the JNDI URL in this file:
<parameter name="jndiURL" value="jnp://localhost:%your_port%"/>
default is:
<parameter name="jndiURL" value="jnp://localhost:21099"/>
9.3. Adapt the path settings to your local installation in jboss-4.2.2.GA/server/jclusterservice/deploy/JClusterWS.ear/JClusterService.jar/usermanagement-utils.properties
sum_users_filepath=JCLUSTERSERVICEROOTDIRECTORY/config/users.xml
e.g.
sum_users_filepath=/home/maspectras/maspectrasjclusterservice/config/users.xml
9.4. Adapt the path settings to your local installation in jboss-4.2.2.GA/server/jclusterservice/deploy/JClusterWS.ear/JClusterService.jar/cluster.properties
9.4.1. The global path settings:
clusterservicedefinition_path=JCLUSTERSERVICEROOTDIRECTORY/config/clusterservice-definition.xml
job_path=JCLUSTERSERVICEROOTDIRECTORY/jobs
jobdefinitions_path=JCLUSTERSERVICEROOTDIRECTORY/job_definitions
e.g.
clusterservicedefinition_path=/home/maspectras/maspectrasjclusterservice/config/clusterservice-definition.xml
job_path=/home/maspectras/maspectrasjclusterservice/jobs
jobdefinitions_path=/home/maspectras/maspectrasjclusterservice/job_definitions
9.4.2. The queueingsystem specific once:
9.4.2.1. Local execution queue
local_execution_job_template_path=JCLUSTERSERVICEROOTDIRECTORY/template/jms-job-definition
e.g.
local_execution_job_template_path=/home/maspectras/maspectrasjclusterservice/template/jms-job-definition
9.4.2.2. Optional if present ... Sun Grid Engine (SGE)
Adapt the paths to the SGE commands
9.4.2.3. Optional if present ... Portable Batch System (PBS/Torque)
Adapt the paths to the PBS/Torque commands
9.5. Install the following applications:
9.5.1. Database repository management initialization:
9.5.2. NCBI-Blast and NCBI-FormatDB
- download from ftp://ftp.ncbi.nih.gov/toolbox/ncbi_tools/ncbi.tar.gz the ncbi toolkit
- install it according to the README from NCBI under JCLUSTERSERVICEROOTDIRECTORY/applications/bin
- copy "blastall" and "formatdb" from "ncbi/build" into JCLUSTERSERVICEROOTDIRECTORY/applications/bin
- copy the whole "data" directory from "ncbi/data" to the location JCLUSTERSERVICEROOTDIRECTORY/applications/data
9.5.3. CLUSTALW2
- download from ftp://ftp.ebi.ac.uk/pub/software/clustalw2/2.0.5/clustalw-2.0.5-src.tar.gz
- install it according to the instructions from EBI under JCLUSTERSERVICEROOTDIRECTORY/applications/bin/
- copy clustalw2 into JCLUSTERSERVICEROOTDIRECTORY/applications/bin
9.6. Adapt the JCLUSTERSERVICEROOTDIRECTORY/config/clusterservice-definition.xml for your local application installation
9.6.1. Change the REPOSITORYMANAGER service definition:
program-path="JCLUSTERSERVICEROOTDIRECTORY/applications/bin/repomanager"
e.g.
program-path="/home/maspectras/maspectrasjclusterservice/applications/bin/repomanager"
and the path parameter:
<parameter position="0" mandatory="true" name="repository" switch="-r">
<parameter-value isdefault="true">JCLUSTERSERVICEROOTDIRECTORY/repository</parameter-value>
</parameter>
e.g.
<parameter position="0" mandatory="true" name="repository" switch="-r">
<parameter-value isdefault="true">/home/maspectras/maspectrasjclusterservice/repository</parameter-value>
</parameter>
9.6.2. Change the NCBI-BLAST/NCBI-FORMATDB service definition:
program-path="JCLUSTERSERVICEROOTDIRECTORY/applications/bin/blastall"
e.g.
program-path="/home/maspectras/maspectrasjclusterservice/applications/bin/blastall"
and
program-path="JCLUSTERSERVICEROOTDIRECTORY/applications/bin/formatdb"
e.g.
program-path="/home/maspectras/maspectrasjclusterservice/applications/bin/formatdb"
9.6.3. Change the CLUSTALW service definition:
program-path="JCLUSTERSERVICEROOTDIRECTORY/applications/bin/clustalw2"
e.g.
program-path="/home/maspectras/maspectrasjclusterservice/applications/bin/clustalw2"
9.6.4. Change the MASSQUANTIFICATION service definition:
program-path="JCLUSTERSERVICEROOTDIRECTORY/applications/bin/msQuantificationCmd"
e.g.
program-path="/home/maspectras/maspectrasjclusterservice/applications/bin/msQuantificationCmd"
9.6.5. The default installation does not require any queueingsystem or cluster and therefore every service
definition is sent to the built-in local java jms queueing system. If you want to run CLUSTALW,
BLAST- and FORMATDB- jobs on a distributed cluster just adapt the configuration parameters described in
3.2 and change in the service definition the parameter queuetype="jms" to queuetype="sge" or
queuetype="pbs".
In such case the JCLUSTERSERVICEROOTDIRECTORY must be shared (rw) under the same path over all
cluster nodes.
9.7. Adapt on the Maspectras side the paths in DATAROOTDIRECTORY/analyses/partitioning/pipeline.xml
<MCLProgramDirectory>/home/maspectras/mcl</MCLProgramDirectory>
<RemoteBlastDatabaseDirectory>JCLUSTERSERVICEROOTDIRECTORY/tmp/BlastDB</RemoteBlastDatabaseDirectory>
<RemoteBlastExecutableDirectory>JCLUSTERSERVICEROOTDIRECTORY/applications/bin</RemoteBlastExecutableDirectory>
<RemoteInputDirectory>JCLUSTERSERVICEROOTDIRECTORY/tmp/Input</RemoteInputDirectory>
<RemoteResultDirectory>JCLUSTERSERVICEROOTDIRECTORY/tmp/Output</RemoteResultDirectory>
e.g.
<MCLProgramDirectory>/home/maspectras/mcl</MCLProgramDirectory>
<RemoteBlastDatabaseDirectory>/home/maspectras/maspectrasjclusterservice/tmp/BlastDB</RemoteBlastDatabaseDirectory>
<RemoteBlastExecutableDirectory>/home/maspectras/maspectrasjclusterservice/applications/bin</RemoteBlastExecutableDirectory>
<RemoteInputDirectory>/home/maspectras/maspectrasjclusterservice/tmp/Input</RemoteInputDirectory>
<RemoteResultDirectory>/home/maspectras/maspectrasjclusterservice/tmp/Output</RemoteResultDirectory>
and the connection parameter ServerURL and ServerURLPlusUser in DATAROOTDIRECTORY/analyses/partitioning/cluster.properties.
Default connection settings presume that the jclusterservice is running on the same host as maspectras on http. If its
runnning on a different machine replace the http://username:password@localhost:21080 by the proper host and port
parameters in DATAROOTDIRECTORY/analyses/partitioning/cluster.properties . If possible secure the connection via SSL
and replace in ServerURL and ServerURLPlusUser the http by https.
9.8. Start the jclusterservice under $JBOSS_HOME/bin with run-jclusterservice.sh
The jclusterservice can run on a different execution host or a cluster system. In
that way the applications queued and executed there, do not influence the performance
of the webinterface.
10. Installation of the markov cluster (for the sequence based clustering)
10.1. Download the MCL package from http://micans.org/mcl/ and install it. mcl 1.005, 05-118 has been
tested with Maspectras
Maspectras requires the programs clmformat, mcl, and mcxassemble.
10.2. Specify the path to the MCL package in the pipeline.xml file located in the
$DATAROOTDIRECTORY/analyses/partitioning
directory:
e.g.: /home/maspectras/mcl
Make sure that the maspectras user has access to /home/maspectras/mcl and to $DATAROOTDIRECTORY and that the executables have executable rights
12. Installation of KAlign (for MS- Evidence based clustering)
11.1. Download the KAlign package from http://msa.sbc.su.se/cgi-bin/msa.cgi and install it. Kalign version 2.03
has been tested with Maspectras
11.2. Specify the path to the KAlign executable in the maspectrasSettings.properties file located in the
$DATAROOTDIRECTORY/analyses/partitioning
directory:
e.g.: kalignURL=/home/maspectras/kalign/kalign
Make sure that the maspectras user has access to /home/maspectras/kalign/kalign and to $DATAROOTDIRECTORY and that the executable has executable rights
12. Get access to the AAS
12.1. Open your Web browser and type http://localhost:17080/UsermanagementWeb
12.2. Login using username: admin password: 12345
(change the password afterwards, since this is the ADMINISTRATOR account for the whole AAS)
12.3. Logout
12.4. Login using username: maspectrasadmin password: 12345
(change the password afterwards, since this is the ADMINISTRATOR account only for maspectras)
13. Get access to Maspectras
13.1. Open your Web browser and type http://localhost:8080/maspectras
14. Test Maspectras
14.1. Open a new browser and type https://maspectras.genome.tugraz.at
14.2. Login as guest user (username: guest ; password: guest)
14.3. In the left menu click "Management" -> "File Upload"
14.4. Click on "Query", type "Name" "=" "ICPL_Protmix_1lizu1he_A_c1_ms2_Mascot" and download the Mascot file (for help see user manual 1.2.1 and 1.2.3)
14.5. Click on "Query", type "Name" "=" "ICPL_Protmix_1lizu1he_A_c1_Centroid" and download the mzXML file containing the raw data (check if the file suffix is mzXML and not mzXML.xml, if not change the suffix to mzXML)
14.6. Logout as guest user and continue working at http://localhost:8080/maspectras
14.7. Upload and initialize the database doc/testdatabase/karl_04090683392.fa with the parsing rules of doc/parsingRules/giDatabase_parserules like in the user manual described at chapter 2.1
14.8. Upload the Mascot file (File Type = mascot) and the mzXML file (File Type = Raw-File) like in the user manual described at chapter 2.2
14.9. When you started the upload of the mzXML file the file is translated into a file format more convenient for calculation. Check the status of this translation at Uploadstatus (user manual 2.3). Wait until "TRANSLATING" is replaced by "TRANSLATION FINISHED"
14.10. Create a new Massspecexperiment (for help see user manual 6.1) and assign the mzXML as RawFile
14.11. Start the parsing of the Mascot file (for help see user manual 6.2)
14.12. When the parsing is finished check your results (for help see user manual 7 and 7.1). In the clustered protein view must be 16 protein(-clusters), with blastall greater or equal version 2.2.18 it will be 20 clusters, then the clustering worked.
15. Installation of Java3D for the client machine
To use the real 3D view Java3D must be installed on the client machine. To download Java3D visit the web-site http://java.sun.com/products/java-media/3D/download.html. It is recommended to increase the memory size for the applet, for more information visit the Maspectras user manual 7.5.1.
16. Test of external DB information fetch
16.1. Open a new browser and type https://maspectras.genome.tugraz.at
16.2. Login as guest user (username: guest ; password: guest)
16.3. In the left menu click "Management" -> "File Upload"
16.4. Click on "Query", type "Name" "=" "M130-E10-G175-C24-P535-1" and download the Mascot file (for help see user manual 1.2.1 and 1.2.3)
16.5. Click on "Query", type "Name" "=" "IPI_HUMAN_APP_v3.41_20080331" and download the database (for help see user manual 1.2.1 and 1.2.3)
16.6. Logout as guest user and continue working at http://localhost:8080/maspectras
16.7. Upload and initialize the downloaded database IPI_HUMAN_APP_v3.41_20080331 with following settings:
Accession-rule: IPI:(\w+\W?\w*)
Description-rule: [^\ ]* [^\ ]* Gene_Symbol.(.*)
Organism-rule: (leave this input field empty)
URL to database: http://www.ebi.ac.uk/cgi-bin/dbfetch?db=ipi&format=default&style=raw&id=
Parser for URL: IPIParser
16.8. Upload the Mascot file (File Type = mascot) like in the user manual described at chapter 2.2
16.9. Create a new Massspecexperiment
16.10. Start the parsing of the Mascot file (for help see user manual 6.2)
16.11. When the parsing is finished check your results and if external information has been fetched (for help see user manual ????????????).