Checklist for Java applications

Checklist for putting a Java application into production:

1. If you have only tested your application on the simulator, you must also test your application using a real Blueworx Voice Response system.  
2. Ensure that your application will answer more than one call, rather than just stopping after the first one: see Developing Java applications for information on how to do this.  
3. Make sure you have done adequate capacity planning. You need to know what your peak volume of calls will be. The base Blueworx Voice Response system must have adequate channels or lines to handle this. You may use one or more base Blueworx Voice Response system, each on the same host as a voice response node. See the General Information and Planning for your base Blueworx Voice Response system.  
4. Install base Blueworx Voice Response systems as necessary: see the Installation information for your base Blueworx Voice Response system.  
5. Set up production voice response nodes as necessary: see Adding a new voice response node to the plex.  
6. Install language support as necessary: see dtjnlsin script.  
7. Install Genesys CallPath support as necessary: see Adding telephony capability.  
8. Install speech recognition and text-to-speech technologies as necessary: see How speech recognition is configured and How text-to-speech is configured.  
9 Set up application nodes: see Setting up an application node.  
10. Ensure that all necessary software is installed on every node. For example, other bean sets such as MQSeries, JDBC, SecureWay, and LDAP.  
11. Ensure that other systems running your business applications are completely set up.  
12. Export voice segments from the simulator, or the test voice response node, to the production voice response nodes, as described in Copying voice segments from one voice response node to another. Voice segments must be imported into each base Blueworx Voice Response system. In an AIX single system image, the voice segments can be imported (using the Blueworx Voice Response for AIX interface) into any SSI node.  
13. Make sure each production voice response node has a NumToApp mapping for the new application: see Mapping a VoiceXML or Java application to a phone number.  
14. Ensure that you start enough instances of the application to handle the peak volume of calls. Java voice applications are different from AIX voice applications, in that you have to make sure that a sufficient number of instances are waiting to answer the call. Use GroupName configuration entries to do this, as described in Ensuring that the call is answered. It's a good idea to start a few more instances than there are channels or lines.