Time Synchronization
An important consideration is time synchronization between related components. Communication between Generic Connector, client applications, and Cisco Finesse carry timestamps. If the system dates and time are not synchronized the system can produce unpredictable results. Therefore, please make every effort to adhere to the following time synchronization guidelines:
Generic Connector, client applications, and Cisco Finesse should have their Time Zone and time configured properly according to the geographic region and synchronized. To configure the time zone, please see the instructions from the hardware or software manufacturer of NTP server. Client applications and Generic Connector should be synchronized to the second. This synchronization should be maintained continuously and validated on a regular basis. For security reasons, Network Time Protocol (NTP) V 4.1+ is recommended.
Browser Requirement
|
MICROSOFT® INTERNET EXPLORER® |
MICROSOFT® EDGE (NON-CHROMIUM) |
MICROSOFT® EDGE CHROMIUM |
GOOGLE CHROME™ |
MOZILLA® FIREFOX® |
APPLE® SAFARI® |
|---|---|---|---|---|---|
|
IE 11 only (EOL December 31, 2020) |
Supports latest stable browser version (EOL December 31, 2020) |
Supports latest stable browser version |
Supports latest stable browser version |
Supports latest stable browser version |
Supports latest browser stable version |
Documentation Reference: https://help.salesforce.com/articleView?id=getstart_browsers_sfx.htm&type=5
Port Utilization
|
Source |
Destination |
Protocol |
Port Required |
|---|---|---|---|
|
Client Machine |
Cisco Finesse |
HTTP |
7442 |
|
Client Machine |
Cisco Finesse |
HTTPS |
7443 |
|
Client Machine |
Cisco Finesse |
HTTPS |
8445 / 8443 |
|
Client Machine |
EF SSO Server A/B |
HTTP / HTTPS |
1125/443 |
|
EF SSO Server A/B |
Cisco IDS A / Cisco IDS B |
HTTP / HTTPS |
8553 |
System Access Requirements
In order to access Salesforce Connector, an admin should be logged in to his Salesforce org to install the package and configure the required settings to use the application.
Below Hardware / Software are only required, if the customer is using SSO-enabled finesse and wants to login agents via SSO
Hardware Requirements for EF SSO Server A/B
These requirements suffice for deployment.
|
Item |
Recommended |
Notes |
|
CPU |
2 vCPU |
Can be co-hosted |
|
Memory |
4 GB |
|
|
Disk Space |
30 GB |
The minimum disk space requirement is 5 GB. The recommendation is to account for transactional storage and logs. |
Software Requirements
|
Item |
Recommended |
Notes |
|
Operating System |
|
supported on these operating systems |
|
Docker Community Edition |
20.10.17 or above |
tested on this version |
|
Docker Compose |
1.29.2 or above |
tested on this version |
|
Git Client |
1.8.3.1 or above |
tested on this version |
|
Linux Utilities |
|
|
|
Certificates for HTTPS |
|
|---|---|
|
Domain Signed Certificate for Cisco Finesse
If customers are using the SelfSigned Certificate on Cisco Finesse then, all agents need to accept the finesse certificate exception first on the browser to run our Connector. To avoid this customer needs to run Finesse on the Domain Signed Certificate
Domain Signed Certificate for EF SSO Server A / B
Out of the box, we run our EF SSO Server A/B on the self-signed certificate, which required an agent to accept the exception and add the certificate to the browser. To avoid this customer needs to provide Domain Signed Certificate for EF SSO Server A / B