Oracle announced that Java Applet and WebStart functionality, including the Applet API, The Java plug-in, the Java Applet Viewer,JNLP and Java Web Start including the javaws toolare all deprecated in JDK 9 and will be removed in a future release. As an alternative , customers are recommended to use Nexaweb launcher to deploy and run nexaweb web application.
This step-by-step guide shows how to perform the migration of Nexaweb application to Nexaweb launcher
Prerequisites:
- Nexaweb platform with version 4.5.66 or greater
- NexawebLauncher Installer
Step-by-step guide
To deploy a Nexaweb application using Nexaweb Launcher, the recommended approach is using Nexaweb Standalone Client, here are the steps:
Info |
---|
|
- Create run.nexaweb file for launching nexaweb web application.
The way to nexaweb web application is by using a run.nexaweb ( nexaweb Launching Protocol) file deployed on the server, when user type the url of a nexaweb file in the browser, the Windows will detect that the response is nexaweb file and it will launch Nexaweb launcher to load the Web Start application according to the setting in the nexaweb file. So a nexaweb file needs to be created for the Nexaweb application.
- Download the latest version nexaweb platform( greater than 4.5.65.0009) and installed it on the Server
- Create a new Nexaweb application project with the 4.5.65.0999 or the later version platform
- copy NexawebImages.jar, NexawebStandaloneClient.jar, and all other jars to WebContent directory as below:
...
b. Create a digester directory and copy run.nexaweb at the step #d2 into it and change its name to getdown.txt (Note: please check if the file extension is .txt after change the name )
c. Copy all jars that project needs to run properly into it and the digest directory looks like as below:NexawebImages.jar, and NexawebStandaloneClient.jar in the digesters direcoty
d. Copy all jars other than above jars in the ClientClassLoader directory, and the digester directory looks as below:
Note: the demo project uses only the standard jars. For the project that uses some other jars, it needs copy all its jars to this directoryan external jar called test.jar. It is put under ClientClassLoader directory, which is as below. If the project does not needs of jars other than NexawebImages.jar, and NexawebStandaloneClient.jar , you don't need create a ClientClassLoader directory.
d
e. Run the command below in command lines below:
...
and it creates two digest files as the screenshot below:
ef. Copy these two digest files to nexaweb project’ to WebContent directory as below :
fh. Restart the nexaweb project and all the setting needed for nexaweb launcher are done .
...