Skip to main content
Question

JSON from ActiveMQ not writing to database.


Forum|alt.badge.img

I have a workspace that I am using a JMSReceiver to receive JSON files from ActiveMQ. I am then using a JSONFlatterner to parse out the JSON fields. When I write the output to an email the attributes get sent to the email body as expected. But when I try writing the same output to a geodatabase feature class or a text file the attributes do not write. In the case of the text file the variables are identical to the variables for the email body - works for the email but not the text file. Am I missing a step that is causing the output not to be written to the text file or geodatabase?

@Value(P_LINK_ANNTENUATION)

@Value(P_LINK_ANTENNA_AZIMUTH)

@Value(P_LINK_ANTENNA_HEIGHT)

@Value(P_LINK_ANTENNA_TYPE)

@Value(RTU)

@Value(SCADA_DB_RTU_ID)

2 replies

ebygomm
Influencer
Forum|alt.badge.img+38
  • Influencer
  • November 21, 2024

Did you ever get anywhere with this?


ebygomm
Influencer
Forum|alt.badge.img+38
  • Influencer
  • November 22, 2024

I can write some data to a gdb by using a time windower and group processing with “Complete Groups when Group Changes” set

 

However, there doesn’t appear to be anyway to write data in a timely manner if there is a gap or the last batch if you manually stop the process.

 

Stated here.

What's Up Wednesday (2-November-2022): Streaming to a Database, Mapping Month Webinars, Conference Videos, and (yes) much more! | Community

“Another interesting twist is that the data isn't written until a feature with a new time window arrives. If there is no new feature, the old data doesn't get written. So that's just something to be aware of.”

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings