Install OpenRemote 2.0 Web Console
Download the Web Console
The next step is to download the pre-compiled Web Console WAR file (refer to the Developer Tutorials if you wish to compile the Web Console from source):
For the following steps, rename your downloaded WebConsole_1_0_0.war to webconsole.war.
Deploy the Web Console
Once you have downloaded the packaged Web Console WAR you need to deploy it on your application server (we'll assume you're using the supplied Apache Tomcat server), this can be done by simply copying the WAR file into the webapps folder.
When Tomcat is next started it will automatically deploy the Web Console application (you should see a webconsole directory under webapps once deployed).
Do not remove the webconsole.war file from the webapps folder as this will un-deploy the application.
All being well you should now be able to access the Web Console at the following URL:
http://host-ip:8080/webconsole (http://localhost:8080/webconsole if Tomcat is running on the computer you are using)
Change host-ip to the IP Address of the computer you are running the Tomcat server on.
Comments (3)
Nov 03, 2011
Mike Scher says:
I believe that the link at the bottom has an error. "webconsole" should be spell...I believe that the link at the bottom has an error. "webconsole" should be spelled "WebConsole" as in http://127.0.0.1:8080/WebConsole/
Dec 19
Patters says:
Does the web console get updated more frequently than the controller? I've been ...Does the web console get updated more frequently than the controller? I've been asked about adding it to the Synology NAS package, but I would rather leave that to the user if it keeps changing.
Dec 24
Juha Lindfors says:
Different components have their own independent release schedules (they're mostl...Different components have their own independent release schedules (they're mostly decoupled through REST APIs so can evolve as long as the REST doesn't change).
Can't say one gets updated more often than others, depending on the lifecycle of the component, they may see frequent update bursts followed by longer periods of stability / no changes.
We talked about this before, but if it is possible to script the creation of Synology packages that might be the way to go. For example, we could push the Java binaries to some pre-determined location where the scripts could fetch them based on some polling schedule (e.g. checking once a day if certain new file pattern appears on some remote directory).
Just throwing an idea out there,
– Juha