Overview of migration between platforms
The basic steps involved in migrating data and applications between platforms are included below. See the identified topics for detailed procedures.
- Download the AVmigr for IR R2.0 migration package from the support.avaya.com web site onto the Avaya IR R1.0, R1.2, R1.2.1, or R1.3 platform and install it using the
pkgadd command. (See Installing the Avaya IR migration package.) - Run the
save_conf command to save the configuration of the current platform to a single XML file. (See Saving the configuration.) - Use the
tar_it utility to package directories and files that need to be moved to the Avaya IR R2.0 platform. (See Migrating data.)Speech and application files can be included because they do not require conversion when moved between IR platforms.
- Make sure that all the required Solaris OS and Avaya software is installed on the Sun Fire 280R or Sun Fire V240 Avaya IR R2.0 platform.
- Verify that all the required RTU licenses have been migrated and configured on the WebLM servers associated with the Sun Fire 280R or the Sun Fire V240 Avaya IR R2.0 platform. For IR R2.0, the licensing mechanism has changed from RTU to WebLM. Contact the Avaya Services organization to perform the transitioning of your RTU licenses to WebLM.
- Use FTP or a similar mechanism to transfer the generated tar file from the previous step to the Avaya IR R2.0 platform.
- Copy the archive files to their respective locations on the Avaya IR R2.0 platform. (See Migrating data.)
- Run the
restore_conf command to restore the configuration from the previously saved XML file. (See Restoring the configuration.) - Ensure that the voice system is up and running.
- Verify through Web Administration that all the required features have been configured correctly.
- If any discrepancies are found, correct them manually.
- Recompile all Avaya IVR Designer and IRAPI applications to ensure that they continue to execute successfully.
Note:
The libraries to include when compiling IRAPI applications have changed. For more information, see Introduction to the IRAPI.
