A .jar file contains the code needed to view a Blaze 3D presentation as a Java applet. This .jar file is downloaded at the start when a Blaze 3D presentation is viewed. Each holomatix.jar file is tailored by Blaze 3D Studio to include only the necessary code for the presentation it was published for. Thus a holomatix.jar file can only be guaranteed to work for that specific project.

When a site visitor views multiple 3D product presentations on a website, it can be useful to use a common .jar file to ensure the smallest payload possible. This is useful when you know for certain that a visitor might view multiple 3D presentations, for example if a Printing Solution is sold and you have separate presentations of a 3D camera and an accessory Printer which you are now selling as a set in a promotion. In this case, the common .jar file would contain all the code needed to view both Blaze 3D presentations. To create a common .jar file in Blaze 3D Studio:

• Publish all the projects on an individual basis. Thus each project will have all the files necessary to display the project on the web (.html, holomatix.jar and all 2D and 3D .swf files).
• Create a new folder and put all the web files (.html, .swf) of each project into this same directory.
• Start a new project in Blaze 3D Studio.
• Add all the swf files for all the presentations (now all in the same common project directory) to the additional project files listing.
• Untick the 'Use default names' option, and rename all the filename prefixes to 'temp' or something similar that does not conflict with your individual project file names.
• Save your project file (.bla) into this common directory.
• Select HTML Format output and publish.

Note that the only file needed from this common directory is the holomatix.jar.

When the files are prepared for use on the website, copy all your individual project folders to your web server (removing the holomatix.jar file from within each of these) and then copy the newly-prepared common holomatix.jar file to the desired location. You would then have a folder that contains holomatix.jar and folders with the source files for each of your products, e.g. if we had a folder called Printing Solution, the contents could be similar to:

Camera folder

Printer folder

holomatix.jar

Now, the last thing needed is to modify each of the .html pages inside the individual product directories to specify the location of the common .jar file. The code needed to do this for the above example is: 

archive="../holomatix.jar"

Now when a user views one of the Camera or the Printer 3D presentations, followed by the other - both will refer to the same .jar file so that they would download it the first time only.