Table of Contents
- 1 Introduction
- 2 Installation of a distributed deployment
- 3 Installation of a standalone deployment
- 4 Planning an installation
- 5 Considerations when planning an installation
- 6 Ready to install and configure
- 7 A quick tour of the configurator
- 8 Installation: In summary
TaskCentre is usually deployed across enterprise networks, so it’s important to plan the environment and resources carefully before attempting an installation. You prepare by checking system requirements, registering an account, obtaining a license key and downloading the product.
An InstallShield Wizard allows you to select the components to install. In addition to the server itself, you install a client and various other components according to your needs. You configure installed components using a special tool, the Configurator. It identifies pre-requisites for each installed feature to function properly.
A standalone installation, with only slightly reduced functionality, can be done for certain purposes, such as demonstrating the product on a single machine.
Installation of a distributed deployment
Installing the TaskCentre Server
For a standard distributed installation, a new installation of TaskCentre always starts with the server itself. Among the other components you select for installation, you will also install the client feature, either on the same machine as the server or on a dedicated workstation.
Configuration of the server entails setting up a data store and a couple of other important settings required before the TaskCentre Server service can be started.
Installation and configuration of the server are examined in detail in the knowledge base article Installing and Configuring the TaskCentre Server.
Installing the Email Trigger (SMTP) Agent
In the example described here, one of the features, the Email Trigger (SMTP) Agent, is installed on the TaskCentre server machine. This is done because the agent cannot be installed directly on a mail server. Instead, it relies on support from the Microsoft SMTP Virtual Server, which runs on Microsoft Internet Information Services (IIS).
Details about configuring the Email Trigger (SMTP) Agent arecovered in the followingknowledge base article Installing and Configuring the Email Trigger (SMTP) Agent.
Installing the Microsoft SQL Server Trigger Agent
Another important feature that needs to be installed is the Microsoft SQL Server Trigger Agent.
The purpose of this component is to monitor data in your business system. The business system stores its data on a SQL Server machine. The SQL Server Trigger Agent gets installed on this machine.
This part of the distributed installation is covered in detail in the knowledge base article Installing and Configuring the Microsoft SQL Server Trigger Agent.
Installing the workflow components
If selected, the workflow components – Web Service, myTaskCentre and Workflow Agent – will be installed on a dedicated server and will need to be configured.
Installation of these components is covered in detail in the knowledge base article Installing the Workflow Components.
The server installation includes a number of tools. Some of these will need to be configured. These include Run Crystal Report and Run Microsoft Word (Merge).
There are also sets of tools, which are not installed as part of the initial product installation. These are made available as tool packs with their own installer. They can be integrated into TaskCentre at any stage.
The knowledge base article Installing Tool Packs examines the installation of tool packs.
Installation of a standalone deployment
Installing a demonstration system
There are times when you may need to install TaskCentre on a single, standalone machine, instead of the standard distributed deployment across a network.
For instance, you may want to set up a single machine that you can use to demonstrate TaskCentre functionality to a prospective customer. Although there may be limitations in not being connected to a network, there are ways of keeping these to a minimum.
Installation and configuration of the product on a standalone machine are covered in the knowledge base article Creating a Demonstration System.
Preparing to install the product
There are certain preparations you need to make before you can install the product.
- Have you registered with Codeless Platforms?
- Have you downloaded the correct version of TaskCentre?
- Do have all the required hardware and software?
- Have you obtained a license key?
Let’s take a look at these preparations in more detail.
Step 1 – Register on the Codeless Platforms web site
First, you need to register. You do this by creating a personal account on the partner portal of the Codeless Platforms web site. This allows you access to resources, including downloads, product updates and marketing information.
Follow this link to register: Community > Partner Area
Once you have filled in and submitted the form, you will receive an email confirming your registration. It is important to use your company’s email address, because its domain name is used to authenticate your registration.
Step 2 – Check system requirements
There are two important sources of up-to-date information about system requirements:
The Software Compatibility Document – for information about dependencies between the TaskCentre release and the surrounding system and application software
The product Release Notes – for installation instructions for the particular release of TaskCentre
You can download these documents – as well as TaskCentre product itself – from the Partner Area page of the Orbis Software web site.
Before performing a new installation, you will be sent a link to the product download page and a license key.
There are two types of keys:
Product key- This activates the product. It is entered during the installation of the product.
Tool license key (QSL file) – After installing the product, the tools commence a 30-day evaluation period. Importing the QSL file permanently activates the tooling.
The only licensing thereafter is the annual renewal of the product key and any new tooling that may be introduced.
Planning an installation
Before you begin the actual installation, you should plan your environment and resources carefully.
Let’s take a look at some of the points to consider.
Considerations when planning an installation
When planning an installation of TaskCentre, there are a number of checks and preparatory tasks to carry out.
There are also questions to consider about authentication. You can read about the limitations of the default local system account.
- Does the server meet the hardware and software prerequisites?
- Is it in the right locale?
- Would a reboot of this server be disruptive to users?
- Do I have sufficient rights to install software on that server?
- What components need to be installed to meet my objectives?
- Are there any firewall or anti-virus implications to consider?
- What is the daily operational load on this server likely to be?
- Which workstations require the client component to be installed?
Agents and other components
- Which machines require distributed agents or components to be installed?
- Is the installation likely to cause and disruption?
- Are there any firewall or anti-virus implications to consider?
Authentication – default account
The TaskCentre Server service by default runs under the local system account. This account has certain limitations.
The local system account may have adequate rights to perform the output operations required in your tasks. However, those output operations may need to communicate with servers in different domains.
You may, for example, be trying to save a file to a different domain. Or you may need to print to a printer that is not accessible through the local system account. Or you may wish to control read/write access to a SQL table created specifically for TaskCentre server usage.
There are many cases where it would prove better to create a windows account for use by the TaskCentre server, to provide a finer level of control than the local account.
Authentication – questions
- Have I got details of the TaskCentre windows account?
- Does that account have a mailbox I can use for replies?
- Do I require email relay and authentication to be setup and should authenticate this with the TaskCentre account?
- Does the TaskCentre account have ownership of any bespoke SQL tables used to store operational data?
- Do I have a read-only account with sufficient rights to read the necessary databases?
- Does the TaskCentre account have rights to save files anywhere on the network?
- Does this account have rights to print to any network printer that may be required?
- Does this account have rights to access any FTP servers that may be required
Ready to install and configure
You’ve planned your installation carefully, registered on the Orbis Software web site, downloaded the product, obtained the license key and read all the essential information.
Now let’s take a brief look at the installation and configuration tools.
An InstallShield Wizard provides a simple interface for the installation and requires very little user input. The user has to;
- Select the features to install
- Enter the license key
- Accept the license terms
The installer prompts with default destinations for;
- The programme files
- The temporary files
The user can accept these defaults or change them to a preferred destination. On finishing the installation, the installer will open the Configurator by default, with an option to deselect this.
A quick tour of the configurator
Click here to view a quick video tour of the configurator. \\ Video needs uploading to WordPress. DO NOT use flash –>
Installation: In summary
TaskCentre is usually deployed across enterprise networks. The resources and environment for a deployment therefore need careful planning. Prior to installation, you should register an account, check the system requirements, download the product and obtain a license key.
You use an InstallShield Wizard to install the product, selecting those components you wish to install. In addition to the server itself, you can install the client feature, the SMTP Agent, the SQL Server Trigger Agent, workflow components and certain tools. Installation of other tool packs can be carried out at a later time.
For certain purposes, such as demonstrating the product from a single machine, you can carry out a standalone installation.
Configuration is made simple with a tool called the Configurator, which identifies the conditions for each installed feature to function correctly and provides the means to modify these settings.