Test installations

Overview

• Who should perform a test installation?
• Setting up the test installation
  • Installation on a new machine or vm
  • Installation on the same server
• This should be tested

A lot of customization can be done in Vertec. For example, customers can work with their own scripts, create link types, configure list settings and much more.

When Update Vertec, there may be changes in the Vertec model or processes, changes in terms, or things that are relatively little used disappear from the surface to make way for someone else.

As far as the data is concerned, this is not a problem with the Convert . However, custom settings may result in adjustments that need to be made manually.

(On-premises customers only)

In the following cases, it is recommended that you set up Update test environment and test your Vertec before upgrading the active installation:

• When many users work with it.
• If you want the Vertec installation to be fully operational immediately after an update.
• With major changes in version.
• If a lot of customizing has been done, i.e. with a high degree of complexity of the installation (e.g. many Supplementary Classes , Link Types and Scripts ).
• To try out features of a new version without affecting ongoing operations.

A test installation should be as close as possible to the production installation. For example, the database server (Firebird, MS SQL server) should be the same as the production one, and the database you are testing should be as up-to-date as possible.

A test installation can be set up on a new computer or a VM (Virtual Machine) or on the same server . We recommend the test installation on a separate machine to avoid possible impact on the production system.

Installation on a new machine or VM

1. Install the new Vertec version on the new computer.
2. Take an up-to-date backup of the Vertec database, or:
3. Make a Backup of the existing database (for MS SQL Server, make a backup as usual).
4. Copy the created backup to the new computer and load it as a productive database.
5. Perform a convert.
6. Start the Vertec desktop app. The startup process may take a little longer on the first launch after the convert.

Source version before 6.4.0.9

As of Vertec version 6.4.0.10, the report templates are no longer located on the file system, but directly in the Vertec database.

The first time the Vertec desktop app is started after the convert, the report templates are copied from the file system to the database. The prerequisite for this is that they can be found on the file system. Vertec follows the Word report template path specified in the system settings General. At the end of the first start, when all templates are loaded, this system setting is deleted from the target database.

Therefore, if you want to test a Vertec version up to 6.4.0.9 with a newer version, you need to make sure that the templates are also accessible on the test server under the same path as in the source database, so set up an appropriate network drive on the new server or store the templates locally in the same location as on the source server.

1. Then launch the Vertec desktop app. The startup process may take a little longer on the first launch after the convert.
2. Check whether your templates are available. The exact procedure is described in the article Migration 6.4.0.10: Report templates no longer on the file system.

Installation on the same server

Installing on the same server is a bit tricky, as setting up in a different directory also creates a service, which can cause problems with the production environment. Therefore, you need to do the following:

1. Create a directory manually, e.g. VertecTest.
2. Manually copy all files and subfolders of your Vertec production installation directory to the newly created directory.
3. From here on, all information refers to the newly created directory.
4. If you are working with MS SQL Server, create a temporary Vertec database there and upload an up-to-date backup of the existing database to this temporary database.
5. In Vertec.ini, change the path to the test database.
6. Adjust the Vertec.ini settings so that the different installations do not interfere with each other. To do this, the different ports must be set Notif . The key to this are the cloud server (since otherwise the productive installation will no longer run) and the Notif, which must not run on the same port as the productive one, so that the test data does not mix with the productive data.
7. It is best to assign an Instance Names in the [Database] section so that you can see on the Vertec interface whether it is a test installation.
8. Install a second cloud server service for this directory and start it.
9. Now launch the Vertec desktop app in the test environment.
10. Change the Document path in system settings to ensure that your tests do not overwrite productive reports or create test reports in customer directories.
11. Close the desktop app and stop the service.
12. Now perform an update in the VertecTest directory with the setup of the version you want to test. Caution: The Vertec Setup only knows one service. If the test environment is on the same server, it is the Vertec production service. This service is shut down during the update, which means an interruption in the Vertec production. Users must therefore be informed in advance to leave Vertec.
13. Restart the service.
14. Start the Vertec desktop app in the test environment and run the Database Convert .
15. MS SQL Server: Then perform a Database Convert as described in the article, using the temporary database. Be sure to adjust the paths of the logical files accordingly, so that the active Vertec database is not accidentally overwritten.
16. After that, restart the Vertec desktop app. The startup process may take a little longer on the first launch after the convert.

Above all, the critical processes and structures should be tested and the features that are important for the operation should be executed. This varies from operation to operation, but usually includes:

• Service Entry
• Expense Recording
• Standard Hours (check overtime and holiday balances)
• Invoicing incl. Reports and possibly Bookkeeping (Caution: Do not post to productive bookkeeping)
• Reports
• Evaluations in lists with special List Settings
• New features based on the release notes

We recommend that key users should test their respective workflows, e.g. the administration the invoicing or the project leader the evaluations.