Distribution of your iiziApp

Distribution of your iiziApp

There is a tutorial video just down below.

Note: This option is not yet available for the early access.

Your IIZI project can be built and deployed to your server through the Distribution option under IIZI found in your project’s properties.

The developed iiziApp can consist of Module projects and Java projects. It can also refer to libraries and directories containing Java code, both project-based and external. In order to run the application on an IIZI Server, the iiziApp must be compiled into a Jar file. The iiziApp compiled into a Jar file is called an Application Distribution. The process of creating this Jar file is called Application Distributor.

The Application Distributor is a utility that is integrated in iiziGo but is also available as a stand-alone Java program that you can run from a batch file or a build system, e.g. Ant.


The Application Distributor must first be configured for a Module project to be distributed. Open the Module project properties dialog and select Enable Application Distribution:

Fill in the Jar file name. If the iiziApp consists of several modules projects, specify them in a comma separated list in Include Modules. Dependent modules and Java project, libraries and directories are always added to the Jar file, with the exception of externals that provides a separate option for the operation to perform.

Dependent modules are known at build time of the distribution when all references are resolved. All the referenced modules (including their references) will therefore be included in the iiziApp. Dependent Java projects, libraries and directories are known from the Java Build Path.


The Externals are external libraries and directories that may be specified in the projects classpaths of the Java Build Path.

If you do not include externals, the Jar file will be smaller and if several module applications share the same externals, you will use less memory for the server because it will only be loaded once. However, the externals must be in the server classpath.

Note: Be careful with this option, as the same class may from a library or a directory can be loaded several times from different iiziApp’s, and each class static (instance) will not be same between two iiziApp’s (meaning that there can be multiple “static singletons”). If this could be the case, you will have to unselect the option Include externals and to set the classpath of the server to include these externals.

Exporting iiziApp

The iiziApp is created by exporting the Module project. Open the Export Wizard using File → Export:

Click on Next and select the project to create a distribution for:

Only projects configured for application distribution are shown above.

When you press Finish, the Application Distributor will be started in a separate Eclipse job.

Note: An application containing errors and/or warnings cannot be exported!