POST
|
Hey Adam - Thank you for the details and including the error from the GEP logs. It may be that that your feature service output (at an instant in time) didn't have one or more required properties. I've seen this "validation failed" error message however when I know that the object in question is fully defined ... so I'm not going to focus too much on this particular error message. I'm more interested in your report that when you open the Data Stores page in Manager you see that the registered server connection displays as not valid. If you click the 'Validate All' button at this point, can the connection be validated? (If the GEP cannot access the registered data store to locate the service folder, I"?d expect that opening the configuration page for the output connector would display empty fields for the "?Service Name"?, "?Layer"? and (if updating features) the "?Unique Field Identifier"?.) To your comment that restarting appears to fix the issue - are you restarting the GEP Windows service? I'm wondering if it is possible that an attempt by GEP to connect to the AGS site using the configured Server connection failed, but restarting GEP forced a second attempt which then succeeded... I think we may be dealing with a Server connection which is intermittently unavailable. Is there a way you can manually verify the connection from your GEP server to your AGS server when you are seeing this issue (outside of GEP Manager)? To your question of submitting incidents/tickets with Esri Technical Support - yes, if we have an issue that can be reproduced (since that is what Esri Support is supposed to do), then please open a new Support incident. Otherwise, posting to the forum as you are gets the issue in front of the development team and we can help diagnose it as quickly as we can make time for the investigation. Thanks for working with us ... /RJ
... View more
08-30-2013
08:20 AM
|
0
|
0
|
26
|
POST
|
Hey Simon - What you are describing ought to work. I conducted tests just the other day in which my GeoEvent Definition had fields 'CodedName' and 'CodedValue' and I sent multiple SMS messages: Message to {$CodedName}: ${CodedValue} We've never referred to these as "macros", but that's kind of like what they are. The ${FieldName} gets expanded in-line to the value contained in that field. The field names are case sensitive. What are you seeing in the SMS you receive? Can you screenshot the entire sms-text-out connector configuration as well as your GeoEvent Definition? Have you tried running the output to a TCP text output to confirm which GeoEvent Definition is being used to handle the event's attribute values? Do you, by chance, have more than one SMTP dependent output connector configured? The "?Send a text message"? and "?Send an email"? output connectors both rely on SMTP... /RJ
... View more
08-28-2013
10:54 AM
|
0
|
0
|
21
|
POST
|
Hello Greg -- The error you posted looks like an issue with the installation of GeoEvent Processor. I might have recommended stopping the ArcGIS GeoEvent Processor service and then deleting the ...\data folder from the set of installation file folders beneath C:\Program Files\ArcGIS\Server\GeoEventProcessor and then restarting the service. But you indicated that you have already tried uninstalling the product, which is a more thorough way of accomplishing the same thing. You indicate that you deleted all of the services. Did you do this before you uninstalled, or after you re-installed? The best way of guaranteeing that you are starting fresh is to uninstall GeoEvent processor, then locate and delete the product's configuration files from the C:\ProgramData\Esri\GeoEventProcessor (WinServer 2008 / Win7) ... you might find these files beneath C:\Documents and Settings\All Users\Application Data\ESRI\GeoEventProcessor on older versions of Windows. If you are still seeing the Unable to start blueprint container for bundle com.esri.ges.manager.internal-agsconnectionmanager org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean error message in the GEP logs after removing the product's configuration files and re-installing, please let us know. /RJ
... View more
08-22-2013
11:03 AM
|
0
|
0
|
111
|
POST
|
Simon - We have had reports - from customers using other adapters - that the Field Mapper processor is not handling hierarchical data. They are also seeing what you describe; null values in their output when hierarchical data is mapped to a flattened schema. We are developing a hot-fix for this for the 10.2.0 release and refactoring how GeoEvent Processor components handle hierarchical fields and fields with cardinality greater-than one. The refactoring will be part of the 10.2.1 product release. For now, I do not have a workaround to suggest. What you are doing appears correct. /RJ
... View more
08-21-2013
04:21 PM
|
0
|
0
|
16
|
POST
|
Adam - There is some internal disagreement on the extent to which deleting the user who created a GeoEvent Service, Input, and/or Output connector will have on a service's viability. One consideration is the type of input(s) and output(s) participating in the service and how exactly the service was designed. If you'd post a screenshot of your service with a description that would help as we work to collect empirical evidence to support/refute some assumptions. /RJ
... View more
08-21-2013
12:45 PM
|
0
|
0
|
9
|
POST
|
This issue - seeing "milliseconds" rather than "seconds" in the user configuration panels of GeoEvent Processor Manager - is only applicable to early adopters who participated in the Beta development of GeoEvent Processor. The configuration of an installed instance of GeoEvent Processor is not deleted when the product is uninstalled or upgraded. Similar to ArcGIS for Server, which preserves the site's configuration store and server directories, GEP preserves its configurable items (GeoEvent Definitions, GeoFences, Registered Folders, etc.) so that they are available following product re-install or upgrade. The location of these files is dependent on whether you were unzipping a build of GEP provided by the development team during the Beta phase or are using the product installer made available with the product's release. If you used the product installer to install GeoEvent Processor, the product's configuration is found in a hidden system folder (C:\Program Data\Esri\GeoEventProcessor on Windows systems). When uninstalling and re-installing the product these files are *not* removed. This is done by design so that configurable items remain configured between upgrades. In this specific case, a GEP administrator could locate the ...\connectors\connectors.xml and edit the file to change the "Update Interval (milliseconds)" to read "Update Interval (seconds)". This has no effect on what GeoEvent Processor does with the value entered by the user; at the 10.2 release the system is consistently using 'seconds' as the unit for user-provided update and polling intervals. GEP administrators who want to ensure a clean install should locate and remove the file folders in the screenshot below after uninstalling the product (or stopping the GeoEvent Processor service). These file folders will be re-created when the GeoEvent Processor is next installed or the process's service restarted. . [INDENT]( ! ) Removing these file folders will delete the registered data stores (Server and Folder), web browser certifications, connector templates, event definitions, GeoEvent services ... etc.[/INDENT] . [INDENT]( ! ) The connector templates and web browser certifications (...\connectors and ...\certs) will *not* be re-generated unless the product is re-installed. Other file folders are re-created when the GeoEvent Processor service starts if they are missing.[/INDENT] . [ATTACH=CONFIG]26859[/ATTACH]
... View more
08-21-2013
09:58 AM
|
0
|
0
|
10
|
POST
|
Mark -- I can comment on a couple of the questions you asked in your post - but perhaps we should schedule a follow-up meeting to look more in depth at what you're seeing. The Monitor page in GeoEvent Processor Manager is your first indication of what GEP has successfully ingested through its input component, processed in/out of the GeoEvent Service, and output through its output component. If there are no errors in the logs, and all of the counts match on the Monitor page, you are usually assured that all of the received event data is being processed and output. Some exceptions: The output connector for SMS ("Send a Text Message") successfully sends its message to the SMS carrier which rejects it. You won't see any indication in GEP that the event data was not received by the intended recipient. X Similarly when updating a published feature service, if ArcGIS for Server is unable to handle the request to update the feature service you might find error messages in the ArcGIS for Server log - but you won't see an indication in the GEP Monitor that features are not being written. You might see error messages in the GEP log. (I recently had to work around an RSS provider which had HTML in one of their tags which ArcGIS for Server wouldn't accept; GEP was posting the JSON without error, but the features were not being added to the target feature service.) So ... I'd say that GEP's Monitor is trustworthy and reliable - but not definitive. You would need to monitor both the GEP logs and the AGS logs if you suspect that event data is being dropped. Since you are not seeing anything in the GEP logs, you might try the following recommendations (passed along from the Server team): From the Server Manager, take a look at each feature service"?s configuration. On the "?Pooling"? tab there are settings for "?The maximum time a client can use a service"? and "?The maximum time a client will wait to get a service"? "¦ reduce these from their defaults down to 5 seconds. Reducing these configurable settings on your target feature service(s) should reduce the server"?s queue sizes and help it more efficiently handle the continuous stream a requests coming from GeoEvent Processor "? which can stress Server by sending more requests than it can process. These settings should NOT be used if you plan on using the REST interface to clean out (delete) features. For example, if you accumulate several tens of thousands of rows it will take longer than 5 seconds to delete the features through the REST interface and your severe time limits on how long a service can be used will force a timeout before the operation is complete. /RJ
... View more
08-19-2013
02:51 PM
|
0
|
0
|
30
|
POST
|
Kevin -- If you wanted to get mobile device location information for the iPhones / iPads you have out in the field, there are a couple of options. 1) If you have ArcGIS Online for Organizations, you could use the Collector and Operations Dashboard applications Esri developed. 2) You could develop a native application using the ArcGIS Runtime SDK for iOS to broadcast the information to GeoEvent Processor. The Collector for ArcGIS allows you to collect features in the field and report them back to an ArcGIS Server. One of its other capabilities is to provide periodic location updates on the field devices to update an ArcGIS Online hosted feature service. The GeoEvent Processor could then poll the feature service to obtain new or updated features. Here are links to the Collector and Operations Dashboard applications: - Collector for ArcGIS http://resources.arcgis.com/en/collector/ - Operations Dashboard for ArcGIS http://www.esri.com/software/arcgis/arcgisonline/apps/operations-dashboard If you take the developer route and elect to build your own native application, then you would have a wide variety of options on how the information could be sent directly to GeoEvent Processor. You could have your application open a TCP or UDP Socket and send delimited text (such as CSV) to the socket. You could also format the information as Feature JSON or Generic JSON. Or you could choose to open a web socket (part of the HTML5 standard) and broadcast any of these formats. GeoEvent Processor would then receive the information directly over the socket / web socket. /RJ
... View more
08-19-2013
02:27 PM
|
0
|
0
|
14
|
POST
|
Ryan - Sorry, no, we do not have an XSD which defines the schema for the XML being created when you export a GeoEvent Processor configuration. There should be no "other" attributes or elements. When GEP exports a configuration, the XML should have everything; if there is no value for a particular property then that tag is supposed to be ouput as an empty tag. Are you developing a custom adaptor, transport (or both) as well as a custom connector? Are you able to export your developed components as an XML configuration ... and want to verify that your export has all of the properties? /RJ
... View more
08-19-2013
02:13 PM
|
0
|
0
|
10
|
POST
|
<continued from last post...> There are some known limitations when working with Filter and Processor elements in a GeoEvent Service. For one, when working with strings, tests for null and empty strings can be tricky. Connectors such as �??Watch a folder for new .csv files�?? and �??Receive text from a TCP Socket�?? represent missing data as empty strings when String values are expected. Empty strings are not null (they are simply zero-length strings). If you want to exclude events with attribute fields which are empty, use a MATCHES operation with the regular expression for an empty string and place the expression in a logical negation. [ATTACH=CONFIG]26625[/ATTACH] There is an enhancement in the product backlog for including additional string methods from a common library such as org.apache.commons.lang.StringUtils which will enable a �??Field Calculator�?? to leverage methods such as startsWith(), endsWith(), UpperCase(), IsAlpha(), and IsNumeric(). Look for this enhancement in a future release. There is also a product backlog item for additional documentation �?? specifically for how to configure the different types of Filter and Processor elements of a GeoEvent Service and the functionality exposed through these elements. Finally, the team is interested in feedback on both what is working for you and functionality you need in order to address the challenges you have when processing real-time data. Please visit the ArcGIS Ideas portal and remember to tag your ideas with �??GeoEvent Processor�?� and check the �??ArcGIS Server�?? box as a product category �?? this will help route your ideas to our team. Ideas and requested enhancements which receive a significant number of �??promotions�?� on the ArcGIS Ideas portal are more likely to be incorporated into the product backlog for inclusion in a future release than ideas posted to the forums. Best Regards - RJ
... View more
08-09-2013
06:59 PM
|
0
|
0
|
33
|
Online Status |
Offline
|
Date Last Visited |
yesterday
|