Configure an ADDP connection to Config Server
Web Engagement Server normally uses standardized Genesys ADDP properties to connect to Genesys servers. However, a successful ADDP connection to Config Server may require extra configuration information, especially when a Config Server connection is not explicitly specified for the Web Engagement Cluster application. This is because the ADDP configuration information is stored on the Config Server—so you can't read it until after you have connected.
To configure your Web Engagement Server to use ADDP for its initial Config Server connection, you must modify your setenv.bat or setenv.sh file:
- Navigate to the installation directory for your Web Engagement Server and open the setenv.bat file (for Windows) or the setenv.sh file (for Linux) with a text editor.
- For Windows:
- Find the line that starts with set USE_ADDP= and set the value to true
- Find the line that starts with set ADDP_TRACE_MODE= and set the value to local, remote, or both. This will enable logging for ADDP-related events.
- For Linux:
- Find the line that starts with USE_ADDP= and set the value to true
- Find the line that starts with ADDP_TRACE_MODE= and set the value to local, remote, or both. This will enable logging for ADDP-related events.
- Save your changes.
Note: If you plan to start Web Engagement Server as a Windows service, you also need to take the following steps so that your changes are applied to the Windows service:
- Run server.bat remove to remove the existing Windows service.
- Run server.bat install to install the updated application as a Windows service.