Below only for TASKCTL4.5 effectively, after the installation program, see the installation program has four options, among them, 1 and 2 is a need to know,
1, the typical installation: this option is a standalone deployment, TASKCTL be used for the first time, I am using this installation, the installation up very worry, later came to know that it will automatically put a Server node and character interface client installed, so that we can quickly experience software, at the same time, also will prompt the user to install TASKCTL produced by some examples, many technical details in the document not describe clearly, here are instructions,
2, the product is custom installation: this option is used in on line, of course, can also be used as a standalone deployment, it needs to choose their own core scheduling is to install the core scheduler or agent or client character interface, etc.,

Here explain TASKCTL Server node type: TASKCTL Server in general there are only two types of nodes, one is the core scheduler node (Server), another is the core of scheduling proxy node (Agent), among them, the service node is a must-have TASKCTL components, in a TASKCTL platform, the one and only one service node, and proxy node, which is the control node, it can be instantiated into MAgent nodes and SAgent nodes, which Server node is the scheduler control node, and the Agent is TASKCTL execution Agent node, proxy node can be multiple, but under the same account on the same Server, there can be only one service or proxy node,