Interact server ports and network security
Configure Interact t to secure your server ports.
Interact runtime ports
Some of these ports can be closed, or are not required by all Interact installations, depending on your configuration.
- Interact application server port for HTTP
- The default port where Interact requests are handled.
- Interact application server port for HTTPS
- The default SSL port where Interact requests are handled.
- Interact systemTablesDataSource port
- See the datasource's JDBC configuration in Marketing Platform.
- Interact learningTablesDataSource port
- See the datasource's JDBC configuration in Marketing Platform.
- Interact contactAndResponseHistoryDataSource port
- See the datasource's JDBC configuration in Marketing Platform.
- Interact prodUserDataSource port
- See the datasource's JDBC configuration in Marketing Platform.
- Interact testRunDataSource port
- See the datasource's JDBC configuration in Marketing Platform.
- ETL communication port
- Configure this port in Interact | ETL | patternStateETL | communicationPort in the configuration properties.
- EHCache multicast port
- Configure this port in Interact | cacheManagement | Cache | Managers | EHCache | Parameter Data | multicastPort in configuration properties when cache mode is distributed.
- ExtremeScale catalog port
- Configure this port in Interact | Cache Managers | Extreme Scale | Parameter Data | catalogURLs in configuration properties.
- Interact JMX Monitoring port
- Configure this port in Interact
| monitoring | port under configuration properties or run
-Dinteract.jmx.monitoring.port=portNumber. - Interact WebConnector port
-
This port is usually the same as the Interact server port, but it is modifiable in jsconnector.xml.
For the ports for any Interact integrated products, see the documentation for those products.
JMX monitoring is not required for typical Interact functionality. However, it is used for diagnostics and monitoring.
JMX port access can be disabled in the Interact configuration or limited to specific IP address through firewall configurations. This is recommended due to the JMX vulnerability recently found in the third party Apache Commons Library.
The JMX remoting functionality in Apache Geronimo 3.x before 3.0.1, as used in IBM WebSphere Application Server (WAS) Community Edition 3.0.0.3 and other products, does not properly implement the RMI classloader, which allows remote attackers to execute arbitrary code by using the JMX connector to send a crafted serialized object. See http://www-01.ibm.com/support/docview.wss?uid=swg21643282.
Interact design ports
Some of these ports can be closed, or are not required by all Interact installations, depending on your configuration.
- Campaign application server port for HTTP
- The default port where Interact requests are handled.
- Campaign application server port for HTTPS
- The default SSL port where Interact requests are handled.
- Campaign listener port
- The port that Campaign uses internally to accept connections from the web client.
- Other Campaign design ports
- See the Campaign documentation for more information on these ports.
- Campaign JMX Connector port
- Configure this port in Campaign | monitoring | port in configuration properties for contact response history monitorying only.
- Campaign operational monitoring server port
- Configure this port in Campaign | monitoring | serverURL in configuration properties.