It is my intention to utilise the GeoEvent Server, hosted on an AWS EC2 (m5.xlarge).
I have (successfully I believe) set up the Portal, ArcGIS Server, and a Spatiotemporal Datastore on the machine, and am looking to set up GeoEvent. I used the AWS Windows AMI for version 10.7 for the installation.
I have tried to follow the guidelines here (Installing GeoEvent Server—ArcGIS GeoEvent Server (Windows) Installation Guide (10.7) | ArcGIS Enter... ), which suggests following the Desktop App to access the GeoEvent Manager. When I do this I get a "404.0 - Not Found" response. Presumably, if I can access the server my ports etc are set up correctly, and so I ask what is causing this issue, and most importantly how can I fix it?
Thanks for getting back to me on this.
No, I get the same response whether I navigate to the Manager via https://gisserver.domain.com:6143/geoevent/manager/ or via the GeoEvent Manager shortcut (which dire...http://localhost:6180/geoevent/goto-manager).
I also get the same response via http://gisserver.domain.com:6180/geoevent/manager/ (and http://localhost:6180/geoevent/rest/).
In place of "gisserver.domain.com", I am trying both localhost and localhost.localdomain. The pre-configured shortcut directs me to localhost, but I was unsure whether the domain needed specifying also. Is this something I should/have defined already?
Considering this behavior occurs with both GeoEvent Manager and GeoEvent's REST endpoint, there could be a few reasons as to why GeoEvent is inaccessible (thus throwing that 404 error when being accessed). With this in mind, I recommend creating a case with Technical Support; doing so would allow for somebody to look into the issue further and get the proper resources looped in.
This issue has been recurring for GeoEvent Server 10.9.1 as well. We did resolve this internally by manually restarting the services for both Gateway and Server and it would launch the manager.
Don't know why this keeps on coming up and we would really appreciate any help.