Test installation

Overview

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

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

When Update Vertec, there may be certain changes in the Vertec model or in certain processes, changes in terms, or things that are relatively little used disappear from the interface to make room for others.

In terms of data, this is not a problem with 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 to set up Update test environment and test your Vertec before updating the active installation:

• When many users work with it.
• If the Vertec installation should be fully operational immediately after an update.
• For large version jumps.
• If a lot of customizing was done, i.e. with a high level of complexity of the installation (e.g. many Additional Classes, Types Of Links and Scripts).
• To try out features of a new version without affecting the running operation.

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

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

Installing on a new machine or VM

1. Install the latest Vertec version on the new computer.
2. Take an up-to-current backup of the Vertec database, or:
3. Make a Backup of the existing database (for MS SQL servers 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. Launch the Vertec Desktop App. The start-up process may take a little longer the first time after the conversion.

Source version up to 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 conversion, 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 template path for Word reports, which is specified in the system settings General. At the end of the first start, when all templates are loaded, this system setting is deleted in the target database.

Therefore, if you want to test a Vertec version up to 6.4.0.9 with a newer version, you have to make sure that the templates are accessible on the test server under the same path as in the source database. Therefore, 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 start-up process may take a little longer the first time after the conversion.
2. Check if 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

It is possible to run a test installation on the same server as the production one, but care must be taken to separate the two installations so that there is no impact on the production system or even a mixing of data. The following instructions should therefore be followed very carefully and carried out in the order indicated.

Set up a test instance

1. First, the existing installation is copied manually:
   • Create a new directory, e.g. VertecTest, and make sure that you have write permission to it.  
   • Then copy all the files and subfolders of your productive Vertec installation directory to the newly created VertecTest directory.
   • If you are working with Microsoft sql server, create a temporary database from Vertec, e.g. VertecTest, and load a backup of the existing database into this temporary database.
2. Now adjust the settings in the Vertec.ini – file under VertecTest so that it does not interact with the productive installation under any circumstances:
   • Change path (ServerName) so that it points to the database in the test directory.
   • If you use MS SQL Server, enter Initial Catalog the instance name of the test installation.
   • It is best to give an Instance Name that corresponds to the test installation so that when you start Vertec you can immediately see whether it is the test installation.
   • Set all ports used differently for productive installation. Example:

     Vertec.ini (productive)

     Vertec.ini (VertecTest)

     [Database] ServerName=MYSERVER:C:\Programme\Vertec\DB\Vertec.fdb User Name=SYSDBA Password=Um-sKbZ5L96pWV+Z         [CloudServer] Server Address=MYSERVER ServerPort=8081 ManagementPort=8082 Notif Server=True [Notif] Host=MYSERVER Port=8091 PollInterval=10000 If the Desktop App is still used somewhere, additionally: [Indexing] Host=MYSERVER Port=8092 See Indexing section for full-text search [indexing]

     [Database] ServerName= MYSERVER:C:\Programme\VertecTest\DB\Vertec.fdb User Name=SYSDBA Password=Um-sKbZ5L96pWV+Z InstanceName=VertecTest [CloudServer] Server Address=MYSERVER Server Port= 9081 Management Port= 9082 Notif server=True [Notif] Host=MYSERVER Port= 9091 PollInterval=10000 If the Desktop App is still used somewhere, additionally: [Indexing] Host=MYSERVER Port= 9092 See Indexing section for full-text search [indexing]

   • Save the changes.
3. Install with the Vertec.CloudServer.exe in the directory VertecTest a second Cloud Server service and start it.

This means that the test instance is ready and the Vertec Cloud App can be started for the first time in the test environment.

Customize settings in the test instance

When you start Vertec in the test environment for the first time, it is important that you review certain settings and adjust them if necessary.

Document storage

• If the Document Storage in your Vertec is usually on Dateisystem oder DMS set, you have two options:
  1. You change the Document Path (base path) to ensure that your tests do not overwrite productive reports or create test reports in customer directories.
  2. You set up the document storage in your test environment Intern. This will automatically save all documents you create in the test database savesrecommended).
• Is the document storage already on Intern you do not have to do anything, the documents are in the database you are currently working with and are also stored theresave

Accounting

If you are working with an Extension to an accounting program, you need to make sure that you are not posting to productive accounting.    

The easiest way to do this is to uninstall the extension) in your Test-Vertec. However, if you also want to test the post in the test environment, change the paths to the clients in the System Settings Account (and in other places, locations check the description of your description)Extension

Outlook App

If you would like to test the trial version with the Vertec Outlook App, we recommend that you use a separate test user in Outlook and register the Outlook App for the trial version as a separate app (e.g. Vertec Outlook Test) and set the System Settings Vertec Apps.    

Update test instance

Once you have completed all the above steps, you can now update the test instance to a newer version if necessary.    

To do this, close the Vertec Cloud App again and stop the service of the test instance.

Since the test environment is on the productive server, the productive Vertec service will be shut down during setup, since the setup knows only one service. Therefore, setting up the test server will also create an interruption in the productive Vertec. User must be informed in advance to leave Vertec.

• Then perform the setup to the current Vertec version.    
• Restart the test instance service (and make sure that the productive Vertec service is also running again).
• Start the Vertec Desktop App in the test environment and run the Database Convert.
• For MS SQL servers, perform a Database Convert according to the article, using the temporary database. Be sure to adjust the paths of the logical files to avoid accidentally overwriting the active Vertec database.

After that, you can reopen the Vertec test environment using the Vertec Cloud App or the Vertec Web App and run your tests there.    

In particular, the critical processes and structures should be tested, and the functions that are important for the operation should be featured. This varies from operation to operation, but most of them include:

• Time Tracking
• Recording Of Expenses
• Standard Hours (checking overtime and holiday balance)
• Invoicing incl. Reports and possibly Accounting (Attention: do not post to productive accounting)
• Reports
• Evaluations in lists with special List Settings
• Your Customizing
• New features based on the release notes

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