Latest Contributions by RJSunderman

‎12-04-2017

Hello John - You are correct - there is no way of using GeoEvent Manager or the GeoEvent Admin API to query the cache used by the inbound 'Poll ArcGIS Server for Features' input to effectively poll for incremental updates. There is a clarification I would offer, based on my read of your question. The cache is not a cache of the actual feature records. GeoEvent is not comparing feature records queried from a feature service to a cached copy of those same records. The cache is only a query key used to construct a WHERE clause. What GeoEvent Server is doing is iterating through all of the records returned by a particular query and caching the single attribute value which is the "greatest" of the feature record set. If the incremental update key is a date, then the date from the feature record with the most recent date is cached (not the entire feature record, just its date). That way, on the next query, GeoEvent Server can construct a WHERE clause to query only for feature records whose date is greater than the most recent date cached from the last set of feature records. A side-effect of this is that if you have false data in your feature records, you can inadvertently block your input from ever receiving incremental updates. Say your data policies are that no date field ever be null. So you default all "unknown" date values to a future value like January 1st 2199. Well, when GeoEvent polls the feature service and encounters one or more records with this future date, it will cache that date and construct it's next query to request only feature records whose "last updated" date is greater than 2199 - which more than likely excludes all feature records. Honestly, an SOI or other ArcObjects solution which is able to listen for something like IObjectClassEvents:onChange is probably the approach you want to take - rather than relying on GeoEvent Server to poll for incremental updates. - RJ

‎10-30-2017

Hello Susan - Please refer to the following thread: GeoEvent process Oracle/SQL connector‌ GeoEvent Server, as it is referred to now at 10.5 and 10.5.1 (vs. GeoEvent Processor or GeoEvent Extension for Server) assumes that a feature service will provide an interface to a feature class in a geodatabase. Additional detail and options are discussed in the referenced thread. - RJ

‎10-13-2017

Daniel Cota Chris Beyett‌ Vladimir Strinski‌ This issue is being tracked by Esri Tech Support as BUG-000107723 The GeoEvent Server product team has accepted the bug an is looking at a possible fix for the 10.6.1 product release. The issue does not appear directly related to the JSON adapter's Learning Mode. It is interesting that the issue's behavior changes in different browser clients with regard to the number of fields beneath a parent. Thank you for that information. As a work around, for 10.5.1 and likely 10.6, please consider manually creating a GeoEvent Definition which is flat (e.g. no Group elements). You should be able to apply your GeoEvent Tags to this flattened structure and/or change a field's data type to specify, for example, that a value ingested as Double can be handled as a Long integer. Note that you should be using flattened event structures with add/update feature as well as stream service outputs -- both outbound adapters in these cases translate an expected flat event structure into Esri Feature JSON (which is hierarchical) as part of their event record dissemination. It may also be possible, though much less palatable, to export the GeoEvent Definition which the GeoEvent Manager web application is not allowing a user to edit, use a text editor to edit the XML, delete the original GeoEvent Definition, and import the changes from the altered XML. I would expect anyone interesting in trying this to work with Esri Tech Support as accidentally changing the XML structure will prevent successful XML import and GeoEvent Definition recovery. - RJ

‎08-21-2017

In addition to what Chris says, keep in mind that the type of inbound connector is irrelevant. Once an inbound adapter takes data from and inbound transport and instantiates a GeoEvent event record ... you can send that event record to any type of output. You can ingest TCP/Text, or XML received via HTTP, and send that data out to a system file, a stream service, or update feature records in a spatiotemporal big data store. The key is probably going to be designing your GeoEvent Service to include a Field Mapper as the final node in the event processing flow, immediately before the event record it sent to your add/update feature records in a spatiotemporal big data store output. If the SBDS output receives an event record whose structure matches the GeoEvent Definition used when the SBDS data source was created ... you shouldn't have any problem adding/updating feature records in the SBDS. - RJ

‎07-26-2017

