Ports in use by Fredhopper – Rezolve Ai Support Portal

The following page provided an overview of the ports that are in use by Fredhopper.

Introduction

The ports used by FAS depends on the "Instance number" with which FAS is started. Instance numbers allow multiple instances to be started on the same environment. Instance 1 is the default. In the most common case there is just 1 instance of FAS running on one system.

Instance	Ports
Instance 1 (default)	8100 to 8200, 4444, 1098 - 1099
Instance 2	9100 to 9200, 4446, 1100 - 1101
Instance 3	10100 to 10200, 4448, 1102 - 1103
Instance 4	11100 to 11200, 4450, 1104 - 1105
Instance 5	12100 to 12200, 4452, 1106 - 1107
instance ....
instance 20 (max)

Port numbers can optionally be modified by copying FAS/etc/instance.conf to FAS/config/instance.conf and changing the port numbers in this configuration file. However we do not recommend this.

Process	Protocol	Port (1)	Port (2)	Port (3)	Port (4)	Comments
ssh	ssh	22	-	-	-	staging / indexing segment -> live segment
deployment agent		8177	-	-	-
datamanager		7100	-	-	-
Replicator		8100	9100	10100	11100	live syncclient fetches indices + business configuration from synscerver on indexer (staging)
Replicator server	JMX	8101	9101	10101	11101
Replicator client	JMX	8102	9102	10102	11102
XML loader	JMX	8103	9103	10103	11104
Search indexer	JMX	8104	9104	10104	11104
Tree builder(s)	JMX	8110 and up	9110 and up	10110 and up	11110 and up
Tree builder(s)		8170 and up	and up	and up	and up
Replicator logs	log4j	8130				Staging client fetches logs from live boxes
Messenger Component	RMI	8140	9140	10140	11140	For distributing messages
Messenger Component	UDP	8141				For discovering other Messengers
Config server	RMI	8150	9150	10150	11150
RMI Naming service	RMI	8160
Frontend	HTTP	8180	9180	10180	11180	PUBLIC INTEGRATION POINT for REST or WebService queries fulfilling the Query API
Frontend internal	HTTP	8181	9181	10181	11181	FOR INTERNAL USE ONLY (do not use, it will cause hanging qservers).
	HTTP	8182	9182	10182	11182	PUBLIC INTEGRATION POINT SEO integration port. All human readable URLS (optimized queries) have to be send to this port
	HTTP	8183	9183	10183	11183	PUBLIC INTEGRATION POINT for status checking (after FAS7.0.4)
	HTTP	8184	9184	10184	11184	PUBLIC INTEGRATION POINT for preview pages (after FAS7.5.0.x)
Staging BM	HTTP	8180	9180	10180	11180	PUBLIC INTEGRATION POINT for REST or WebService queries fulfilling the Query API
Staging BM internal	HTTP	8181	9181	10181	11181	FOR INTERNAL USE ONLY
	HTTPS	8443	9443	10443	11443	Not supported
AJP connector	AJP	8109	9109	10109	11109	Not supported
jboss:service=invoker,type=jrmp RmiObjectPort	RMI	4444	4446	4448	4450
jboss:service=WebService Port	HTTP	8083	8084	8085	8086
QServer JMX	JMX	8190	9190	10190	11190	jConsole
Local agent JMX RMI Connector	RMI	1098	1100	1102	1104
Local agent JNP port	JNP/JNDI	1099	1101	1103	1105	used to shutdown the qserver and send other commands
FSM-QServer	HTTP	8211	9211	10211	11211
Suggest (old)	HTTP	8251	9251	10251	11251	Old stand-alone version of suggest (prototypes)
Suggest (FAS)	HTTP	8180	9180	10180	11180	Suggest deployed into existing FAS, sharing the ports of FAS
Suggest	HTTP	8380				Stand-alone version of suggest (port is adjustable via setting)
Personalization	HTTP	8480				Personalization default port
Personalization Indexer	HTTP	9200				Personalization indexer default port
Targeting QServer	HTTP	8651	9651	10651	11651
~~Reporting Server~~	HTTP	8280	9280	10280	11280	Obsolete, no longer supported

Additional Notes

(1), (2), (3), (4) refer to the default setups for the different instances (as of 6.2.* there are 20 FAS instances possible).
the tree builder needs one port for each universe. By default, the ports are given out consecutively, it is not recommend nor supported to change the ports. If you must change them use [instance.conf] to assign known ports to each universe/instance combination.
the bindings for the config server are tentatively, and not used for the moment.