Planning the migration of Java and VoiceXML applications

You should read this section only if you have existing VoiceXML or Java applications.

If you are already using VoiceXML 2.0, VoiceXML 2.1, or Java applications, your application data is not affected during the migration to Blueworx Voice Response Version 6.1, so you do not need to take any action to run such applications when migration is complete. Your dtj.ini file is replaced by a new version, but a copy of your existing file is saved, and renamed to dtj.ini.V4.2.orig, so any customization that you have made to the file previously can be restored by copying across the updates.

If you are using VoiceXML 1.0 applications, these are not supported in Blueworx Voice Response Version 6.1. However, you can convert any VoiceXML 1.0 applications to comply with the VoiceXML 2.1 specification, by using the migration facility provided in the WebSphere Voice Toolkit Version 6.0, which can be downloaded free from Some editing may also be required and you will need to make a change to the AppName entry in the configuration file (see Blueworx Voice Response for AIX: Deploying and Managing VoiceXML and Java Applications for details). You can then use the Voice Toolkit to test these migrated applications before starting the migration of Blueworx Voice Response.

If you are currently using the old Java and VoiceXML Environment (DTBE) that supported VoiceXML 1.0 applications, you must remove it before you can start the migration to Blueworx Voice Response Version 6.1. You also need to save any voice segments and configuration files (.cff) that you use before installing the new version. These actions are documented in Preparing to migrate VoiceXML and Java applications.

After installing the new software, you can then restore your data following the instructions in Restoring your VoiceXML and Java data.

Note: Although Java applications that were developed using JavaBeans can still run in Blueworx Voice Response Version 6.1, the programming tools used with this method are no longer supported, and so all new applications should be developed using the Java API.