Upgrading POM

Last Updated : Oct 28, 2025 |

Before you begin

Ensure that you are on the supported releases of Avaya Experience Portal.

Procedure

  1. Log in to Avaya Experience Portal by using one of the following user profiles:

    • root

    • sroot

  2. Based on your operating system, do one of the following:

    • For Red Hat Enterprise Linux (RHEL), use the root user profile.

    • For Avaya Enterprise Linux (AEL), use the sroot user profile.

  3. Run the following command to mount the POM iso image to the server:

    mount —o loop <absolute path of the iso image> /mnt

  4. Run the following command to change the directory to mnt:

    cd /mnt

  5. Run the following command:

    ./installPOM

    The system displays the following message:

    *** Starting POM Installation *** ***************************************************************** ** *** Restarting and checking vpms service status, please wait... *** ***************************************************************** ** tomcatd ( pid xxxxx ) is running... SL ( pid xxxxx ) is running... ActiveMQ is running ... Overall Status: VPMS is running ***************************************************************** ** *** EP service status [OK]*** ***************************************************************** ** "

    Before starting the installation, the installer checks for VPMS services and the state of the components such as Tomcat, SL, ActiveMQ, and VPMS. If any of the components is not running, the installer aborts the upgrade. Therefore, you must ensure that all components are functional. If all the VPMS services and the components are functional, the installer stops the VPMS service and the system displays the Running CLI installation program message.

    While the installer stops the VPMS service, the system displays the following message:

    ***************************************************************** ** *** Stopping vpms service, please wait... *** ***************************************************************** ** Stopping individual components: Stopping Tomcat.............Counter: 10. Tomcat is not running: 0 Tomcat not shut down gracefully; forceful shut down being enacted Will kill tomcat PIDs: xxxxx Stopping SL...... successful Stopping ActiveMQ...... successful VPMS Shutdown Status: [ OK ] Overall Status: VPMS is stopped (all processes are stopped ) ***************************************************************** ** *** vpms service stopped... Starting POM Installation... *** ***************************************************************** **

    After the VPMS service stops, the system displays a message as follows:

    Running CLI installation program

    POM.04.01.00.00.00.xxx Welcome to the installation of Avaya POM POM.04.01.00.00.00.xxx! The homepage is at: http://www.avaya.com/"

  6. Type 1 to continue.

    If the installer detects an earlier release of POM, it provides the following options:

    • POM Upgrade

    • POM Un-Install

      For information about uninstallation, see Implementing Avaya Proactive Outreach Manager.

  7. Type 0 to upgrade.
  8. Optional To quit the upgrade process at any point, do the following:
    1. Press 4.
    2. On the confirmation screen, press 1.
  9. Type 1 to continue.

    The installer displays the POM Upgrade Warning window as follows:

    ******************************************************************* *** POM Upgrade Warning*** ******************************************************************* POM Upgrade will delete the existing $POM_HOME folder and reinstall the new binaries of this version. Please take the backup of any user created files and log files. Also this will upgrade the existing POM database schema. BEFORE CONTINUING, THE DATABASE ADMINISTRATOR SHOULD TAKE A CURRENT BACKUP OF THE POM DATABASE Press 1 to Continue, 2 for Previous, 3 to Redisplay or 4 to Quit [1] "

  10. Type 1 to continue.

    The installer displays the Upgrade Summary window displaying the following:

    Upgrade Summary Note: The last portion of the upgrade might take several minutes to complete. Please be patient and wait for the Post Upgrade Summary to be displayed. IMPORTANT : PLEASE DO NOT ABORT --------------- ---------------------------- Following packages will be upgraded. VPMS/EPMS Plugin POM Server DD/AAOD Applications Installed Version: POM.04.xx.xx.xx.xxx will be upgraded to New Version: POM.04.01.00.00.00.xxx Press 1 to Continue, 2 for Previous, 3 to Redisplay or 4 to Quit [1] 1 "

    • All packages that get upgraded

    • From and To releases of the upgraded packages.

    Caution:

    If you type 1 on the Upgrade Summary window, you cannot navigate back to the upgrade.

    Do not quit the upgrade until the installer completes the upgrade and displays the Post Upgrade Summary window.

    After the upgrade begins, the system displays the following message:

    [ Starting to unpack ] [ Processing package: (1/4) ] [ Processing package: EPMS plugin (2/4) ] .[ Processing package: POM Server (3/4) ] [ Processing package: AAOD Application (4/4) ] ..[ Unpacking finished ] After the upgrade is complete, the system displays the following message: Installation was successful. Application installed on <installation path> ================================================================= [ Console installation done ] /etc/alternatives/java_sdk_1.8.0//bin/java Entry for alias pomservercert successfully imported. Import command completed: 1 entries successfully imported, 0 entries failed or cancelled MAC verified OK Making Appserver server configuration changes... SSL is NOT enabled in /opt/AppServer/Tomcat/tomcat/conf/server.xml at port 7443, now making POM specific changes..... mv: `/opt/AppServer/Tomcat/tomcat/conf/server.xml.ssl' and `/opt/ AppServer/Tomcat/tomcat/conf/server.xml.ssl' are the same file /opt/AppServer/Tomcat/tomcat/conf/server.xml changes done ..... Updating the catalina.sh JAVA_OPTS_POM_APP Variable is already found /opt/AppServer/Tomcat/tomcat/bin/catalina.sh changes done .... =================================================================== === It has been found that the existing POM certificate is a selfsigned certificate. IT IS RECOMMENDED TO GENERATE A NEW CERTIFICATE BY EXECUTING SCRIPT $POM_HOME/bin/pomCertificateGenerate.sh =================================================================== === Moving installation log files to: /opt/Avaya/avpom/POManager/logs ================================================================= If you are using an external application server and you have installed the POM DD/AAOD Application package while installing POM, you need to: a--> Copy the *.war files from $POM_HOME/DDapps to $CATALINA_HOME/ webapps of the external application server. b--> Copy files from $POM_HOME/DDapps/lib/* to $CATALINA_HOME/lib of your external application server. c--> Enable the SSL Configurations for application server. d--> Restart the external application server. Please restart the system now !"

    Note:

    Continue with the upgrade procedure without restarting the system. You can restart after the system as instructed in step 14.

  11. To enable Advanced Campaign and List Management, press y.

    After this feature is enabled, you cannot disable it. You can choose to enable this later. For more information, see Administering Avaya Proactive Outreach Manager.

  12. To start migration of campaign filters to filter templates, press y.

    You must migrate filter conditions in all campaigns to filter templates. The migration associates the configured contact list to the campaigns and newly created filter templates to contact lists. This is a mandatory step for the campaign to run. You can choose to enable this later. For more information, see Administering Avaya Proactive Outreach Manager.

  13. POM prompts you Do you want to enable Advanced guard time now? Press y if you want to enable advanced guard times. Enabling this option requires all contact lists to be re-imported. You can choose to skip by pressing n if you do not want to enable Advanced guard time. The option can be enabled any time later by executing the command $POM_HOME/bin/enable_Advanced_Guard_Time. When you enable the option, you must re-import all the Contact lists. If the option is already enabled in your system, POM does not prompt you during install or upgrade. The Advanced Guard Time encompasses the following features:

  • Timezone based record selection

  • User configurable allowed and disallowed times for calling

  • List distribution

    You can read more about these features in the Release Notes and enable them anytime later. Enabling this feature makes existing contact lists non-usable. All contact lists will have to re-imported. After the option is enabled, you cannot disable Advanced Guard Time.

  1. To enable classification of SIP response code 403 as ‘CALL_FORBIDDEN’ then run the following command as root user: $POM_HOME/bin/updatePOMConfig CallForbidden true
    Note:

    During the upgrade process, FIPS enabled POM system loses all FIPS related configuration. You must enable and configure FIPS again. For more information, see Enabling FIPS topic in the Implementing Avaya Proactive Outreach Manager guide.

  2. Restart the system.
  3. If you have a multiple POM server environment, you must follow the same steps for upgrading POM on auxiliary servers.

    You must restart the Campaign Manager service.

    Caution:

    Do not run the installDB.sh script post upgrade to recreate the POM schema as POM uses the existing schema.

    Note:

    When the POM system executes campaign export, the export files containing the campaign processed contact records are available in the respective organization directory. When you upgrade to POM 4.1, take a backup of old export directory. You can see the details of the old export directory in the Global configurations page.

    Note:
    After upgrading POM to release 4.1, all purges are:

    • Configured for all organizations.

    • Scheduled to run daily at 00:00 hours.

    POM deletes the Purge schedules that are configured earlier to release 4.1.