TaskMan monitoring of sites

The Infor Framework TaskMan service must be set up to monitor each site on which users will be executing reports, stored procedures, IDO methods, executables, or other background tasks.

Entities must be monitored, since financial reports can be run on them.

During installation, a shared folder called SyteLine is set up on the server. When you enter information on the Intranets form, you must specify the path to this shared folder as the TaskMan Path. That path, which is used for all sites on the intranet, is usually set to \\server\SyteLine, where server is the server containing the shared folder.

Using the Service Configuration Manager on the server, you specify which configurations will be monitored by TaskMan on that server. Any configuration that is being monitored by the TaskMan service must also be monitored by the Event Service.

Using multiple servers

You may have more than one application and web server with identical configuration settings, pointing at the same application databases. You can configure the TaskMan service on each of the servers so that TaskMan monitors the same configurations on each server.

One server could be used as a "report server" and would contain the shared folder SyteLine. That server would be used for processing all reports, background tasks, etc. for the entire system.

You can have more than one TaskMan service instance monitoring the same application database (ActiveBGTasks_mst table). Whenever task requests come in from a site, the appropriate server’s TaskMan service would pick them up. The TaskMan services on all the servers would access the shared UNC path (specified in the TaskMan Path on the Intranets form).

When initiating TaskMan, the system calls a stored procedure to retrieve the TaskMan Path value; then all report task requests are based on that path.



As long as each TaskMan service startup account has read/write privileges for the report server shared folder (\\RptServer\SyteLine), and the TaskMan Path for each site’s intranet is pointing at the appropriate shared UNC path, the system can handle these tasks from any site:

  • Look for requested report files on the report server
  • Direct Microsoft SQL Server Reporting Services (SSRS) to generate output files in a specified output folder
  • Create error/log files on the report server