Installing POM on the primary EPM server using the interactive mode

Last Updated : Oct 29, 2025 |

Before you begin

Ensure that the EPM server is running that is VPMS service is in the running state.

Procedure

  1. Log in to primary Avaya Experience Portal as a root user for Red Hat Enterprise Linux (RHEL) or Avaya Enterprise Linux (AEL).
  2. To mount the POM iso image on the server, in the command line, type mount —o loop <absolute path of iso image> /mnt
  3. To change the directory to mnt, type cd /mnt
  4. Type ./installPOM and press Enter.

    The system checks if the Experience Portal Manager (EPM) is running successfully. The system also checks the Tomcat server and the other services displayed in the list.

    [root@pupomcpe17315 mnt]# ./installPOM*** Starting POM Installation ***
*******************************************************************
*** Restarting and checking vpms service status, please wait... ***
*******************************************************************
*******************************************************************
*** EP service status [OK]***
*******************************************************************
*******************************************************************
*** Stopping vpms service, please wait... ***
*******************************************************************
*******************************************************************
*** vpms service stopped... Starting POM Installation... ***
*******************************************************************
Running CLI installation program...

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


Press 1 to Continue, 2 for Previous, 3 to Redisplay or 4 to Quit [1]
  5. On the Welcome screen, type one of the following:

    • 1 to continue.

    • 2 to go back to previous step.

    • 3 to redisplay menu options.

    • 4 to quit the installation.

    Note:
    At any point during the installation, if you press 4 to quit, the system displays the following confirmation message: 
    1 Yes
2 No
Do you want to exit? [2]
  6. On the End User License Agreement page, type 1 and press Enter.

    The screen refreshes with 1 - I accept the terms of the license agreement as the selected option.

  7. Press Enter and then, type one of the following:

    • 1 to continue.

    • 2 to go back to the previous step.

    • 3 to redisplay menu options.

    • 4 to quit the installation.

  8. Type the installation path manually, or press Enter to select the default path. The default path is /opt/Avaya/avpom.
    Note:

    If you are installing POM on AEL, you must select the default path.

    If the installation path that you specify, exists then the system displays the following message: 
    The directory already exists! Are you sure you want to install here and possibly overwrite existing files?

    1. Yes

    2. No

    Do you want to continue?

    • Type 1 to overwrite the existing files or type 2 to specify the installation path.

  9. Type one of the following:

    • 1 to continue.

    • 2 to go back to previous step.

    • 3 to redisplay menu options.

    • 4 to quit the installation.

  10. For the Primary EPM, install the following packages:

    • EPMS plug-in

    • POM server

    • Avaya Orchestration Designer application

    By default, the system selects all packages and you can cancel the selection of Avaya Orchestration Designer application. The EPMS plug-in and the POM server package are mandatory.

    1. Type 3 and press Enter to select or clear the Avaya Orchestration Designer application package.
      Note:

      To install Avaya Orchestration Designer locally instead of using an external application server, after you install POM, run the InstallAppServer.sh script file and copy *.war files from $POM_HOME/DDapps to $APPSERVER_HOME/webapps, and copy files from $POM_HOME/DDapps/lib/* to $APPSERVER_HOME/lib/ folder. To check the path of the InstallAppServer.sh, see the Avaya Experience Portal documentation.

    2. Type r to redisplay.
    3. Type c to continue and press Enter.
  11. Type one of the following:

    • 1 to continue.

    • 2 to go back to previous step.

    • 3 to redisplay menu options.

    • 4 to quit the installation.

  12. Type 0 to create a new certificate or 1 to import the security certificate from specified location, and press Enter.
    Note:

    To import the security certificate, ensure that the certificate format is a PKCS#12 file and stores both the root certificate and the root certificate key. It is not recommended to use self signed certificate.

    The system displays the security certificate.

  13. Type one of the following:

    • 1 to continue.

    • 2 to go back to previous step.

    • 3 to redisplay menu options.

    • 4 to quit the installation.

    The system displays the Installation Summary screen, which consists of: 
    The installation path

    All the packages that you select for installation 

    The space occupied by each package

    The used and free system space
    The system also displays the following message: 
    The last portion of the install might take several minutes

    Please be patient and wait for the Post Installation Summary to begin

    IMPORTANT: PLEASE DO NOT ABORT THE INSTALLATION
  14. Type one of the following:

    • 1 to continue.

    • 2 to go back to previous step.

    • 3 to redisplay menu options.

    • 4 to quit the installation.

    Caution:

    If you type 2 after this step, you cannot navigate back to change the installation.

    Important:

    Do not quit the installation until the system displays the Post Installation Summary screen.

    The system begins the installation. After the installation 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
    Exporting the unencrypted private..
Importing keystore /opt/Avaya/avpom/POManager/config/pom.p12 to /opt/Avaya/avpom/POManager/config/pomKeyStore...

    Entry for alias pomservercert successfully imported.

    Import command completed:  1 entries successfully imported, 0 entries failed or cancelled.

    Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /opt/Avaya/avpom/POManager/config/pomKeyStore -destkeystore /opt/Avaya/avpom/POManager/config/pomKeyStore -deststoretype pkcs12".
Executing sslEnabledForAppserver Fresh Install Case
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 ....
Encrypting the private key...
Private key encryption done.
Moving installation log files to: /opt/Avaya/avpom/POManager/logs
=================================================================

    If you are using an external application server and you have installed the POM 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--> If the file log4j-1.2.15.jar is present in $CATALINA_HOME/lib, then delete it from your external application server.
    c--> Copy files from $POM_HOME/DDapps/lib/* to $CATALINA_HOME/lib of your external application server.

    d--> Enable the SSL Configurations for application server.

    e--> Restart the external application server.

    Please restart the system now !
    Note:

    The Primary server folder $POM_HOME/DDapps/lib* and the External Application Server folder $CATALINA_HOME/lib must contain the same files. If the External Application Server folder $CATALINA_HOME/lib contains any other files than the Primary server folder $POM_HOME/DDapps/lib, ensure you keep only JAR versions of files that are available in $POM_HOME/DDapps/lib.

  15. Restart the system by typing reboot.
  16. Install Oracle driver or MS SQL driver. For more information, see Installing the Oracle driver or Installing the MS SQL driver.
  17. Configure the database. For more information, see Configuring the POM database on the primary POM server.
  18. To enable classification of SIP response code 403 as CALL_FORBIDDEN, run the following command as root user:

    $POM_HOME/bin/updatePOMConfig CallForbidden true