Follow-On Topics

Related Topics

# Installing King Task Centre

The following topic describes how to install the King Task Centre server and client.

Terminology

|  | Client refers to the main King Task Centre interface, primarily used to create tasks

|  | Server refers to the back-end database and store where all King Task Centre data and task information is held.

Running the Installation

It is recommended you perform the installation locally, rather than over your network.

1. Download the King Task Centre 2018 Update 1 installation from our Partner Area.
2. Unzip the file to your preferred location on the King Task Centre server.
3. Run Setup.exe.
4. From the Welcome screen, click Install.
5. The C++ Redistributable Packages are a necessary component of King Task Centre. Click Install to continue the installation.
6. A reboot is required after each package installation. Click Yes to confirm the reboots. Clicking No aborts the installation.

   NOTE:

   After each reboot, the King Task Centre installation automatically restarts after a short period of time. No further action is needed to make the installation window reappear.

7. Click Yes to confirm the restarts of IIS. Clicking No aborts the installation.
8. Click Next.
9. Enter your King Task Centre product key and click Next.

   Note that the key is case-sensitive.

   If you do not have a product key, contact your business partner or account manager.

10. Click Yes to confirm your acceptance of the End-User License Acceptance. The installation does not continue unless this is accepted.
11. From the Select Features screen, leave everything selected, else clear the selection for those features to not install:

    |  | Client — The King Task Centre user interface, see Using the King Task Centre User Interface
    |  | Server — The back-end of King Task Centre, that is, the database and store
    |  | Microsoft SQL Server Trigger Agent — See About the Microsoft SQL Server Trigger Agent
    |  | Workflow Job Trigger Agent — See About the Workflow Job Trigger Agent
    |  | Email Trigger (SMTP) Agent — See About the Email Trigger (SMTP) Event Agent
    |  | myTaskPortal — See About myTaskPortal
    |  | Web Service — See About the Workflow Web Service
    NOTE: At this stage, the server is not checked for availability of all the prerequisites required for each of the selected features. This is checked during configuration, after the features have been installed. |

12. Click Next.
13. To change the destination folder where the King Task Centre server is installed, click Browse and select the relevant folder, else click Next to accept the default.
14. To change the temporary folder used by the King Task Centre installer, click Browse and select the relevant folder, else click Next to accept the default.

    The installation continues. A reboot is not required to complete the King Task Centre installation.

15. When complete, you can choose whether to Check product configuration after installation closes. It is recommended you do this as you cannot launch the King Task Centre client until you have completed basic configuration at least.

    Ensure Check product configuration after installation closes is selected, and click Finish.

16. Go to Basic Configuration.

Basic Configuration

The following describes the basic configuration required to get King Task Centre running for task usage (all standard tools will be available apart from the Event tools). For a detailed description of how to configure the Event agents and other features of the Configurator, go to Using the Configurator.

TIP:

If you have closed the installer without enabling Check product configuration after installation closes, you can launch the Configurator by either:

- Going to Start > Programs > King Task Centre > Configurator (for servers running up to Windows Server 2008); or
- Typing "Configurator" from the Start menu's run (search) bar

2. The Configurator opens to Server > Store > Configuration. In the background, the Configurator will have checked that the operating system meets the Client's Prerequisites. If not, an error is displayed. It will also have checked the operating system meets the Server's Prerequisites. If not an error is displayed. Select Change store configuration, then choose either: Connect to / Create a new Microsoft SQL Server Store — The store is held in a Microsoft SQL Server database, either locally or remotely Connect to / Create a new internal store — The store is held in a proprietary database, on the same machine as the King Task Centre server What is a store? The King Task Centre server contains a data store where information, such as configured tasks, are stored. Such a store can be held:
   |  | Locally (referred to as an Internal store)
   |  | In a local Microsoft SQL Server store
   |  | In a remote Microsoft SQL Server store
| Click the image to view full size.