Hello Azin - The ArcGIS Server documentation includes reference architectures for deploying additional server roles (such as GeoEvent Server) to your ArcGIS Enterprise. The terms I'm using here are consistent with the 10.5.x product release. There are reference architectures for high availability as well as for GeoEvent Server. Based on the icons you included in your system architecture illustration, I might assume you've seen these references - but I wanted to make sure. I would point out that the reference architecture for GeoEvent Server which depicts a horizontal scale-out deliberately has white space between the machines: The white space is intended to depict your first stipulation -- that you do not 'Join Existing Site' when installing the GIS Server component of ArcGIS Server with the intention of later installing GeoEvent Server. Each of the three GeoEvent Server machines depicted above exist in their own site. They do not know anything about one another. This is to prevent leveraging a concept we refer to as "GeoEvent Clustering" which we introduced with the 10.3 release. Changes to address some issues were included with the 10.4 release. We eventually realized that the concept was fundamentally not working as we intended, and the advice now for releases 10.3 / 10.4 / 10.5 is to not have more than one GIS Server in a site when GeoEvent Server is installed. We are working on developing a "Gateway" component for 10.6 with the intent that GeoEvent Server will again offer some resiliency and improved scalability. However, until then, your challenge is to figure out how to configure an external component to handle event distribution to two or more instances of GeoEvent Server which do not know anything about one another. We prepared a GeoEvent Server Resiliency tutorial which proposes using Kafka as an external message broker. Kafka provides load balancing to your real-time event message ingest by holding messages in a queue until consumers (individual GeoEvent Server instances) fetch them at the rate they are able to process them. My terminology may be off; I would recommend you refer to Kafka's documentation as you read through the GeoEvent Server Resiliency tutorial. I hope this information is helpful -- RJ

‎06-15-2017

Hello Tony - The GeoEvent Server Field Calculator's expression parser does not accept VB or Python function syntax. It is a simple expression parser with limited support (through wrapper functions) for methods in the Java String Class which return non-list, non-arrayed values (e.g. int or string). Given an inbound event record: [{"UserID":"6a3fe3eb-4d6494d","URL":""}] You could configure a Field Calculator with the following expression to build the URL you are looking for. 'http://www.openstreetmap.org/trace/' + substring(UserID, length(UserID) - 7, length(UserID)) + '/data'‍ Notice that the literal strings are denoted with single-quotes, not double-quotes. Also, I am using nested calls to length() within my substring() function invocation. I need to specify a beginIndex and endIndex for the string I want to extract from the event attribute UserID. These values can be either computed or hard-coded. If you knew that the user id was always going to be formatted as it is in this example you could use substring(UserID,9,16) instead. Generally speaking, when invoking one of the Java String methods as a wrapper function, you have to insert the name of the event field you want the function to use as a 0th argument and you must use the most general function signature available (e.g. Java has methods for both substring(int beginIndex) and substring(int beginIndex, endIndex), but the function parser cannot support overloaded function signatures, so you must use the more general of the two and supply both indexes rather than allowing the invocation to assume "from here to the end of the string". Hope this information helps - RJ

‎06-09-2017

Unfortunately one of the design objectives for GeoEvent Server is to keep the product database agnostic. The map/feature service REST endpoints are the intended interface between GeoEvent inputs, outputs, and processors (such as Field Enricher) and data in an enterprise geodatabase. Database administrators have successfully created spatial views and registered these views with ArcGIS Server to create the service endpoint GeoEvent requires in order to access the database records. Cross Reference: https://community.esri.com/message/392202?sr=search&searchId=eda2663c-5cdb-4e62-9178-7ea09a82a61a&searchIndex=0‌

‎06-07-2017

There were fixes which appear related to the issue you're describing in patches released for the 10.4.1 and 10.5 product releases. If you haven't already, would you please download and apply one of the following, which ever one is appropriate for your deployment: ArcGIS 10.4.1 GeoEvent Extension Patch 2 ArcGIS GeoEvent Server 10.5 Patch 1 Esri Technical Support might be able to offer assistance. If you elect to submit a support incident, you might reference BUG-000100502. Hope this information helps - RJ

