Skip to content

Knowledge Base

White Paper Libary

Upgrading TaskCentre — From v4.1 to BPA Platform 2018 Update 1

 

NOTE: This article has been updated and moved to the Codeless Platforms Documentation Portal.

If you are seeing this message and have not been redirected, click: How to Upgrade BPA Platform.

 

<!–

Introduction

This article describes how to upgrade TaskCentre v4.1. The upgrade must be completed in stages as a single jump from v4.1 to v2018 Update 1 is not possible. Because of this, this article is suitable to use when upgrading from any version to the latest; ensure you start the procedure from the step appropriate to the version you are currently running, all stages still apply.

Note: For the 2018 Update 1 release, we rebranded “TaskCentre” as “BPA Platform”. For this article, “TaskCentre” is used when referring to the pre-upgrade machine, “BPA Platform” for post-upgrade.

The upgrade path is as follows:

  • v4.1 (Build 300) to v4.5 SR4 (Build 1065)
  • v4.5 SR4 to v4.6 (Build 1944)
  • v4.6 to 2018 Update 1 (Build 4121) — Note that the same procedure applies when upgrading from v4.7 to 2018 Update 1

Stage 1: Back up the TaskCentre Store

The TaskCentre Store holds all tasks and their associated properties, such as, data, repositories, variables, formulas, functions, and so on.

It is recommended that you take a backup of the TaskCentre store, which can be restored should a problem with the upgrade arise. You do this as follows:

  1. Disable all of your tasks — This prevents them running while being upgraded, which could cause task failures:
    • From the TaskCentre client, right-click on each task in turn and select Disable
  2. If your TaskCentre installation makes use of an internal store, do the following:
    • The internal store is located in an IWDB folder. By default, this is located in the root of C:\ — C:\iwdb — although a custom location can be specified at install time. Copy this folder to another suitable network location.
  3. If your TaskCentre installation makes use of a SQL Server-hosted store, do the following:
    • By default, the TaskCentre store database name is TCDatabase, although a custom database name can be specifed at install time. The backup of this database should be included as part of the organisational backup. If not, log into the Microsoft SQL Server Management Studio and back up the database from there.

Stage 2: Download the Software

Download each release first before beginning:

Extract the zip files to a location accessible by the TaskCentre server as well as any installed Remote Agents.

Stage 3: Upgrade Remote Agents

Agents cannot communicate with the BPA Platform server if their version and build are different to the server.

Although the Email Trigger (SMTP) (formerly SMTP) and Workflow Job Trigger (formerly Workflow Job) Agents can be upgraded after the server, it is recommended you upgrade all remote Agents first.

Any Agents installed on the TaskCentre server are upgraded when the server is; if your installation only makes use of local agents, this step can be skipped.

To upgrade remote agents, do the following:

  1. From the machine hosting the remote Agents, run the setup.exe for TaskCentre v4.5 SR4.
  2. Click Yes to confirm the upgrade.
  3. Accept all the default settings.
  4. When you get to the Select Features dialog, ensure the relevant Agent is selected along with Client.
  5. Continue with the upgrade.
  6. When completed, do not launch the Configurator; just exit the installation wizard.
  7. Run the setup.exe for TaskCentre v4.6.
  8. Repeat steps 2 to 6 to upgrade to v4.6.
  9. Run the setup.exe for BPA Platform 2018 Update 1.
  10. Repeat steps 2 to 5 to upgrade to v2018 Update 1.
  11. Launch the Configurator.
  12. Ensure all details for the connection to the BPA Platform server are still correct.

Stage 4: Upgrade the TaskCentre Server

Any Agents installed local to the server are upgraded at the same time.

  1. From the machine hosting the TaskCentre server, run the setup.exe for TaskCentre v4.5 SR4.
  2. Click Yes to confirm the upgrade.
  3. Accept all the default settings and continue with the upgrade.
  4. When completed, do not launch the Configurator; just exit the installation wizard.
  5. Run the setup.exe for TaskCentre v4.6.
  6. Repeat steps 2 to 4 to upgrade to v4.6.
  7. Run the setup.exe for BPA Platform 2018 Update 1.
  8. Repeat steps 2 to 3 to upgrade to v2018 Update 1.
  9. Launch the Configurator.
  10. Re-establish the connection to the BPA Platform store, re-register any Agents that were previously active, and ensure any outstanding prerequisites for installed features are met.
    Note: A lot of prerequisites for BPA Platform features were updated for the BPA Platform 2018 Update 1 release — For a detailed description, go to the BPA Platform 2018 Update 1 Release Notes.

Stage 5: Upgrade any Remote TaskCentre Clients

If you make use of remote TaskCentre clients, you must upgrade them after the server upgrade.

Repeat the steps in Stage 4 to upgrade any remote clients.

The client cannot communicate with the BPA Platform server if their version and build are different.

If the TaskCentre client and server are local to each other, the client is upgraded when the server is.

Stage 6: Verification and Testing

Once the upgrade of the server, client(s), and any agents have been completed, you can verify that it has been successful as follows:

  • Within BPA Platform, go to Help > About BPA Platform. Check the version and build numbers are correct:
    BPA Platform 2018 Update 1 Help About
  • Check that all folders, tasks, users, user groups, repositories, variables, formulas and functions are all available.
  • Check that the data is still available in the repositories.
  • Check that the global configuration for the tools is correct.
  • Check that the ODBC and OLEDB data connections are still connected.
  • Check that all previously installed Agents are available and registered.
  • Run Maintenance (go to Manage > Maintenance) and check the Event Log for any possible errors.
  • Enable the disabled tasks and run a sample of them to ensure that they are operational.
Article originally published 03 December 2015 — Article updated 31 October 2018

–>