Latest Contributions by RJSunderman

Hello Dennis - Would you mind sending me the JSON you are using? Are you using a File/Text input or are you POSTing the data to a GEP REST endpoint? I'd like to try and reproduce what you are observing and want to follow as close as possible the steps you followed to cause the problem to manifest. I may also need a MPK map package defining the schema of the features you publish as a feature service, so that I can configure a field mapper from the JSON to the Feature Service schema. Thanks - RJ ... View more

Mark - I was able to confirm that neither the syntax ${FieldName[idx]} nor ${Fieldname}[idx] appear to work with the 10.2.1 product release when attempting to configure an SMS or E-mail output to pull values out of a list added to a GeoEvent by a GeoTagger processor. I think I'm able to do what you're trying to do, however, if I incorporate a Field Calculator. I reconfigured the GeoTagger processors in my service to use the 'List' GeoTag Format rather than the default DelimitedValue format. Then, before the enriched event is sent to the Output connector,  I configured a Field Calculator (see illustration below) to extract a String element from the List into a new field. Then I reference the new field in the email-text-out Output, to avoid having to combine the square-brackets required for indexing with the curl-brackets used to indicate in the Output's configuration that we are inserting a value from an event field. [ATTACH=CONFIG]30413[/ATTACH] You might recognize that a GeoTagger processor is really a specialized implementation of a Field Enricher processor and a spatial filter and consider exactly what you are trying to accomplish with the event enrichment being performed by the GeoTagger. If you were to configure the GeoFences property of your GeoTagger with ".*/.*" the processor would consider all GeoFences in all GeoFence Categories. In this case, I don't think you'll be guaranteed that enrichment will occur in the same order every time. That is to say, if you always pull the 0th item from the GeoTags field (assuming that field is a List) you may not always get the name of a GeoFence from the same category (assuming that you have GeoFences in more than one category). Multiple GeoFences, which may or may not overlap, which are organized in multiple categories, might necessitate you take a specific approach when designing your GeoEvent Service. We will look into addressing the apparent syntatic limitation when working with event fields which are Groups and Lists in the different Notification output connectors. Hope this information helps - RJ ... View more

Hello Mark - Would you mind packaging your map document and data as a MPK and sending that to me?  I'd like to take a look at the features used to publish the feature service. As for your second question, synchronizing your GeoEvent Processor's GeoFences through the MapServer endpoint is really the same as using the FeatureServer endpoint. GEP is retrieving the coordinate data from the features in the service and then using the retrieved coordinates for its spatial comparisons. GEP is not referencing the actual features from the feature service, so there's no clear benefit to using the MapServer over the FeatureServer endpoint. - RJ ... View more

Hello Mark - Is there any documentation on the GeoTag format property of the Processor element? I don't really understand the purpose or intended usage of this option. No, the Tutorial" rel="nofollow" target="_blank">http://www.arcgis.com/home/item.html?id=265c334a47994dcc95e1bd57cf20e98e]Tutorial - Introduction to GeoEvent Processor currently available on the Product Gallery does not explain the three options for the GeoTag Format property of the GeoTagger processor. It uses the default (DelimitedValue) without explaining what the other options (Group and List). I will work to better address this in the version of the tutorial being developed for the 10.2.1 product release. If I remember correctly, 'Group' will create a cardinal list of group elements, with the GeoFence name (and optionally the category name) of each GeoFence which satisfies the spatial expression (e.g. INSIDE .*/.*) whereas 'List' generates a simple cardinal list with the GeoFence name (and optionally the category name) of each GeoFence as separate list elements. So the 'List' enrichment similar to 'DelimitedValue', except that each value is in a list rather than in a String separated with commas. Your best bet for now is to review the GeoEvent Definition created by the GeoTagger processor and look to see how it defines the field element containing the event enrichment values. Is there anyway to access the separate items in the geotags fields? If you are using the default, DelimitedValue, to combine the GeoFence names (and optionally category names) of the different GeoFences in which your event is INSIDE (for example), then you only have a comma separated list of values with no way to index into the string. If you were to experiment with using either the Group or the List output format options, then you might be able to include an expression like ${GeoTags[0]} to obtain the first ordinal from a cardinal field GeoTags. Whether that gives you a String (Category/FenceName) or a Group element (with subfields .Category and .Name) depends on whether the GeoTagger processor is configured to enrich events with a 'Group' or 'List'. I haven't tried this myself, so I'm not sure of the syntax. I will try to make some time to do so and reply back to this thread. - RJ ... View more

3. Select 'Trace' for 'Log Level' Completely misstated - apologies. You should set the logging level to 'INFO' for 'ROOT'  (not 'TRACE') in order to reduce log verbosity. Setting the logging level to 'TRACE' as I suggested turns verbose logging on. - RJ ... View more

