Migrate Visma Business produktlinje applications to another machine

User guide for migrating application servers and services from one machine to another machine with Visma installations (Visma Business, Visma Document Center and Visma User Directory)

Steps on original server

Om denne oppgaven

Merk: You should not combine an upgrade of the products and a migration to another server. The best approach is to always upgrade the products first on the existing server (ensure they are working fine after the upgrade) and then migrate the already upgraded applications afterwards.

Follow the steps for the server migration:

Prosedyre

  1. Disable Visma.net integration in Visma User Directory.
  2. Disable Visma User Directory integration in Visma Document Center.
  3. Disable the option VUD innlogging in the Systemoppl.behandl. field in the Systemopplysninger table in Visma Business.

    Make sure that you can log in to Visma Business with system user credentials after disabling VUD login; credentials are needed when performing the configuration phase on the new server.

    Notice that the password in Visma Business for system user can be different than the password in VUD.

  4. Stop all possible third party integrations and applications that are accessing the data or interfaces of Visma Business produktlinje applications.
  5. If database address will change, release licences from the applications.

    Make sure that you have the licence keys available; they are needed during the configuration on the new server.

  6. Stop all Visma Business produktlinje services.
  7. Create a backup of all company databases (F[nnnn]) from Microsoft SQL Server Management Studio.
  8. Create database backups of the system level databases. For example, vbsys, vdc_systemdb and VUD.
  9. Copy all the relevant files from the local hard disk to new location (PDF documents etc…).

Steps on destination server

Prosedyre

  1. Restore all the databases. All company databases need to be restored before you can continue with the next steps because of the script.
  2. Open Microsoft SQL Server Management Studio. Before running the script, you need to identify if the SQL connection in the old machine is different from the new SQL connection in the destination machine.
    • Use Different_SQL_Authentication.sql script if the connection to the old SQL Server is DIFFERENT from the connection to the new SQL Server. Examples:
      • Windows Authentication was used; the new connection uses SQL Authentication (user name and password)
      • SQL Authentication (user name and password) was used; the new connection uses Windows Authentication
      • SQL Authentication (user name and password) was used; the new connection uses SQL Authentication but with a different user name or password
    • Use Same_SQL_Authentication.sql script if the connection to the old SQL Server is the same as the connection to the new SQL Server. Examples:
      • Windows Authentication is used on both the old and the new server
      • Same SQL Authentication (user name and password) is used on both the old and the new server
  3. Restart Visma User Directory service.
  4. Install Visma Business produktlinje with the following settings:
    During the configuration step, select:
    • New Catalog database
    • Existing VUD database
    • Existing vbsys database
    • Existing Vdc_systemdb database

    Enter the passwords for Visma Business system user and Visma User Directory vudadmin user. They are the same as in the old server.

    Latest report package will be installed from the version you run the configuration with.

    Complete the installation.

  5. Start Visma Business.

    Activate the licence.

  6. Restart Visma Business Services.
  7. Log in to Visma Business.
    Open the Systemopplysninger table:
    • Enable VUD innlogging in the Systemoppl.behandl. field
    • Update the field Visma Business applikasjonsinstans URI i VUD (the new value can be found in Visma User Directory, go to Application Instances and copy the value in Instance uri for vbsys)
    • Log out from Visma Business
    • Log in to Visma Business and the VUD login screen will appear. Login with VUD credentials
  8. Log in to Visma Document Center:

    Activate the licence.

    Enable Visma User Directory

Relocating Visma Cloud Gateway (tidl. Visma On Premises Gateway) server

Om denne oppgaven

This information can be found in the Visma Cloud Gateway guide. There is a section containing the details how to relocate locally installed applications (with or without Visma Cloud Gateway) while keeping the same licence, and how to set up Visma Cloud Gateway to another server while keeping existing Visma.net data.
Merk: Visma Cloud Gateway certificate has to be re-uploaded from Visma Business
Merk: If Visma Cloud Gateway is installed on a different machine than Visma Business produktlinje, the URL must be:
  • in Visma Business; entered in the Visma Cloud Gateway adresse field in the Systemopplysninger table
  • in Visma User Directory; given in the VUD server configuration file


Vi setter pris på dine tilbakemeldinger. Send tilbakemelding til Visma på dette emnet.