Latest Contributions by RJSunderman

Sorry Jim - I don't have much experience working with EDN licenses, so I'm not able to advise you on how to determine what level of EDN licensing Avista has acquired. I'm going to pass this inquiry along with your contact information to Esri Customer Service. Someone should get back with you shortly. - RJ ... View more

Hello Jacob - You should be able to specify a URL parameter which includes embedded username and password credentials when configuring a Poll an External Website for XML inbound connector. However, you should be aware that doing poses a security risk, potentially exposing your credentials as the URL parameter is readable by anyone able to access your Server's REST endpoints ... specifically the GeoEvent endpoints on port 6180 (e.g. http://MyServer.MyDomain:6180/geoevent/rest). The better approach would be to configure a new inbound connector using the HTTP‑BasicAuthentication transport and XML adapter. The transport and adapter are both available out of the box. Configuring a new connector does not require any SDK development. From within GeoEvent Manager, navigate to Site > GeoEvent > Connectors and click Create Connector. In a separate tab/window you can click to open any of the existing connectors to see how they have been configured and use them as an example. If you do decide to use the out-of-the-box Poll an External Website for XML inbound connector, you may find that you need to URL encode the credentials you are embedding in the connector’s URL property. The correct syntax, I believe, is https://<user>:<password>@app.site.com/ So, for example, you would URL encode your string as follows: (Plain Text):  https://Jacob26:[email protected]/feeds/assets.xml (URL Encoded):  https%3A%2F%2FJacob26%3Apassword123%40app.site.com%2Ffeeds%2Fassets.xml I tend to use http://meyerweb.com/eric/tools/dencoder/ when I need to interactively encode / decode URL strings. Looking at the examples you posted … you may also find that you need to drop the @domain.com suffix from the URL. I am less sure about this than recommending you URL encode the value however. It may be that if you URL encode the value then you’ll be able to specify the fully-qualified credentials:  [email protected]:[email protected] Hope this information helps - RJ ... View more

Hello Felipe - The GeoEvent Extension does not provide an outbound connector specifically for the Whatsapp instant messaging application. It appears that Whatsapp is an XMPP based application and GeoEvent does include an XMPP adapter. You will probably find that you have to configure a custom connector using the out-of-the-box MessageFormatter adapter and XMPP transport however to get GeoEvent notifications to work with your Whatsapp application. In GeoEvent Manager, navigate to Site > GeoEvent > Connectors and look for the Send an Instant Message outbound connector (one of the connnectors available out-of-the-box). You can edit this connector to review its configuration and use that as a sample for configuring your own custom outbound connector. There is a section in the Notifications Tutorial​ which discusses how the Send an Instant Message connector is used. The exercises uses the Openfire / Spark XMPP client/server from igniterealtime.org. Installing these might help you figure out how Whatsapp needs to be configured to work with the custom XMPP outbound connector you configure for GeoEvent. Hope this information is helpful - RJ ... View more

James - My apologies that no one has gotten back with you in response to your questions. If you are able to install the GeoEvent Extension, but cannot load the GeoEvent Manger web application when browsing to https://localhost:6143/geoevent/manager and want to check product licensing, there is a run-checklicense.bat script in the ...\Program Files\ArcGIS\Server\GeoEvent\bin folder. Edit the script so that it appears as follows (new lines frequently do not register for me correctly in the installed file): echo off set output= set JAVA_EXE=C:\Program Files\ArcGIS\Server\framework\runtime\jre\bin\java FOR /F "delims=" %%i IN ('"%JAVA_EXE%" -cp .\PostInstaller.jar com.esri.geoevent.license.LicenseStatusCheck') DO set output=%%i if [%output%] == [] GOTO NOT_LICENSED echo License is valid exit /b 1 :NOT_LICENSED echo License not valid exit /b 0 The script should run the java.exe located in the JRE bundled with your ArcGIS Server installation, loading the specified *.jar file and executing the specified LicenseStatusCheck to verify your GeoEvent Extension has been correctly licensed. Hope this information helps - RJ ... View more

Jim - The various extensions for ArcGIS Server are not available with a 'Basic' EDN subscription, but several, including the ArcGIS GeoEvent Extension for Server, are available with a 'Standard' subscription. All of the ArcGIS Server extensions are available with an 'Advanced' EDN subscription. Esri Developer Network - EDN Subscriptions Include - RJ ... View more