‎05-31-2017

This article is the second of two articles examining enhancements made to the HTTP transport for the GeoEvent Server 10.5 release. This article examines the outbound transport. The previous article examining the inbound transport can be found here. In this article, I would like to provide detail for an enhancement made to the HTTP outbound transport for the GeoEvent Server 10.5 release. The following capability is listed on the What's new in ArcGIS GeoEvent Server web help page: HTTP outbound transport now supports field value substitutions in the HTTP GET mode Beginning with the 10.5 product release, an output leveraging the HTTP transport can be configured to substitute event attribute values into the URL of a request GeoEvent Server will send to an external server. The attribute values are incorporated as query parameters (as opposed to the request’s content body). The new capabilities of the HTTP transport will be described below with exercise steps you can follow to demonstrate the capabilities. ~~~ When you want to send data from event records to an external server or application you typically configure an outbound connector – such as the Push JSON to an External Website output. GeoEvent Server will incorporate the event data into the content body of a REST request and send the request to the external server as an HTTP/POST. This capability has been available in the last several releases. A device on the edge of the Internet of Things, however, might prefer to receive requests with event data organized as query parameters rather than in a request's content body. This way the entire data payload is in the URL of the request -- leaving the content body of the request empty. It might seem a little odd for a GeoEvent Server output, which is not intended to receive or process any type response, to make an HTTP/GET request. But the capability was introduced to enable GeoEvent Server to issue activation requests to devices which require data values be sent using query parameters. ~~~ Exercise 2A – Use HTTP/GET to send event data as query parameters to an external server Why exactly are we configuring a custom outbound connector? How's it different than the the Push JSON to an External Website connector available out-of-the-box? For this exercise: Configure the following GeoEvent Server output connector. Browse to Site > GeoEvent > Connectors and select to create a new outbound connector. Default values for the "Shown", "Advanced", and "Hidden" properties are included beneath the illustration. Shown Properties Default Value URL [ no default value defined ] Advanced Properties Default Value Use URL Proxy False URL Proxy [ no default value defined ] HTTP Timeout (in seconds) 30 Hidden Properties Default Value Formatted JSON False MIME Type text/plain Acceptable MIME Types text/plain Post/Put body MIME Type text/plain Parameters [ no default value defined ] Header Parameter Name:Value List ( blank ) HTTP Method Get Mode Client Save your newly configured custom outbound connector. Navigate to Services > Outputs and select to create a new (Custom) HTTP/GET request with event data as query parameters output. Configure the output as illustrated below, replacing yourServer and yourDomain with a valid server and domain for your organization. Note the URL specified in the illustration: https ://yourServer.yourDomain/server/rest/services/SampleWorldCities/MapServer/0/query?where=city_name='${Origin}'&f=json The format of the URL assumes that an ArcGIS web adapter (named 'server') has been configured and that an external server or client application receiving this URL could use it to query the "Sample World Cities" map service on your ArcGIS Server. GeoEvent Server will substitute the variable ${Origin} in the URL's query parameter with an actual attribute value from a received event record, enabling the external server or client application to make a more specific query based on real-time events. Save your updated output, then publish a GeoEvent Service which incorporates your output and an input of your choice. You can use any type of input, so long as the GeoEvent Definition associated with event records received by the input includes an attribute field named Origin. Queries through a web adapter to a Portal secured web service from an unauthenticated source will return an error. Since the Sample World Cities web service is secured by Portal in my current deployment, I expect the request made by GeoEvent Server will generate an error. In order to complete the demonstration we will use the GeoEvent Server's debug logs to confirm that the output has constructed a valid query and sent the request to the ArcGIS Server map service. Navigate to the Logs page in GeoEvent Manager. Click 'Settings' and enable DEBUG logging for the feature service outbound transport logger (com.esri.ges.transport.http.HttpOutboundTransport). Send an event record to your GeoEvent Server input whose Origin attribute is the name of one of the cities in the Sample World Cities map service (e.g. Chicago). Refresh the Logs page in GeoEvent Manager and you should see log messages with information similar to the following: com.esri.ges.transport.http.HttpOutboundTransport https ://caramon.esri.com/server/rest/services/SampleWorldCities/MapServer/0/query?where=city_name='Chicago'&f=json: Request succeeded {"error":{"code":499,"message":"Token Required","details":[]}} The first message shows that 'Chicago' was indeed substituted into the query parameters by the GeoEvent Server output and a request was made. The error may or may not be displayed; as indicated above, the map service in my case is Portal secured and this request did not include a token authenticating the request. There are a couple of things you'll want to keep in mind. The URL you use to configure the the output must URL Encode its query parameters to make them HTTP safe. But the value is being substituted by GeoEvent Server is based on a string received from a real-time data source. This means you may have some work to do to make sure that "San Francisco" is represented as San%20Francisco not San Francisco before an event record is sent to an output. Also, the enhancement being introduced in this article was designed specifically for HTTP/GET since those requests do not include a JSON payload in the request’s body. However, some rudimentary testing suggests that you can use HTTP/POST as well; I suppose it would be up to the external server receiving the request whether or not to honor an HTTP/POST and either ignore the request’s JSON payload or potentially consider its content in addition to the values in the query parameter. Finally, you do have some freedom in how the request’s query string is specified. For example, you could construct a parameterized string something like; GeoEvent Server will handle the substitution of the multiple parameter values: query?where=city_name+IN+%28%27${CityA}%27%2C%27${CityB}%27%29&f=json If you send the string highlighted above through an HTML decoder you'll see that it is equivalent to: where=city_name IN ('${CityA}','${CityB}')&f=json I hope these two blogs were helpful. Please comment below with questions and I'll do my best to answer them. -- RJ

