Versions Compared

Old Version 4

changes.mady.by.user Xuri Chen

Saved on

compared with

New Version 5

changes.mady.by.user Xuri Chen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

  1. Nexaweb platform with version 4.5.66 or greater
  2. 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
  1. Nexaweb Launcher is based on an open source project GetDown. For information on GetDown project, please refer to: GetDown
  2. For more information on Nexaweb Launcher, please refer to: Nexaweb Launcher
  3. For more information on Nexaweb Standalone Client, please refer to: Standalone Client
  1. 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.

    1. Download the latest version nexaweb platform( greater than 4.5.65.0009) and installed it on the Server
    2. Create a new Nexaweb application project with the 4.5.65.0999 or the later version platform
    3. copy NexawebImages.jar,  NexawebStandaloneClient.jar,  and all other jars to WebContent directory as below:

             Note:  NexawebStandaloneClient  You can find NexawebStandaloneClient.jar are come from Platform .\Nexaweb Platform 4.5.65\binand NexawebImages.jar in the bin directory where Nexaweb Platform is installed

            d. Edit web.xml to add runNexaweb  jsp and  /runNexaweb  url mapping as below:

...

2. Digest the jars and create digest.txt and digest2.txt and upload them to the nexaweb application

           Nexaweb launcher uses Getdown’s digester to generate jar’s digest and use the digest to check if it needs to download a new version jar file or not. So the users need to digest all jars the web application needed and put them in the same directory with GetDown.txt which is just the same file run.nexaweb in a different name. After generating the digest files, they need to be added into WebContent directory too as the jars.

    a. Down load digesters jar: getdown-1.7.1-SNAPSHOT.jar  from nexaweb download site

...