Hello Alice - I spoke with Michael Seybert in Esri customer service. He indicated that he works with your CIO (Teresa Luna?) ... Michael should be contacting you or someone in the Idaho OCIO soon. I can confirm that the ArcGIS GeoEvent Extension for Server is in fact an extension for the ArcGIS Server product. It was first introduced as the "GeoEvent Processor" with the 10.2 product release of ArcGIS and renamed shortly thereafter to more appropriately identify it as an extension to the ArcGIS Server product. GeoEvent is licensed separately from ArcGIS Server as an add-on / extension. It is Esri corporate policy to not discuss licensing terms or quote product costs through the forums or blogs. An organization's licensing is generally negotiated taking in to account the number of licenses and products you need to support your enterprise. You might find the following links helpful: ArcGIS Capabilities - Real-Time GIS​ Real-Time Data Feeds and Sensors - GeoEvent Extension GeoEvent Extension - Tutorials If you do not hear back from Michael in a couple of days, please give him a call at 888-377-4575. Best Regards -- RJ ... View more

Thank you for your clarification Rainer.  I adjusted my test to use an outbound connector configured to use the Generic-JSON adapter and WebSocket Transport running in SERVER mode. This connector configuration was depreciated with the 10.3 release. Event processing throughput is severely impacted when a GeoEvent Service contains an output running in SERVER mode and the GeoEvent Extension is run on multiple machines in an ArcGIS for Server cluster. The performance considerations, however, are not an issue when running a single instance of the GeoEvent Extension ... and establishing a WebSocket based output running in SERVER mode is the only way to connect a web browser to the WebSocket as a client to review the JSON output in the browser window. I think my test is now closer to replicating your setup. I was able to reproduce the issue you describe on a 10.2.2 product release after just a few minutes sending 10 events per second. What I'm seeing does look a lot like the issue I was referring to in my previous reply where the generic JSON adapter would occasionally output invalid JSON records. My apologies, I thought this was an issue I observed in 10.2.1 which was fixed in 10.2.2 ... I found the issue record I was recalling and confirmed with a developer that the issue was found in the 10.2.2 release and was addressed in the 10.3 release. I was able to import my 10.2.2 GeoEvent configuration into a clean 10.3 environment and retest. I used your Track Simulator to simulate 10 separate tracks, pushing 10 events per second into the GeoEvent Service. I ran the simulation for 20 minutes sending over 12,000 events through the GeoEvent Service. Copying the JSON being output to the web browser's window into a text editor for analysis, I could not find any irregularities in the JSON displayed in the web browser client output. If you continue to observe the issue in either the 10.3 or 10.3.1 product release of GeoEvent, please submit an incident with Esri Technical support and we will work to establish an on-line meeting to reproduce the issue in your environment. We can then work to reproduce it here in Redlands so that we can investigate further. Best Regards - RJ ... View more

Hello Rainer - Yes, please confirm the release of GeoEvent that you are using. I seem to recall occasionally seeing the generic JSON adapter output invalid JSON records when sending many dozens of events a second to an outbound connector. The issue had nothing to do with the TRACK_ID or unique identification of tracks however, so I'm not sure if the issue I'm recalling has anything to do with what you are observing. The issue I'm recalling was addressed in the 10.2.2 product release I believe. In any case, I used your JavaScript Track Simulator to simulate a half-dozen inbound tracks. Your tool is generating Esri Feature JSON (which GeoEvent interprets / adapts using its "JSON" adapter) as opposed to Generic JSON or the GeoJSON format (supported at the 10.3.1 product release). I fed your simulator's input into a 'Receive Features on a REST Endpoint' input and directed GeoEvents adapted by that input to a 'Push JSON to an External WebSocket' output. I created a 'Receive JSON on a WebSocket' input (which runs in SERVER mode) to provide a hosted WebSocket for the output (which runs in CLIENT mode) to connect to. Finally, I created a 'Write to a JSON File', configured to not output formatted JSON, and configured a GeoEvent Service as follows: I typically refer to this as a "WebSocket Chain". The input to the upper-left, accepting Esri Feature JSON from your simulator, could be receiving any data feed. It sends the GeoEvents it constructs to a WebSocket output which are subsequently received by the paired WebSocket input (the second input illustrated above). GeoEvents received by this second input are then redirected into the system file. I ran the simulation for five minutes receiving a total of 1788 events on the rest-features-in input. All of the events received by this input were processed through the WebSocket Chain and were written into the *.json system file. Copying the contents of the *.json system file into an on-line JSON validator I found the file's contents to be valid and the expected number of events in the file. If the generic JSON adapter, the component responsible for generating the payload sent out the websocket-external-json-out, were generating invalid JSON I would expect to see some level of event loss in the *.json system file. I ran my tests using the 10.3.1 release candidate of GeoEvent. - RJ ... View more

10.3 Product Update At the 10.3 release of GeoEvent we began exposing some configurable properties through the GeoEvent Manager and retiring files from …\GeoEvent\etc rendered obsolete. The list of SMS carriers and their associated gateways is one of these properties. In GeoEvent Manager, if you navigate to Site > Settings you will see a page allowing you to Configure Global Settings. Search or scroll to locate the SMS Settings properties: Click to edit and you should be able to add regional carriers and their gateways to allow SMS notifications to be sent using GeoEvent. Look for an update to the Notifications tutorial to be uploaded this week (11-April-2015). Hope this information helps – RJ ... View more

Hello David - If the field type within your GeoEvent is already of type Geometry, then no, you cannot use a Field Calculator processor (for example) to reach into the Geometry object and extract out coordinate values. You might want to take a look at the Extent Enricher Processor available on the Gallery. The source code for this custom processor is available on GitHub here. As I understand it, the processor allows you to enrich an event with fields providing the minimum and maximum X and Y values. The processor can optionally enrich the event with a second Geometry representing the center point of the original geometry. I believe the processor, given a Point geometry, will return to you identical minimum X and maximum X values ... the minimum Y and maximum Y would likewise be the same. Hope this information helps - RJ ... View more

We have just today completed rework to the Notifications tutorial using the 10.3.1 product release and are copy editing the tutorial now. There are some changes to screenshots illustrating how to configure the outbound connectors for notifications, but the existing Notifications tutorial (10.2.x)​ should be sufficient to help you design e-mail notifications. We should have an updated Notifications tutorial uploaded this week or early next week. The notifications tutorial covers how to design GeoEvent Services to generate SMTP e-mail notification, SMS Text notification (which also relies on SMTP), as well as XMPP Instant Message. You should not expect to find help on how to configure an e-mail notification output, for example, in the product introduction tutorial. Some topics have to be split out to different tutorials as we work to manage the scope the product introduction tutorial - by far our largest tutorial. A 10.3 revision for the product introduction tutorial was released early February 2015. The product team works to update the tutorials as quickly as we can get to them. Many of the 10.3 connectors (Twitter, Instagram, etc.) had not been uploaded simply because their tutorial had not been updated so we didn't consider the offering complete. We've recently adjusted our release criteria and at least upload compiled *.jar files on the Gallery even if a revised tutorial is not available. If we have to release a connector without a tutorial, you'll find a README in the bundle you download indicating that content and exercises in the previous version's documentation should provide sufficient information to get started using the upgraded component ... just be aware minor differences could exist between the content, exercise steps, and screenshots as you are going through it. Tutorials are available on the ArcGIS GeoEvent Gallery​​​. If the content provided by an earlier release of a tutorial does not answer questions you have, please e-mail the GeoEvent Team at [email protected] and let us know. Please include GeoEvent Tutorial Feedback in the subject of your e-mail. This will help us determine which tutorials are the most important to the user community at large. ... View more

Astha - To ensure that your GeoEvent Stream Service deletes old features, there are three things you need to do to, in addition to checking Store Latest and specifying the Update Interval and Maximum Feature Age, when publishing the Stream Service: Make sure that an appropriate field has been tagged as the TRACK_ID Make sure that an appropriate field has been tagged as the TIME_START The date/time value in the event data is correctly expressed as epoch milliseconds UTC The first two are easy to check. In the ArcGIS REST Services Directory open the page for your Stream Service. In the upper left corner click the JSON link to view a JSON representation of the Stream Service's properties. In the first "paragraph" of the JSON, look to see if "trackIdField" and "startTimeField" are defined as the expected event attribute fields from your GeoEvent Definition. To check the third, in the ArcGIS REST Services Directory, open the page for the buddied Feature Service (should have the same basename as your Stream Service) and query the layer containing the features being retrained for the Stream Service. Copy / Paste the long integer representation of the date/time (the epoch milliseconds UTC) into a converter such as the Epoch and Unix Timestamp Conversion Tool and verify that the feature has the expected date/time value. If you could, please test using the default update interval and maximum feature age values (10 seconds and 60 minutes). If it is still not working we may need to dig in further. It may be that your chosen flavor of RDBMS (Oracle, PostGRE, vs. Sql Server) is not accepting the query expression GeoEvent is creating. - RJ ... View more

Rafael - sorry for the delay in responding to your post to the forum. There are some limits with how a Filter is able to parse a string representation of a date/time in order to evaluate a less-than / greater-than expression. Combining a date value and a time value together is not working. For example, instead of doing something like TIME_START = 3/16/2012 02:25:31 PM you need to write separate expressions for the date and time and then combine them using logical operators (AND, OR). For example, you cannot do this: But you could do something like this: Also, you might try working with the date/time values as long integers representing Epoch millisecond values. I know that within a Field Calculator you can perform simple arithmetic on a date/time to add, for example, an hour's worth of milliseconds to a value:  TIME_START + (60 * 60 * 1000). I'm not sure without conducting some experiments how a Filter will interpret an expression such as:  TIME_START >= 1331864731000. Hope this information is of some help - RJ ... View more