Manual installation of Frameset / Engage?
I've just installed Longview 2017 Update 1 on a fresh, new server, to try it out. I just used 127.0.0.1 as a server. Reason for this was, that registering my FQDN as a Longview server triggers a 1722 error (can't reach the server).
I used a workaround to make the applications work by re-installing the Client Components and CGI using my FQDN.
I switched on user management during install - I skipped Engage.
But now, a bit further in the process, I want to install Engage (because I also want to use the Administration application). In arcplan 8, this was a matter of running the Engage Configuration Manager (ECM.exe), but it seems that this handy executable is not there anymore.
Knowing that my FQDN is giving issues (unclear why, by the way), I just re-start the automatic Web Server Configuration of 127.0.0.1, which triggers the Engage installation. And I get an Unexpected error. But I anyway don't like the method of having to completely reconfigure my web server in order to install the add-on Engage. Ideally, I'd like the ECM back, but it isn't there...
No Engage for the moment then, I thought, but creating the HTML5 page for Administration gives me a missing components warning. And the solution that worked in arcplan 8, copying the Frameset files, is not valid anymore (and worked only for the java client anyways)...
So here's the question:
If I want to bypass the automatic configuration options (which generate errors), HOW do I get Administration and Engage to work? Which files do I need to copy from where to where?
- 1,151 views
- 0 previews
- 1 version
- 2 replies
- 1 follower
- Posted By:
- Erik Jansma
- September 28, 2017
About this forum
- 41,096 views
- 303 topics
- 9 followers
Looking for something you can't find? Have a suggestion on how we can improve? We want to hear from you!