This content has been marked as final. Show 5 replies
I believe this must have been a blip of some kind (perhaps the spawned window that prompted you for a password change was usurped by another window from another app or similar). The password expiry functionality is fairly simple and well tested. It does not vary between platforms.
In answer to 1, if you installed EDQ using the Windows installer, you will have installed Tomcat, Java, and Postgres. There is no need for anything further on the server, though if you want to update the JDK and point Tomcat at it you can. However, all clients that access the EDQ server do need to have a JRE installed (Java 1.6 or later), so that they can launch the client applications with Java Webstart.
In answer to 2, any client works, and the experience is the same. For installation purposes it is probably easiest just to log into the Server Configuration or User Configuration web pages to bring up the prompt to enter a new password.
Mike appreciate your feedback
For the question #1 - install JDK on the Server Machine [ on top of the JRE which is installed OTTB by OEDQ ], the issue gets resolved [ i.e., I am able to perform client activities on the Server]. should this be stated in the install guide as a requirement seems like support was not convinced that JDK was required but optional.
To be clear on what happened here:
- You installed EDQ as a server on a Windows machine. This installs the JRE and other required components is a complete server install, intended largely for test and development use. Clients also with the JRE would be able to connect to the server and use the client apps.
- On the server machine, Windows did not recognize the installed JRE (as installed using the EDQ Windows Installer) under Control Panel -> Java. I think if a standalone JRE installer is not used, Windows does not necessarily link to the JRE correctly. This meant that you could not launch the Webstart apps on the server machine itself.
So, installing a separate JDK solved the problem because Windows then recognized the installed version of Java and enabled Java Webstart. You could have achieved the same effect by pointing Java at the right JRE in the control panel. The server installation was already complete.
Hope this makes sense.