POST
|
K DeVogelaere, If you're regularly having to update tokens because they're expiring, you may consider introducing the GeoEvent Datastore Proxy into your environment. It's a Java WebApplication designed to act as the endpoint GeoEvent communicates with, but is responsible for updating tokens when connecting to a system that requires username/password for authentication to either the WebTier or GIS Tier. You can view the project here Esri/geoevent-datastore-proxy · GitHub and download the first release here Release Initial Release of GeoEvent DataStore Proxy · Esri/geoevent-datastore-proxy · GitHub . If the proxy looks like something you'd be interested in, you could submit a Tech Support incident if you need some help configuring the proxy for your environment. -Javier
... View more
09-10-2015
08:23 AM
|
0
|
1
|
19
|
POST
|
A B, To your follow-up questions: 1 If the ArcGIS Server is configured so that the WebSocketContextURL points to the external proxy and the proxy is correctly configured to proxy the WebSocket connections to GeoEvent, then clients will not need to see port 6143. (The screenshot is used as a sample of how to set the property, not as an example of how to configure the property without a port.) 2 As far as SSL Certificates are concerned, if the proxy is configured to proxy connections to https://geoevent:6143/ ... for the WebSocket connections, then you'll have to configure the Proxy server to trust the certificate configured for use by GeoEvent. If you want your clients to use HTTPS when connecting to the external proxy, then the certificate for your proxy must be one that the clients will trust. Some browsers will show the Mixed content message if you have an HTML page loaded using HTTPS but then get some images or other content using HTTP. So configuring the certificate (either on GeoEvent or the Proxy) so that it is trusted by all clients may or may not get rid of the warnings depending on your webapp implementation. Hope this helps. -Javier
... View more
09-01-2015
09:37 AM
|
0
|
0
|
13
|
POST
|
How are you trying to use the .NET proxy in relation to GeoEvent.
... View more
08-19-2015
10:26 AM
|
0
|
0
|
38
|
POST
|
Bryan, Sorry for the delay in replying. In the hopes you haven't given up, I'm attaching a sample adapter that uses JNI. Hopefully you can use this as a guide to create your custom Processor. Feel free to forward along any questions. -Javier
... View more
08-06-2015
12:34 PM
|
0
|
0
|
10
|
POST
|
Sharon, In order for this trick to work, you must stop the Windows services for GeoEvent and ArcGIS Server first. Once they're both stopped, then you go and check the config folder for the *.wlock or *.wlock.info files and kill any processes that may still be running that show as being launch from C:\Program Files\ArcGIS\Server or C:\PROGRA~1\ArcGIS\Server. Once you've done both of those with the services not running, then restart ArcGIS Server followed by GeoEvent. This sequence usually rescues RabbitMQ for me, but the order is important. Can you please confirm you tried doing the steps in the order mentioned above? -Javier
... View more
05-22-2015
05:35 PM
|
2
|
4
|
42
|
POST
|
Minfin, GeoEvent runs its own server, this is why it doesn't use port 6080. If there is nothing listening on port 6143 when you hit https://localhost:6143/geoevent/manager/index.html after starting the GeoEvent service, chances are the license you've installed is not valid. Look in the log file GEO_EVENT_INSTALLDIR\data\log\karaf.log and look for a line with contents "License status: GeoEventProcessor." That line will tell you if the license is valid or invalid.
... View more
01-30-2015
01:17 PM
|
0
|
0
|
8
|
POST
|
Jacob, Out of curiosity, what version of CXF did your POC use? I'm also wondering if the issue was something to do with OSGi (the container which runs GeoEvent) and class loaders not being able to find your stub classes. -Javier
... View more
10-27-2014
03:09 PM
|
1
|
1
|
83
|
POST
|
Darryl, Please go through tech-support to create an issue so that we can get to the bottom of this. -Javier
... View more
09-08-2014
10:40 AM
|
0
|
0
|
17
|
POST
|
Darryl, Are you using GeoEvent 10.2.2? In prior versions, that config file was not there. Unfortunately, timeouts aren't modifiable in this config file. All of our Http Connections have a timeout of 30 seconds as we try to stay as close to real-time as possible. -Javier
... View more
09-05-2014
08:49 AM
|
0
|
2
|
17
|
Online Status |
Offline
|
Date Last Visited |
11-19-2020
07:29 PM
|