The procedure below is identical to the one used to deploy XXE using Java™ Web Start. The only difference is that you need to use different options for the deploywebstart
command-line utility.
Install a Java™ 1.5+ JDK (a JRE is not sufficient) on the deployment server. Example: let's call this server rapido
.
Make sure that the
directory is referenced in $JAVA_HOME
/bin/$PATH
because deploywebstart
needs to run command line tools such as keytool
and jarsigner
.
Install XXE on the server. Example: /opt/xxe/
.
Customize XXE if needed to. Example:
Create directory /opt/xxe/addon/custom/
. This directory will contain all the add-ons you want to deploy.
Unzip one or more add-on distributions in /opt/xxe/addon/custom/
.
You'll find the add-on distributions packaged by XMLmind in http://www.xmlmind.com/xmleditor/addons.shtml.
This customization of the XXE distribution can be done by hand by unpacking add-on distributions anywhere inside /opt/xxe/addon/
, or more simply by using the integrated add-on manager ( → ).
In the latter case, just make sure to check "Install add-ons in XXE installation directory" in the Preferences dialog box ( → , Install add-ons section) before using the add-on manager.
Test your customized distribution by running /opt/xxe/bin/xxe
on the server.
If you use the RenderX XEP plug-in, make sure that you have finished its installation by converting at least a document to PDF or PostScript®.
Run the deploywebstart
command-line tool:
/opt/xxe/bin$ ./deploywebstart -applet xxe -index
-applet xxe
is used to generate in /opt/xxe/webstart/
a xxe.jnlp
file describing the deployment of XXE as an applet rather than using Java™ Web Start.
-index
is used to generate a simple index.html
file in /opt/xxe/webstart/
. This file contains the applet element.
The default codebase http://rapido.my_company.com/xxe
should work fine for this example. If this is not the case, you'll have to use the -codebase
option.
Jars are signed using a self-signed certificate issued by the person who ran deploywebstart
. If you want to sign the jars with an actual certificate, you need to use all the four -storepass
, -keystore
, -keypass
, -alias
options.
Publish your customized distribution on your intranet using a HTTP server. Apache example:
Add a similar snippet to /etc/httpd.conf
:
<Directory /opt/xxe/webstart/> AllowOverride None Order Deny,Allow Deny from All Allow from my_company.com Options Indexes Includes </Directory> Alias /xxe /opt/xxe/webstart/
Restart apache:
# cd /etc/rc.d # ./apache restart
Point your Web browser to http://rapido.my_company.com/xxe
.