During the UNIX installation of the Software AG Directory Server, Entire Net-Work Server, and Entire Net-Work Client components of Entire Net-Work, you are prompted to indicate whether they should be installed as system services (daemons). This document describes the behavior and prerequisites for such installations. It covers the following topics:
Only a UNIX system administrator with superuser privileges can install the Entire Net-Work component services as system services using the Entire Net-Work installation procedure. If you do not have system administrator superuser privileges while performing the installation (if you enter "none" at the prompt during the installation) and you indicate during the installation that the Entire Net-Work component services should be installed as system services, the Entire Net-Work software is not installed. However, an installation script is generated that can be run by a system administrator with superuser privileges later.
If you do not want the component services autostarted, you can install the Directory Server, Entire Net-Work Server, and Entire Net-Work Client without superuser privileges. Entire Net-Work Administration Open Systems installation always requires superuser privileges.
Note:
System Management Hub (SMH) installations require superuser
privileges. So, if you are also installing SMH or the Entire Net-Work component SMH
agents, you will need to be logged in as a superuser.
The installation of Entire Net-Work component services occurs when you install the rest of the software using the UNIX installation script. During the installation, you are prompted to indicate whether the component services (daemons) should be installed as system services. If you respond that they should be, the services are installed at the system level and are automatically started upon completion of the installation. Thereafter, they will also be automatically started each time the machine on which they are installed is started. When you request that the services be installed at the system level, you are also requested to specify the run level for the service.
If you specify that the Entire Net-Work component services should not be installed as system services, the services are installed, but not at the system level. In this case, the services will never be autostarted after a machine reboot or whenever a machine is started. However, depending on the component being installed, you may be prompted to indicate whether or not the service should be started by the installation. The following table describes:
the default setting for whether Entire Net-Work component services should start up as system services
the installation and service startup behavior of Entire Net-Work component services when they are not installed as system services:
| Component Service | System Service Default Setting | Behavior when not installed as a system service |
|---|---|---|
| Directory Server | Yes (start as a system service) | The service is automatically started at the end of the installation. Thereafter, the service will need to be restarted manually each time the machine on which it is installed is started, as described in Manually Starting Entire Net-Work Services. |
| Entire Net-Work Client | No (do nt start as a system service | A prompt appears asking whether you want the service started at the end of the installation. If you respond "no", the service is not started at the end of the installation; if you respond "yes", the service is started at the end of the installation. Thereafter, the service will need to be restarted manually each time the machine on which it is installed is started, as described in Manually Starting Entire Net-Work Services. |
| Entire Net-Work Server | Yes (start as a system service) | A prompt appears asking whether you want the service started at the end of the installation. If you respond "no", the service is not started at the end of the installation; if you respond "yes", the service is started at the end of the installation. Thereafter, the service will need to be restarted manually each time the machine on which it is installed is started, as described in Manually Starting Entire Net-Work Services. |
| Entire Net-Work Administration Open Systems | Yes (start as a system service) | A prompt appears during the installation of the System Management Hub (SMH) asking whether you want the SMH services started at the end of the installation. If you respond "no", the services are not started at the end of the installation; if you respond "yes", the service is started at the end of the installation. Thereafter, the service will need to be restarted manually each time the machine on which it is installed is started, as described in Manually Starting Entire Net-Work Services. |
If the Entire Net-Work component services are not automatically started after a machine reboot or when a machine is started, you can manually start them using the following UNIX shell scripts:
| To manually start the service for: | Use this shell script: |
|---|---|
| Directory Server | adidmn.sh |
| Entire Net-Work Client | wclstart.sh |
| Entire Net-Work Server | wcpstart.sh |
For information on manually starting the System Management Hub (SMH) services, refer to your SMH documentation.
To manually stop the Entire Net-Work component services, use the following UNIX shell scripts:
| To manually stop the service for: | Use this shell script: |
|---|---|
| Directory Server | stopadi.sh |
| Entire Net-Work Client | wclstop.sh |
| Entire Net-Work Server | wcpstop.sh |
For information on manually stopping the System Management Hub (SMH) services, refer to your SMH documentation.
