[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #GFC-281181]: Adde server



Hi Randy,

re:
> I have a machine with mcidas MD files on them. I would like this machine
> to be an ADDE server for those files. I have never done this before and
> am unsure of the procedure.

Are you using Unidata McIDAS?  If yes, the procedure is very simple and is
discussed in the Unidata McIDAS-X Users Guide:

http://www.unidata.ucar.edu/software/mcidas/2005/users_guide/upc_configuremcidas.html

The instructions contained in this URL assume:

- you are using Unidata McIDAS
- you have installed McIDAS in an account named 'mcidas'
- you have setup an account named 'mcadde' that:
  - is NOT a login account
  - has the SAME home directory as the user 'mcidas'
- you have configured your 'mcidas' account to define needed Unix
  environment variables for McIDAS (e.g., MCDATA, MCPATH, MCTABLE_READ, 
MCTABLE_WRITE,
  etc.)
- your system administrator has configured your machine's firewall to allow
  communications through port 112
- the site is using the Unidata LDM and McIDAS-XCD in combination with one 
another

The configuration that is explained is one where McIDAS-XCD is creating output
data files (e.g., MDXXnnnn, GRIDnnnn, *.XCD, *.IDX, etc.) in a single directory
that is identified by the McIDAS string XCDDATA.  In the Unidata McIDAS scheme 
of
things, users define a set of file REDIRECTions that locate the files that 
McIDAS-XCD
creates/updates/maintains.

The basic concepts are simple:

- "teach" McIDAS about the location of the data files to be served by defining
  file REDIRECTions (e.g., REDIRECT ADD MDXX "/data/mcidas).  The file of 
example
  REDIRECTions in my distribution is ~mcidas/data/EXAMPLE.NAM.  The user
  makes the copy ~mcidas/data/LOCAL.NAM which s/he then edits to set the 
REDIRECTion
  paths to reflect her/his McIDAS installation and desired output directory.

- make a copy of the file containing example ADDE server mapping table
  configurations (a series of DSSERVE commands).  The file in my distribution
  is ~mcidas/data/DSSERVE.BAT.  The copy to be made would be 
~mcidas/data/LSSERVE.BAT.
  The user then edits LSSERVE.BAT to include or exclude dataset definitions that
  s/he wants while adjusting file locations (DIRFILE= keyword values) wherever
  needed.  NOTE: DSSERVE.BAT has definitions for all of the datasets that one
  could create with McIDAS-XCD and for images included in the Unidata IDD 
'UNIWISC'
  (GOES imagery), NNEXRAD (NEXRAD Level III products), and NEXRCOMP (NEXRAD 
Level III
  composite images).  It is most likely that you would comment out (or delete) 
most
  of the definitions in your local copy, LSSERVE.BAT.

- after making changes the local file copies above (LOCAL.NAM and LSSERVE.BAT), 
the
  user 'mcidas' would CD to her/his McIDAS working directory (~mcidas/workdata 
for
  Unidata McIDAS; ~mcidas/mcidas/data for SSEC McIDAS) and make the definitions
  active:

  <as 'mcidas'>
  cd ~mcidas/workdata
  te.k XCDDATA \"/directory_where_your_XCD_datafiles_live
  redirect.k REST LOCAL.NAM
  batch.k LSSERVE.BAT

After the last step, the user 'mcidas' should be able to access the various data
as LOCAL-DATA.  You should test this using things like:

<as mcidas>
cd ~mcidas/workdata
dmap.k MDXX
dsserve.k LIST RTPTSRC
ptlist.k RTPTSRC/PTSRCS FORM=FILE ALL

Your question goes beyond this, however, since you want this machine to act as
a remote ADDE server.  The steps past this point are very simple in Unidata
McIDAS:

- copy ~mcidas/admin/mcadde_env.ksh ~mcidas/.mcenv
- edit ~mcidas/.mcenv and modify the environment variables to match
  your McIDAS installation (may require no modifications)
- setup the ADDE remote severe access as 'root':

<as 'root'>
cd ~mcidas
sh ./mcinet2005.sh install mcadde

Assuming that there were no errors while running mcinet2005.sh, and assuming
that your system administrator has configured your machine's firewall to allow
traffic through port 112, you should now be able to access the ADDE datasets
defined above (the batch.k LSSERVE.BAT step) through the remote interface.

> Thanks,

No worries.  Good to see you at AMS...

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: GFC-281181
Department: Support McIDAS
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.