| # Finish the cluster installation Post-installation steps clustering After the installation of LN on all the nodes, some additional manual actions are needed. All other configuring tasks of the cluster resources must be done with the Windows Cluster Administrator (Windows 2003) or Failover Cluster Manager (Windows 2008). Please consult the Windows documentation for more information. It is recommended to put all BSE related resources in one group and manually create the IP address and Network name resources in the same cluster group. The network name can then be used for all clients to connect to the BSE. If a Network name resource was created, then the Baan Environment resource must be made dependent on this resource. Setup a failover job daemon Install the job daemon manually (with the Infor Manager snap-in)on every node where it is needed to start the job daemon after an failover of a node. If the job daemon is not installed as a service, no job daemon will be started after failover to that node. If a job daemon was installed as a service - the baan management snap-in will install it as a manual service - the service will be started upon cluster node failover. Maintenance & Administration on cluster aware BSE The Infor Manager snap-in can only handle administration tasks if the cluster disk where the BSE is installed is owned by the current node. Stopping or starting services from snap-in is not possible. The Windows cluster administrator has precedence in managing all BSE services (Infor ES Logic Service, Shared Memory and Job daemon). The Windows cluster administrator will restart an service as soon as it is stopped. Use the Windows Cluster Administrator to manage cluster resources. If the ERP LN environment needs to be updated, the cluster disk used for that ERP LN environment must be owned to the cluster node running the Installation Wizard. Updating of an ERP LN environment on a cluster will result in down-time of that environment. |