Gateway Service: Difference between revisions
| Line 2: | Line 2: | ||
[[Image:Gateway service.jpg|500px]] | |||
{| | |||
|Orange | |||
|[[Image:Gateway service.jpg|right|500px]] | |||
<center>Gateway Service Diagram</center> | |||
|- | |||
|} | |||
== BES gateway_module == | == BES gateway_module == | ||
Revision as of 19:03, 28 January 2011
Overview
| Orange |  |
BES gateway_module
The gateway_module for the BES is written. Version 0.1 is checked into subversion repository and we are currently testing the software. Additional features are being added, such as
- Whitelisting secure domains for passing through the Hyrax server.
- Making sure temporary files are removed after being processed
- Testing.
OLFS gateway_service
which is responsible for decoding the incoming dataset URLs.
This is all very similar to a version of the WCS gateway that we put up a while back.
Since the idea is that Mirador will generate URLs to be encoded and passed to the gateway as part of a DAP URL I am attaching a tar file that contains an application for encoding and decoding this URL content. Give it a whirl - it's a java application in a jar file. There is a bash script (hexEncode) that should launch it. You may need to adjust the file permissions on the script as ANT (which bundled the jar) may have dropped the executable permissions. The source code for it is available here:
http://scm.opendap.org/svn/trunk/olfs/src/opendap/gateway/EncodeDecode.java
I have also attached a picture that you may find useful.
Nathan
