Update an ArcGIS online hosted feature service with geoevent processor?

[thomasbales]

I have been using geoevent processor to track assets and interact with geofences from a server that is located inside the corporate firewall. What I would like to do is automatically connect to a few ArcGIS online hosted feature services and update those layers from my managed database. Is this possible?

Thanks,

Tom

[EricIronside]

Hopefully you've found your answer by now, but if not:

1. Log into GeoEvent Manager

2. Go to the Site tab at the top and select DataStores on the left

3. Press the 'Register ArcGIS Server' button

4. On the dialog, select the AGOL optoin at the top. Enter your connection info/credentials and press 'Register'

Once you've done that, your AGOL servcies will show up just like a regular connection to ArcGIS Server in your inputs/outputs.

[AllWeatherHeather]

Are there specific role privileges in ArcGIS Online that the connecting user must have for this to work? Also, if our organization chooses to switch off built-in user accounts accessing AGOL in favour of an enterprise solution like ADFS will built-in user credentials still be valid in the GeoEvent Manager?

Thanks!

Heather

[ChrisBeyett]

Hi Heather, 

GeoEvent typically likes to issue a transactional type of request to an ArcGIS Online organization. They are made either to gather information regarding the ArcGIS Online organization (number of items the user owns, service metadata, permissions, etc) or to push data to a particular feature service. The type of ArcGIS Online role determines what type of action GeoEvent can make. Below is a general outline of what can be done with each role:

User Role: GeoEvent can only poll from the specific user. No data can be written to the Hosted Feature Service.

Publisher Role: Normally the best role for ArcGIS Online, as GeoEvent can both poll from and write to any Hosted Feature Service as well as create new ones

Administrator Role: All functions of the publisher plus all rights to administer the organization. Use for testing/proof of concept, but it's always a best practice to limit the amount of administrative users within the organization.

To your question of switching from built-in users, ADFS is a type of SAML login and actually sits on top of the ArcGIS Online login. When ADFS is configured, the organization will have the option to keep both the existing built-in user accounts as well as utilize the ADFS authentication. It normally displays as a login box with two options, prompting the user to choose either built in or ADFS credentials. You could setup GeoEvent with an ArcGIS Online built-in user with a publisher role and require all other domain employees to login using their ADFS credentials. It would be a great way to split up the workload of GeoEvent and designate it with it's own account.

Also keep in mind that when using GeoEvent with a specific user account in the data store connection, GeoEvent will only be able to read items that are owned by this user. If an enterprise login user publishes a hosted feature service that should be used with GeoEvent, they will have to transfer ownership of that item to the account that GeoEvent is connecting as.

Hope this helps,

Chris