Multiple Advisors Deployments on One System
35px|link= Starting in release 8.5.0, you can deploy more than one distinct Advisors deployments on one system (see the Figure – Multiple Advisors Deployments on one System). Each Advisors deployment has its own independent configuration, and its own databases.
To manage this:
- There are two port numbers that Advisors modules use to communicate; these are stored in properties files after installation:
- ActiveMQ.properties governs aspects of Java Message Service (JMS)communication.
- Caching.properties defines the port used by the distributed caching facility.
- The Platform installer accepts and sets values for configurable ports of Geronimo. The properties of the Geronimo configurable ports are defined in geronimo-tomcat6-minimal-2.2.1\var\config\config-substitutions.properties.
If there are no port number defined, or if they are not valid number, then Geronimo will not start.
The Advisors installer supplies default values for these ports. It saves the values you choose, default or different, in the properties file created by the installation. You can change these values for a second deployment of Advisors, and preserve the values in the ant.install.properties file to be used when re-installing.
The default value that you see in the Platform installer for the activeMQ.port is 61616.
The default value that you see in the Platform installer for the distributed.caching.port is 11211.
The default values that you see in the Platform installer for the Geronimo configurable ports are the following:
- HTTPPort=8080
- NamingPort=1099
- JMXPort=9999
- HTTPSPort=8443
- AJPPort=8009
Example
The nodes of an Advisors deployment (Advisors 1) use a set of values for the ports on every system on which the nodes are installed. For example:
- ActiveMQ.port 61616
- distributed.caching.port 11211
- HTTPPort=8080
- NamingPort=1099
- JMXPort=9999
- HTTPSPort=8443
- AJPPort=8009
- ftpService.port=6021
The nodes of a second Advisors deployment (Advisors 2) must use different values for the ports. For example:
- ActiveMQ.port 61617
- distributed.caching.port 11212
- HTTPPort=8081
- NamingPort=1100
- JMXPort=10000
- HTTPSPort=8444
- AJPPort=8010
- ftpService.port=6022
Workforce Advisor contains an FTP server that accepts data directly from the IEX TotalView data source. The FTP server listens on port 6021, by default. This is the ftpService.port number used in the example. You specify this port number during installation of Contact Center Advisor/Workforce Advisor. Advisors stores the FTP service port number in the conf/WorkforceAdvisor.properties file.
The following Table shows the configuration file associated with each Platform installer screen on which you enter port-related values. The Table also shows the port properties that are saved, and which you can re-configure post-installation.
| Platform Installer Screen | Corresponding Configuration File | Port Property |
|---|---|---|
| Application Server Configuration | geronimo-tomcat6-minimal-2.2.1\var\config\config-substitutions.properties | HTTPPort, NamingPort, JMXPort, HTTPSPort, AJPPort |
| Cluster Node Configuration | conf/ActiveMQ.properties | ActiveMQ.port |
| Cache Configuration | conf/Caching.properties | distributed.caching.port |
| Workforce Advisor Server - IEX TotalView | conf/WorkforceUtilization.properties | ftpService.port |
Recommendations for Configuration
Genesys recommends the following configuration for multiple deployments on one system:
- Separate the two Advisors deployments by tenant in the Genesys Configuration Server. If you cannot do this for any reason, then separate the object permissions for the respective connection users (that is, the Advisors user for each of the nodes) in the Configuration Server so objects are not used in both nodes.
- Use two separate Object Configuration users; one for each deployment.
- Deploy two separate Apache instances. Ensure the Apache configuration file (httpd.conf) for the Advisors Platform node for which you entered port numbers (that is, the node that does not use the default port numbers) includes the same HTTP and AJP ports as specified in the Platform installer. For example, if you specified AJP port 8019 and HTTP port 8015 for your second Platform instance, then the Apache configuration file must use those same port numbers for AJP and HTTP proxy passes in the ProxyPass sections.