Actions

Regenerate applications

Check this to have the selected application projects regenerated as part of the export process packaging.

By default, this option is not selected. However, if the grammars are retargetted, Dialog Designer automatically sets this option so that the grammars are generated properly within the application.

Rebuild applications

Check this to have the selected application projects rebuilt as part of the export process packaging.

By default, this option is not selected. However, if the grammars are retargetted, Dialog Designer automatically sets this option so that the grammars are built properly within the application.

Packaging

Deploy project class files as

Select how Dialog Designer should deploy the class files for the application project. Select from the following options:

• JAR file - (Default) Packages the project .class files into a single, self-contained Java ARchive (JAR) file.

• class files - Deploys the project .class files as separate files within the WAR file.

For run time, it makes little difference which option is chosen. The JAR file option, however, has the following advantages:

• JAR files tend to keep the run-time environment cleaner.

• It is easier to replace a single JAR file, if you need to, than to replace a whole batch of .class files.

Include source code

To make the Dialog Designer source code available for others to study, use, modify, or debug, select this option.

Include project meta files

Project meta files are files such as .prompt files, .gram files, .flow files, and so on. To include the project meta files in the WAR file, select this option.

Including these files in the WAR file makes it easier to check files into a source control system, e-mail to others, or deploy the project with all files.

Include extra files and folders

If a designer has included extra files and folders in his project, by selecting this check box, the files are added with maintained folder structure to the exported .war/.ear file. The resources are copied into the root of the .war/.ear file and directory structures are maintained.

Note: Avaya recommends files and folders are added to the data/ directory, which will automatically be included in the packaged WAR/EAR file.

Exclude JDBC resources from the context file.

Tomcat only. Select this option to exclude JDBC resources from the context file to the exported WAR/EAR file.

This is used when a global database definition has been defined in Tomcat's configuration files that the Dialog Designer application should use.

Exclude languages

Note: This setting is available for exports of speech application projects only.

Select this option to exclude one or more sets of language files currently included in your speech project files to the exported WAR/EAR file.

If the project only has a single language, this check box is not selectable.

Exclude phrase audio files

Note: This setting is available for exports of speech application projects only.

Select this option to exclude the project audio files from the WAR/EAR file. This is useful for deploying a project update without updating the audio files on the server. This will result in a smaller WAR/EAR file.

Reusable Modules

Note: This setting is available to exports of speech application projects only.

Deploy projects to the Dialog Designer reusable modules directory

If the selected projects are designed to be used as reusable modules with other speech application projects, select this option.

When selected, the wizard deploys a copy of the WAR file to the reusable modules directory. For more information about this option, see Deploying Projects as Dialog Designer Modules.

Tracing

Note: This setting is available to exports of speech application projects only.

Turn off tracing in deployed application

By default, tracing is off in a deployed application, but clear this option to turn it on (which is effectively enabling the localapptrace parameter in the ddrt.properties file).

Note: Setting the ddrt.properties file for a module has no affect on that module's tracing.

The Parent app with modules will also log trace and report information in its log for the modules as well as itself, but nothing will get logged in the module's trace or report logs.