Domain Architecture and Environment Strategy
An Infor LN domain consists of a database, application server processes, and configuration settings that together form a complete LN environment. Production organizations typically maintain multiple domains: development for building and testing changes, test/QA for user acceptance, training for user education, and production for live operations. Domain architecture decisions affect how changes flow from development to production and how issues are diagnosed.
- Maintain at minimum four domains: development, test, training, and production for proper change management
- Size non-production domains to mirror production data volumes for realistic testing of performance changes
- Configure domain-specific parameters: batch processing schedules, printer mappings, and integration endpoints
- Document the domain refresh process for restoring production data to non-production environments periodically
User and Security Administration
LN user administration involves creating user accounts, assigning roles and companies, configuring menu access, and managing password policies. LN's authorization model is role-based with company-level access control. Users can be assigned to multiple companies with different roles in each.
Effective administration requires automated provisioning processes tied to HR systems and regular access certification reviews.
- Automate user provisioning from HR systems using LN's user management APIs or batch import tools
- Assign roles at the company level, a user may need different permissions in different LN companies
- Implement single sign-on (SSO) through LDAP or SAML integration to reduce password management overhead
- Conduct quarterly access reviews certifying that each user's role assignments match their current job function
System Maintenance and Monitoring
LN domain maintenance includes database backup and recovery, application server monitoring, batch job management, and log file maintenance. Establish daily, weekly, and monthly maintenance routines. Daily: verify batch job completion and check error logs.
Weekly: review system performance metrics and disk space. Monthly: apply patches, archive old data, and verify backup recoverability through restore tests.
- Verify critical batch jobs completed successfully every morning before business operations begin
- Monitor LN application server processes for memory leaks and restart on a defined maintenance schedule
- Archive historical transaction data per your retention policy to maintain database query performance
- Test backup restoration quarterly to verify that disaster recovery procedures actually work as documented
Try it here, free
Infor LN Common Data (tcmcs) General Tables Reference
The tcmcs general tables that almost every LN session references, with key field, maintenance session, typical referencing tables and table sharing guidance.
Need help with LN domain administration? Our administrators manage 50+ LN environments, get expert support.