Configuring the NexJ Studio web install

The installation and update site files for NexJ Studio are contained in the p2site repository folder.
The files are initially configured for an update site being hosted at http://localhost. If you want to run your install and update site from a different server, or from a folder on that server, you must reconfigure the files.

These steps all refer to the files stored in the p2site repository directory and must be carried out before you deploy the files to your web server.

To configure the web installer file before deployment:
  1. Update the installer.properties file:
    1. Set eclipse.p2.metadata to the update site URL. This is the site that will be housing the NexJ Studio files that you want to install. The initial value for this property is http://localhost.
    2. Set eclipse.p2.artifacts to the same update site URL.
    3. Set eclipse.p2.defaultInstallLocation to the location that you want to install NexJ Studio by default on your users' computers.
      Note: Because of the way that Microsoft Windows handles the security of program file directories, we recommend setting this value to install NexJ Studio into its own folder, outside of both the Program Files and Program Files (x86) directories.
  2. In the following files, update the codebase attribute of the root jnlp node to the URL of the update site that you are creating:
    • features/org.eclipse.equinox.p2.installer.feature_4.5.jnlp
    • features/org.eclipse.equinox.p2.installer.feature_4.5_old
    • features/org.eclipse.equinox.p2.installer.feature_4.5A
    • features/org.eclipse.equinox.p2.installer.feature_4.5B
    • features/org.eclipse.equinox.p2.installer.custom_4.5.jnlp
    • studio_install.jnlp
    For example, if you are creating an update site at http://example.com/installer, then you should update the root node to:
    <jnlp spec="1.0+" codebase="http://example.com/installer"> 
  3. In the studio_install.jnlp file, set the value of the com.nexjsystems.installer.installDescription property to the fully qualified URL of the installer.properties file. For example:
    <property name="com.nexjsystems.installer.installDescription"
    value="http://example.com/installer/installer.properties"/> 

You can now deploy the contents of the p2site repository folder to your web server.

Important: Ensure that the following MIME types have been defined for your web server, to enable it to correctly identify and handle files required by the installer.
File extension Handler type
.property text/plain
.jnlp application/x-java-jnlp-file
Numerical extensions from .000 to .999 application/java-archive

For more information about Microsoft Internet Information Services (IIS) and MIME types, see the "Configuring MIME Types in IIS 7" topic on the Microsoft web site at http://technet.microsoft.com/en-us/library/cc753281%28v=ws.10%29.aspx.

For more information about Apache HTTP Server and MIME types, see the mod_mime module description on the Apache web site at http://httpd.apache.org/docs/current/mod/mod_mime.html.

To install the product, you should provide users with a hyperlink to the studio_install.jnlp file, for example, http://example.com/installer/studio_install.jnlp.