PreviousNextIndex

Application Deployment > Deploying Projects as Dialog Designer Modules
 
Deploying Projects as Dialog Designer Modules

Note:

This section only applies to speech applications.

When creating a large and complex speech application, it is often a good idea to identify parts of the application that can be reused by other parts of the application. Reusable parts can be created as modules.

For example, in a banking application, a module might collect the account number of a caller and then write the account number to a variable. This module may be used by many different parts of the main application, including the parts devoted to checking accounts, savings accounts, mortgage accounts, and so on.

To deploy a Dialog Designer Speech Project as a reusable module:

  1. Open the Export wizard by performing one of the following actions:
  1. From the Select an export destination list, select Export Dialog Designer Projects, and then click Next.
  1. From the Available Projects list, select the project you want to export as a reusable module, and then click Next.
  1. Make any changes you need to on this page, and then click Next.
  1. Select the check box labeled: Deploy projects to the Dialog Designer reusable modules directory
  1. In the Deploy Project message box, click Yes.
  1. Click Finish.

Note:

The Export wizard also creates a copy of the WAR file at whatever location you specified as the Destination Directory on the Export Dialog Designer projects page. This WAR file is the file to deploy on the application server for use with the parent application. If you do not deploy this to the application server along with any other application project WAR files, the parent application will not be able to find or use it.

Note:

If you are storing "custom object" (objects that you define) in session properties and wish to pass them between to modules (Web applications), the code for the objects must be in the <tomcat_home>/common/lib so that the class loader works properly.     If that code is on <appname>/WEB-INF/lib then an object instantiated in project A cannot be accessed on project B. By moving the implementation of the class to the common lib and in turn the common class loader, the implementation may be shared across Web applications.


PreviousNextIndex

©2009, Avaya Inc. All rights reserved.