Procedure

Use the following procedure when you are ready to start the migration.

1. Preparing a regression test to check for successful migration : You can either use one of your own applications, or one of the sample applications provided, to record items such as:
   • An audio name
   • A user greeting
   • A voice message
   • A voice segment

   Ensure that you include the date and time in the items you record. Also, export or save these items if you are exporting or saving your real data. (Note that audio names, user greetings, and voice messages cannot be exported, so you need to record a voice segment if you want to use the application export–import method.)

   You will use these items to test that you can still access your data after the migration.

   Depending on the pSeries model, this can take from 20 minutes to over 2 hours, but it means that you can restore the system if anything goes wrong. Doing a system backup now could save you a lot of time later.

2. Backing up the AIX system image: Click Operations —> Quiesce Shutdown.
3. When Blueworx Voice Response has terminated, use the DT_shutdown command to ensure any long-running tasks are ended.
4. Backup the system image. Use the mksysb command to back up the data in the root volume group. Use the savevg command to back up other volume groups. See the AIX: Installation Guide, for further information about how to use these commands.
5. Configuring custom servers: Restart Blueworx Voice Response.
6. Custom servers supplied with Blueworx Voice Response are ready to run without any special action. However, if you are migrating from a previous release of Blueworx Voice Response, or if you are migrating to a later version of AIX, you must rebuild and reinstall any custom servers that were not supplied with the product. Therefore, if you have configured a custom server to start automatically whenever Blueworx Voice Response is started, you need to change this configuration so that Blueworx Voice Response will not attempt to start the server before you have had a chance to rebuild it for use with the current release.

   To change the custom server configuration:

   1. Click Operations —> Custom Server Manager.

      The system displays the Custom Server Manager window.

   2. If the IPL Status field for a server shows the value Autoexec, click on the field, then click Auto-start off from the pop-up menu. Continue until all servers have the status Installed.
   3. Close the window.
7. Changing the operating status: To avoid incurring telephony errors when you start Blueworx Voice Response, set the value of the Operating Status parameter for all trunks to Defined.

   To change the parameter:

   1. Click Configuration —> Pack Configuration, then click Change.
   2. Click the Operating Status push button for the first pack.

      The system displays the Operating Status window.

   3. Click Defined, then click OK.
   4. Repeat steps 7.b and 7.c until all trunks have the Operating Status Defined.
8. Shutting down : When you are ready to begin the migration process, click Operations —> Quiesce Shutdown.
9. If Blueworx Voice Response Version 4.2 is at fix level 4.2.0.550 or higher, the system parameter database must be restored to an earlier version prior to the migration so that any Blueworx Voice Response Version 6.1 updates can be applied.

   To restore the system parameter database:

   1. cd into $SYSPARM_DIR (/usr/lpp/dirTalk/db/sysparm_dir)
   2. Restore the database using the command: cp rd.data.4.2.0.550 rd.data

Next step:

• If you are going to use saveDT to backup data, go to Saving your current data.
• Otherwise, go to Starting installation of Blueworx Voice Response.