For Peoples curiosity, here is a list of versions of edge agent and Kinetic versions. I don’t believe the Kinetic minor release number matters, however since 2025 the Edge Agent Config in the menus allows to select a version to configure. Screen shots to follow.
I included the information from the help about for each version I downloaded from. I didn’t realize there was a platform UX version, which I thought was interesting.
Epicor opened a problem to fix the multiple installers and just link to the latest in on-prem 2024.2. I assume that will apply to 24.2 and newer but not sure.
I am pretty confident now that while you can open the classic screens using the local client, there is either something wrong with the way the VD version is operating, or the 2023.2 web app itself is not passing the correct information… I would have expected it not to matter RDS or not considering it works with the local version. The only thing I can think is that in local mode the default port is 6071 and in RDS it is a random port for the edge agent. Maybe that’s where the difference lays… But how does the browser know what port the edge agent is running on that’s what I’m curious about. Not a great deal in the f12
i already wrote - it uses cookie in default browser. EA tray starts on random port and creates cookie with that port information using the default service port for EA.
Browser HP reads that cookie from the EA on the default port and then connects to that port.
As for smart client - that is a simple pipe, it is easier because we control both sides, unlike with browser.
As we can see 2025.2 generates two wsedge socket requests and 2023.2 only 1. With some differences (clientInstanceValue. The null references I have seen while testing have been because of that payload difference.
From what it looks that value tells epicor which edge agent port to respond on, whti that information being stored in the browser.
The way this is generated is baked into the the js, so really nothing that can be done. Sadly 2023.2 is in sustaining support so there is little that is going to be able to be done about this.
So there seems to be a few things going on. Why does it work with the local client and not in RDS? Essentially the standard port is 6071, and I am guessing that if you changed the port in the edge agent maintenance, then deployed using the silent installer, the local may not work for 2023.2 as 6071 is baked into the UI code.
Anyone got any creative ideas to get around this limitation for 2023 to get it to work in RDS?
That’s all I have on this topic. Now we have to and revisit our upgrade plan.
@Olga I appreciate your time in responding to the thread. I know sometimes it can be like to talking to a tree when people try to explain something to me. The whole why it worked in local and not in RDS had me totally stumped, but now I know. Thanks
But how does the browser know what port the edge agent is running on that’s what I’m curious about. Not a great deal in the f12
