Deploy/webstart

From Omar Wiki

Jump to: navigation, search

Contents

[edit]

RegistryBrowser Java UI w/ JNLP (Java WebStart)

[edit]

Using Java Webstart Distribution of Java UI at SourceForge

This is the path of least resistance for someone wishing to run Java UI with minimal installation and configuration steps.

  • Try the following URL assuming that Java Webstart is already installed: 
 http://ebxmlrr.sourceforge.net/3.0/registryBrowser/jnlp/registryBrowser.jnlp
  • Repeat first step after installing Java Plugin
  • The first time Java Webstart runs it will download all the jars needed for Java UI to run. Thsi will take a long time. Subsequent times will be faster as the ownloaded jars will be cached.
  • When asked whether to accept signature by Farrukh Najmi go ahead and accept and grant all requested permissions to Java Webstart application.

The remainder of this document if for those users that are buidling a Java Webstart (JNLP) distribution of Java UI and is not relevant to most end-users.

[edit]

Building and Deploying Java UI Webstart Distribution

[edit]

Preparing the Jars

It is very important that all the jars are signed by the same key, otherwise JNLP will fail to start Registry Browser Java UI. In order to achieve that, you must remove the signature from dependencies, including Sun JARs from JWSDP. You can use the clean-jar-signatures target and the following command is the suggested way to do it: 

ant clean compile jars clean-jar-signatures signjars

Notice that clean-jar-signatures is not a dependency for any task and must be run manually, after any time you perform clean and dependencies are replaced.

Also, make sure the list of jars in build-webstart.xml and in registryBrowser-jnlp.jsp are synchronized of Registry Browser Java UI dependencies list.

[edit]

Deploying Java UI WebStart Distribution to SF

You MUST follow steps for Building the Java UI WebStart Distribution first. See upload-webstart-files target in build-webstart.xml (this action is limited to team members).

[edit]

Deploying Java UI WebStart Distribution Within OMAR WebApp

You MUST follow steps for Building the Java UI WebStart Distribution first.

JNLP Registry Browser can be included in the built WebApp by including this property in local.build.properties: 

war.includes.webstart=true

Jars will be signed with Farrukh key from the server keystore. To change that, use the following properties: 

omar.signjars.alias=
omar.signjars.keyPassword=
omar.signjars.keyStore=
omar.signjars.keyStoreType=
omar.signjars.keyStorePassword=

After that, build WAR and deploy as usual. Registry Browser should be available at /browser/jnlp/ (example: http://localhost:8080/omar/browser/jnlp/).

[edit]

Further Considerations

  • Registry Browser Java UI on WebStart has been tested and verified on JDK 5. There were issues running it on JDK 1.4.2 WebStart, please report back if you get it to work on 1.4.2.
  • The certificate used to sign the jars might be self-jenerated / not certified by a CA (Certificate Authority). In that case, you should see a message like "Could not validate the certificate....". The message can be ignored if you trust the server where Registry Browser Java UI is coming from - unless you are worried about someone spoofing the Java UI.
Retrieved from "http://ebxmlrr.sourceforge.net/wiki/index.php/Deploy/webstart"
Personal tools