[Thread Prev][Thread Next][Index]
Re: Problems setting up insitu data access
Just to clarify:
When Andrew built his LAS with genLAS.pl (make in the las/server
directory) the xml files were being read from the proper directory and
the LAS UI server was configured properly. When the Apache server
received the product requests for
"http://prey.shore.mbari.org/las-bin/LASserver.pl" it read the alias for
/las-bin and directed the request to an older LAS PRODUCT server which
did not know about the insitu operations.
Chase, Andrew wrote:
Thanks to everyone for the help. Joe McLean helped me solve the problem. My httpd.conf file was still pointing to an older installation of las, so the xml files were coming from that older installations server directory.
-Andrew
-----Original Message-----
From: Chase, Andrew [mailto:achase@mbari.org]
Sent: Tuesday, November 09, 2004 12:06 PM
To: 'las_users@noaa.gov'
Subject: RE: Problems setting up insitu data access
A little more information.
In las.xml, in the operations element, I have this:
<!-- Operations supported by this server -->
<operations url="http://prey.shore.mbari.org/las-bin/LASserver.pl">
&operations;
&insitu_operations;
</operations>
when I insert a spelling error into the &operations;
reference and run $LAS/server/make I get an error in the make
process. However, when I insert a spelling error in
&insitu_operations I get nothing, still the same error from
the UI as before, but nothing from make.
My declaration of the entity looks fine:
<!-- Declaration of operations files to be included -->
<!ENTITY operations SYSTEM "operations.xml">
<!ENTITY insitu_operations SYSTEM "insitu_operations.xml">
And the insitu_operations.xml file is in the server
directory, I even opened up the permissions on it, in case
that was the problem. For whatever reason, LAS isn't seeing
that insitu_operations entity...
-Andrew
-----Original Message-----
From: Chase, Andrew [mailto:achase@mbari.org]
Sent: Tuesday, November 09, 2004 11:43 AM
To: 'las_users@noaa.gov'
Subject: RE: Problems setting up insitu data access
Hi Roland,
Thanks for your reply. I'm pretty sure I've got the proper
references to the insitu_operations.xml in the las.xml file
as well as the insitu_operations.xml file in the server
directory. I double-checked those steps of the setup process
after I received your email, and I made sure to verify that I
followed the directions laid out in the documentation. I'm
still getting the same error though. I'm going to go back
through one more time and make sure my configuration follows
the documentation, any other suggestions?
Thanks for explaining the path mapping to element
hierarchies, that makes a lot more sense.
Cheers,
Andrew
-----Original Message-----
From: Roland Schweitzer [mailto:Roland.Schweitzer@noaa.gov]
Sent: Tuesday, November 09, 2004 11:25 AM
To: Chase, Andrew
Cc: 'las_users@noaa.gov'
Subject: Re: Problems setting up insitu data access
Andrew,
You need to make sure the file insitu_operations.xml is in your
$LAS_HOME/server directory. If not copy it over from
contrib/insitu/server/.
Then add a reference to it in the <operations> element of
your las.xml
file. E.g.
<!ENTITY InsituOperations SYSTEM "insitu_operations.xml">
...
<operations url="http://server.com/las-bin/LASserver.pl">
&StdOperations;
&InsituOperations;
</operations>
By the way, the paths /lasdata/operations/insitu_data_cdf and
the like
refer to element hierarchies in the XML document, not Unix file
systems. The software is looking for a definition in an element
hierarchy like this:
<lasdata>
<operations ...>
<insitu_data_cdf.../>
...
</operations>
</lasdata>
which you will be supplying by installing the reference to the
insitu_operations.xml file.
Roland
Chase, Andrew wrote:
Hello fellow LAS users,
I'm working on serving non-gridded data from a database and
as a first step I've been trying to setup the insitu dataset
that comes with the LAS distribution. I'm using LAS version
6.4.1 on a itanium 64 running Redhat 9. I went through the
'make insitu' process and everything seemed to install fine.
However, when I try to get any sort of output from the the
insitu dataset I get an error.
With the following options selected:
Select view: Longitude-Depth Sections
Select output: ASCII table
Select region: Full Region
Select time range: 01 Jan 1986 to 31 Dec 1988
Select depth range: 0 to 2000
Select Constraints: None
Rather than getting the expected ASCII table, I receive the
following error:
LAS Error
The following error message was received from LAS:
Can't find match target '/lasdata/operations/insitu_data' at
'insitu_data' at ../xml/perl/LAS.pm line 613
Depending on the selected view and selected output, I get
other similar errors:
LAS Error
The following error message was received from LAS:
Can't find match target
'/lasdata/operations/insitu_data_cdf' at 'insitu_data_cdf' at
../xml/perl/LAS.pm line 613
LAS Error
The following error message was received from LAS:
Can't find match target '/lasdata/operations/insitu_meta_xy'
at 'insitu_meta_xy' at ../xml/perl/LAS.pm line 613
Looks like I've got some sort of path configuration problem,
but I can't find any documentation on how to set up the
lasdata path. Additionally, I can't find an "operations"
directory within my LAS installation. I see a .jnl file named
insitu_meta_xy in $LASHOME/server/jnls/insitu/ is this what
LAS is looking for? I don't see any files named insitu_data
or insitu_data_cdf anywhere in the $LASHOME directory.
Any thoughts, suggestions?
Thanks,
Andrew
Andrew C. Chase
Software Engineer
Monterey Bay Aquarium Research Institute
(831) 775-1865 :: Work
(858) 349-3443 :: Cell
[Thread Prev][Thread Next][Index]
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement