| # Enterprise Server Service Manager Introduction You can manage LN on your Windows server by means of an Infor Enterprise Server Service Manager snap-in for the Microsoft Management Console (MMC). You can use the Infor ES Service Manager snap-in to do the following: View all LN environments. View the status of the LN-specific services for each LN environment. Add, change, or remove LN-environment-specific variables. Install, start, and stop LN-specific services. Edit the settings of the LN-specific services. This chapter includes the following: An overview of the ES Service Manager snap-in The LN management procedures Overview of the Enterprise Server Service Manager snap-in The Enterprise Server Service Manager snap-in for the Microsoft Management Console (MMC) enables you to manage LN Software Environments (BSE) on your system. The ES Service Manager snap-in installs automatically on the LN server during the installation of LN. The ES Service Manager lists the LN environments (BSEs) on your system. You can independently administer the displayed BSEs. The ES Service Manager does the following: Displays the ES Logic Service for every LN installation. You can use the ES Service Manager to enable or disable the Logic Service for each LN installation. Displays the Shared Memory Service for every BSE. You can use the ES Service Manager to enable or disable the Shared Memory Service for each BSE. ES Logic Service Use the ES Logic Service to configure the LN connection protocols. The ES Logic Service connects the LN Web UI client to the LN server and checks whether the user has the authorization to connect to the LN server. With the ES Logic Service, you can start/stop the LN Virtual machine (VM) and the database driver. The ES Logic Service offers you the following methods to connect to the LN server: Rexec The standard remote execution protocol. Rexec does not use passwords encryption. BaanLogin Encrypts the password of the users. Federation Services Provides central authentication and authorization for multiple applications. Federation Services makes single-sign-on (SSO) available for LN. This method is also used if single-sign-on is achieved through Integrated Windows Authentication. Security Support Provider Interface (SSPI) Only available on Windows and later. Single-sign-on (SSO) is a mechanism with which a single action of user authentication and authorization can permit a user access to all computers and systems on which the user has access permission, without the need to enter multiple passwords. SSO does not use passwords, but uses the Windows user authentication. With SSO, users are no longer required to perform multiple logons, nor must users remember multiple passwords to access network resources. The user logs on once on Windows and no further passwords are required. All SSO-specific information is stored in a single repository, the Active Directory, which provides a single, authoritative listing of each user’s rights and privileges. You can change a user’s privileges and the results will be distributed network wide. If the SSPI protocol is used for authentication, the Infor ES Logic service must run on a system, which has sufficient rights to authenticate identities of incoming user requests, using/accessing the Active Directory Server for the Windows Domain the Infor LN server is member of. If that system cannot authenticate the user identity, the user logon is denied. Contact your local Windows administrator regarding trusts and authentication settings of the Infor LN system and the Active Directory Server/Domain controller(s). Such relationship(s) must exist before (domain) users can be validated. See the Infor Enterprise Server Single Sign On User Guide (U9559 US). Shared Memory Service With the Shared Memory Service, you can configure LN ’s shared memory. The shared memory is a part of the physical memory intended for common use. Programs communicate with each other with shared memory. The use of shared memory results in faster access to the components loaded in shared memory. Before you start the application, you must initialize and set up the shared memory. The following components can be loaded into shared memory: Report objects Program objects Table definitions LN management procedures The ES Service Manager provides the tools to manage and administer LN on your system. With the ES Service Manager, you can: Start or stop an LN Software Environment (BSE). Enable, disable, start, or stop the Shared Memory Service of the current BSE environment. Configure the ES Logic Service. Enable, disable, start, or stop the ES Logic Service for a system’s LN environments. Configure the shared memory parameters. Rename BSE environments. Edit the BSE variables. Note For ERP releases prior to Infor Baan 5.2a, you can also use the Infor ES Service Manager to enable, disable, start, or stop the following: The Job Daemon service by ERP installation For porting sets prior to 7.1d.12: the ERP Licensing Service by BSE. From porting set 7.1d.12 licensing is managed externally by the Infor Solution License Manager (SLM). These options are not available for newer releases. For Infor Baan 5.2a and later, the following applies: The Solution License Manager (SLM) manages licensing externally. For porting sets prior to 8.3a the Application Services Manager (ASM) manages the Job Daemon service externally. From porting set 8.3 a you can choose whether you want to use ASM or the Job Daemon Service. Important! Optionally, you can start, stop and disable services via the Windows Service Manager, or via the -start, -stop, and -remove command line options. However, to enable a service you must use the ES Service Manager snap-in. You cannot enable services via the Windows Service Manager or via the -install command line option. It is recommended to perform all actions via the ES Service Manager snap-in. To start an LN software environment (BSE) The following procedure describes how to start or stop an LN software environment (BSE): Start the ES Service Manager from the Microsoft Windows Start menu. In the Tree pane of the ES Service Manager, expand the LN server node that contains the software environment. Select the LN software environment (BSE) you want to start and, on the toolbar, click the Start Service button. The BSE is now running. To configure the ES Logic Service To configure the ES Logic Service of an LN Software Environment (BSE), take the following steps: Start the ES Service Manager. Start the ES Logic Service Properties dialog box. Enter or modify the Service Properties Save the Service Properties changes Restart the Logic Service Restart the Shared Memory Service. To configure the Shared Memory Service To configure the Shared Memory Service of an LN Software Environment (BSE), take the following steps: Start the ES Service Manager. Select the LN Software Environment (BSE) for which you want to configure the shared memory. Start the Shared Memory Properties dialog. Enter or modify the shared memory properties. Save the changed shared memory properties. Restart the Shared Memory Service. Note The Loaded Shared Memory tab shows the loaded shared memory objects. The Shared Memory Areas tab shows a list of the available shared memory areas and their addresses. To rename BSE environments You must make sure that the BSE environments on your system are unique. You can, therefore, rename environments if required. To rename a BSE environment, take the following steps: Start the ES Service Manager. Rename a selected BSE environment. To edit the software environment variables You can use the Enterprise Server Service Manager to edit the software environment variables to change the behavior of the Enterprise Server. To edit the software environment variables, take the following steps: Start the ES Service Manager. Start BSE Properties dialog Enter the variable name, for example, BSE_SORT. Enter the value of the variable, for example, for the BSE_SORT variable, enter the path to the directory where the temporary data must be stored during the sort process. Save the new variable. |