Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: Modesto Vega on August 05, 2022, 02:19:47 am

Title: Upgrade path to Sparx EA v16 and PCS v5
Post by: Modesto Vega on August 05, 2022, 02:19:47 am
We are planning our upgrade to Sparx EA v16 (build 1605) and PCS v5 (build 105). Am I correct to assume the following?

Can anybody think of any gotchas (other than odd v16 and v5 behaviours)?
Title: Re: Upgrade path to Sparx EA v16 and PCS v5
Post by: Sunshine on August 05, 2022, 04:29:42 pm
Thats pretty much it but it depends on what you are upgrading from exactly. If its earlier than V15.2 then you may need to upgrade the schema. https://sparxsystems.com/resources/repositories/index.html (https://sparxsystems.com/resources/repositories/index.html).
Needless to say any new features used with V16 won't be seen too well in earlier versions.
Title: Re: Upgrade path to Sparx EA v16 and PCS v5
Post by: OpenIT Solutions on August 05, 2022, 05:35:54 pm
One note of caution on 16 64bit. In my testing, i got timeout errors when opening a package with a large number of elements/subpackages in. When i tried with the 32 bit version all was ok. I need to do more testing. Bit if you have a large repository ... i'd run some tests yourself first...
Title: Re: Upgrade path to Sparx EA v16 and PCS v5
Post by: Modesto Vega on August 05, 2022, 08:09:48 pm
Thank you for both replies.

Are you getting the timeouts with local repositories or with server based repositories? If server base, what RDBMS are you using?
Title: Re: Upgrade path to Sparx EA v16 and PCS v5
Post by: Graham_Moir on August 06, 2022, 04:02:19 am
Quote from: OpenIT Solutions on August 05, 2022, 05:35:54 pm
One note of caution on 16 64bit. In my testing, i got timeout errors when opening a package with a large number of elements/subpackages in. When i tried with the 32 bit version all was ok. I need to do more testing. Bit if you have a large repository ... i'd run some tests yourself first...

Same here, we have reverted to 32-bit throughout for now.  MS-SQL DBMS   with quite a small repository.
Title: Re: Upgrade path to Sparx EA v16 and PCS v5
Post by: Graham_Moir on August 06, 2022, 04:05:08 am
Quote from: Modesto Vega on August 05, 2022, 02:19:47 am
We are planning our upgrade to Sparx EA v16 (build 1605) and PCS v5 (build 105). Am I correct to assume the following?
  • The PCS backend (including WebEA and WebConfig) can be upgrade 1st.
  • Sparx EA 15.2 (build 1559) should work fine with PCS v5 (build 105).
  • We should be able to run a mixed Sparx EA setup for a while - i.e., v15 and v16 clients interfacing with PCS v5 (build 105).

We have been unable to use 15.x which doesn't seem to work with the latest PCS so we're going straight to 16.

Can anybody think of any gotchas (other than odd v16 and v5 behaviours)?
Title: Re: Upgrade path to Sparx EA v16 and PCS v5
Post by: Modesto Vega on September 05, 2022, 08:19:38 pm
Having read through https://sparxsystems.com/enterprise_architect_user_guide/16.0/the_model_repository/pcs-64bit-migration.html (https://sparxsystems.com/enterprise_architect_user_guide/16.0/the_model_repository/pcs-64bit-migration.html) and https://sparxsystems.com/enterprise_architect_user_guide/16.0/the_model_repository/cloud_server_client_add_native.html (https://sparxsystems.com/enterprise_architect_user_guide/16.0/the_model_repository/cloud_server_client_add_native.html). I find the following screenshot confusing
(https://sparxsystems.com/enterprise_architect_user_guide/16.0/images/pcs-databasemanager-add-native-ss.jpg).

Why is the database user mandatory? Why does it have to specify in the connection? I am expecting Pro Cloud Server to use the service account to access the database.