Solutions Pre-requisite

...

Type	Source Host	Source Port	Destination Host	Destination Port
TCP	<Client Application>	any	EF Connector	61616/61614
TCP	EF Connector (B)	any	EF Connector	61616/61614
HTTP	For status monitoring from any machine		EF Connector	8162
XMPP	EF Connector	any	Cisco Finesse	5222, 5223, 7071, 7443
HTTP/S	EF Connector	any	Cisco Finesse	80, 8080, 443, 8443
NTP	EF Connector	any	NTP Server	123
DNS	EF Connector	any	DNS Server	53
Spring Port	EF Connector	any	EF Connector	8112

<Client Application> is a machine running client application of EF Connector. For server-based applications like Siebel, it’s Siebel Communication Server. For desktop-based applications, it’s the machine address of the agent desktop running the desktop application.
In a redundant deployment, both EF Connector instances communicate with each other on the same TCP OpenWire port 61616. In the table above, it’s mentioned as EF Connector (B) ⇒ EF Connector.
These are defaults set in EF Connector, but you can always change the default configuration.

...

Download the docker-compose an env file from Google-Drive
Create a folder on a Linux machine in any path of your inside root.
Place the files inside the created folder as follows:
Open env.txt file with text editor
Image Modified
Make the desired changes and update the file
now run deploy.sh file and you can see after completion your docker image is running
After that run the following commands to edit the ActiveMQ configuration

...

Versions Compared