‎05-31-2017

This article is the first of two articles examining enhancements made to the HTTP transport for the GeoEvent Server 10.5 release. This article examines the inbound transport. The second article examining the outbound transport can be found here. In this article, I would like to provide detail for an enhancement made to the HTTP inbound transport for the GeoEvent Server 10.5 release. The following capability is listed on the What's new in ArcGIS GeoEvent Server web help page: HTTP inbound transport now accepts GET requests in the query parameters Beginning with the 10.5 product release, an input leveraging the HTTP transport can be configured to support an external server or application which incorporates its data payload in the URL of the request (as opposed to the request’s content body). The new capabilities of the HTTP transport will be described below with exercise steps you can follow to demonstrate the capabilities. ~~~ When you want to receive event records as an HTTP/POST request from an external server or application you typically configure an inbound connector – such as the Receive JSON on a REST Endpoint input. GeoEvent Server will create a REST endpoint to which the external server can post its event data with the event data included in the content body of the request. This capability has been available in the last several releases. A device on the edge of the Internet of Things, however, might prefer to organize the event data as query parameters and incorporate its data payload in the URL of the request -- leaving the content body of the request empty. For example: http :// localhost:6080/geoevent/rest/receiver/http-receiver?field1=v1&field2=v2&field3=v3 http :// localhost:6080/geoevent/rest/receiver/http-receiver?data=v1,v2,v3 Beginning with the 10.5 product release an input pairing either the out-of-the-box JSON or TEXT adapter with the HTTP inbound transport can be configured to support the use cases above with an HTTP/GET request. ~~~ Exercise 1A – Use HTTP/GET requests to send event data to GeoEvent Server as query parameters Create the following GeoEvent Definition Configure the following GeoEvent Server input connector Note the new 10.5 parameter: Get Request Contains Raw Data Review the help tip provided for this parameter. If the inbound connector is running in SERVER mode and receives an HTTP/GET request, if the request content body is empty and the request URL includes query parameters, the default (‘No’) will consider each name/value pair as a separate attribute value in an event record. If the default is changed to ‘Yes’ you will be expected to specify the one query parameter which will be considered the event’s raw data. Configure a GeoEvent Server output connector and publish a GeoEvent Service You can use any outbound connector which supports JSON event record displays. Recommended output connectors are ‘Send Features to a Stream Service’ or ‘Write to a JSON File’. Send the following HTTP/GET request to your input connector’s endpoint http://yourServer.yourDomain:6180/geoevent/rest/receiver/rest-json-in?fname=Robert&lname=Lawrenson&employee_id=123 You should observe the event count of your ‘Receive JSON on a REST Endpoint’ input increment as HTTP/GET requests are made on your input’s REST endpoint ~~~ Exercise 1B – Explore HTTP/GET requests whose query parameters include comma delimited values Rather than incorporating the event data into a series of key/value pairs, the event data can be conveyed using a single query parameter whose value is a set of comma delimited values. The delimited text values will require an inbound connector which leverages the TEXT adapter (rather than the JSON adapter used in the previous exercise). GeoEvent Server does not include a “Receive TEXT on a REST Endpoint” inbound connector out-of-the-box, so you will need to configure one for this exercise. Configure the following GeoEvent Server input connector. Browse to Site > GeoEvent > Connectors and select to create a new inbound connector. Default values for the "Shown", "Advanced", and "Hidden" properties are included beneath the illustration. Shown Properties Default Value Event Separator \n (newline) Field Separator , (comma) Incoming Data Contains GeoEvent Definition False Create Unrecognized Event Definitions False Create Fixed GeoEvent Definitions False GeoEvent Definition Name (New) [ no default value defined ] GeoEvent Definition Name (Existing) [ no default value defined ] Language for Number Formatting [ no default value defined ] Advanced Properties Default Value Acceptable MIME Types (Server Mode) text/plain Expected Date Format [ no default value defined ] Build Geometry From Fields False X Geometry Field [ no default value defined ] Y Geometry Field [ no default value defined ] Z Geometry Field [ no default value defined ] Well Known Text Geometry Field [ no default value defined ] wkid Geometry Field [ no default value defined ] Get Request Contains Raw Data True Parameter Name for the Raw Data data Hidden Properties Default Value Mode Server Use Long Polling False Frequency (in seconds) [ no default value defined ] Receive New Data Only False Post/Put body MIME Type [ no default value defined ] HTTP Method Get Header Parameter Name:Value List ( blank ) Post/Put From Parameters Post/Put Parameters ( blank ) Content Body [ no default value defined ] Parameters [ no default value defined ] URL [ no default value defined ] URL Proxy [ no default value defined ] Use URL Proxy False Acceptable MIME Types (Client Mode) [ no default value defined ] HTTP Timeout (in seconds) 30 Append to the End of Payload [ no default value defined ] Save your newly configured custom inbound connector. Navigate to Services > Inputs and select to create a new (Custom) Receive TEXT on a REST Endpoint input. Configure the input as illustrated below. Use the GeoEvent Definition you created for the last exercise. Publish a GeoEvent Service which incorporates your newly configured input and any outbound connector which supports JSON event record displays. You can use the outputs configured for the previous exercise if you wish. Send the following HTTP/GET request to your input connector’s endpoint (note the endpoint's name has changed): http://yourServer.yourDomain:6180/geoevent/rest/receiver/custom-receive-text-rest-in?data=Robert,Lawrenson,123 You should observe the event count of your ‘(Custom) Receive TEXT on a REST Endpoint’ input increment as HTTP/GET requests are made on your input’s REST endpoint. ~~~

‎04-18-2017

On both the Linux and Windows platforms, GeoEvent Server is run from within a Java Virtual Machine (JVM) instance. The out-of-the-box default configuration allocates only 4GB of your server's available RAM to this JVM. All GeoEvent Server operations requiring RAM draw from this allocation. Some reasons you might want to increase the amount of RAM allocated to the GeoEvent Server's JVM include: A need to load a large number of geofences into the GeoEvent Server's geofence manager A need to process a large velocity or large volume of event records (more than a few hundred per second) A need to cache a large amount of information from a secondary enrichment source for event record enrichment An expectation that real-time analytics using Incident Detectors will generate a large number of concurrent incidents An expectation that real-time analytics requiring state (e.g. Track Gap detection and monitoring, or spatial conditions such as ENTER / EXIT) will need to work with a large number of assets with unique track identifiers System administrators who have determined that their server machine has sufficient available RAM, and who have also determined that their GeoEvent Server deployment has a need to allocate more RAM to the JVM instance running GeoEvent Server, can follow the steps outlined below to increase the memory available to GeoEvent Server by allocating more RAM to the hosting JVM. Stop GeoEvent Server On a Windows platform, make sure the GeoEvent Server Windows Service and its associated java.exe process are stopped. Open the ArcGISGeoEvent.cfg configuration file in a text editor On a Windows platform, this file is found in the ...\ArcGIS\Server\GeoEvent\etc folder by default When located beneath C:\Program Files you will need to edit this file as a user with administrative privilege Locate the block of JVM Parameters in the file Note that at different releases the indexes for the JVM parameters will be different from the illustration below Click the image below for an enlarged view in a new tab / window: Increase the -Xmx parameter for the Java Heap Size from its default (4096m) to specify a larger allocation For example: -Xmx8192m Note that the allocation is in megabytes Save your edits to the ArcGISGeoEvent.cfg file (and dismiss your text editor) Start GeoEvent Server Using system administrative tools you should be able to verify that the JVM instance (java.exe process) never consumes more memory than what is allocated by the ArcGISGeoEvent.cfg configuration file, and that more than the default 4GB is now available for GeoEvent Server operations.

‎03-16-2017

Tom - I am seeing the same com.esri.arcgis.discovery.json.JSONException thrown by the Check RabbitMQ diagnostic utility. I added a comment to the thread you referenced (Re: Diagnostic utility for checking the status of the RabbitMQ platform service ). I have to assume that the utility is not going to work with releases beyond 10.3.1 for which it was originally developed. Here are a some trouble shooting steps you might try with your 10.4.1 deployment. I would encourage you to submit this to Esri Technical Support as an incident and ask them to contribute to this thread with steps taken if you are able to work with them to resolve the issue. Stop the ArcGIS Server windows service At 10.4.1 a service dependency should also stop the GeoEvent Extension windows service. If not, please select and explicitly stop the GeoEvent windows service. Check the list of running processes on your Windows platform. The following processes, launched as part of the rabbitmq/erlang framework, part of the ArcGIS Server product's framework (...\ArcGIS\Server\framework\runtime) should no longer be running; they should have stopped when you stopped the ArcGIS Server windows service: Process Name: epmd.exe ExecutablePath: …\rabbitmq\erlang\ERTS-5~1.4\bin\epmd.exe Process Name: erl.exe ExecutablePath: …\rabbitmq\erlang\bin\erl.exe Process Name: win32sysinfo.exe ExecutablePath: …\rabbitmq\erlang\lib\os_mon-2.2.14\priv\bin\win32sysinfo.exe Process Name: inet_gethost.exe ExecutablePath: …\rabbitmq\erlang\erts-5.10.4\bin\inet_gethost.exe With GeoEvent stopped, delete its runtime files from its product directory folder: (...\ArcGIS\Server\GeoEvent\data) Start the ArcGIS Server windows service At this point you can check to verify that you can launch the ArcGIS Server manager web app to check the health of your Server site. You can also follow the steps from my 22-May-2015 comment to access the undocumented administrative endpoints for the RabbitMQ platform service. Administrative endpoints for the platform services were exposed through the ArcGIS Server Administrator Directory as part of the 10.5 product release. Start the GeoEvent windows service and check the logs for a message with text similar to: com.esri.ges.framework.messaging.jms-messaging GeoEvent successfully connected to ArcGIS Server Platform Service RabbitMQ's message broker Test to see if you can receive event records on an inbound connector and if the 'In' / 'Out' event counts for a GeoEvent Service incorporating that inbound connector also increment as event data is ingested. Hope this information helps - RJ