In this case I would recommend that you alter your Input component's configuration to indicate that, no, the event stream does not contain the name of the event definition. You will want to specify that, yes, you do want a fixed event definition to be created and provide a name which does not include the ':' which the product currently recognizes as an illegal character. Please see the attached screenshot below. The event definition created will be reused for every event whose signature (number of attribute fields and data types) matches the first event received. - RJ ... View more

Hello Ayman - Thank you for clarifying what you were trying to accomplish. My apologies for misunderstanding... At the 10.2 / 10.2.1 release, the Output connector supporting logging event data to a CSV system file won't support what you are trying to do dynamically ... unless you know in advance the track IDs of the vehicles being reported by your AVL system. For example, if you knew that vehicles TRC2478, TRC290, and TRC2812 were expected to report, you could use filters to isolate events for each reporting vehicle and direct those vehicle reports to separate Output connectors. You would need to specifically configure each Output connector to write to either a file or sub-folder dedicated to a specific vehicle. If the track IDs of the vehicles being reported by your AVL system are not known, then pre-configuration of Output connectors and addressing the need with event filtering is obviously not an option. In that case you would have to develop a custom transport using the GeoEvent Processor SDK. Your custom transport could parse the outbound stream to discover the track ID, determine if a system file/sub-folder had been established for that vehicle, and take appropriate action. The ability for a transport to query an outbound stream for a track id was developed for the 10.2.1 product release. As a side note, Notifications (e-mail, SMS message, etc.) have been enhanced to enable service designers to retrieve address information from event attribute data in order to dynamically direct notifications to recipients. This capability will be available in the 10.2.2 product scheduled for release in March 2014. If similar capability is important to your successful adoption of GeoEvent Processor when working with system file output, please post the idea to the ArcGIS Ideas portal (http://ideas.arcgis.com). Community support for an idea helps us prioritize future product enhancements. Be sure when submitting ideas to tag the idea with "GeoEvent Processor" and check the "ArcGIS Server" category. Regards - RJ ... View more

From GeoEvent Processor Manager: Select 'Logs' to switch to the 'View Log Messages' page Click 'Settings' to display the 'Log Settings' dialog Select 'Trace' for 'Log Level' Select 'ROOT' for 'Logger' Click 'Save' This should reset your GeoEvent Processor logging to a non-verbose level. ... View more

Hello Dennis - Yes, you can edit a GeoEvent Definition by editing the XML you export from Manager, but this isn't exactly recommended. The 10.2.1 product release will include the ability to edit hierarchical (group) elements as well as cardinal (list) elements. The attached ZIP contains an MP4 video which shows this. The 10.2.1 product is scheduled for public release next week (January 7th). If you do find yourself needing to edit and/or create an event definition outside of Manager, I've included a screenshot in the ZIP which shows how the XML nodes are nested for the 10.2.1 release. I don't think this has changed since 10.2 - but that is part of the reason for recommending that you not edit the XML yourself. If the development team decided to change the node structure we would consider that an internal change not necessarily advertise it. I wouldn't want you to borrow trouble by editing a file we didn't intend you to edit. Proceed with caution. - RJ ... View more

