ProCloud Server and DirectAccess

[Modesto Vega]

Has anybody tried deploying ProCloud Server using DirectAccess - please see https://docs.microsoft.com/en-us/windows-server/remote/remote-access/directaccess/directaccess - to connect to it?

[skiwi]

We access PCS using direct access for WebEA, Floating licence server, WebConfig, and HTTPS model access. Haven't managed to get RAS working for other reasons (including difficulty following instructions). We are using AD SSO.


Our problems seem to relate to WebEA where we are told that a token/licence is not required, but WebEA doesn't work without a token (support are looking at this).
That we run out of our two tokens (with only one user), we can't see who/where the tokens are being used, and there seems to be no mechanism to release them (also asked support to look at this). It looks a bit like PCS is counting each instance of a user (e.g. single user (SSO) opens two  browser WebEA sessions and uses two tokens!!!)

[Paolo F Cantoni]

We access PCS using direct access for WebEA, Floating licence server, WebConfig, and HTTPS model access. Haven't managed to get RAS working for other reasons (including difficulty following instructions). We are using AD SSO.


Our problems seem to relate to WebEA where we are told that a token/licence is not required, but WebEA doesn't work without a token (support are looking at this).
That we run out of our two tokens (with only one user), we can't see who/where the tokens are being used, and there seems to be no mechanism to release them (also asked support to look at this). It looks a bit like PCS is counting each instance of a user (e.g. single user (SSO) opens two browser WebEA sessions and uses two tokens!!!)

(my emphasis)
Hi Skiwi,
Are you saying the instructions were clear but you didn't follow them or that the instructions were unclear?

Also, we're very interested in your journey with PCS and WebEA so please keep us informed!

Paolo

[skiwi]

re you saying the instructions were clear but you didn't follow them or that the instructions were unclear?
Also, we're very interested in your journey with PCS and WebEA so please keep us informed!

Paolo

The instructions may be clear, but they didn't work for me when I first attempted to follow them.
Due to other issues, as alluded to above, I haven't progressed with this.


The driver for this was replacing our licence server.
This then lets us use the PCS HTTPS server to connect to the models - also not requiring a licence (in theory), which requires less setup (e.g. providing direct access to the database), and is more resilient (over network disconnections).
So it is natural to explore WebEA and RAS

[Modesto Vega]

Thanks skiwi.

Are you referring to the instructions in the Sparx Systems website for WebEA?


Paolo - We have WebEA, WebConfig and ProCloud Server installed and it works fine over the VPN. Ideally we would like to use both (PCS and WebEA) over DirectAccess without using the VPN but WebEA over DirectAccess will also be good enough. Sparx Systems official answer is that although DirectAccess may work it is not supported.

We deployed PCS in one server and WebEA + WebConfig into another server. I am not convinced this is going to be the final setup (see last paragraph). We are using IIS to host WebEA and WebConfig and let PCS run using the embedded web server.

The biggest "complain" I have is that the Floating License Server requires HTTPS and getting a certificate is non-trivial (but there are workarounds).

[skiwi]

Are you referring to the instructions in the Sparx Systems website for WebEA?

yes, - Reuseable Asset Service (RAS) (sparxsystems.com) pdf

[skiwi]

The biggest "complain" I have is that the Floating License Server requires HTTPS and getting a certificate is non-trivial (but there are workarounds).

Actually I'm not fussed by the fact that you have to log in to the licence server in addition to EA.
The purpose for this is lost on me, and there is no option to turn authentication to the licence key server (LKS) off - work around is to publicise in the install instructions the LKS user id and password !

[Sunshine]

Not using cloud pro server but we did find using floating license server over direct access didn't work. We found DA used ipv6 but the floating license server only worked on ipv4.

[Eve]

... the floating license server only worked on ipv4.

Which is one of the reasons why you should switch to using PCS.

[Modesto Vega]

... the floating license server only worked on ipv4.

Which is one of the reasons why you should switch to using PCS.

But, unless I am mistaken, when using the Floating License Server with PCS you must use HTTPS. In some organisations getting a certificate  is non-trivial task. Perhaps I am misunderstanding the documentation but I don't understand why PCS offers you both HTTP and HTTPS as options but to connect to the Floating License Server you must use HTTPS.

[skiwi]

The main reason we moved to PCS was to replace the legacy licence server.
Fortunately you can use self signed certs Add Trust with a Certificate Authority (CA) | Enterprise Architect User Guide , or your organisation's Private CA.

I understand that HTTPS connections from EA to the repository through PCS are also supposed to be free, but if we don't have a licence token loaded they don't work for us. I'm hoping to hear back from support on this.