|
⇤ ← Revision 1 as of 2012-07-09 23:33:39
Size: 1218
Comment:
|
Size: 2398
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| The machine that serves as the web server for both sites is solarweb. It serves the /web filesystem that is generally mounted as "/web" on many machines. The files that are relevant to exports live in three places on this filesystem: 1. /web/jsoc/htdocs/ajax contains links to the exportdata.html source, which is shared by both the external and internal system; 2. /web/jsoc/cgi-bin/ajax contains the cgi programs, and links to programs, used by the external export system; and 3. /web/jsoc2/cgi-bin/ajax contains the cgi programs, and links to programs, used by the internal system. | The machine that serves as the web server for both sites is solarweb. It serves the /web filesystem that is generally mounted as "/web" on many machines. The files that are relevant to exports live in three places on this filesystem: 1. /web/jsoc/htdocs/ajax contains links to the exportdata.html source, which is shared by both the external and internal system; 2. /web/jsoc/cgi-bin/ajax contains the cgi programs, and links to programs, used by the external export system; and 3. /web/jsoc2/cgi-bin/ajax contains the cgi programs, and links to programs, used by the internal system. There is also a link from /web/jsoc/htdocs2 to /web/jsoc/htdocs - this construct is what allows the external and internal systems to share exportdata.html. The ultimate source for exportdata.html is /home/jsoc/cvs/Development/JSOC/proj/export/webapps/exportdata.html. This is the file that /web/jsoc/htdocs/ajax/exportdata.html links to. In exportdata.html are references to files containing javascript. These files live in the /home/jsoc/cvs/Development/JSOC/proj/export/webapps/exportdata.d directory. The html in exportdata.html accesses these files by first resolving the URL http://jsoc.stanford.edu/ajax/exportdata (in the case of the external system), then looking in the exportdata.d in this resolved directory. In /web/jsoc/htdocs/ajax there is a link named exportdata which links to /home/jsoc/cvs/Development/JSOC/proj/export/webapps, so http://jsoc.stanford.edu/ajax/exportdata resolves to /home/jsoc/cvs/Development/JSOC/proj/export/webapps. The javascript is therefore in /home/jsoc/cvs/Development/JSOC/proj/export/webapps/exportdata.d. Given this structure, it is easy to set-up a development environment by creating two links (discussed in "How to Develop"). |
Export System
The Way Things Work
The export system implementation involves many components. Starting at the "highest" level, the web pages http://jsoc.stanford.edu/ajax/exportdata.html and http://jsoc2.stanford.edu/ajax/exportdata.html provide interfaces that allow users to initiate export requests, as well as check-on the status of pending requests. The first URL provides access to the external, or public, export system, whereas the second URL provides access to the internal, or private, one. The public system provides access to public data, which is a subset of the data available from the private system.
The machine that serves as the web server for both sites is solarweb. It serves the /web filesystem that is generally mounted as "/web" on many machines. The files that are relevant to exports live in three places on this filesystem: 1. /web/jsoc/htdocs/ajax contains links to the exportdata.html source, which is shared by both the external and internal system; 2. /web/jsoc/cgi-bin/ajax contains the cgi programs, and links to programs, used by the external export system; and 3. /web/jsoc2/cgi-bin/ajax contains the cgi programs, and links to programs, used by the internal system. There is also a link from /web/jsoc/htdocs2 to /web/jsoc/htdocs - this construct is what allows the external and internal systems to share exportdata.html.
The ultimate source for exportdata.html is /home/jsoc/cvs/Development/JSOC/proj/export/webapps/exportdata.html. This is the file that /web/jsoc/htdocs/ajax/exportdata.html links to. In exportdata.html are references to files containing javascript. These files live in the /home/jsoc/cvs/Development/JSOC/proj/export/webapps/exportdata.d directory. The html in exportdata.html accesses these files by first resolving the URL http://jsoc.stanford.edu/ajax/exportdata (in the case of the external system), then looking in the exportdata.d in this resolved directory. In /web/jsoc/htdocs/ajax there is a link named exportdata which links to /home/jsoc/cvs/Development/JSOC/proj/export/webapps, so http://jsoc.stanford.edu/ajax/exportdata resolves to /home/jsoc/cvs/Development/JSOC/proj/export/webapps. The javascript is therefore in /home/jsoc/cvs/Development/JSOC/proj/export/webapps/exportdata.d. Given this structure, it is easy to set-up a development environment by creating two links (discussed in "How to Develop").