Configuring applications and licenses

Last Updated : Oct 27, 2025 |

Before you begin

If you are using an external application server, ensure that you install Java 1.8.0_121 and Apache Tomcat version 8.5.11 and later.

Procedure

  1. Log in to EPM using the username and password provided during the Avaya Experience Portal installation.
  2. To configure the applications locally on primary or auxiliary EPM using the web interface, in the left pane, click System Configuration > Applications. All application names, except PomDriverApp and Nailer, are case-sensitive. You must spell the application names exactly as follows:
    1. PomDriverApp: https://<application server ip>:port-number-configured-on-application-server/PomDriverApp/ccxml/start.jsp where the application type is POM:Driver, Enable TTS, Outbound Type
    2. Nailer:https://<application server ip>:port-number-configured-on-application-server/Nailer/ccxml/start.jsp Application Type= POM:Nailer, Outbound Type
    3. AvayaPOMNotifier: https://<application server ip>:port-number-configured-on-application-server/AvayaPOMNotifier/Start Application Type = POM:Application/VXML, Outbound Type
    4. AvayaPOMAnnouncement: https://<application server ip>:port-number-configured-on-application-server/AvayaPOMAnnouncement/Start Application Type = POM:Application/VXML, Outbound Type
    5. AvayaPOMAgent: https://<application server ip>:port-number-configured-on-application-server/AvayaPOMAgent/Start Application Type = POM:Application/VXML, Outbound Type
    6. AvayaPOMSMS: https://<application server ip>:port-number-configured-on-application-server/AvayaPOMSMS/Start Application Type = SMS, Inbound Type
    7. AvayaPOMEmail: https://<application server ip>:port-number-configured-on-application-server/AvayaPOMEmail/Start Application Type = Email, Inbound Type
      Note:

      You must configure at least one application with the name Nailer and PomDriverApp respectively with POM:Nailer and POM:Driver type.

      For a multi zone setup, configure minimum one nailer application and one driver application on a POM system for each zone.

      For an organization enabled system, you must configure both the Nailer and PomDriverApp applications for the default organization for each zone.

      Each organization in the zone must have the same URL.

  3. The following steps are to configure the Avaya Orchestration Designer applications only locally on primary EPM using the $POM_HOME/bin/insert_POM_Apps.sh script. This step is not applicable for configuring auxiliary EPM setup. In case the application server is local to EPM, the IP address of the aux hosting the application server must be mentioned as an alternate IP in the applications configuration.

    1. Log in to command line interface using root credentials.

    2. Type cd $POM_HOME/bin.

    3. Type ./insert_POM_Apps.sh

    4. Type the EPM web administrator username.

    5. Type the EPM web administrator password.

    6. Reenter the password for verification.

    7. Type the IP address of the EPM application server on which the Avaya Orchestration Designer applications are installed.

    8. On web user interface click System Configurations > Applications to verify the applications added by Avaya Experience Portal.

    9. Select PomDriverApp, and from the Speech Servers option, select the TTS resource and add a selected voice.

  4. If you use an external application server, do the following:
    1. Copy the *.war files from $POM_HOME/DDapps to $CATALINA_HOME/webapps of the application server.
    2. If the file log4j-1.2.15.jar is present in $CATALINA_HOME/lib, then delete it from your external application server.
      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.

    3. Copy files from $POM_HOME/DDapps/lib/* to $CATALINA_HOME/lib of the application server.
    4. Edit <APPSERVER_HOME>/conf/server.xml and add the following connector node: 
      <Connector protocol="HTTP/1.1" port="7443" minSpareThreads="5" maxSpareThreads="75" enableLookups="true" disableUploadTimeout="true" acceptCount="100"  maxThreads="200" scheme="https" secure="true" SSLEnabled="true" keystoreFile="/opt/AppServer/Tomcat/tomcat/conf/myTrustStore" keystoreType="JKS" "keystorePass="changeit" clientAuth="false" sslEnabledProtocols="TLSv1.2" ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_EMPTY_RENEGOTIATION_INFO_SCSV"/>
    5. Edit <APPSERVER_HOME>/bin/catalina.sh file to append the JAVA_OPTS variable export JAVA_OPTS="$JAVA_OPTS -Dorg.xsocket.connection.client.ssl.sslengine.enabledProtocols=TLSv1.2”. If it is not defined, then declare new JAVA_OPTS variable export JAVA_OPTS="-Dorg.xsocket.connection.client.ssl.sslengine.enabledProtocols=TLSv1.2"
  5. Restart the external application server.
    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.

  6. Use Avaya WebLM to configure the license information for POM. Configure licenses for the following three channels:

    • SMS channel: Sends SMS using Short Message Peer-Peer Protocol (SMPP). Ensure you have an SMS channel configured license on Avaya Experience Portal.

    • Email channel: Sends email messages using Simple Mail Transfer Protocol (SMTP). Ensure you have an email channel configured license on Avaya Experience Portal.

    • Voice channel: Assigns various Avaya Orchestration Designer applications for live voice or answering machine as part of the contact strategy.

  7. Specify the hostname or IP address of the License Server with the port number on Avaya Experience Portal. The administrator allocates licenses for telephony ports, ASR, and TTS connections.