Multiple Advisors Deployments on One System
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 three 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 numbers defined, or if they are not valid numbers, 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 in the Platform installer for the Java activeMQ.port is 61616.
The default values in the Platform installer for the distributed caching ports are:
- distributed.caching.port=11211
- distributed.caching.maxport=11212
- HTTPPort=8080
- NamingPort=1099
- JMXPort=9999
- HTTPSPort=8443
- AJPPort=8009
- ActiveMQ.port 61616
- distributed.caching.port 11211
- distributed.caching.maxport 11212
- HTTPPort=8080
- NamingPort=1099
- JMXPort=9999
- HTTPSPort=8443
- AJPPort=8009
- ftpService.port=6021
- ActiveMQ.port 61617
- distributed.caching.port 11213
- distributed.caching.maxport 11214
- HTTPPort=8081
- NamingPort=1100
- JMXPort=10000
- HTTPSPort=8444
- AJPPort=8010
- ftpService.port=6022
The default values in the Platform installer for the Geronimo configurable ports are the following:
The following Table shows the configuration file associated with each 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 distributed.caching.maxport |
| Workforce Advisor Server - IEX TotalView | conf/WorkforceUtilization.properties | ftpService.port |
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:
The nodes of a second Advisors deployment (Advisors 2) must use different values for the ports. For example:
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.