Infor SyteLine4 min readNetray Engineering TeamUpdated March 4, 2025

How to Set Up the SyteLine Utility Server

The SyteLine utility server handles background processing tasks that would otherwise consume application server resources and degrade interactive user performance. MRP regeneration, APS scheduling, report generation, data replication, and ION document processing all run on the utility server. Proper configuration isolates heavy batch workloads from the user-facing application tier, ensuring that a 4-hour MRP run does not slow down order entry or shop floor transactions.

Installing and Configuring the Utility Server

Install the SyteLine utility server components from the Infor SyteLine installation media by selecting the Utility Server option during setup. The installer deploys the SLUtilityService Windows service and the utility server configuration files to the installation directory. Configure the utility server's database connection in SLUtilityConfig.xml to point to the same SyteLine database used by the application server. Set the service account to a dedicated domain account with SQL Server db_owner permissions on the SyteLine database and local administrator rights on the utility server machine.

Run the SyteLine installer with the Utility Server component selected and specify a dedicated installation directory separate from any application server
Configure the database connection string in SLUtilityConfig.xml with the same database server and database name as the application tier
Set the SLUtilityService Windows service to run under a dedicated domain service account with SQL Server db_owner permissions
Configure the service startup type to Automatic (Delayed Start) to ensure the utility server starts after SQL Server and network services are available

Configuring Background Job Queues and Schedules

The utility server processes jobs from the SyteLine job queue stored in the BGTaskQueue table. Configure job types and schedules through the Background Task Manager form in System Administration. Assign resource-intensive tasks like MRP, APS planning, and mass report generation exclusively to the utility server by setting the ServerType parameter to Utility in each task definition. Create separate job queues for different priority levels—Critical for MRP and APS, Normal for reports and replication, and Low for data cleanup and archive tasks.

Open Background Task Manager and assign MRP, APS, and replication tasks to the Utility server type to offload from the application tier
Schedule MRP regeneration during off-hours with a typical window of 10 PM to 6 AM to avoid impacting interactive user sessions
Configure parallel job execution by setting MaxConcurrentJobs to match 60-75% of available CPU cores on the utility server
Set up job failure notifications via email using the SMTP configuration in System Administration to alert administrators within 5 minutes

Monitoring Utility Server Health and Performance

Monitor the utility server through the Background Task History form, which logs job execution times, completion status, and error details in the BGTaskHistory table. Configure Windows Performance Monitor to track CPU utilization, memory consumption, and disk I/O on the utility server. Set alert thresholds to trigger when CPU exceeds 90% for more than 15 minutes or when available memory drops below 2 GB, indicating that job concurrency should be reduced or hardware resources increased.

Review Background Task History daily to identify failed jobs, long-running tasks exceeding their SLA, and recurring error patterns
Configure Windows Performance Monitor with counters for Processor % Processor Time, Memory Available MBytes, and Disk Queue Length
Set up automated alerts when MRP or APS jobs exceed their expected runtime by more than 50% indicating data or configuration issues
Enable SyteLine utility server logging at the Information level in SLUtilityService.config for operational visibility without excessive disk usage

Frequently Asked Questions

Can the utility server run on the same machine as the application server?

Technically yes, but this is strongly discouraged for production environments. Co-locating both servers causes resource contention—a 4-hour MRP run will consume 60-80% of CPU capacity, degrading interactive user response times by 200-400%. Deploy the utility server on a dedicated machine with at least 8 cores and 32 GB RAM. For small implementations under 25 users, co-location is acceptable if job scheduling avoids business hours.

How long does a typical MRP regeneration take on the utility server?

MRP regeneration time depends on the number of items, BOM depth, and planning horizon. A mid-size manufacturer with 10,000-25,000 active items typically sees MRP complete in 1-4 hours on a utility server with 16 cores and 64 GB RAM. SSD storage for the SQL Server tempdb reduces MRP runtime by 25-40% compared to spinning disks. Net change MRP runs processing only changed items complete in 15-45 minutes.

What happens if the utility server goes down during a job?

When the SLUtilityService stops during job execution, in-progress jobs are marked as Failed in the BGTaskQueue table with the error timestamp. Upon service restart, the utility server checks for orphaned jobs and can automatically retry them based on the RetryOnFailure setting. Configure RetryCount to 3 with a 10-minute RetryInterval for critical jobs like replication. MRP jobs should not auto-retry—investigate and resolve the root cause before manual restart.

Key Takeaways

1Installing and Configuring the Utility Server: Install the SyteLine utility server components from the Infor SyteLine installation media by selecting the Utility Server option during setup. The installer deploys the SLUtilityService Windows service and the utility server configuration files to the installation directory.
2Configuring Background Job Queues and Schedules: The utility server processes jobs from the SyteLine job queue stored in the BGTaskQueue table. Configure job types and schedules through the Background Task Manager form in System Administration.
3Monitoring Utility Server Health and Performance: Monitor the utility server through the Background Task History form, which logs job execution times, completion status, and error details in the BGTaskHistory table. Configure Windows Performance Monitor to track CPU utilization, memory consumption, and disk I/O on the utility server.

Need help optimizing your SyteLine utility server for faster MRP runs? Netray's agents can analyze your job queue configuration and recommend performance improvements.

Talk to an Expert See a Demo

Related Resources

Infor SyteLine