About Model Packages

A model package is a .zip archive that you create using the packagemodel command. A model package can contain the following items:

• Model file (.model)—A model file is the only file that must be in the model package. It can be located anywhere. You specify its location when you run the command to create a model package file (packagemodel).
• Optional: Event handler files (*.JAR)—If your deployment includes event handlers, the event handler folders must be located in a folder named scripts beneath the folder that contains the model file.
• Optional: A configuration descriptor (deploy_desc.xml)—If your deployment includes a configuration descriptor, it must be located in a folder named deploy beneath the folder that contains the model file.
• Optional: A model variable list descriptor (mvl_desc.xml)—If your deployment includes a model variable list descriptor, it must be located in a folder named deploy beneath the folder that contains the model file. (See the documentation for the packagemodel command for exceptions.)

The following figure illustrates the contents of a model package:

After you run the packagemodel command, a model package with a .zip file extension is created in your current working directory (unless you've specified a different name and location for the model package using the -package switch).

While a model package can only include one model, that model can, in turn, be deployed to multiple servers, optionally with different configuration information for each server.