Release Notes for Avaya Proactive Contact 5.0 Migration. Release Notes for Avaya Proactive Contact 5.0 Migration

Transcription

1 Release Notes for Avaya Proactive Contact 5.0 Migration

2 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer: Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer: Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty: Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: License: USE OR INSTALLATION OF THE PRODUCT INDICATES THEEND USER'S ACCEPTANCE OF THE TERMS SET FORTHHEREIN AND THE GENERAL LICENSE TERMS AVAILABLEON THE AVAYA WEB SITE ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single standalone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Designated System(s) License (DS): End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically or this purpose. Concurrent User License (CU): End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Database License (DL): Customer may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. CPU License (CP): End User may install and use each copy of the Software on a number of Servers up to the number indicated by Avaya provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya's prior consent and payment of an upgrade fee. Named User License (NU): Customer may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. "Named User," means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a "Named User" may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Product. Shrinkwrap License (SR): With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "clickwrap" license accompanying or applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User s request (see Third-party Components" for more information). Copyright: Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components: Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: Preventing toll fraud: "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention: If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: Trademarks: Avaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents: For the most current versions of documentation, see the Avaya Support Web site:

3 Table of Contents 1. Checklist before beginning with migration process Summary of procedure for migration Migrating from Avaya Proactive Contact 4.x to Avaya Proactive Contact Preparing dialer files and database for migration on HP DL385 G2/G5/IBM x3650 M Installing Avaya Proactive Contact 5.0 Linux ES Bootable Installing Avaya Proactive Contact Dialer Migrating Dialer Configuration files, Calling lists, and Database Post-migration procedure Migrating from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact Installing Avaya Proactive Contact 5.0 Linux ES Installing Avaya Proactive Contact 5.0 Dialer Preparing data on Avaya Proactive Contact 3.0.x Dialer for migration Transferring configuration files to Avaya Proactive Contact 5.0 Dialer Importing data from Avaya Proactive Contact 3.0.x Dialer Post-migration procedure List of Customer Fixed Issues, Known Issues, Troubleshooting, and Improvements Contact Support Appendix A Installing Avaya Proactive Contact 5.0 Dialer and Database Appendix B List of files migrated during the migration procedure Appendix C Checklists for migration Migrating from Avaya Proactive Contact 4.x to Avaya Proactive Contact Migrating from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact Page 1

4 Revision History Version Date 0.1 January 5, January 19, January 28, February 25, March 2, March 4, March 25, March 28, May 17, June 27, 2011 Page 2

5 Migration is defined as a new installation, accompanied by migration of data from the previous version that is in use. It is a change in the hardware as well as software from the existing version in use. 1. Checklist before beginning with migration process Ensure that you have the IBM x3650 M2, HP DL 385 G2/G5, or HP DL 360 G7 server to install Avaya Proactive Contact 5.0. Ensure that you have the ISOs of Avaya Proactive Contact 5.0 as below: Dialer/Database Linux ES Bootable WebLM can be co-resident with the Dialer or be installed on a Window s server. Therefore, accordingly ensure you have a Window s server, if required. Two blank DVD/Tape. In case of Third party host, ensure you have enough free space as per the size of the backup. For installing Avaya Proactive Contact 5.0, host name of the dialer should be the same as of the Avaya Proactive Contact 4.x system. For Opt-out and ECPA features, Generic needs to be loaded on the PG230RM. 2. Summary of procedure for migration The summary of procedure for migrating from Avaya Proactive Contact 4.x to Avaya Proactive Contact 5.0 is as follows. For detailed steps, refer the appropriate sections. Procedures to be performed on Avaya Proactive Contact 4.x system: 1. Run migration script to prepare configuration files, calling lists, and users for migration to Avaya Proactive Contact Run migration script to prepare database for migration. Procedures to be performed on Avaya Proactive Contact 5.0 system: 1. Install Avaya Proactive Contact Migrate configuration files and calling lists. 3. Migrate database. 4. Perform all the post migration procedures mentioned in the following sections. The summary of procedure for migrating from Avaya Proactive Contact 3.x to Avaya Proactive Contact 5.0 is as follows. For detailed steps, refer the appropriate sections. Procedures to be performed on Avaya Proactive Contact 3.x system: Page 3

6 1. Prepare calling lists for migration to Avaya Proactive Contact Prepare database for migration to Avaya Proactive Contact Prepare list of Avaya Proactive Contact users for migration to Avaya Proactive Contact 5.0. Procedures to be performed on Avaya Proactive Contact 5.0 system: 1. Install Avaya Proactive Contact Prepare calling lists, database, and users for migration. 3. Transfer/Update configuration files to Avaya Proactive Contact 5.0 system from Avaya Proactive Contact 3.0.x. For the files to be transferred/updated, refer appropriate sections in this document. 4. Migrate the calling lists. 5. Migrate the database. 6. Perform the post-installation procedure as mentioned in the Avaya Proactive Contact 5.0 Dialer release notes. 7. Migrate the users. 3. Migrating from Avaya Proactive Contact 4.x to Avaya Proactive Contact 5.0 You can migrate from the following versions: Avaya Proactive Contact Avaya Proactive Contact 4.1 Avaya Proactive Contact Avaya Proactive Contact Avaya Proactive Contact Avaya Proactive Contact 4.2 Avaya Proactive Contact When migrating from Avaya Proactive Contact 4.x to Avaya Proactive Contact 5.0, you can migrate from the HP DL385 G2/G5/IBM x3650 M2 server to HP DL 360 G7 Server or to HP DL385 G2/G5/IBM x3650 M2 server. For migrating, you must perform the following tasks in the given order: 1. Preparing dialer files and database for migration on HP DL385 G2/G5/IBM x3650 M2 2. Installing Avaya Proactive Contact 5.5 Linux ES Bootable 3. Install Avaya Proactive Contact Dialer 5.0 Page 4

7 4. Migrate Dialer configuration files, Calling lists, and Database Each of these tasks is explained in detail in the subsequent sections. NOTE: It may not be possible to restore the Mondo Backup taken on a HP ProLiant DL 385 G2/G5/IBM x3650 M2 to an HP DL 360 G7 server because HP DL 360 G7 servers do not support RHEL 4.4/ Preparing dialer files and database for migration on HP DL385 G2/G5/IBM x3650 M2 This section describes the steps required to prepare the following for migration: Dialer configuration and calling lists files Database Preparing dialer files and users for migration See Appendix B for the files that are migrated automatically during the migration process. IMPORTANT: If you have done any customizations or if you need any other file from the Avaya Proactive Contact 4.x system apart from the files listed in Appendix B, you will need to migrate them manually. To prepare the calling lists and dialer configuration files: 1. Login to Avaya Proactive Contact 4.x dialer system as admin user. 2. Stop all the dialer processes by using the following commands : stop_pds stop_mts stop_db 3. Insert Avaya Proactive Contact 5.0 Dialer DVD on Avaya Proactive Contact 4.x Dialer system. 4. Login as sroot user on the Avaya Proactive Contact 4.x dialer. 5. Mount the DVD using the following command: mount /mnt/cdrom cd /mnt/cdrom 6. The migration script allows you to take a backup on a DVD/Tape/Third Party Host. NOTE: If you are taking a backup on Tape/Third Party Host, then skip Step 6 and 7 and resume from Step 8. If you plan to use DVD as the backup media for migration, then run the following commands: Page 5

8 cp -pr PC5.0_Mig pc_mig /tmp cd / umount /mnt/cdrom 7. Remove the Avaya Proactive Contact 5.0 Dialer DVD from the DVD drive. cd /tmp 8. Insert a blank DVD/Tape as per the media you want to take the backup on. If you are taking backup of prepared files using a third party host, then first type 3 to select the Manage migration configuration option for the third party host. NOTE: You must consider the following if taking a backup on a Third Party Host: - While using Third Party host, if you want to keep the backup on the same system, then provide the IP address in the Manage migration configuration option. - The migration script displays a prompt for you to enter the password several times. You must enter the password whenever the script gives the password prompt. - Once the backup starts, no activity is displayed on the screen, which indicates that the backup activity is in progress. Do not enter anything during this time unless prompted by the script. - If you are migrating from Avaya Proactive Contact system, then take a backup of sh_eng.msg present in the /opt/avaya/pds/language directory. To take a backup run the following commands: cd /opt/avaya/pds/language cp sh_eng.msg sh_eng.msg Run the migration script as below:./pc5.0_mig 10. In the main menu, type 1 to select Prepare data for migration (to a new PC 5.0 system) option. 11. In the next screen, type 1 to select the Prepare dialer files for migration (calling lists and dialer config files) option. 12. In the Select media menu, select the appropriate option to take back up of prepared files for migration on DVD/Tape/Third Party Host. NOTE: If the file size of system and calling lists is greater than 4 GB, then you can take a backup only on a DDS Tape or on Third Party Host. The files that are backed up are listed at the selection. 13. The PC5.0_Mig script creates the userlist.txt file in the /opt/avaya/pds/config directory which includes the users of group type Page 6

9 sysadm, system, agent, pcanal, auditor, rbac, and rbacadmin. This file is present in the following format: username:group:password:description where: username - Username of the users on Avaya Proactive Contact 4.x system (8 characters or less) group - Group name to which the users belongs. password - Sets a default password for the user. description - Description of the user 14. After the backup process is complete, remove the DVD/Tape on which the backup is taken and press Enter to go back to main menu and type 0 to exit from the menu. Preparing database for migration NOTE: Perform this procedure only on a primary dialer. To export database data from the Avaya Proactive Contact 4.x system: 1. If you want to take the backup on DVD, then run the following command: cd /tmp If you want to take the backup on Tape/Third party host, then run the following command: cd /mnt/cdrom 2. Insert a blank DVD/Tape to take the backup of the database files. 3. Run the migration script as follows:./pc5.0_mig 4. In the main menu, type 1 to select the Prepare data for migration (to a new PC 5.0 system) option. 5. In the next screen, type 2 to select the Prepare database for migration option. 6. In the Select media menu, select the appropriate option to take back up of database data files (export data) on DVD/Tape/Third Party Host. NOTE: If the file size of system and calling lists is greater than 4 GB, then you can take a backup only on a DDS Tape or on Third Party Host. 7. After the backup process is complete, remove the DVD/Tape from the drive, press Enter to go back to main menu and press 0 to exit. Page 7

10 3.2. Installing Avaya Proactive Contact 5.0 Linux ES Bootable Install Avaya Proactive Contact 5.0 Linux ES Bootable (Material ID: ) on the IBM x3650 M2, HP DL 385 G2/G5, or HP DL 360 G7 server. Also, ensure that this system has the same hostname as the system from which the backup was taken. To find out the hostname, run the hostname command. For details on installation, refer to the Avaya Proactive Contact 5.0 Linux ES Bootable release notes. You can download the release notes from the Avaya Support site at Installing Avaya Proactive Contact Dialer 5.0 To install Avaya Proactive Contact 5.0 Dialer, refer to Appendix A Migrating Dialer Configuration files, Calling lists, and Database This section describes the steps required to migrate the following on the Avaya Proactive Contact 5.0 system: Dialer Configuration files and Calling lists Database NOTE: While performing the following procedures, if you get the message /dev/dvdwriter already mounted or /DVD_MNT is busy, then unmount /DVD_MNT using the following command: unmount /DVD_MNT Migrating Dialer Configuration files and Calling lists IMPORTANT: If you are migrating from Avaya Proactive Contact system, then first run the following commands: cd /opt/avaya/pds/config cp -p group.pds group.pds.5.0 If you are migrating from Avaya Proactive Contact 4.0.1/4.1/4.1.1/4.1.2 system, then first run the following commands: cd /opt/avaya/pds/config cp -p app.edt app.edt.5.0 To migrate dialer configuration files and calling lists: 1. Insert Avaya Proactive Contact 5.0 Dialer DVD on the Avaya Proactive Contact 5.0 Dialer system. 2. Login as sroot user. Page 8

11 3. Mount the DVD and run the following script: mount /mnt/cdrom cd /mnt/cdrom 4. If the backup media used in sub-section Preparing dialer files for migration was DVD, then execute the following commands on the Avaya Proactive Contact 5.0 Dialer: cp -pr PC5.0_Mig pc_mig /tmp cd / umount /mnt/cdrom Remove the Avaya Proactive Contact 5.0 Dialer DVD from the DVD drive. cd /tmp If the backup media used for backing up the data in Avaya Proactive Contact 4.x was not DVD, then skip this step. 5. Insert the DVD/Tape on which the backup of dialer configuration files and calling lists was taken. If you are restoring (restore and migrate) prepared files using a third party host, then first type 3 to select the Manage migration configuration option and then give appropriate parameters for the third party host. NOTE: You must take the following points into consideration if taking a backup on a Third Party Host: - While using Third Party host, if you want to keep the backup on the same system, then provide the IP address in the Manage migration configuration option. - The migration script displays a prompt for you to enter the password several times. You must enter the password whenever the script gives the password prompt. - Once the backup starts, no activity is displayed on the screen, which indicates that the backup activity is in progress. Do not enter anything during this time unless prompted by the script. 6. Run the following script:./pc5.0_mig 7. In the main menu, type 2 to select the Perform migration (to a new PC 5.0 system) option. 8. Type 1 to select the Migrate system configuration files and calling list option. 9. In the Select media menu, select the appropriate option to restore and migrate prepared files for migration on DVD/Tape/Third Party Host. Page 9

12 10. After the restore and migrate process is complete, remove the DVD/Tape from which the backup was taken from the DVD/Tape drive and press Enter to go back to the main menu, type 0 to exit from the script. IMPORTANT: If you are migrating from Avaya Proactive Contact system, then run the following commands: cd /opt/avaya/pds/config cp p group.pds.5.0 group.pds If you are migrating from Avaya Proactive Contact 4.0.1/4.1/4.1.1/4.1.2 system, then run the following commands: cd /opt/avaya/pds/config cp p app.edt.5.0 app.edt See Appendix B for the files that are migrated automatically during the migration process. IMPORTANT: If you have done any customizations or if you need any other file from the Avaya Proactive Contact 4.x system apart from the files listed in Appendix B, then migrate them manually. Migrating Database Perform this procedure only on the primary dialer. To import database to the Avaya Proactive Contact 5.0 system: 1. If the backup media used was DVD to take a backup of the database, configuration files, and calling lists, then run the following command: cd /tmp If the backup was taken on Tape/Third party host, then run the following command: cd /mnt/cdrom 2. Insert the DVD/Tape on which the database backup of the Avaya Proactive Contact 4.x dialer was taken. 3. Run the following script:./pc5.0_mig 4. In the main menu, type 2 to select the Perform migration (on a new PC 5.0 system) option. 5. Type 2 to select the Migrate database data option. Page 10

13 6. In the Select media menu, select the appropriate option to import database data from DVD/Tape/Third Party Host to Avaya Proactive Contact 5.0 database. 7. After the backup process is complete, remove the DVD/Tape from the DVD/Tape drive respectively, press Enter to go back to the main menu and press 0 to exit Post-migration procedure Perform the following post-migration procedures: Configure the system Copy crontab for admin if not already present Migrate the calling list Turn off the SSL Configuring the system Configure HA LDAP in Pod Start up the Dialer processes Migrate users from Avaya Proactive Contact 4.x to Avaya Proactive Contact Login to the dialer as admin user. 2. Go to /opt/avaya/pds/etc directory. Edit master.cfg to set the following parameter: DBSERVERIP: IP address of the primary dialer Copying crontab for admin if not already present 1. Login to the dialer as admin user on Avaya Proactive Contact 4.x and Avaya Proactive Contact 5.0 system. 2. Run the command crontab l on both the dialers. 3. Ensure that the entries present in crontab in the Avaya Proactive Contact 4.x dialer are also present on the Avaya Proactive Contact 5.0 dialer. If not, then execute the following steps: a. Copy admin.cron file from /opt/avaya/pds/config of the 4.x dialer onto the /opt/avaya/pds/config directory of the Avaya Proactive Contact 5.0 dialer. b. Login to Avaya Proactive Contact 5.0 dialer as sroot user. c. Go to directory /opt/avaya/pds/config d. Run the command: crontab /opt/avaya/pds/admin.cron Page 11

14 Migrating the calling list NOTE: Perform this procedure if you have migrated from Avaya Proactive Contact 4.0.1/4.1/4.1.1/ You must have sufficient free disk space to ensure successful backup. For example, if the calling list size is 1GB, then ensure that you have 2GB of available disk space before starting the migration process. To take the back up and migrate the calling lists, run the following script: Go to /opt/avaya/pds/tools/shell Command: cd /opt/avaya/pds/tools/shell Execute the script update_clist Command:. /update_clist NOTE: For each calling list file with size 1.5 GB, approximate time required for migration is minutes. For each record in the calling list, file size is increased by 16 bytes. Avaya recommends that you keep the size of the Calling list file to less than 2 GB for the proper functioning of the Dialer. You can use the following formula to verify the size of the calling list. New calling list size (bytes) = Original calling list size (bytes) + (number of calling list records x 16). NOTE: This formula provides you with an approximate value and not the exact size of the calling list. Turning off the SSL Perform this procedure if SSL was turned off in the Avaya Proactive Contact 4.x system: 1. Login to the dialer as sroot. 2. Run the following command: ssl_conf Configuring HA LDAP in POD Perform this procedure only if you want to setup a dialer in a pod configuration. To configure HA LDAP, see High Availability LDAP Configuration for Avaya Proactive Contact 5.0 on After configuring HA LDAP, run the following commands on all the dialer in the pod to verify that the LDAP servers on all the dialers in the pod can communicate with each other: ldapsearch H ldaps:// <local-hostname>:636 ldapsearch H ldaps://<remote-hostname>:636 Page 12

15 Where: <local-hostname> is the dialer on which the command is run. A list of all the users in the LDAP database on the dialer, on which the command is executed, is displayed. <remote-hostname> are the other dialers in the pod. A list of all the users in the LDAP database on the remote dialers is displayed. Starting up the Dialer processes 1. Execute the following command: manage_corba_users D <DIALERID> -A For example, manage_corba_users -D 10 -A 2. Start the database by running the following commands: start_db check_db Verify that all the database processes are running. 3. Run the Mid-Tier software by running the following commands: start_mts check_mts Verify that all the Mid-Tier processes are running. 4. Start the Dialer software by running the following commands: start_pds check_pds check_mts Verify that all the Dialer processes are running. Migrating Users from Avaya Proactive Contact 4.x to Avaya Proactive Contact 5.0 The PC5.0_Mig script creates a file named as userlist.txt in the /opt/avaya/pds/config directory, which includes the users of group type sysadm, system, agent, pcanal, auditor, rbac, and rbacadmin. The password for all the users included in the file is pcs123 by default. This file is present in the following format: username:group:password:description where: username - Username of the users on Avaya Proactive Contact 4.x system (8 characters or less) Page 13

16 group - Group name to which the users belongs. password - Sets a default password for the user. description - Description of the user Edit the userlist.txt file if you want to: Add or delete some users from this file. Change the password of the users. The default password present in the file is pcs123. If you want the password of the users to expire on the first login, then set the value for the FORCEPWCHANGE parameter to 1 in the /opt/avaya/pds/config/createop.cfg file. Run the following steps to re-create all the Avaya Proactive Contact 4.x users on the Avaya Proactive Contact 5.0 system: 1. Login to the dialer as admin user. 2. Run the following command: createop -l /opt/avaya/pds/config/userlist.txt NOTE: If the username already exists on the Avaya Proactive Contact 5.0 dialer, then createop does not add the user and the following message is displayed: Invalid or Duplicate user. NOTE: Install WebLM and Internet Monitor, if required, only after the migration process is complete. Refer to the WebLM and Internet Monitor release notes at 4. Migrating from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact 5.0 You can migrate from the following versions: Avaya Proactive Contact Avaya Proactive Contact Avaya Proactive Contact Avaya Proactive Contact If you want to migrate from Avaya Proactive Contact 3.0.x (Hardware:C8000) to Avaya Proactive Contact 5.0, then you must procure a HP DL 360 G7 machine, install Avaya Proactive Contact 5.0, and then move all the data to the new system. To migrate from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact 5.0, you need to perform the following tasks in the given order: 1. Installing Avaya Proactive Contact 5.0 Linux ES Page 14

17 2. Installing Avaya Proactive Contact 5.0 Dialer 3. Preparing data on Avaya Proactive Contact 3.0.x Dialer for migration 4. Transferring configuration files to Avaya Proactive Contact 5.0 Dialer 5. Importing data from Avaya Proactive Contact 3.0.x Dialer Each of these tasks is explained in detail in the subsequent sections Installing Avaya Proactive Contact 5.0 Linux ES Install Avaya Proactive Contact 5.0 Linux ES Bootable (Material ID: ) on HP DL 360 G7 server. For installation procedure, refer to the Avaya Proactive Contact 5.0 Linux ES Bootable release notes. You can download the release notes from the Avaya Support site at Installing Avaya Proactive Contact 5.0 Dialer To install Avaya Proactive Contact 5.0 Dialer, refer to Appendix A Preparing data on Avaya Proactive Contact 3.0.x Dialer for migration You must prepare the following on Avaya Proactive Contact 3.0.x for migration: Calling lists Database Users Copying scripts required for migration Before migrating data from Avaya Proactive Contact 3.0.x Dialer, perform the following procedure: 1. Insert the Avaya Proactive Contact 5.0 Dialer DVD in the Avaya Proactive Contact 5.0 Dialer. 2. Login as sroot user to the Dialer. 3. Mount the DVD using the following command: mount /mnt/cdrom 4. Go to the following directory: cd /mnt/cdrom/pc_mig/pc_mig3.0.x_to_ Copy the following files to Avaya Proactive Contact 3.0.x Dialer on /tmp directory: start_mig DBExport_3.0.xto5.0 PrepareUserForMigrate_3.x_5.0 Page 15

18 Migrating the Calling lists The start_mig script converts the calling lists from the Avaya Proactive Contact 3.0.x format to Avaya Proactive Contact 5.0 format. NOTE: The start_mig script should be run only on the HPUX Operating system. This script is exclusively for Avaya Proactive Contact 3.0.x systems. Only the calling lists in the standard format, such as list# and inbnd#, where the value of # is from 1-999, are converted by this script. If you want to re-run the start_mig script, ensure that you have deleted the $VOICEDIR/staging/inprogress/listcfg directory. To convert the calling lists: 1. Login as admin user on Avaya Proactive Contact 3.0.x system. 2. Set the execute permission for the start_mig script using the following command: cd /tmp chmod 555 start_mig 3. Execute the script on Avaya Proactive Contact 3.0.x using the following command: start_mig n The script creates PC3toPC4.tar of all the calling lists applications from calllist.tbl in the /tmp directory on Avaya Proactive Contact 3.0.x Dialer. Migrating the database NOTE: Ensure that the dialer and midtier operations are not in progress and database clients are not connected to either of the databases. All the Database operations are performed by the Oracle user. Data export is performed using the exp tool (Oracle 10g) for Avaya Proactive Contact 3.0.x. To export data from Avaya Proactive Contact 3.0.x Dialer: 1. Login to the Avaya Proactive Contact 3.0.x dialer as admin user. 2. Shut down the dialer, midtier and database processes using the stop_pds;stop_mts and stop_db commands. 3. Logout as admin user and login as root user. 4. Copy the DBExport_3.0.xto5.0 script to the path /home/oracle/migration and set the following ownership and permissions: cp DBExport_3.0.xto5.0 /home/oracle/migration cd /home/oracle/migration Page 16

19 chown oracle:oinstall DBExport_3.0.xto5.0 chmod 755 DBExport_3.0.xto To export data from the database, run the DBExport_3.0.xto5.0 script:./dbexport_3.0.xto5.0 The Export_PC3db.tar is created under the /tmp directory. Migrating the users To add all the users present on Avaya Proactive Contact 3.0.x system to the Avaya Proactive Contact 5.0 system: 1. Login to the Avaya Proactive Contact 3.0.x dialer as admin user. The /etc/passwd file contains all the users present on the dialer, except the NIS users. If NIS is configured on Avaya Proactive Contact 3.0.X, then you must get the list of users and their corresponding group from the System Administrator. 2. Go to /tmp directory and run the following script:./prepareuserformigrate_3.x_5.0 The userlist.txt file is created in the /opt/avaya/pds/config directory which includes the users of group type sysadm, system, agent, and pcanal. If NIS is present on the system, then copy the list of users from the NIS to a temporary file such as /opt/avaya/pds/config/userlist.txt. 3. Ensure that the details of the users from NIS file are in the following format: username:group:password:description where: username - Username of the users on Avaya Proactive Contact 3.0.x system (8 characters or less) group - Group name to which the users belongs. password - Sets a default password for the user. description - Description of the user 4.4. Transferring configuration files to Avaya Proactive Contact 5.0 Dialer Transfer/Update the following files from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact 5.0. Page 17

20 File Type File Name Location on Avaya Proactive Contact 3.0.x Dialer Configuration file Telephony Modification to be done in the files or parameters, if any master.cfg /opt/avaya/pds/etc Update the values of the parameters in the master.cfg file on Avaya Proactive Contact 5.0 as were present in the master.cfg of Avaya Proactive Contact 3.0.x. dgswitch.cfg voicemsg.cfg opmon.cfg phonefmt.cfg swif_ct.cfg /opt/avaya/pds/config NOTE: swif_ct.cfg is applicable if you were using a soft dialer and migrating from Avaya Proactive Contact 3.0.x soft dialer to Avaya Proactive Contact 5.0 soft dialer. Jobs *.job /opt/avaya/pds/job Selections and Strategies Completion codes Configuration files File created by the Calling list migration Compressed file created by Copy all the *.S /opt/avaya/pds/callsel and *.G files compcode.cfg /opt/avaya/pds/config Update all the customer enabled completion codes from Avaya Proactive Contact 3.0.x system to Avaya Proactive Contact 5.0. locale.cfg /opt/avaya/pds/config Update all the changes timezone.cfg from Avaya Proactive stdday.cfg Contact 3.0.x system to currencyfmt.cfg Avaya Proactive Contact 5.0 system. PC3toPC4.tar /opt/avaya/pds/ staging/inprogress Export_PC3db.tar /tmp Page 18

21 File Type File Name Location on Avaya Proactive Contact 3.0.x Dialer the Database migration script Text file userlist.txt /opt/avaya/pds/config containing Avaya Proactive Contact 3.0.x users Modification to be done in the files or parameters, if any NOTE: Apart from the above mentioned files, ensure that you import all the customizations done on the Avaya Proactive Contact 3.0.x system to the Avaya Proactive Contact 5.0 system Importing data from Avaya Proactive Contact 3.0.x Dialer Import the following from Avaya Proactive Contact 3.0.x Dialer to Avaya Proactive Contact 5.0 Dialer: Calling lists Database Importing the Calling lists Extract the PC3toPC4.tar file copied from Avaya Proactive Contact 3.0.x Dialer to Avaya Proactive Contact 5.0 Dialer in Section 4.4, and then import the calling lists. To import the calling lists: 1. Insert the Avaya Proactive Contact 5.0 Dialer DVD into the DVD drive. 2. Login as sroot user on Avaya Proactive Contact 5.0 system. 3. Go to /opt/avaya/pds/staging/inprogress using the following command: cd /opt/avaya/pds/staging/inprogress 4. Extract the PC3toPC4.tar file using the following command: tar -xvf PC3toPC4.tar 5. After the files are extracted, copy the *.ky files to the following location: /opt/avaya/pds/config 6. Copy the entries from agentkey_pc4.tbl file and include them in the agentkey.tbl file present in the /opt/avaya/pds/config directory. Page 19

22 7. Copy the entries from calllistapp.tbl file and include them in the calllistapp.tbl file present in the /opt/avaya/pds/lists directory. 8. Run the pcmig_3.0.x_to_5.0 script from Avaya Proactive Contact 5.0 Dialer DVD: mount /mnt/cdrom cd /mnt/cdrom/pc_mig/pc_mig3.0.x_to_5.0./pcmig_3.0.x_to_5.0 This script adds the parameters to list#.fdict of Avaya Proactive Contact 3.0.x calling list and job files. Importing the Database To import data to the Avaya Proactive Contact 5.0 database: 1. Login to Avaya Proactive Contact 5.0 dialer as admin user. 2. Stop all the dialer, midtier, and database processes using the stop_pds,stop_mts and stop_db commands. 3. Login as sroot user. 4. Go to /tmp directory where you had copied the Export_PC3db.tar file in Section 4.4. cd /tmp 5. Extract the exported data from the Export_PC3db.tar file by using the following command: tar -xpvf Export_PC3db.tar P 6. Insert Avaya Proactive Contact 5.0 Dialer DVD. 7. Copy the DBImport_3.0.xto5.0 script from Dialer DVD to the path /home/oracle/migration and set the following ownership and permissions: mount /mnt/cdrom cd /mnt/cdrom/pc_mig/pc_mig3.0.x_to_5.0 cp DBImport_3.0.xto5.0 /home/oracle/migration cd /home/oracle/migration chown oracle:oinstall DBImport_3.0.xto5.0 chmod 755 DBImport_3.0.xto To import the data to Avaya Proactive Contact 5.0 Database, run the DBImport_3.0.xto5.0 script:./dbimport_3.0.xto5.0 Page 20

23 4.6. Post-migration procedure Perform the following post-migration procedures: Configure HA LDAP in Pod Start up the Dialer processes Migrate users from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact 5.0 Configuring HA LDAP in POD Perform this procedure only if you want to setup a dialer in a pod configuration. To configure HA LDAP, see High Availability LDAP Configuration for Avaya Proactive Contact 5.0 on After configuring HA LDAP, run the following commands on all the dialer in the pod to verify that the LDAP servers on all the dialers in the pod can communicate with each other: ldapsearch H ldaps:// <local-hostname>:636 ldapsearch H ldaps://<remote-hostname>:636 Where: <local-hostname> is the dialer on which the command is run. A list of all the users in the LDAP database on the dialer, on which the command is executed, is displayed. <remote-hostname> are the other dialers in the pod. A list of all the users in the LDAP database on the remote dialers is displayed. Starting up the Dialer processes 1. Start the database by running the following commands: start_db check_db Verify that all the database processes are running. 2. Run the Mid-Tier software by running the following commands: start_mts check_mts Verify that all the Mid-Tier processes are running. 3. Start the Dialer software by running the following commands: start_pds check_pds Page 21

24 check_mts Verify that all the Dialer processes are running. Migrating the Users To import all the users from the userlist.txt file: 1. Login to the dialer as admin user. 2. Go to /opt/avaya/pds/config directory. 3. Edit the userlist.txt file if you want to, for example: o o Add or delete some users from this file. Change the password of the users. The default password present in the file is pcs123. If you want the password of the users to expire on the first login, then set the value for the FORCEPWCHANGE parameter to 1 in the /opt/avaya/pds/config/createop.cfg file. 4. Type createop -l /opt/avaya/pds/config/userlist.txt. NOTE: If the username already exists on the Avaya Proactive Contact 5.0 dialer, then createop does not add the user and the following message is displayed Invalid or Duplicate user. This step completes the migration process. NOTE: Install WebLM and Internet Monitor, if required, only after the migration process is complete. Refer to the WebLM and Internet Monitor release notes at 5. List of Customer Fixed Issues, Known Issues, Troubleshooting, and Improvements For information on Customer Fixed Issues, Known Issues, Troubleshooting, and Improvements as included in the Avaya Proactive Contact 5.0 release, refer to the "List of Fixed Issues, Improvements, Known Issues, and Troubleshooting for Avaya Proactive Contact 5.0 (Dialer, OS, Agent, Agent API, Supervisor, and Database)" document on the Avaya Support site: Page 22

25 6. Contact Support You can contact Avaya Proactive Contact Technical Support through Internet, , or telephone. To contact Avaya Proactive Contact support using telephone, call at one of the following numbers: Global Support Services (GSS) Canada Customer Care Center Remote Service Center Hungary Caribbean and Latin America EMEA Services - Post Sales Technical Support Asia/Pacific Regional Support Center / and (India) For details, visit: 7. Appendix A Installing Avaya Proactive Contact 5.0 Dialer and Database To Install Avaya Proactive Contact 5.0 Dialer on a fresh system: 1. Insert the Dialer installation DVD in the DVD drive of Linux machine. 2. Log in to the dialer as sroot user. 3. Mount the DVD using the following command: mount /mnt/cdrom cd /mnt/cdrom 4. Execute the PC5.0_Installer script using the following command:./pc5.0_installer The following messages are displayed: Welcome to Avaya Proactive Contact Installation. Log file - '/var/log/pc install.log'. For details please follow the log file Validating user.. Collecting current environment.. 5. On the Select a language to install prompt, select the required language. The following message is displayed on the screen: Installing OS updates now.. Page 23

26 After the OS updates, the Base dialer installation begins. The following message is displayed: Checking/installing base DIALER packages.. After the Base dialer is installed, the oracle.profile is updated. The following message is displayed. Updating Oracle's.profile.. After updating oracle.profile, Avaya Proactive Contact 5.0 installer installs Oracle. The following messages are displayed: Finished invoking ORACLE installer. Checking for 'Oracle' base package... OK Checking for 'Oracle Updates'... OK Oracle installation verified OK. 6. After the Oracle Installation, the installer installs the base MIDTIER packages. The following messages are displayed: Checking/installing base MIDTIER packages..... Checking/installation of base DIALER and MIDTIER packages complete. Continuing with check/installation of other DIALER and MIDTIER packages.. Finished installing all DIALER and MIDTIER packages. 7. After the installation of Dialer and Mid-tier packages, the post-installation configuration is started. The following messages are displayed: Running post-install configuration... Upgrading tsapi-client-linux rpm package.. Installing libkeepalive library libkeepalive is released under the GNU General Public License (GPL).The object code is located at /usr/lib, the source code and license file are located at /opt/avaya/pds/tools/opensource/libkeepalive.the copyright notice may be found in the release notes Page 24

27 Setting product baseline.. done. 8. After the configuration is complete, the installer verifies the installation. If all the required dialer components are installed, the following messages are displayed: All DIALER packages verified OK. Oracle installation verified OK. Installation verification complete. 9. After the successful verification, the system is rebooted automatically within one minute. The following prompt is displayed: Rebooting NOW After rebooting, execute the following commands to remove the Dialer CD from the Linux Machine: cd / eject 8. Appendix B List of files migrated during the migration procedure The following files are migrated from the Avaya Proactive Contact 4.x system to the Avaya Proactive Contact 5.0 system. IMPORTANT: The following files are migrated automatically by the migration script; however, if you have done any customizations or if you need any other file from the Avaya Proactive Contact 4.x system, you will need to migrate them manually. /opt/avaya/pab/config /opt/avaya/pds/config /opt/avaya/pds/etc/master.cfg /opt/avaya/pds/callsel /opt/avaya/pds/job /opt/avaya/pds/ivr /opt/avaya/pds/lists /opt/avaya/pds/staging/pending /opt/avaya/pds/staging/inprogress /opt/avaya/pds/staging/deleted /opt/avaya/pds/customs /opt/avaya/pds/histrpt Page 25

28 /opt/avaya/pds/reports /opt/avaya/pds/scrnbld /opt/avaya/pds/newconfig/cron /opt/avaya/pds/scripts /opt/avaya/pds/templates /opt/avaya/pds/tools/config /opt/avaya/pds/tools/inbound /opt/avaya/pds/tools/infinity /opt/avaya/pds/tools/lists /opt/avaya/pds/tools/scripts /opt/avaya/pds/tools/verify /opt/avaya/pds/tools/virtual /opt/avaya/pds/tools/xml /opt/avaya/pds/xfer/public/etc /opt/avaya/pds/xfer/public/pcanal /opt/avaya/pds/xfer/public/public /opt/avaya/pds/xfer/public/update_data/updated /opt/avaya/pds/ktbs /opt/avaya/pds/listdist /opt/avaya/pds/reportgen /opt/avaya/pds/switch /opt/avaya/pds/tape /opt/avaya/pds/xfer/clist /etc/hosts /etc/rc.config.d /etc/exports The following files are backed up but not restored: /opt/avaya/pds/config/snmp /opt/avaya/pds/config/dynlog /opt/avaya/pds/config/jobmon.mnu /opt/avaya/pds/config/jobmon.ctb /opt/avaya/pds/config/roleassign.conf Page 26

29 /opt/avaya/pds/config/passwd.pds /opt/avaya/pds/ivr/ivr_passwd.pds Page 27

30 9. Appendix C Checklists for migration 9.1. Migrating from Avaya Proactive Contact 4.x to Avaya Proactive Contact 5.0 Sr. No. Task Description Notes Yes/No 1 Have you taken a backup of the configuration files, calling lists and users using the Avaya Proactive For Migrating from Avaya Proactive Contact 4.x to 5.0 refer to section 3.1. Perform this step only if you are migrating from a previous release of Avaya Proactive Contact. Contact 5.0 Migration script? 2 Have you taken a backup of the database using the Avaya Proactive Contact 5.0 Migration script? 3 Have you installed Avaya Refer to section 3.2 Proactive Contact 5.0 Linux ES? 4 Have you installed Avaya Proactive Contact 5.0 Dialer and Database? Refer to section Have you transferred the data from Avaya Proactive Contact 4.x to Avaya Proactive Contact 5.0 Dialer? 7 Have you performed postmigration procedure? Perform this if you are Migrating from Avaya Proactive Contact 4.x to Avaya Proactive Contact 5.0, refer to section 3.4 Refer to section 3.5 Page 28

31 9.2. Migrating from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact 5.0 Sr. No. Task Description Notes Yes/No 1 Have you installed Avaya Proactive Contact 5.0 Linux ES? 2 Have you installed Avaya Proactive Contact 5.0 Dialer and Database? 3 Have you migrated the data from Avaya Proactive Contact 3.0.x Dialer (calling list, database, users)? 4 Have you transferred the configuration files from Avaya Proactive Contact 3.0.x to Avaya Proactive Contact 5.0 Dialer? 5 Have you imported the data from Avaya Proactive Contact 3.0.x Dialer to PC 5.0? 6 Have you performed post-migration procedure? For Migrating from Avaya Proactive Contact 3.x to Avaya Proactive Contact 5.0, refer to section 4.1 Refer to section 4.2 Refer to section 4.3 Refer to section 4.4 Refer to section 4.5 Refer to section 4.6 Perform this step only if you are migrating from a previous release of Avaya Proactive Contact. Page 29