The utility for validating application deployments is designed to help ensure that the application has been properly deployed on the application server. While it is not guaranteed to catch all deployment errors, it usually catches the vast majority of them.
To use this utility:
- Access the index.html page.
- Click Validate (in the bullet Validate the application dependencies).
- The Web browser displays the validation page for the selected application.
- Inspect the validation page for any sign of a problem with the installation and deployment of the application on the application server.
In general, green text indicates that a setting is properly configured. Yellow text
indicates that an optional setting is not as expected, but in most cases, it does not
indicate a condition that would prevent the application from running properly. Red
indicates that a required setting is not right and, therefore, that the application
probably will not function as expected.
This page is divided into three basic areas:
- Application details - Provides information about:
- Dialog Designer version, framework runtime version (scert.jar), framework runtime common version (scertcommon.jar), Axis version (axis.jar), starting language, platform, ASR, SSML usage, and WebLM URL.
- License status for platform, including whether runtime, CTI and IC connectors are enabled, or not.
- HTTP and HTTPS Proxy settings
- General Dependency Area Details - Provides information for the following dependancy areas:
- Libraries - Displays the status of logging, licensing, and encoding run-time support library files that must be installed for the application to run properly.
- Web Services - Displays the status of client Web services that must be installed for the application to run properly. The following Web services are searched for using the Validate option:
- org.apache.axis.Version found in <tomcat dir>\common\lib\axis.jar
- javax.xml.rpc.Service found in <tomcat dir>\common\lib\jaxrpc.jar
- org.apache.commons.discovery.ResourceDiscover found in <tomcat dir>\common\lib\commons-discovery-0.2.jar
- org.apache.commons.logging.LogFactory found in <tomcat dir>\bin\commons-logging-api.jar
- javax.activation.DataSource found in <tomcat dir>\common\lib\activation.jar
- javax.xml.soap.SOAPBody found in <tomcat dir>\common\lib\common\lib\saaj.jar
- javax.wsdl.PortType found in <tomcat dir>\common\lib\wsdl4j-1.5.1.jar
- Database - Displays the status of database connectivity files that must be installed for the application to run properly, including:
- Jar files used by Tomcat for connection pooling
- Installed JDBC driver files (application server dependent)
- Testing option to validate data sources added in Dialog Designer
- Interaction Center - Displays the status of the Interaction Center connector which is relevant only if an application will be using the IC connector.
- CTI (Computer Telephony) - Displays the status of the CTI connector which is relevant only if an application will be using the CTI connector.
- Required dependencies - Displays information about any other modules that the application requires in order to run properly.
- Any modules that an application depends on must reside on the same application server. If the module is missing, the validation utility flags it as an error. If the version is different or the application and module are set to use different versions of the run-time support files, the validation utility flags a potential error.
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.
See Preparing the Application Server to Run Dialog Designer Applications.
Tip: