Cache Task Manager Usage and Configuration

I was curious if application partners were developing their own task managers for scheduling background tasks, or using the built in task schedule that is part of the Cache platform.

For those that are using the Cache task manager, what has been your method for distributing default tasks that your application needs during initial install as well as upgrades?  Are you distributing an export of the %SYS.Task object, or perhaps you are distributing an installation script that adds a task to the task scheduler when it is first run?

 

 

  • 0
  • 0
  • 939
  • 0
  • 3

Answers

We distribute a COS routine which runs after our application update is imported and does all the necessary job: checks if the TASKMGR's task already exists in schedule, and sets it up if not. Some tasks are the subject for manual setup as their settings may depend on local instance specific.

We have built our own schedulers in the main but for the odd Cache Task Manager task we have created we just export and import the subclass.

Centrestack Cloud Server (Server Agent) runs as a Windows Service in the background. Since it is a background service, it always runs regardless of the users logging into the server.he administration of the server agent is done via a Windows application – the Cloud Server Console. Most of the time, the Cloud Server Console will launch into web browser based administration console.There are two consoles, one on the web portal and service host the other one runs natively on local machine. The one on the web portal is for general administration like settings. The one runs natively is for advanced troubleshooting.