‎01-04-2017

Hello Greg - From what you've indicated, you have faithfully tried everything I know to try to investigate the ArcGIS Server platform service which provides GeoEvent its message broker (e.g. RabbitMQ). Your indications suggest to me that the platform service did not get installed / upgraded ... you may have to uninstall GeoEvent, uninstall ArcGIS Server and attempt to re-install the product (versus attempting an in-place product upgrade). I've contacted Esri Technical Support - someone should be reaching out to you soon. Unfortunately the RabbitMQ platform service is somewhat of a black box from a GeoEvent perspective. It it's healthy and running, GeoEvent works - if not then GeoEvent won't work at all. I've contacted Tech Support because this is an area of the ArcGIS Server platform that I cannot offer further advice on. Good Luck - RJ

‎01-03-2017

Hello John - I just posted a blog with a series of videos demonstrating how to use Stream Services. https://community.esri.com/community/gis/enterprise-gis/geoevent/blog/2017/01/03/stream-services-store-latest-and-related-features?sr=search&searchId=360aafbf-dace-4585-bf93-c7fa1124b4dc&searchIndex=0‌ Please take a look at how the video demonstrates bringing in a live feed from the ISS and then try matching the processing of your simulated event records to that workflow. Hope this helps - RJ

‎01-03-2017

Hello Everyone -- I've recently completed three short videos which illustrate how to use stream services and capabilities related to stream services -- specifically 'Store Latest' and 'Related Features' which were never covered in the product tutorial available on line. We are working on updating the tutorial's exercises and narrative to be consistent with these new videos, but I don't want to hold the videos until the tutorial re-write is complete. (The videos will eventually be bundled with the tutorial for download.) The basic stream service capability provided by GeoEvent did not change with the ArcGIS 10.5 product release. However, some minor changes in behavior were made with regard to 'Store Latest' when working within different enterprise configurations, such as single-machine vs. multi-machine and when you have federated with a Portal for ArcGIS vs. when you have not federated with a Portal. Enhancements to the 'Related Features' configuration workflow now allow you to select the feature service from which related features will be obtained (rather than having to manually enter the URL of an existing feature service). Three MP4 files have been attached to this blog. Please check-out the videos -- they are each only 10 to 15 minutes. Let the team know (e-mail [email protected]) if you think bundling a short video with a less detailed tutorial is an approach which works for introducing product updates and documenting product functionality. Best Regards -- RJ

Online Status	Offline
Date Last Visited	‎05-21-2026 12:39 PM

My Ideas

Latest Contributions by RJSunderman

Re: Query in-memory cache when Polling an ArcGIS Feature Service

Re: How to map oracle table with Lat\Long values using GeoEvent Server

Re: GeoEvent 10.5.1 stuck at "Please wait while the field is edited..."

Re: No events are written to SBDS with TCP-text-in

Re: GeoEvent and High Availibility

Re: Field Calculator erroring on ":" in string field.

Re: Add SQL Server as an input to Geoevent

Re: GeoEvent Data Store registration fails after validation

Enhancements to the GeoEvent Server's outbound HTTP transport (10.5)

Enhancements to the GeoEvent Server HTTP Inbound Transport (10.5)

Increase the RAM allocation to the JVM running GeoEvent Server

Re: Geoevent Services not producing any in/out results

Re: Diagnostic utility for checking the status of the RabbitMQ platform service

Re: Can't output GeoEvent stream service on ArcGIS JavaScript or online map

Stream Services, Store Latest, and Related Features

Re: Support for string manipulation and pattern ma...

Support for string manipulation and pattern matchi...

Re: GeoEvent input connector using token authentic...

Re: Updating the Status of a Fire Unit

Re: Is there a way to delete records from a Featur...

ArcGIS Arcade

ArcGIS Analyse