3. Click Next.
4. If you have chosen to create a new Microsoft SQL Server Store, do the following, else skip to step 5:
   1. SQL Server — Enter either the IP address, hostname, or fully qualified domain name (FQDN) of the remote Microsoft SQL Server machine where the store is saved. If the database is held locally, either enter "`localhost`" or select Localhost underneath.
   2. Database — Either provide a new database name for this store, or leave the default name of "BPAPlatform".
   3. Select the appropriate authentication King Task Centre will use to access the database:
      - Windows Authentication — Select this to use the credentials of the logged in Windows user.
      - SQL Server Authentication — Select this to provide separate SQL Server credentials. Enter these into Username and Password underneath.
   4. Click Next.
   5. By default, the database file (`.mdb`) and database log file (`.ldb`) for the SQL Server store are saved to the Microsoft SQL Server installation folder (typically `c:\Program Files\Microsoft SQL Server\` and so on).

      If required, you can change the location of the database file and database log file, else skip to step 4.f:

      1. Select Override Default Database Location and enter the new path for the SQL Server store's `.mdb` file.
      2. Select Override Default Log File Location and enter a new path for the SQL Server store's `.ldb` file.
   6. Click Save. Skip to step 6.
5. If you have chosen to create an internal store, do one of the following:
   - To accept the default location of the store (`c:\iwdb`), click Save.
   - To change the location of the internal store, select Change Database Location, then click Browse and choose a suitable location. Click Save.
6. You are prompted for new credentials for the King Task Centre store. Enter a new Password, and repeat the same password in Confirm to ensure they match.
7. Click OK.
8. This procedure so far covers the basic configuration to allow access to the King Task Centre client. At this point, you can click Close and launch the King Task Centre client. All standard tools are available for task creation except for the Event tools. You can return to the Configurator at any time to complete the configuration for the other features.

   If required, you can continue configuring all available features now. Go to Full Configuration.

Full Configuration

The following procedure assumes you have completed the Basic Configuration and are continuing with the configuration.

1. If you have installed the Email Trigger (SMTP) Agent, do the following, else skip to step 2:
   1. To change the location and/or name of the Email Trigger (SMTP) agent, do the following, else go to step 1e:
   2. Select Change Settings.
   3. If required, change Server to be the IP address, hostname or FQDN of the machine where the Email Trigger (SMTP) agent is installed.
   4. If required, change Agent Name to the relevant Email Trigger (SMTP) agent name.
   5. Click Save.
   6. Enter the King Task Centre Administrator password. Typically, this is the one created in step 6 of the Basic Configuration section above.
   7. Click OK.
2. If you have installed the Workflow Job Trigger Agent, do the following, else go to skip to step 3:

1. To change the location and/or name of the Workflow Job Trigger agent, do the following, else go to step 2e:
2. Select Change Settings.
3. If required, change Server to be the IP address, hostname or FQDN of the machine where the Workflow Job Trigger agent is installed.
4. If required, change Agent Name to the relevant Workflow Job Trigger agent name.
5. Click Save.

3. If you have installed the Microsoft SQL Server Trigger Agent, do the following, else skip to step 4:
   1. To change the location and/or name of the Microsoft SQL Server Trigger agent, do the following, else go to step 3f:
   2. Select Add a new SQL Server Agent Instance.
   3. If required, change Agent Instance Name to the relevant Microsoft SQL Server Trigger agent name.
   4. If required, change Server to be the IP address, hostname, or FQDN of the machine where the Microsoft SQL Server Trigger agent is installed.
   5. Select the relevant SQL Server Instance from the drop-down menu. If everything is installed locally, there should only be one entry of MSSQLSERVER.
   6. Click Save.
   7. Click Save again to register the agent.

   You can add multiple Microsoft SQL Server Trigger agents to monitor different database instances. For a detailed description of how to add those, go to Event Agents > Microsoft SQL Server Trigger Agent > Configuration.

4. If you have installed the File System Event Agent, do the following, else skip to step 5:
   1. To change the location and/or name of the File System Event Agent, do the following, else go to step 4e:
   2. Select Change Settings.
   3. If required, change Server to be the IP address, hostname, or FQDN of the machine where the File System Event Trigger Agent installed.
   4. If required, change Agent Name to the relevant File System Event agent name.
   5. Click Save.

   You can add multiple File System Event Trigger Agents to monitor different folder locations and even network locations. For a detailed description of how to add those, see About the File System Event Agent.

5. If you have installed myTaskPortal, do the following, else skip to step 6:
   1. From the Website drop-down list, choose the relevant IIS website created for myTaskPortal. The default is Default Web Site.
   2. Click Save.
6. If you have installed the Web Service, do the following, else skip to step 7:

1. From the Website drop-down list, choose the relevant IIS website created for the web service. The default is Default Web Site.
2. Click Save.

7. If you plan to use the Run Microsoft Reporting Services tool in tasks, do the following, else skip to step 8:
   1. If there are any missing components required by the Run Microsoft Reporting Services tool, click the Install button, the follow the instructions on the screen.
   2. Click Next.

   For a detailed description of the Run Microsoft Reporting Services tool, see About the Run Microsoft Reporting Services Tool .

8. If you plan to use the Run Crystal Report tool in tasks, do the following, else skip to step 9:
   1. If there are any missing components required by the Run Crystal Report tool, click the Install button, then follow the instructions on the screen.
   2. Click Next.

   For a detailed description of the Run Crystal Report tool, see About the Run Crystal Report Tool .

9. If you plan to use the Run Microsoft Word (Merge) tool in tasks, do the following, else skip to step 10:
   1. If there are any missing components required by the Run Microsoft Word (Merge) tool, click the Install button, the follow the instructions on the screen.
   2. Click Next.

   For a detailed description of the Run Microsoft Word (Merge) tool, see About the Run Microsoft Word (Merge) Tool .

10. Click Close.

Copyright © 2018 Quadrant Software B.V. All rights reserved.