Here we say TASKCTL deployment process, TASKCTL deployment can be divided into single machine deployment and online deployment deployment (cluster), said first we need to prepare something, first of all we need to official website to download the server and client installation package, and then to prepare a Windows the FTP tool and decompression tool, here we use a Linux virtual machine VMWare Player installed to as our server, create four accounts in the system (TASKCTL magent, sagent1, sagent2), is used to simulate TASKCTL cluster deployment, although each node is installed on the same server, but both installation and software implementation methods, and formal environment is the same, also can show from the side server resources TASKCTL occupies little,
Because the virtual machine is using a Red Hat Enterprise Linux 5 this release, so the download server, we choose the For Linux 4.5 this version, the desktop client, if installed in the Windows system. Net framework4.5, choose TASKCTL4.5 directly, if not, the first install. Net framework4.5, after download, unzip the service end, and then uploaded to the taskctl account, the following went into the installation of the formal process,
? Single deployment
TASKCTL standalone deployment
? Install Windows client
Windows client installation is very simple, first of all, the downloaded client package decompression, then double-click the Taskctl 4.5.1 Setup. Exe program to install, if you don't need to change directory, can all the way until the next step to complete the installation, explain Taskctl Windows client, the client is divided into three software: Admin, Designer, Monitor,
Admin TASKCTL platform is mainly used for management, such as: each node start-stop, global variables, management, import and export project, project management, and so on platform level maintenance operations,
Designer is mainly used for various processes and the design of the timer,
Monitor is TASKCTL platform monitoring operational software, is mainly used for monitoring the operation situation of operational processes and timer
To test whether our server installation is successful, we need to open the Admin client to verify,

Select the login server, and then enter the IP address and port number service node, the user name and password are the default admin, and then click login, enter the main interface
We can see already deployed nodes, can see so many nodes, because at the time of installation with built-in examples of node configuration, really only Server nodes deployed, the following, we select the Server node, and then click the stop button in the lower-right corner of the window, if prompt say "stop" success, deployment is successful then we,
? Cluster deployment
TASKCTL cluster deployment
? Load balancing
In the cluster deployment, on the basis of above can realize TASKCTL load balancing, require at least a master agent node (MAgent) and one from the proxy node (SAgent), implement is very simple, only need to design in the Designer, the task of agentid attribute is set to give priority to the name of the agent node (MAgent) plus a pair of brackets "[MAgent]", then, will handle all the tasks you need to do load balancing, respectively, on top of the master agent and from the agent, the task of environment must agree, for instance: we put a on the master agent server is called test. Sh shell script below the $HOME directory, then the test from the proxy server. Sh script also to put in $HOME directory, under the premise, TASKCTL scheduling core will judge which use a proxy server processing tasks, such as:

MainModul_rootnode & lt;/name>

MainModul_beginjob & lt;/name>


Test
[magent]

MainModul_JobNode0 & lt;/name>
$HOME/test. Sh


MainModul_JobNode1 & lt;/name>
$HOME/test. Sh


MainModul_JobNode2 & lt;/name>
$HOME/test. Sh


MainModul_JobNode3 & lt;/name>
$HOME/test. Sh


MainModul_JobNode4 & lt;/name>
$HOME/test. Sh


MainModul_JobNode5 & lt;/name>
$HOME/test. Sh



MainModul_endjob & lt;/name>

CodePudding user response:

I to take it, thank you ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~