Difference between revisions of "BioMart Tutorial 2011"

From GMOD
Jump to: navigation, search
(→‎Creating Access Point)
(→‎System overview and installation)
Line 21: Line 21:
 
# Server: min. 1 GB memory, 3 GB for better performance
 
# Server: min. 1 GB memory, 3 GB for better performance
  
 +
= Add a section here for installing VirtualBox or VMware and start up the VM =
 +
 +
# where to download virtualbox etc.
 +
# where to get VM image (download? or get it from USB key)
  
 
= Downloading & Installing BioMart =
 
= Downloading & Installing BioMart =

Revision as of 17:12, 13 October 2011

{{#icon: Biomart250.png|BioMart|200|BioMart}}

{{#icon: 170px-October2011Logo.png|October 2011 - Toronto		 2009 GMOD Summer School - Toronto, Canada}} BioMart Session

2011 GMOD Community Meeting &
Ontario Institute for Cancer Research
Toronto, Canada
14 October 2011
Junjun Zhang, Elena Rivkin and Anthony Cros

__NOTITLE__


This tutorial walks you through how to install and configure a local installation of BioMart.



System overview and installation

Prerequisites for BioMart:

  1. Software: Java 1.6, Ant and SVN client
  2. OS: Linux, Mac & Windows
  3. Server: min. 1 GB memory, 3 GB for better performance

Add a section here for installing VirtualBox or VMware and start up the VM

  1. where to download virtualbox etc.
  2. where to get VM image (download? or get it from USB key)

Downloading & Installing BioMart

Two components are necessary for this tutorial: MartBuilder is installed form an older version of BioMart (0.7), and MartConfigurator is installed from the most recent version (0.8) (until all features are fully ported to the new version)

Installation of MartBuilder and MartConfigurator has already been done on the VM image under ~/biomart_0_7.template and ~/biomart_0_8.template, but we are going to do once together for demonstration purposes.

Refer to BioMart Documentation for more information.

Biomart 0.7 (MartJ -> MartBuilder + MartRunner)

MartJ contains applications necessary to create a Mart: MarBuilder and MartRunner.

Check Section 2 in Installing BioMart for more information.

Download & extract tarball content with: 

 $ mkdir ~/biomart_0_7 # arbitrary name of course
 $ cd ~/biomart_0_7
 $ wget ftp://anonymous@ftp.ebi.ac.uk/pub/software/biomart/martj_current/martj-bin.tgz # or get it from MartJ
 $ tar zxvf martj-bin.tgz # creates "martj" directory
 $ cd martj
 $ ls bin/martbuilder.sh bin/martrunner.sh # what we care about

Biomart 0.8 (MartConfigurator)

Checkout latest release using SVN: 

 $ mkdir ~/biomart_0_8 # arbitrary name of course
 $ cd ~/biomart_0_8
 $ svn co https://code.oicr.on.ca/svn/biomart/biomart-java/branches/oct_3_2011 # creates "oct_3_2011" directory
 $ mv oct_3_2011 martconfigurator # friendlier name
 $ cd martconfigurator
 $ ant # build project with ant; in the future, you may use: ant clean dist
 $ ls dist/scripts/martconfigurator.sh dist/scripts/biomart-server.sh # what we care about

Building mart

This section will show you how to create a (simplified) mart containing 1 dataset based on the VEGA database, using MartBuilder.

Describing mart (MartBuilder)

Creating/loading sample mart

Start MartBuilder

From the directory ~/biomart_0>7/martj, issue: 

 $ bin/martbuilder.sh

MartBuilder should open with an empty mart.

Add a schema

Choose Schema->Add to open the dialog to add a schema.

  1. Name: vega
  2. Database type: MySQL
  3. Using MyISAM: checked
  4. Host: localhost
  5. Port: 3306
  6. Database: mini_hsap_vega
  7. Schema: mini_hsap_vega
  8. Username: biomart
  9. Password: biomart

ignore the last 3 fields (used for partitioning which is not covered in this tutorial)

Mb add schema2.png

Click the Test button to ensure we can connect to the database. Click the Add button in order to proceed with the dataset description.

You should now see the source database show in MartBuilder.

Note that if you did not specify a schema when creating your database, your tables will be in the default schema for your platform:

  1. MySQL: has no notion of schema, database acts as a schema
  2. PostGreSQL: public
  3. Microsoft SQL Server: dbo
  4. Oracle & DB2: the username of the user who created the database

Choose dataset

We are going to create a dataset based on the tables "gene" and "transcript" (as main and submain tables respectively, as described in presentation)

  1. Right-click on the "gene" table
  2. Click on Create dataset TODO

the gene table should be highlighted already as we arrived on the current menu by clicking on it

  1. add the transcript table (standard "Ctrl + click)
  2. Press the Create button

Mb create dataset.png

This shows how the dataset will be structured once materialized

Mb dataset.png

Materializing mart (MartBuilder->MartRunner)

Your dataset does not actually exist yet. In order to create it, you need to generate the SQL for it then run that SQL against your database.

BioMart offers a tool (MartRunner) that does that for you, using JDBC. The SQL used is as ANSI-compliant as possible, with some exceptions based on the RDBMS in use.

1. We now going to transform the source data into target dataset, but before that, we have to create a target database: 

 $ MY_DESTINATION_DATABASE=mini_hsap_vega_mart
 $ mysql -hlocalhost -P3306 -ubiomart -pbiomart -e "create database $MY_DESTINATION_DATABASE"

In theory one could materialize a mart in the same database as the source one provided there is no table name conflicts, but this is strongly discouraged.

Also we have to have MartRunner running. Lets run it over a local port (any free one will do).

2. Start martrunner with: 

 $ MY_MART_RUNNER_PORT=9876
 $ bin/martrunner.sh $MY_MART_RUNNER_PORT

MartBuilder will send the materialization SQL to MartRunner through that port (in this example, 9876), and MartRunner will execute the transformation SQL.

Note that MartRunner may be run from another machine, as we specify its connection parameters to MartBuilder (see below).

We go back to MartBuilder, and click on the Build Mart button to pop up the following dialog:


  1. Datasets: gene
  2. Schema partitions: ignore
  3. Target database: mini_hsap_vega_mart (the one we just manually created)
  4. Target schema: mini_hsap_vega_mart
  5. Send SQL to: MartRunner (other options are available)
  6. MartRunner host name: localhost
  7. MartRunner port number: 9876 (the one we just arbitrarily chose because it was free)
  8. Database server name: localhost
  9. Database server port number: 3306


Mb build mart dialog.png


Click on the Generate SQL button

Mb sql generation.png

3. Monitor progress using the Monitor MartRunner progress

Ensure everything is successful (green font):

Mb job finished.png

Your schema now contains a mart with a complete dataset ready for configuring with MartConfigurator.

Configuring mart (MartConfigurator) - basic

This section will show you how to configure the created VEGA mart using MartConfigurator


Start MartConfigurator

Start MartConfigurator with the following command in the directory of your installation: 

 $ dist/scripts/martconfigurator.sh


Add Mart

1. Wizard step 1/4:

Fill in the fields using the following values:

  1. source profile: vega (anything will do)
  2. source type: RDBMS

Mc add source wizard 1.png

2. Wizard step 2/4:

  1. RDBMS: MySQL (keep MyISAM)
  2. Host: localhost
  3. Port: 3306
  4. User: biomart
  5. Password: biomart
  6. Database: can leave empty for now

Mc add source wizard 2.png

3. Wizard step 3/4:

Select mini_hsap_vega_mart, the mart that we just built using MartBuilder/MartRunner and based upon the mini_hsap_vega database

Mc add source wizard 4.png

4. Wizard step 4/4:

  1. Create naive configuration
  2. Choose the main table gene__gene__main (only one)

Mc add source wizard 5.png

5. Done!

You are now connected!

The panel on the left corresponds to source schemas; in our case we only have one mart that has one dataset: mini_hsap_vega_mini, but there could be more

The panel on the right corresponds to configuration of those source schemas (accessibility, rendering, linking, ...)

Mc connected.png

Creating Access Point

Simply drag-and-drop the source from the left side (Source frame) to anywhere on the right side (Portal frame)

It will add an access point to the mart. The default name is mini_hsap_vega_mart_ap, ap standing for Access Point, but you can give it a name of your choice.

Note that clicking the Add Access Point button would yield the same result. You would then be given a list of the existing marts to choose from.

Mc ready.png

Customizing configuration

Double-click on the access point mini_hsap_vega_mart_ap to bring out the configuration editor (will be detailed in the following section)

Mc config.png


Configuring mart (MartConfigurator) - more advanced

The display name of any object (a container, attribute, or filter) can be changed by selecting that object (by clicking on it) and then double clicking the displayname property in the lower right-hand pane.

Deploy BioMart Server

To test the registry, you can now click on the Start Server button in the upper right. You will be prompted to save the registry file you have created, and after doing so, the server will be deployed on your local machine, port 9000. Your web page should open automatically when the local server is ready. You can also deploy BioMart from the command line on the server. To deploy BioMart, from the directory of your installation, run the following command:

./dist/scripts/biomart-server.sh start

To Stop the server, use the command:

./dist/scripts/biomart-server.sh stop


More exercises with MartConfigurator

Here we should include

  • rename 'default' GUI tab to "Form"
  • add another GUI tab name it as "Wizard", and set the GUIType to MartWizard
  • add vega mart via DB based BC
  • create an AccessPoint under Form, and another one under Wizard
  • deploy
  • exam chromosome filter (singleSelect), gene type filter (multiSelect), how to edit dropdown options for those filters
  • exam Multiple Chromosomal Regions (Chr:Start:End:Strand) filter
  • create attribute list
  • add pathway dataset via URL data source
  • drag&drop pathway name attribute to vega AP under Form GUI tab, this will trigger link creation (detailed below)
  • link creation between pathway and vega gene. use ensembl gene id as the attribute/filter pair to build the link
  • deploy the server and select pathway name together with other attribute from vega gene dataset, exam the result
  • drag&drop pathway name filter to vega AP under Wizard GUI tab, then deploy the sever and choose pathway filter then exam result


Set Filter typesSet Attribute URLSelect GUI type

Creating Links between sources

If two data sources contain common information (e.g. a Gene/Protein ID), this can be used to create a link, allowing filters and attributes from one data source to appear in the other. These are called “pointer attributes” and “pointer filters,” and the attribute or filter to which they point is called the “target. ”To add a pointer to an access point, double click on that access point in the portal tab to edit it. In the top left corner of the editing window, click on the Import from sources button.

You will be given a list of the existing data sources to choose which one you would like to make an access point for. After giving the new access point a name of your choice, it will appear in the GUI tab. Double-clicking on the access point icon will open a new window that allows you to modify the access point. References

5. Querying a BioMart server via REST API

5.1 MetaData queries

http://localhost:9000/martservice/marts

http://localhost:9000/martservice/datasets?mart=gene_vega

http://localhost:9000/martservice/accesspoints?datasets=&mart=gene_vega

http://localhost:9000/martservice/attributes?dataset=hsapiens_gene_vega&mart=gene_vega

http://localhost:9000/martservice/filters?dataset=hsapiens_gene_vega&mart=gene_vega

5.2 Data query

<xml> <Query processor="TSV" header="true" limit="-1" client="webbrowser"> <Dataset name="hsapiens_gene_vega" config="gene_vega_ap"> <Filter name="chromosomal_region" value="2:1000000:2000000:1,4:9000000:11000000:-1"/> <Filter name="biotype" value="protein_coding"/> <Attribute name="vega_gene_id"/> <Attribute name="vega_transcript_id"/> <Attribute name="vega_translation_id"/> <Attribute name="chromosome_name"/> <Attribute name="start_position"/> <Attribute name="end_position"/> <Attribute name="strand"/> <Attribute name="band"/> </Dataset> </Query> </xml>

Paste this piece of XML in a web browse address as: 

http://localhost:9000/martservice/results?query=paste_query_xml_string_here


To read more about BioMart, refer to the recent articles describing the BioMart software and its applications.

1. Zhang J, Haider S, Baran J, Cros A, Guberman JM, Hsu J, Liang Y, Yao L, Kasprzyk A. BioMart: a data federation framework for large collaborative projects. Database (Oxford). 2011 Sep 19:2011:bar038.

2.Guberman JM, Ai J, Baran J., et al. BioMart Central Portal: An Open Database Network for the Biological Community. Database (Oxford). 2011 Sep18;2011:bar041.

3. Zhang J, Baran J, Guberman JM, Haider, S, Hsu J, Liang Y, Rivkin E, Wang J, Whitty B, Wong-Erasmus M, Yao L, Kasprzyk A. International Cancer Genome Consortium Data Portal - a One-stop Shop for Cancer Genomics Data. Database (Oxford). 2011 Sep19;2011:bar026.

Retrieved from "http://gmod.org/mediawiki/index.php?title=BioMart_Tutorial_2011&oldid=19137"