<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Output Failure in ArcGIS GeoEvent Server Questions</title>
    <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/output-failure/m-p/703914#M3067</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Ayman -&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- RJ&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Jan 2014 20:38:52 GMT</pubDate>
    <dc:creator>RJSunderman</dc:creator>
    <dc:date>2014-01-02T20:38:52Z</dc:date>
    <item>
      <title>Output Failure</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/output-failure/m-p/703913#M3066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I want to have 2 output, where the second output will receive data only if the first output fail. Is this can be achieved in GEP.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Dec 2013 02:10:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/output-failure/m-p/703913#M3066</guid>
      <dc:creator>aymansalah</dc:creator>
      <dc:date>2013-12-31T02:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: Output Failure</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/output-failure/m-p/703914#M3067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Ayman -&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- RJ&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jan 2014 20:38:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/output-failure/m-p/703914#M3067</guid>
      <dc:creator>RJSunderman</dc:creator>
      <dc:date>2014-01-02T20:38:52Z</dc:date>
    </item>
  </channel>
</rss>

