Before you deploy your application on a production system, it is important that you have tested your applications using a real telephone, switch, and a voice response node that has the base Blueworx Voice Response system running on it.
You must test your applications using a real system because applications may behave differently when under load.
The following table summarizes the testing of applications running in a node on a Blueworx Voice Response system.
| How you... |
Running in a node |
|---|---|
| Specify the phone number for an application |
Java and VoiceXML: NodeName configuration entry for the voice response node: NumToApp=number,name |
| Specify the Java class to be used |
Java and VoiceXML: AppName configuration entry AppClass=name. For VoiceXML applications this is always com.ibm.wvr.vxml2.DTVoicelet2 (VoiceXML 2.1) |
| Add your class or jar file to the CLASSPATH |
Java applications only: NodeName configuration entry NodeClassPath=.... This is appended to the CLASSPATH of the host where the voice response node is. |
| Specify the application name (which is used in the NumToApp= mapping) |
Java and VoiceXML: AppName configuration entry AppName=name |
| Specify the voice response node to be used |
Java and VoiceXML: This depends on how you start the application: see Starting applications. |
| Specify the locale (optional: if not specified, voice response node locale is assumed) |
Java and VoiceXML: AppName configuration entry Locale=identifier |
| Specify application parameters |
Java and VoiceXML: AppName configuration entry Parameter=name,value. |
| Specify RecoDefinitions and TTSDefinitions (optional: can be specified at node level) |
Java and VoiceXML: AppName configuration entry RecoDefinition=recotype,locale and TTSDefinition=TTStype,locale |
| Specify RMI port (if necessary) |
Java and VoiceXML: HostName configuration entry RMIPortNumber=number |