Author Topic: Upgrade PCS for EA16.1"load balancing and connection management" improvements  (Read 2793 times)

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1321
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Hi,

I read the following in Sparx newsletter about the release of EA 16.1

Load balancing and connection management to Pro Cloud Server
Enhanced load balancing and optimization of communications between Enterprise Architect and Pro Cloud Server.
Version 16.1 of Enterprise Architect includes many changes to improve and manage communication with Pro Cloud Server instances.
•   Load balancing and intelligent client throttling ensure optimal individual connectivity while supporting large teams of concurrent modelers
•   New strategies to enhance the modeling experience when using Enterprise Architect over high latency (slow) networks
•   New approaches to handling error conditions and disruptions
•   Restructuring memory usage in Pro Cloud Server and Enterprise Architect to provide less load during high usage scenarios such as XMI model import


A number of clients have reported performance issues working on EA via the PCS when working from home via the VPN. So any improvement in this area is worth trying.
It is not clear from the above whether the improvement requires an update on the PCS when using EA 16.1. I saw a new 5.1 PCS version is available (5.1.121) ; is an upgrade to this version required?
Last time I tried the PCS 5, I experienced some issues e.g. the multiplicity drop down values in the properties of a selected connector in EA was empty.
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8017
  • Karma: +118/-20
    • View Profile
You'll need both to get full advantage of the changes. You may get some improvement upgrading EA only, but the optimizations were about upgrading both.

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1041
  • Karma: +28/-8
    • View Profile
[SNIP]
Last time I tried the PCS 5, I experienced some issues e.g. the multiplicity drop down values in the properties of a selected connector in EA was empty.
On PCS 5 (not 5.1), we have not experienced the behaviour you mention above. The biggest issues we found during the upgrade had to do with the PCS floating license server client not accepting a fully qualified server name when installed side-by-side with PCS (it does not happen if the client is installed on a different machine), and PCS enforcing a whitelist - i.e., restoring the default whitelist each time the configuration manager or webconfig was run.

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1321
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Thanks for the reply. I will test EA 16.1 with the latest PCS build.
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Guillaume

  • EA Practitioner
  • ***
  • Posts: 1321
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
On PCS 5 (not 5.1), we have not experienced the behaviour you mention above. The biggest issues we found during the upgrade had to do with the PCS floating license server client not accepting a fully qualified server name when installed side-by-side with PCS (it does not happen if the client is installed on a different machine), and PCS enforcing a whitelist - i.e., restoring the default whitelist each time the configuration manager or webconfig was run.

Hi Modesto,

I just came across this issue with the FLSClient (403 forbidden - white list error). Did you find a solution ? I attempted to connect to the server using its name (not the fully qualified) but it didn't work.
It only works if I connect to the localhost ...

Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1041
  • Karma: +28/-8
    • View Profile
Hi Guillaume,

We installed the FLS client in a different machine, in our case the virtual server hosting WebEA, and added the IP address of the virtual server to the whitelist. We couldn't find another way to get our setup working. If you do not have another virtual server, trying installing it side-by-side with Sparx EA and whitelist an IP range including the IP of the machine where Sparx EA is installed.