The BridgeDb Webservice provides a REST service to access identifier mapping data. It uses the BridgeDb Java library and RESTlet technologies to make the webservice available.
Use the latest jar file available here: link
BridgeDb ID mapping databases are found on this website.
These derby databases are used to perform identifier mapping for a particular species.
The location of the downloaded files is needed for the below described gdb.config file.
The gdb.config ("gene database configuration") file in the repository should be customized to point to each local derby file you have downloaded.
For example, if you are only interested in mapping identifiers for Homo sapiens, your gdb.config file would look like:
Homo sapiens C:/.../Path_To_Derby_Database/Hs_Derby_Ensembl_XXX.bridgewhere "Homo sapiens" and the path to the derby database are separated by a tab.
When starting the webservice, the gdb.config file will be parsed to determine which gene databases you have configured.
Navigating to the folder where you saved the jar file and run the following line:
java -jar target/BridgeDbWebservice-*-jar-with-dependencies.jarThe jar file takes three optional parameters, the port, a boolean if CORS should be enabled, and the server URL. For example, the following the are valid instructions to start a server:
java -jar target/BridgeDbWebservice-*-jar-with-dependencies.jar 8888
java -jar target/BridgeDbWebservice-*-jar-with-dependencies.jar 8888 false https://example.org/Point your browser to: http://localhost:8080/Human/attributeSet
Please see Swagger Documentation for your reference to see which endpoints are available for you to use.
Update the version numbers in these three files:
pom.xmlCITATION.cffsrc/main/resources/webservice.props