Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Introduction

Introduction

Java Web Start is a framework for launching Java applications directly from the web. The Elastic Path Commerce Manager is capable of running within this framework.When the Java Web Start Commerce Manager is set up, a user simply needs to click a JNLP file and the Commerce Manager Client automatically downloads, caches, and runs locally. Updates to the Commerce Manager on the Java Web Start server are also automatically downloaded and installed when the user clicks the JNLP file.
DANGER
Java Webstart for CM Client Fails on Startup

Java Webstart for CM Client fails to start up with Java 7u51 due to the enhanced security introduced in this update 51. Elastic Path is currently working to fix this issue.

Why use this feature?

Using Java Web Start with the Commerce Manager has a number of benefits:

  • Run the Commerce Manager Client on any computer that supports Java Runtime.
  • Update the Commerce Manager on the server and the updates are automatically distributed to the Commerce Manager clients.
  • Install the Commerce Manager once on a web server, and easily deploy it to multiple locations.

Where is feature located?

<EP_Source>\cmclient\com.elasticpath.cmclient.product.feature.jws

Key Java Web Start Files

The following information describes key Java Web Start files and their relation to the Commerce Manager application.JNLP FileThe JNLP file is an XML file that provides information to Java Web Start about what application is starting up and what resources are required to start it. Java Web Start parses the JNLP file, downloads the resources from the Internet, and starts the application. This file describes:

  • Information about the application (Name, vendor, description, etc)
  • Graphical resources (icons, splash screens)
  • Security and Permission information
  • Application resources (JARs, JVM)
  • Information about the server hosting its resources
  • The class to start the application (eg. Equinox's WebStartMain)
  • Platform information (OS, WS, Architecture, Java version)

cmclient.jnlpThis is the Commerce Manager client's JNLP file. This file describes:

  • Information for OSGi
  • Information for Equinox to start the application
  • A reference to cmclient-feature-jws.jnlp (described below)
  • Platform information (OS, WS, Architecture, Java version)

When cmclient.jnlp is loaded, Java Web Start downloads the Equinox JAR and cmclient-feature-jws.jnlp. After processing cmclient-feature-jws.jnlp, Java Web Start runs Equinox and uses OSGi and the resources listed in cmclient-feature-jws.jnlp to start the Commerce Manager client.

cmclient-feature-jws.jnlpThis JNLP file references the plugin JARs that need to be downloaded and run by Java Web Start in order to start the Commerce Manager application.On first launch, Java Web Start downloads cmclient-feature-jws.jnlp from the internet, parses the list of resources defined in the file, and retrieves them from the web server. Java Web Start then checks the resources are signed by the same certificate.