Summary
In the below sections, we are going to review some recommendations to have a successful upgrade which can be a time-consuming process.
It is important to understand that Repository is a server-side model management system that solves the day-to-day challenges of modeling in a team environment, where model collaboration, versioning, security and component reuse are vital which allows team members to share and re-use assets across projects.
All these objects (diagrams, images, users, and more) are stored in form of metadata in the Repository database, also any process with them (publications, check-in/out, creating users and more) are all represented in queries that are run against the database.
Knowing the above information will help understand that the whole upgrade procedure rests mostly on making sure the database server is stable and does not drop connections while running the necessary queries for that, this will need to be reviewed by the company’s DBA team.
Setting up environment
- Back up your Repository database:
- Make sure no users are currently using Team Server or Data Architect as during this process the server will be down and they will not be able to access it, if there is an ongoing process it may get interrupted possibly causing metadata corruptions.
- Verify your system specifications match with the recommended ones, also it is important to understand that having more quantity and size on diagrams will require more resources in general. To maintain scalability please plan accordingly, here are some recommendations: https://docwiki.embarcadero.com/TeamServer/ERStudio/210/en/Installation_Notes#System_Requirements
- Also, verify your database requirements with the same mindset as above: https://docwiki.embarcadero.com/TeamServer/ERStudio/210/en/Database_Server_Requirements
- Do not install or attempt to install Data Architect on the same machine that Team Server is going to be upgraded to, this may cause many harm to your Repository Database metadata and the installation files in general. Team Server already has a lite version of this software bundled which has the specific goal of generating diagram images during publication.
- Gather all the necessary details to perform a smooth upgrade, on a basic upgrade these are the required ones:
- Superuser credentials (Default are Admin / Admin)
- IDERA Login credentials
- Licensing details, normally users use a .slip file that can be easily imported in Configurator.
- Database details:
- Vendor
- Hostname and port
- User credentials with the according privileges (DBO for SQL Server for example)
- Database name
- Windows account credentials
- Optionally, HTTPS/SSL certificate and SSO/LDAP information for advanced login options for users.
Performing the upgrade
Once you have curated all the recommendations, please refer to this documentation and follow it step by step just like the first installation was:
https://docwiki.embarcadero.com/TeamServer/ERStudio/210/en/Install_and_Configure_Team_Server_and_Repository
Below I will leave some notes on that on my experience are necessary to understand the process:
- Running the installer: If you receive errors while performing this action there are two commons issue that you need to take care of:
- Make sure the user running it as administration privileges and read/write on installation folders
- There is also the possibility that due Windows apps administration in general the installation files are corrupted causing problems to install/uninstall, we have some steps for that here in Support please reach us out.
- Launching the Configurator: Users will need to run this via browser, make sure yours is up to date. Also, sometimes the Launch Configurator shortcut may not work to avoid long waits simply use direct URL with explicit port: http://<server-name>:<port>/Configurator/Login
- Installation Options: On any upgrade you will always select ‘Upgrade or connect to an existing database’ including when you are hosting the application server on a different machine, the other option will entirely wipe the database as a fresh one so please avoid selecting it.
As per remaining steps, I think the documentation article covers them very well as they are mostly environment details that will require other teams involvement to guarantee that everything is filled correctly, if you are receiving any error on this you can verify Configurator.log located on <InstallDir>\Idera\Idera Team Server “version”\logs, or open up a support case for further guidance.
