| # Setup of the guide The remainder of this document contains the following chapters: The system administrator’s tasks This chapter describes the tasks and responsibilities of the system administrator, for example to assign user accounts and passwords, establish security access levels, allocate storage space, and watch for unauthorized access. License management and validation You can use a license management mechanism to regulate the commercial use of LN. The license management mechanism is in fact a copy protection mechanism. The unprotected software must be validated and patched before a specified expiration date. After installation, the core LN application can run for 30 days without a license mechanism. However, integrations will not work. Users can request a temporary key for demo and trial versions. This key is valid for 14 days. The temporary license is mainly introduced to overcome delays in delivery of permanent license keys. For testing and demonstration purposes, unprotected software is dispatched with limited validity. This chapter describes the license management mechanism and the validation procedure. System recovery If a serious error occurs, and the system cannot be rebooted, you must restore LN from a back-up file saved on a separate system. The procedure to follow after a serious crash is referred to as the hard-crash procedure. This chapter describes the steps required to carry out the hard-crash recovery procedures for both UNIX and Windows. Version and release management You must manage the various versions of LN packages, their corresponding releases, and the various customizations. LN offers a comprehensive solution with the version and release management mechanism. Within this concept, multiple versions of an application can run simultaneously in the same LN environment. This chapter describes the concept of version and release management and the procedures to create a software environment. User management The LN administrator uses LN ’s User Management to enable users to work with LN and to give these users authorizations related to their role. This chapter describes the following procedures: How to create a user account The Authorization Management System (AMS) Note If the licensing of LN is based on named users, the LN user accounts that are created in User Management must correspond with the user names in the named user list in the Infor Solution License Manager (SLM). Audit Configuration Management This chapter provides an overview of the steps you must take to configure the audit settings. According to this configuration the audit trails are created. The audit configuration is based on audit profiles. In an audit profile, you define which tables and fields are audited, and when the table and fields are audited. The audit trail is stored in sequence files, which are generated for each combination of company and table. The chapter also describes the procedures for various other Audit Management features, such as how to import and export profiles, generate reports, and migrate from an earlier version of Infor Enterprise Server. Note Several important parameter tables must be audited mandatory. The audit history data of those tables will be used by Infor Support. RDBMS Administration LN supports several relational databases (RDBMSs) for which you can authorize the LN user. An LN user must be able to use the information that is stored in the RDBMS. Before the LN user can access a database, you must provide the LN user permission to access the RDBMS. This chapter describes how to give LN users access to an RDBMS and how to optimize the database table and index repository for an improved interaction between LN and the database. Device management One of LN ’s most important tasks is to generate output. Raw data is fed into LN and processed into reports, sales invoices, salary check, and so on. Before you can print the data that is processed by LN, you must first make sure that your operating system supports the printers in your company. You can print LN reports on various types of devices, for example, output files and printers. This chapter describes how to set up printers for LN and the related sessions. Note Infor also supports the use of external reporting tools, an example is Cognos. Text management You can use text for various purposes in LN. You can, for example, use text to provide information about LN itself, for example, technical documentation and release notes for software components. You can also use text to provide information on the data stored in the tables of the database: For example, a text that is linked to a certain record can contain information about an item or sales order pertains to that record. The text editor enables you to write queries. This chapter describes the following procedures in regard to text management: The text parameters procedure, which defines the basic parameters for the use of text The text maintenance procedure Job management You can use LN ’s job management to schedule jobs at non-peak hours to improve the overall system performance in a heavily loaded environment. You can schedule the jobs to start processes periodically, at a defined interval, or immediately. Typically, you use LN management for print and processing sessions. Infor Enterprise Server Service Manager The Infor ES Service Manager snap-in for the MMC provides the tools to manage the LN Software Environments (BSE) on your system through Microsoft’s Management Console (MMC). You can use the Infor ES Service Manager snap-in to administer LN systems on your Windows server. With the Infor ES Service Manager snap-in you can: View all LN environments. View the status of the LN-specific services for each LN environment. Add, change, or remove LN environment-specific services for each LN-specific environment. Install, start, and stop LN-specific services. Edit the settings of the LN-specific services. This chapter describes the Infor ES Service Manager procedures. |