No Results
Edge Client Proxy (ECP)

The ECP connection makes it easier to connect edgeCore to third-party applications without having to use web adapters.

Prerequisites

  • In edgeCore’s conf folder, set the following in environment.bat/environment.sh files: HTTP_SSL=true

  • You need a valid HTTPS certificate for the server.
  • In edgeCore’s tomcat folder, go to conf > server.xml file and add the following line to Connector: maxHttpHeaderSize=”65535″

  • We recommend requesting the latest version of ECP from our Support team. edgeCore uses 2.0.40 version of ECP, so after obtaining the latest one, you need to upload it first and then activate it.

Activating ECP

  1. Go to Extensions.

  2. Find ECP and click to update it to the latest version available.

  3. Logout and stop edgeCore.

  4. Clear the cache. (this will only need to be done the first time)
  5. Restart edgeCore.
  6. Upon login, go to Extensions to verify that ECP is activated.

Creating ECP Connection (Atlassian example)

Having verified that ECP is activated, you can now proceed to create a connection. For the purpose of this example, we are going to use ECP to connect to Atlassian (Confluence/Jira).

  1. In Connections, click + New Connection and select Web Content/Client Proxy/ecp.

  2. Click Use Selected.
    A new window is displayed.
  3. Connection Name is prepopulated, but you can change it.
  4. Click Next to go to the Endpoint step.
  5. In Endpoint > Destination, enter the URL of the website without any query string parameters (in this case, your Atlassian space);
    for example, https://yourspacename.atlassian.net/
  6. Click Next to test the connection.
  7. Save the connection.
  8. In the pipeline, find the newly created connection, click the gear icon and select + to create a feed.
  9. Feed Name is prepopulated, but you can change it.
  10. Make sure that the selected Rule is ECP.
  11. Click Next to go to Preview.
  12. In Preview, you should see the Atlassian login page.
  13. Provide your login information.
    You will see your dashboard from which you can access Jira.
  14. Save the feed.

Supported Integrations

The following integrations are supported:

Product Product Version edgeCore Version
Analytics 4 4.7.0
Forbes N/A 4.6.4
Google Trends N/A 4.7.0
Grafana 11.0.0 4.7.0
HCSS Telematics N/A 4.6.2
Hubspot N/A 4.7.0
Jira N/A 4.7.0
Kibana v10.3.1 4.7.0
New Relic N/A 4.7.0
Outlook 2406 4.7.0
Reveal Fleetmatics N/A 4.7.0
SalesForce N/A 4.7.0
ServiceNow Washington DC 4.7.0
Sharepoint N/A 4.7.0
Solarwinds 2024.1 4.7.0
Splunk 9.1 4.7.0
Zoominfo Zoominfo lite 4.7.0
BabelStreet N/A 4.7.0
Vidrovr N/A 4.7.0
SemRush N/A 4.7.0
Linkedin N/A 4.7.0
Azure Portal N/A 4.7.0
Nagios N/A 4.7.0
Zabbix N/A 4.7.0

We recommend requesting the latest version of ECP from our Support team for the integrations to function as intended. edgeCore uses 2.0.40 version of ECP, so after obtaining the latest one, you need to upload it first and then activate it.

Troubleshooting

If you are facing any issues after the installation, we strongly recommend you go through all of the setup steps and check if everything was done correctly. If the issue persists, the next step is to reach out to our team to help you with the issue. The first step to troubleshooting ECP is (if possible) giving access to your environment or app that you are trying to set up to our team as that will drastically decrease time of resolution. Due to the nature of adapters, troubleshooting will require testing after each iteration to pinpoint and resolve the issue, which is why access to environment/app is crucial.
If you cannot provide access, the next step is to acquire screenshots of the browser console, HAR file, and edgeweb.log and send them back to us in order for us to investigate the issue. The best way of collecting the most accurate HAR files will be through the Fiddler app which needs to be deployed in you system. However, if this is not a possibility, HAR capture can be done via your browser although it will be far less reliable for pinpointing the issue.


Terms | Privacy