K2 blackpearl Product Documentation: Installation and Configuration Guide
Upgrade K2 blackpoint > K2 blackpearl

Upgrade requirements

Read KB001386 - How to Upgrade from K2 blackpoint 4.6.4 to K2 blackpearl 4.6.5 before reading this topic to understand the upgrade path in K2 4.6.5.

Prerequisite

Only K2 blackpoint 4.6.4 is upgradable to K2 blackpearl 4.6.5. All prior versions of K2 blackpoint must first be upgraded to K2 blackpoint 4.6.4 before they can be upgraded to K2 blackpearl 4.6.5.

License Keys

When upgrading, the K2 blackpoint license key is no longer valid for a K2 blackpearl installation. During the course of the upgrade, the K2 Installer will prompt the installer for a license key. The machine key is still valid and is used to obtain the new valid license key for your K2 blackpearl installation. If you attempt to use the K2 blackpoint license key, it will notify you that the license key is invalid and prohibit the installation's progress. Once a new license key has been obtained and entered, the installation can proceed.

K2 blackpoint Databases

The upgrade will run database scripts that ensure the existing databases are updated for use by K2 blackpearl. When upgrading a distributed installation, the K2 Server must be upgraded before any of the other K2 components that are distributed. The databases must be updated at the same time, but this is done at the same time as the K2 Server is upgraded. Minor updates are made to the databases, which do not impact on the database structure, the data integrity or the time required to upgrade your system.

Installation Folder

The K2 blackpoint installation folder naming is retained when K2 blackpearl is used to upgrade K2 blackpoint. This is done purposefully to retain the system configuration found in the various configuration files. Owing to this if your K2 blackpearl installation was formerly a K2 blackpoint installation, this must be remembered to avoid future confusion.

Permissions

Ensure that you have the correct permissions to run the upgrade to avoid installation issues such as upgrading the workstations using a local domain admin will result in the client not being registered in the database. For the correct installation and upgrade permissions refer to the permissions topic.

How to upgrade

The setup manager must be run from the desktop of the local machine.

The two basic iterations of K2 blackpoint that would be upgraded are a standalone installation and a distributed installation.

Upgrade a standalone installation

 With the standalone installation upgrading the machine, upgrades the entire deployment.

Upgrade a distributed installation

When a distributed installation is being upgraded, you always start with the K2 Server before upgrading the other components for example SharePoint. Always upgrade in the following order:

  1. K2 Servers
  2. Reporting services
  3. Workspace
  4. Other components in any order

When you upgrade the K2 Server the databases are upgraded at the same time, which means that the SQL server must be up and running during the upgrade of the K2 Server.

Running K2 blackpoint on the same farm as K2 blackpearl, or visa versa, is not possible or supported if attempted.

Steps to upgrade

Locate the executable and double click the file. The installation will initialize and the K2 blackpearl Maintenance screen will display.

Select your option and continue through the Setup Manager steps as described in the Installation section of this help.

Before the installation begins, the Upgrade Summary page will be shown, showing what components were previously installed and what will be upgraded or added.

 

 


K2 blackpearl Product Documentation: Installation and Configuration Guide 4.6.10