www.archive-org-2014.com » ORG » O » OPENDAP

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 580 . Archive date: 2014-01.

  • Title: Is DODS available for Windows 95/98 or Windows NT? | OPeNDAP
    Descriptive info: ›.. Frequently Asked Questions.. Platforms Portability.. Is DODS available for Windows 95/98 or Windows NT?.. Wed, 05/11/2011 - 15:50 —.. nehal bathani.. Yes, we have ported several of the DODS clients to Windows and they are available as a beta release.. Please take a look at our.. Windows Port.. page.. to post comments..

    Original link path: /node/154
    Open archive

  • Title: Microsoft Windows Support | OPeNDAP
    Descriptive info: QuickStart.. Support.. Documentation.. User Documentation.. Design Documentation.. Movies.. Project Documentation.. Available Clients.. Available Servers.. Workshops Presentations.. Sources of Data.. Mail Lists.. OPeNDAP Wiki.. › Microsoft Windows Support.. Microsoft Windows Support.. Note:.. Windows versions of the OPeNDAP software is available here and on the main.. download.. This page provides some background information on the port, especially on the different types of libraries supported.. You can get the same software, or in some cases.. newer software.. , from the main download page by following the.. Windows links there.. DODS 3.. 4.. 4 Native Win32 port.. 4 is available for Windows 2000 and Windows XP.. This distribution contains the DODS core (DAP) library, the netCDF client library, the Matlab command-line client, the IDL command-line client and the FreeForm Server.. A Dods Development environment for Win32 is also included.. This development environment includes the Dods Core Library (libdap) as well as other select libraries upon which the core library depends (libcurl, libz, libxml2 and libxdr) and all supporting headers.. Each of these libraries are provided in 6 different models - Static Singly-Threaded, Static Multi-Threaded, Dynamic Multi-Threaded plus debug versions of each of these three libraries.. These six models of libraries are provided for libdap, libcurl, libz, libxml2, libxdr and the Freeform library.. Four models of the NetCDF library are provided (no DLL models).. The below table outlines the 6 library models:.. Library Model.. Microsoft Compiler Option Used to Build.. Format of Library Name.. Format of Name of the Associated DLL.. Static Singly-Threaded.. /ML.. lib*ST.. lib.. N/A.. Static Multi-Threaded.. /MT.. lib*MT.. Dynamic Multi-Threaded.. /MD.. lib*MD.. dll.. Static Singly-Threaded Debug.. /MLd.. lib*STD.. Static Multi-Threaded Debug.. /MTd.. lib*MTD.. Dynamic Multi-Threaded Debug.. /MDd.. lib*MDD.. To install Dods for Windows, download the.. distribution.. to your desktop and double click on it.. Then Follow the on-screen instructions.. If you have a previous version of Dods installed,.. you must first uninstall.. it via "Add/Remove Programs" component within the Control Panel.. 4 for win32 was built with Microsoft Visual C++ 7.. x.. If you use the development environment provided to construct or relink a Dods client, you must also use MS VC++ 7.. 4 Native Win32 port(beta).. 4 is available for Windows NT, Windows 2000 and Windows XP.. Other versions of Windows are not supported.. It contains the DODS core library (DAP), the netCDF client library,  ...   2000 and Windows XP.. 2 native Win32 port.. 2 is now available as a Windows port (6 February 2002).. It contains: the Matlab client; the IDL client; our test client, geturl; the DODS core (DAP) library; and the netCDF client library.. Note: We support this port for NT-based kernals only (NT, W2K and XP).. We do not support this port on win9x-based systems though it may work fine.. To install this port: first, uninstall any existing version of DODS; download the.. installShield self-extracting archive.. ; double click; and follow the on-screen instructions.. To run DODS exe's and dll's, you will need to set various environment variables, e.. g.. , path, IDL_PATH, and MATLABPATH, depending on which tools you are going to run.. Other environment variables must be set to use the DODS libraries.. 1 native Win32 port.. DODS has a port for MS Windows platforms (95, 98, 2000, and NT).. It is a native Windows port (using the Visual C++ compiler) and is available as a beta release.. Download our.. self-extracting archive.. This port is of three DODS clients: the Matlab client, the IDL client, and geturl.. (The Matlab GUI is not included, you will need to get that directly from the.. FTP site.. ).. Tip:.. From a DODS support email, a discussion of setting your PATH so Matlab can find the DODS client (probably applies to IDL as well):.. I believe it is just a matter of having the directory of the.. dll's on your PATH.. To pick up the matlab dll for instance I have C:\Program Files\URI\DODS\bin in my path.. Your location of this dll will vary somewhat depending upon where to choose to install Dods at installation time.. How you set the path varies by the win32 host you are on.. 95/98 - edit autoexec.. bat.. In Win2000, double click on "System" in the control panel and select the Environment Variables push button.. In NT, it is probably set the same or similar to the way it is in Win2000.. Here's the URL for that email,.. http://www.. unidata.. ucar.. edu/glimpse/dods/287.. An older port using Cygwin to emulate the Unix environment contained a number of DODS servers.. The Cygwin port is no longer supported but is available if desired.. If you are interested in the Cygwin port, please email us at.. support@unidata.. edu..

    Original link path: /faq?q=winPort
    Open archive

  • Title: What are the issues involved in building and running DODS on SGI? | OPeNDAP
    Descriptive info: What are the issues involved in building and running DODS on SGI?.. Wed, 05/11/2011 - 15:51 —.. See the.. notes on SGI issues..

    Original link path: /node/155
    Open archive

  • Title: SGI Issues | OPeNDAP
    Descriptive info: › SGI Issues.. SGI Issues.. There are a number of issues that have caused problems with builds (and running the resulting binaries) on SGI machines.. The main issue with respect to DODS is how the different architectures affect use of the DODS libraries and the Matlab and IDL clients.. Here is a.. description of our standard SGI binary distribution.. Issues:.. Other Issues:.. Third-party Packages:.. Architectures.. OS Versions.. Hardware.. Compiler Versions.. Matlab.. IDL.. Standard SGI Distribution.. Our standard SGI binary distribution is built on an SGI Irix 6.. 5 machine for the n32/mips-3 architecture.. The Matlab client will come with two loaddods.. mexsgi files: loaddods.. mexsgi is the binary for the n32 architecture, loaddods.. mexsgi64 is a binary for the 64 architecture.. Details for the IDL distribution are still being decided.. If you are using DODS version 3.. 0 (we recommend using 3.. 1), see the.. 0 note below.. We are still developing our strategies for dealing with these issues.. If you have comments, please let us know by emailing.. Architecture.. There are a variety of SGI architectures.. Each one is some combination of the four possible instruction sets and the three binary formats (ABI).. Instruction Sets.. '-mips1';.. '-mips2';.. '-mips3'; and.. '-mips4';.. Application Binary Interface (ABI), i.. , the format/interface of the binary files.. '-o32' - for the "old" 32-bit ABI (which was standard on IRIX 5) and is either mips-1 or mips-2;.. '-64' - the 64-bit ABI (which was introduced on IRIX 6.. 0) and is either mips-3 or mips-4; and.. '-n32' - the new, high-performance 32-bit ABI (which was introduced on IRIX 6.. 2) and is either mips-3 or mips-4.. Though these architecures are backward compatible (i.. , a 64 bit machine can run binaries built in any architectures), every part (all objects and libraries) for a given executable must be in the same architecture.. In other words, you cannot link together objects that are built for different architectures.. This means caution must be taken when linking applications with the DODS libraries we build (i.. , the DODS core (DAP) library, libdap++.. a; the netCDF API library, libnc-dods.. a; and the JGOFS API library, libjg-dods.. a) and with the architectures of the commercial applications we build clients for (i.. , Matlab and IDL).. See the information below on the architectures of.. and.. Also, see the.. note on shared objects.. The basic problem here is that several Irix OS versions work exclusively on certain hardware platforms.. Here's a (not terribly detailed) summary:.. Irix  ...   architectures.. Please send us (.. ) the output so we can add to this list.. We have been recommending use of gcc 2.. 8 for some time now due to some (former) dependence on the Gnu library.. However, we have had some difficulties on SGIs due to the version of the libstdc++.. a library that was distributed with gcc 2.. 8.. Using gcc 2.. 8 with a newer version of libstdc++.. a holds promise but we have not thoroughly tested it.. The egcs compiler works.. And, now that egcs and gcc have merged back together, gcc 2.. 95 also works.. Note: The dependence on the Gnu library has been removed.. We are working to make the build process more generic so DODS can be built on development environments other than GNU.. The required architecture of the DODS Matlab client (which is used by the DODS Matlab GUI) depends on a selection during installation of Matlab.. The two available installations (and the architecture of the respective shared libraries, with which the DODS Matlab client needs to link) are:.. SGI - has o32/mips2 shared objects.. SGI64 - has 64/mips4 shared objects.. You can determine the architecture of your Matlab installation by running 'ver' at the Matlab prompt.. The first line containing Matlab version info will state either 'SGI' or 'SGI64', e.. ,.. MATLAB Version 5.. 3.. 10183 (R11) on SGI64.. The required architecture of the DODS IDL client depends on the version of IDL you are running.. The architecture of the IDL shared libraries, with which the DODS IDL client needs to link, is as follows:.. o32 (mips 1) shared objects for IRIX IDL 5.. 2 and.. n32 (mips 3) shared objects for IRIX IDL 5.. 2.. 1 and above.. Notes.. Shared Objects Note.. : Remember when dealing with shared objects, since the objects are linked at runtime, any error including architecture mismatch will be a runtime error.. 0 Note.. : For DODS version 3.. 0, we skirted the issue by providing an Irix 5.. 3 build.. It has been tested in a very limited way on Irix 6.. 5 machines.. However, we've heard of incompatibilities between Irix 5.. x and 6.. x at least in terms of linking to the 5.. x libraries on 6.. x machines.. Which means that if you plan to link your applications against any of the DODS libraries, this solution may not (probably won't?) work for you.. As far as the servers go, they seem to work fine on 6..

    Original link path: /faq?q=sgiProbs
    Open archive

  • Title: How do I build the Matlab server and client on SGI? | OPeNDAP
    Descriptive info: How do I build the Matlab server and client on SGI?.. Wed, 05/11/2011 - 15:53 —.. To build the Matlab server, your entire DODS build (actually, just dap, packages, and ml-dods) must be in the same architecture as the Matlab libraries (o32/mips2 or 64/mips4).. We haven't yet succeeded at building all of DODS in either of these architectures.. Here are our main problems:.. currently, gcc does not support o32 and.. we've run into some trouble linking 64 bit objects (problem with linker setup?).. we haven't had time to work on this problem.. To build the Matlab command line client, build in the same architecture as the rest of your DODS build.. If that architecture does not match the architecture  ...   be built in the architecture of the Matlab libraries even though the rest of DODS is not.. To build loaddods as either o32/mips2 or 64/mips4:.. Note: gcc does not support '-mabi=o32' but will build '-mabi=64'.. However, SGIs cc supports both '-o32' and '-64'.. edit Makefile.. if using cc, add '-o32' or '-64' to CFLAGS;.. if using gcc, add '-mabi=64' to CFLAGS;.. remove '-gstab' from CFLAGS; and.. change CC to 'cc' or leave as 'gcc';.. make sure LDFLAGS points to the correct Matlab library (in case you have both architectures installed on your machine).. remove (or rename) loaddods.. o, variable.. o, queue.. o, extend.. o, error.. o, MLVars.. o (new as of 3.. 1.. 4), and process_values.. x);.. run '$MAKE loaddods'..

    Original link path: /node/156
    Open archive

  • Title: How do I test my DODS server(s)? | OPeNDAP
    Descriptive info: Server Issues.. How do I test my DODS server(s)?.. Wed, 05/11/2011 - 15:55 —.. There are several ways to test a DODS server.. One of the simplest ways is to use any web browser to look at a dataset.. For a description of how to do this, see our.. description of how to access DODS data with a browser.. You can also test out a server by using the 'geturl' tool.. It should be in your $DODS_ROOT/bin directory.. To use 'geturl', give it the -d, -a, or -D option and the URL of your dataset.. For instance,.. geturl -d.. http://test.. opendap.. org/dap/data/nc/fnoc1.. nc.. Yet another way to test and debug a server is to directly connect to the HTTP server.. Thus bypassing *all* interpretation of the return data stream, both from the DAP and the libcurl (HTTP) library.. Here's the procedure.. Type the following, making the substitutions for the server/URL you want to debug:.. telnet host with server 80 (assuming the server is running on port 80, substitute the correct port otherwise).. GET URL fragment following the hostname HTTP/1.. Host: hostname.. blank line.. Following the blank line you will  ...   use HTTP/1.. Following the GET line there are one or more HTTP/1.. 1 headers which supply additional information to the server.. HTTP/1.. 1 only.. requires.. that the Host: header be present.. There are other request headers you can use.. Consult the HTTP/1.. 1 specification.. Here is an example.. The matching URL is.. http://dodsdev.. gso.. uri.. edu/dods-test/nph-dods/data/nc/fnoc1.. dds.. [jimg@comet jimg]$ telnet dodsdev.. edu 80 Trying 198.. 116.. 10.. 229.. Connected to dodsdev.. Escape character is '^]'.. GET /dods-test/nph-dods/data/nc/fnoc1.. dds HTTP/1.. 1 Host: dodsdev.. edu HTTP/1.. 0 200 OK XDODS-Server: DAP/3.. 2 Date: Thu, 08 Jul 2004 17:01:59 GMT Last-Modified: Mon, 15 Apr 2002 22:49:39 GMT Content-type: text/plain Content-Description: dods_dds Dataset { Int16 u[time_a = 16][lat = 17][lon = 21]; Int16 v[time_a = 16][lat = 17][lon = 21]; Float32 lat[lat = 17]; Float32 lon[lon = 21]; Float32 time[time = 16]; } fnoc1.. nc; Connection closed by foreign host.. A few things to think about if your server isn't working:.. Check the permissions on your CGI scripts.. They must have execute permission.. If you are using a FreeForm server, see the question.. Why can't I get my FF server to serve my data?..

    Original link path: /node/157
    Open archive

  • Title: Why can't I get my FF server to serve my data? | OPeNDAP
    Descriptive info: Why can t I get my FF server to serve my data?.. Wed, 05/11/2011 - 16:29 —.. Here are a few suggestions for troubleshooting your FF server:.. 1) First, test that your format files are defined properly and that it fits your data files by running.. chkform.. on them.. You can also check that your data is being interpreted as you desire by running.. newform.. Both.. are FreeForm tools that come with the DODS FreeForm Server distributions.. (They should be located in the bin/ directory of your distribution.. So that.. can display your data, you will need an 'ASCII_output_data' section in your format description file.. Like this:.. ASCII_input_data  ...   data, pay attention to the whitespace in your data files.. FreeForm will gag if whitespace extends beyond the line length determined by the format description.. For instance, if the format descriptor fits.. '34.. 523 1.. 45'.. FF will give an error on.. 45 '.. There needs to be whitespace filler if the data in a line doesn't cover the entire format.. For instance, if the format descriptor fits this data.. 456 234.. 456'.. FF will die on this data.. but will not die on.. The enote type doesn't seem to work quite like that.. For instance, if the format fits.. 456 2.. 34e-2'.. FF will die on.. 3e-2 '..

    Original link path: /faq?q=ffServerData
    Open archive

  • Title: How do I find the version of the server I'm talking to? | OPeNDAP
    Descriptive info: How do I find the version of the server I m talking to?.. Wed, 05/11/2011 - 17:15 —.. Append `.. ver' to a DODS URL.. Or you can use `version' as the dataset name to get the version of a server without knowing any of the data file names.. returns an XML document that describes the server's software components and their versions in addition to the DAP protocol versions supported by the server.. Older servers return a plain text document with less information..

    Original link path: /serverVersion
    Open archive

  • Title: How do I configure a secure (i.e., password protected) server? | OPeNDAP
    Descriptive info: How do I configure a secure (i.. , password protected) server?.. Wed, 05/11/2011 - 17:17 —.. See our web page.. About Data Security..

    Original link path: /node/173
    Open archive

  • Title: ABOUT DATA SECURITY | OPeNDAP
    Descriptive info: › ABOUT DATA SECURITY.. ABOUT DATA SECURITY.. There are two levels of security which DODS data servers support: domain restrictions and user restrictions.. In conjunction with a World Wide Web server, access to a DODS server can be limited to a specific group of users (authenticated by password), specific machine(s) or a group of machines within a given domain or domains.. NOTES:.. DAP 3.. 4 includes support for Digest authentication, which significantly increases the robustness of password access.. DODS versions 3.. 2 and greater software contains significant improvements in the way password authentication is handled.. Older versions of the DODS clients prompted for the password with each and every interaction between client and server.. Now credentials may be embedded in URLs and are remembered and reused for the duration of a session.. The security features of DODS servers depend heavily on the underlying WWW daemon because we felt this was the best way to solve the thorny problem of ensuring only authorized users accessed data.. By using the daemon's authorization software we are ensuring that the security checks used by DODS have been tested by many many sites.. In addition, WWW daemons already support a very full set of security features and many system administrators are comfortable and confidant with them.. The tradeoff with using the web daemon's security system for our servers is that two security settings must be made for each group of data to be configured and more than one DODS server may be needed even if you're serving only one type of data.. Because the security features rely almost entirely on the host machine's WWW server, the steps required to install a secure DODS server will vary depending on the WWW server used.. Thus, before installing a secure DODS server, check over your WWW server's documentation to make sure it provides the following security features: access limits to files in the document root on a per user and/or per machine basis, and the ability to place CGI scripts within the document root directory.. As an alternative to the second requirement, a server may provide a way to place access limits on a CGI script not within the document root directory hierarchy.. IMPORTANT.. Because security features are used to protect sensitive or otherwise important information, once set-up they should be tested until you are comfortable that they work.. You should try accessing from at least one machine that is not allowed to access your data.. If you would like, we will try to access your data, assuming that our machines are among those not allowed, to help you evaluate your set-up.. Since the security features are provided by a WWW server, it is highly likely that they are functional and extensively tested.. While problems with these features have shown up in the past (e.. , the Netscape SSL server bug) they are generally fixed quickly.. Thus there is good reason to assume that your data are safe if you choose to set-up your DODS server as a secure one.. However,.. there is a chance.. that a defect in the WWW server software will allow unauthorized people access; how big that chance is depends on the WWW server software you use and how extensively its security features are tested.. That level of testing is completely beyond our control.. It is important to distinguish securing a DODS server from securing data.. If data are served using DODS then those data are also also accessible through a web browser (although it might be hard to figure out the URLs, it is still possible for the data to be accessed).. So the data themselves need to be stored in directories that have limited access.. If all data access will take place through a DODS server this limitation can exclude all access.. except.. the local machine.. This is the case because some the DODS server's function requires being able to read the data through the local host's web server.. For example, if the DODS server cannot read information about the dataset as DODS objects then it cannot build the INFO document.. It bears repeating: If you're serving sensitive information with DODS, that information is accessible two ways, one via the DODS server and two through the WWW server.. You need to make sure.. both.. are protected.. In the past it was possible to install two or more DODS servers on a computer and  ...   MACHINE TO REQUEST DATA ITSELF Allow from __YOUR_SERVER_HERE__ Require valid-user # ALL VISITORS NEED USERNAME AND PASS BUT NOT SERVER Satisfy any AuthType Basic AuthUserFile /etc/httpd/conf/htpasswd.. groups AuthName "Secure data".. ScriptAlias /secure/ "/home/httpd/html/secure/".. The first group of lines establishes the options allowed for the `secure' directory, including that it can contain CGI programs.. The lines following that establish that only users in the Apache password file can access the contents of the directory, with the exception that this server is allowed to access the directory without authentication.. This last bit is important because DODS servers sometimes make requests to themselves (e.. , when generating an ASCII response) but don't pass on the authentication information.. *.. Regarding the 'Satisfy any' directive, Brock Murch says:.. I thought that one needed an "Allow from all" since I want my users to connect from anywhere, which would have necessitated a "satisfy all" since I needed the passwd authentication as well.. I didn't know that the "Deny from all" would still allow anyone in so long as the AuthType etc was included and authentication took place.. Since this is the case a "satisfy any" will do as I have denied all ip access except for the server itself.. The second group of lines secure the data itself from accesses which bypass the DODS server.. The ScriptAlias line tells Apache that executable files in the directory are CGIs.. You can also do this by renaming the nph-dods script to nph-dods.. cgi and making sure httpd.. conf contains the line:.. AddHandler cgi-script.. cgi.. The AuthType directive selects the type of authentication used.. Apache 2.. 0 supports 'Basic' and 'Digest' while other servers may also support GSS-Negotiate and NTLM.. Version 3.. 4 of the DAP software supports all these authentication schemes, although only Basic and Digest have been thoroughly tested.. Configuration of Apache 2.. 0 for Digest authentication is slightly different then for Basic authentication, but is explained well in Apache's on line documentation.. Copy the server into the new directory.. Copy the CGI dispatch program and the server filter programs in to the newly created directory.. Use the `installServers' script for this.. The script is available in the etc directory of our source distributions and is also bundled with our binary distributions.. Note that if you're using the extension `.. cgi' to tell Apache that nph-dods is a CGI you must rename nph-dods to nph-dods.. cgi.. If you forget to do that then you will get a Not Found (404) error from the server and debugging information generated by the DODS server won't appear in Apache's error_log even if it has been turned on.. You are done.. Tips.. Here are some tips on setting up secure servers:.. Using the per-directory limit files makes changing limits easier since the server reads those every time it accesses the directory, while changes made to the httpd.. conf file are not read until the server is restarted or sent the HUP signal.. Using httpd.. conf for your security configuration seems more straightforward since all the information is in one place.. Using the installServers script it is easy to set up a suite of DODS servers and then use symbolic links (make sure to turn FollowSymLinks on in httpd.. conf) to `mount' datasets under those servers.. When doing this look for `loops' in Apache's DocumentRoot that will allow users to circumvent your security by accessing data using a different path.. If the protections are set up so that it is impossible for the server host to access the data and/or the DODS server itself, then an infinite loop can result.. This can be frustrating to debug, but if you see that accesses generate an endless series of entries in the access_log file, it is likely that is the problem.. Make sure that you have `allow from.. ' set for both the directory that holds the DODS server and that holds the data.. Also make sure that the server's name is set to the full name of the host.. Configuring a secure DODS server can be frustrating if you're testing the server using a web browser that remembers passwords.. You can turn this feature off in some browers.. Also, the geturl tool supplied with DODS can be useful to test the server since it will not remember passwords between runs.. Thanks.. * Brock Murch.. worked out some thorny configuration details for securing the Apache/DODS combination..

    Original link path: /faq?q=server_security
    Open archive

  • Title: How can I determine the usage statistics for my OPeNDAP Server once it is installed? | OPeNDAP
    Descriptive info: How can I determine the usage statistics for my OPeNDAP Server once it is installed?.. Wed, 05/11/2011 - 16:21 —.. OPeNDAP server software resides on the same computer (in general) as the data being served.. The OPeNDAP server will use some lower-level web server software (e.. , Apache Server or Tomcat) to make the actual connection to the Internet.. Most web server software creates and maintains a log file of all the incoming (http, e.. ) requests, and some indication of the success and/or failure mode of the response.. The log files are often in a standardized form but are individually configurable by the system administrator.. Most sites that are interested in  ...   These "metrics" might include: number of hits, number of successful hits, number of repeat users, and volume of data delivered.. A few details for Linux or unix machines running an Apache web server.. A typical place to look for the web server logs is.. /usr/local/apache/logs.. but the actual location depends on how and where the server was installed.. Check with your system administrator for the specifics on your machine.. You can find more information on Apache's server software at.. apache.. org.. , including more information on log files.. There are also freeware log analysis packages available that could be useful.. For instance, you can check out Analog logfile analysis at:.. analog.. cx/..

    Original link path: /node/159
    Open archive





  • Archived pages: 580