VERIFIED SOLUTION i

Configuring EngageOne Deliver (formerly known as e-Messaging) for use with EngageOne Server

Product Affected: EngageOne Deliver, EngageOne Server
In order to configure EngageOne Deliver for use with EngageOne Server follow the steps below:
  • Modify the following files in the core.war - this can be found in the EngageOne Deliver installation directory, though may be deployed elsewhere depending on the Web Application Server in use.
    1. Modify the servlet.properties file in core.war\WEB-INF\servlet.properties
      • Add the hostname and the IP address of the EngageOne server to "outprofile.provider.allowed=localhost,127.0.0.1,0:0:0:0:0:0:0:1"
      • e.g. "outprofile.provider.allowed=localhost,127.0.0.1,0:0:0:0:0:0:0:1,<EO Hostname>,<EO IP address>"
    2. Modify the engageone.properties file in core.war\WEB-INF\classes\engageone.properties
      • Modify the EngageOne Server Domain, userID and Password parameters to reflect the values within EngageOne
      • Modify the "engagone.wsdlURL" parameter by replacing "IP_ADDRESS:PORT" with the EngageOne IP address and port number.
      • e.g. "engageone.wsdlURL=http://<EO IP address:EO port number>/EngageOneWS/RequestStatusUpdateService?wsdl"
  • Modify the JVM settings within the EngageOne Web Application Server to include the following:
    1. "emessaging.service.endpoint=http://<EngageOne Deliver server Hostname or IP address:port>/emessaging/resource/outboundprofiles"
      • If using EngageOne Deliver 1.5 and above the service endpoint is "emessaging.service.endpoint=http://<EngageOne Deliver server Hostname or IP address:port>/emessaging/resource/v1/outboundprofiles"
    2. "emessaging.vendor.identifier=<Vendor Name>"
    3. "emessaging.base.folder.share=<Vendor Folder Path>"
UPDATED:  August 8, 2019