List of Connections

The table below lists all iWD component connections and their types.

iWD Component		Role	Connections	TLS	TLS Configuration Provider
iWD Manager	PSDK	Client	Configuration Server	mutual (*)	There are two level of connections from iWD Manager to Configuration Server: System level—used to read configuration of other connections and iWD manager parameters. Will use autoupgrade scheme. User level—used to login users into iWD manager. Will use autoupgrade scheme.
	PSDK	Client	Interaction Server	mutual
	PSDK	Client	UCS	mutual
	PSDK	Client	Message Server	mutual
	REST	Client	History Node	mutual (*)	(REST) javax.ws.rs...Client Standard (PSDK like) configuration via Connection/Application/Host. One connection to HN or HN cluster per tenant.
	REST	Server	Web browser or custom desktops	mutual (*)	(REST) Tomcat. Rest API for iWD Manager UI and/or custom desktop. Standard (PSDK like) configuaration via Port/Application/Host.
iWD Data Mart	PSDK	Client	Configuration Server	mutual (*)	Connection to Config Server is opened on start, then closed so it is not kept open. Will use autoupgrade scheme.
	PSDK	Client	Message Server	optional (*)	Centralized logging is not implemented, will do TLS only if there is enough time to implement centralized logging
	JDBC	Client	iWD Data Mart database	tls	Configured via URL or JVM options or combination depending on database JDBC driver.
	JDBC	Client	ConfigServer DB	tls	Configured via URL or JVM options or combination depending on database JDBC driver. DM has connection to Config Server DAP.
	REST	Client	iWD History Node	mutual	(REST) javax.ws.rs...Client. Standard (PSDK like) configuaration via Connection/Application/Host. Single connection to HN or HN cluster.
	REST	Server	iWD Plug-in for GAX	mutual	(REST) Dropwizard's Jersey. Standard (PSDK like) configuaration via Port/Application/Host. All Data Marts must have same TLS configuration (different certificates or certificate location is supported).
			LCA	no (*)	Will not implement as located on the same host
iWD History Node	PSDK	Client	ConfigServer	mutual (*)	Connection to Config Server is opened on start, then closed so it is not kept open. Will use autoupgrade scheme.
	JMS	Client	Interaction Server Event Log	mutual	Standard (PSDK like) configuaration via Connection/Application/Host.
	PSDK	Client	Message Server	optional (*)	Centralized logging is not implemented, will do TLS only if there is enough time to implement centralized logging
	JDBC	Client	History Node DB	tls	Configured via URL or JVM options or combination depending on DB JDBC driver.
	REST	Server	iWD DataMart and iWD Manager	mutual	(REST) Dropwizard's Jersey, REST API for Data Mart and iWD Manager. Standard (PSDK like) configuaration via Port/Application/Host. All history nodes in cluster must have same TLS configuration (different certificates or certificate location is supported).
Stat Server Extensions	JDBC	Client	iWD Data Mart database	tls	Configured via URL or JVM options or combination depending on DB JDBC driver.
iWD GAX Plugin	JDBC	Client	Interaction Server DB	tls	Configured via URL or JVM options or combination depending on DB JDBC driver.
	REST	Client	iWD Data Mart	mutual	Standard (PSDK like) configuaration via Connection/Application/Host. Connection to Data Mart is created in GAX applicaton itself. If configured on connection level will read TLS settings from first Data Mart connection. Code is based on org.springframework.. RestTemplate (needs to be customized in order to set ssl parameters)
iWD Web	REST	Server	Web browser	mutual	(REST) Tomcat
	PSDK	Client	Interaction Server	mutual
	PSDK	Client	Message Server	mutual
	REST	Client	WSCP	mutual	Spring HttpComponentsMessageSender. Configured via HttpClient.