Hello Ayman - What you describe I see folks doing all the time - by accident. Consider the event data illustrated below (ignore the empty lines, they are there only to help make the data more readable). If an Input such as "?Receive text from a TCP Socket"? were configured with the Incoming Data Contains GeoEvent Definition parameter set 'Yes', and the Create Fixed GeoEvent Definitions parameter also set 'Yes', GeoEvent Processor would receive the first event for flight SWA2706 and look for an event definition with that name. Failing to find one it would create a new one. The next event for flight SWA724 would likewise fail to find an existing event definition with that name and create a new one. This process would continue for the first nine events (as the tutorial's data only has nine uniquely identified flights) before existing event definitions would be found by name and used. You can imagine how, if an analyst did not have significant control over the data being received, that dozens and dozens of event definitions could conceivably get created which differ in name only. I included an illustration of this following the sample event data below. Best practice is to know the format of the event data you expect to receive, create a suitable event definition for that schema, and couple an Input with a specific event definition to receive the expected data. Normally you wouldn"?t expect the event schema of data coming over a dedicated channel to change, and if a provider were sending different classes of events over a single channel you would probably only want to take one particular class of the data being provided. The ability to configure an Input to create event definitions for you based on data discovery is intended to make the product more generic and more user-friendly. But it does not absolve you of your responsibility know and understand the structure of the data you expect to receive. - RJ ... View more

Hello Ayman - The situation I think you are describing, a GeoEvent Service with active failover, is not configurable out-of-the-box. You would need to implement a custom service component using the GeoEvent Processor SDK to either detect or anticipate the failure, and then handle the failure appropriately. The Output components provided out-of-the-box have no callback mechanism to alert GeoEvent Processor that the Output failed to correctly handle data it received. There is no way to alert the service containing the Output that an event needs to be reprocessed along a different event path. If an Output is responsible for updating a feature service, for example, but the server hosting the feature service is unreachable for some period of time, you will likely see the error logged but you cannot configure GeoEvent Processor to automatically recover and re-process the event. - RJ ... View more

Hello Ayman - I have a device that send the following string to GEP "POS:TRAFFAVL0049,1363478415,+25.32340050,+51.48632812,-12.847000,548946,2800847,3.9,141.7,35,16,0,1.570,44,39R" The first String POS is a static value, but next to : is a dynamic value as in the example above it's TRAFFAVL0049. A quick remark on your input - since the entire string is quoted, your event really only has one input field, a literal string. The fact that the string contains commas is irrelevant. If you want to send events into GeoEvent Processor whose attribute values are comma separated values, you need to drop the quotes so that the attributes will be recognized as separate values. As I understand the string sent to GEP should contain in the first string a name of geoevent definition. How I can create a GeoEvent defenition based on the above String. Receiving event data as comma separated text, you can configure an Input connector (�??Receive text from a TCP Socket�?? for example) to use the first field's value to determine an appropriate event definition to apply to the remainder of the event�??s payload (e.g. the remaining comma separated values). But you don�??t have to�?� Figure 1 below illustrates the default �?? the Input is configured to expect the event definition be specified as the first value. If you can change the response to the first Yes/No parameter to �??No�?? a new parameter will appear asking if you want GEP to attempt to create event definitions for events it does not recognize based on data discovered in the event (see Figure 2). If you configure your Input to create a fixed GeoEvent Definition, you should specify a name for the event definition that will be created. This implies that all of events received on the specified port will share a common schema �?? a common practice, but not a requirement imposed by the product. Figure 3 illustrates a more generic case in which you specify that, no, the event data does not specify an event definition, and no, you do not want GeoEvent Process to attempt to create one. Instead, you specify that all events received on the specified port should be evaluated using the specified event definition �?? �??AVL-Data�?? in the illustration. I this case you would need to either create the event definition within Manager, or repurpose an existing definition created previously. If you absolutely have to �?? because you cannot otherwise have the system component which provides the event data remove the quotes �?? we can probably design a GeoEvent Service which will trim the quotes from the received data string and write the modified event data out as true comma separated values (rather than as a quoted string). A second Input might then be used to re-ingest the processed data �?� but you will find this approach presents you with new challenges such as how you want to handle the processing of duplicate events. Hope this information helps - RJ ... View more

You might want to take a look at this thread:  lost" rel="nofollow" target="_blank">http://forums.arcgis.com/threads/94947-lost-geoevent-services-on-server-reboot]lost geoevent services on server reboot Summary Points: We recommend a minimum of 6GB of RAM for GEP (vs. the 4GB minimum recommendation for ArcGIS Server). GeoEvent Processor has a default 2GB limit for RAM allocation. You can configure this for your instance. Locate the product installation folder �?�\ArcGIS\Server\GeoEventProcessor\etc on your system and open the ArcGISGeoEventProcessor.cfg file in a text editor. You should be able to locate the configuration setting toward the top of the file: # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=2048 The default sizes for the queues used by the Event Processing framework can also be adjusted; you would only need to consider that if you were working with high volumes of event data. To adjust the queue sizes edit the com.esri.ges.messaging.jms.cfg and increase the defaults to reflect the following: com.esri.ges.messaging.jms.destinationPolicy.queue.memoryLimit (10 megs) com.esri.ges.messaging.jms.destinationPolicy.topic.memoryLimit (10 megs) com.esri.ges.messaging.jms.destinationPolicy.topic.memoryLimit (1 gig) Regards - RJ ... View more

Hello Elisabeth - Attached is a preview draft of the NMEA Connector tutorial. This should be uploaded to the GeoEvent Product Gallery shortly. The draft attached below may have some rough spots (copy editing on the document is not yet complete), but the content is all there. Please let me know if you have any questions or feedback on changes needed to the tutorial. Please note that this draft of the tutorial was prepared for the GeoEvent Processor 10.2.1 product release, which should be publicly available the second week of January 2014. The most significant change you would probably notice is that the Service Designer, the separate application you run to design and publish GeoEvent Services at 10.2.0, was retired. The functionality has been integrated into the GeoEvent Processor Manager at 10.2.1. I mention this so that you are not confused if you go to the GeoEvent Services page in Manager and don't see an 'Add Service' button ... you won't see that until you have the 10.2.1 product release. - RJ ... View more

Apologies - forgot to attach the promised performance planning and capacity documents. ... View more