How to Configure the SyteLine Application Server
The SyteLine application server is the central processing layer that handles IDO requests, form rendering, business logic execution, and database communication. Proper configuration of IIS application pools, IDO runtime settings, and connection pooling directly impacts system responsiveness and concurrent user capacity. This guide covers initial server setup, performance tuning parameters, and monitoring configurations for production-grade SyteLine application server deployments.
IIS Application Pool and Web Site Configuration
SyteLine's application server runs as an IIS web application with dedicated application pools for the IDO runtime and the web client. Open IIS Manager and configure the SyteLine application pool to use .NET CLR version 4.0 with Integrated Pipeline mode. Set the application pool identity to a dedicated service account with SQL Server access to the SyteLine database. Configure idle timeout to 0 (disabled) and recycling intervals to every 24 hours during a maintenance window to prevent session drops during business hours.
- Set the SyteLine application pool to .NET CLR v4.0 Integrated Pipeline mode with a dedicated service account identity
- Disable idle timeout by setting it to 0 minutes to prevent the application pool from shutting down during low-activity periods
- Configure regular recycling to occur at 2:00 AM daily to clear memory leaks without impacting business-hour operations
- Set the maximum worker processes to 1 for the IDO runtime pool to prevent IDO cache inconsistency across multiple processes
IDO Runtime and Connection Configuration
The IDO runtime configuration is managed through the SyteLine Configuration Manager (SLConfigMgr.exe) located in the SyteLine server installation directory. Configure the database connection string, IDO cache settings, and session timeout values. Set the IDOCacheTimeout to 3600 seconds for optimal performance with metadata caching, and configure MaxConcurrentSessions based on your licensed user count plus a 20% buffer. The connection pool size in the SQL Server connection string should be set to 2x the expected concurrent user count with a minimum of 50 connections.
- Run SLConfigMgr.exe to set the database connection string with Pooling=true, Min Pool Size=50, Max Pool Size=200 parameters
- Configure IDOCacheTimeout to 3600 seconds to cache IDO metadata and reduce database round trips by 40-60% per session
- Set MaxConcurrentSessions to your licensed user count plus 20% buffer to accommodate peak usage without session rejections
- Enable IDO request logging at the Warning level in the SLRuntime.config file for production troubleshooting without excessive I/O
Load Balancing and High Availability
For environments with 100+ concurrent users, deploy multiple SyteLine application servers behind a load balancer. Configure sticky sessions (session affinity) on the load balancer to ensure each user's requests route to the same application server for the duration of their session. Use Windows Network Load Balancing (NLB) or a hardware load balancer like F5 with health check probes targeting the SyteLine health endpoint. Each application server node should have identical SLRuntime.config settings and connect to the same SQL Server database instance or Always On Availability Group.
- Deploy 2+ application server nodes behind a load balancer with sticky session affinity for consistent user routing
- Configure health check probes to poll the SyteLine /health endpoint every 30 seconds with a 3-failure removal threshold
- Synchronize SLRuntime.config and web.config files across all nodes using a configuration management tool or shared network path
- Use SQL Server Always On Availability Groups for the database tier to eliminate single-point-of-failure at the data layer
Frequently Asked Questions
How many concurrent users can a single SyteLine application server handle?
A properly configured SyteLine application server on a 16-core, 64 GB RAM server can handle 75-150 concurrent users depending on transaction complexity. Heavy IDO operations like MRP processing or complex report generation reduce capacity. Monitor CPU utilization and keep it below 70% average to maintain sub-3-second form load times. Add a second application server node when average CPU consistently exceeds 65%.
What is the recommended server hardware for a SyteLine application server?
For 50-100 concurrent users, provision a server with 8+ CPU cores, 32 GB RAM, and SSD storage for the SyteLine installation directory. For 100-200 users, scale to 16 cores and 64 GB RAM. The application server is CPU-bound during IDO processing and memory-bound during form rendering, so prioritize clock speed over core count for single-server deployments. Always use a dedicated server—avoid co-hosting with SQL Server.
How do I restart the SyteLine application server without disconnecting users?
Use the IIS application pool recycling feature instead of a full server restart. In IIS Manager, right-click the SyteLine application pool and select Recycle. This creates a new worker process and gracefully drains the old one over 90 seconds by default. Active users may experience a brief 2-5 second delay during the transition but will not lose their session data. Schedule recycling during low-usage periods for minimal impact.
Key Takeaways
- 1IIS Application Pool and Web Site Configuration: SyteLine's application server runs as an IIS web application with dedicated application pools for the IDO runtime and the web client. Open IIS Manager and configure the SyteLine application pool to use .NET CLR version 4.0 with Integrated Pipeline mode.
- 2IDO Runtime and Connection Configuration: The IDO runtime configuration is managed through the SyteLine Configuration Manager (SLConfigMgr.exe) located in the SyteLine server installation directory. Configure the database connection string, IDO cache settings, and session timeout values.
- 3Load Balancing and High Availability: For environments with 100+ concurrent users, deploy multiple SyteLine application servers behind a load balancer. Configure sticky sessions (session affinity) on the load balancer to ensure each user's requests route to the same application server for the duration of their session.
Need expert help tuning your SyteLine application server? Netray's infrastructure agents can analyze your configuration and recommend optimizations for your user load.
Related Resources
How to Set Up the SyteLine Utility Server
Configure the Infor SyteLine utility server for background job processing including MRP, replication, report generation, and scheduled task execution.
Infor SyteLineHow to Configure Performance Monitoring in SyteLine
Set up performance monitoring for Infor SyteLine including IDO request tracing, SQL query analysis, application server metrics, and user experience monitoring.
Infor SyteLineHow to Configure Session Management in SyteLine
Configure SyteLine session management including timeout policies, concurrent session limits, license optimization, and session monitoring for Infor CloudSuite Industrial.