Model Source Control

Implementing source and version control for your host application model files is an important consideration in a large production environment. Host Integrator does not contain any source control features. To control your model source files you should use one of the available configuration management software packages like Microsoft's Visual SourceSafe. Each host application model contains a number of files that you need to keep together in order to ensure its uniqueness.

To implement source control for a model file, save the following files and preserve the following folder structure:

• The <Model name> folder, which is by default created in the \<VHI install directory>\models folder.

In the <Model name> folder are the following files and folders:

• The .model file file, which is saved in the \<VHI install directory>\models\<Model name> folder.
• The .snapshot file file, which is saved in the \<VHI install directory>\models\<Model name> folder.
• The Traces subfolder.

The Traces subfolder contains screen trace files (.hetrace), which are used with the Host Emulator to provide a live host simulation of the model. The trace files are mainly used for onsite debugging to assist technical support in pinpointing issues concerning a model.

• The Scripts subfolder.
  
  In particular, build.xml, the \src subfolder, and the \lib subfolder are required for event handler maintenance.

• For 3270 and 5250 models, the .nav file.

Navigation files allow you to load and run 3270 and 5250 models in the Host Emulator. If you do not need to be able to load and run the model in the Host Emulator, the .nav file is not needed.

If your navigation file is missing, you can save another one. Select Save from the File menu. In the Save Model dialog box, select Save Host Emulator navigation file and click Save.

For complete information on the Host Emulator, see the Host Emulator Reference.

Note: If you want to save the settings for this model so that it will be the basis for creating other models, select Save Settings As.... The .dtool file you create can include Design Tool-specific configuration information such as window size, colors, keymapping, and preferences, as well as information about the host application and connection settings.