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

[LDM #QPY-276402]: LDM & edexBridge

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #QPY-276402]: LDM & edexBridge
  • Date: Tue, 16 Feb 2016 12:20:36 -0700
Matt,

Our AWIPS II expert, Michael James, might be able to help you -- except he's 
unavailable until next week.

I think there's a directory that's observed by EDEX: if something is put there, 
then it will be processed. Have you tried that method?

> Steve,
> 
> I am using the '-edex' option, yes.
> 
> I have edited my pqact.conf file to only handle the file
> TIPI10_KNES_111303_106608.2016021114 and store it in the /data_store, per
> the line below.
> 
> NOTHER  TIPI10_KNES_111303_106608.2016021114    FILE    -overwrite -log
> > -close -edex
> > /data_store/sat/20160211/13/VIIRS/TIPI10_KNES_111303_106608.2016021114
> >
> 
> When I manually ingest  the file TIPI10_KNES_111303_106608.2016021114,
> pqact picks up and files it to the data store, but there is never anything
> communicated over edexBridge to qpid. Would you know of someone I can
> contact that may be able to help me resolve the issue?
> 
> Thanks!

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: QPY-276402
Department: Support LDM
Priority: Normal
Status: Closed