Starting the Realm Server
This section describes how to
start the Universal Messaging realm server by using the command prompt of your operating system or by using operating system shortcuts. For similar instructions on how to
stop the realm server, see the section
Stopping the Realm Server.
Note:
Starting and stopping the realm server is also possible using the Command Central interface. Refer to the appropriate section of the Administration Guide for information.
Automatic startup of the realm server
If you selected the option to install the realm server as a service (on Windows) or a daemon (on UNIX-based systems) while you were installing the Universal Messaging product, the service/daemon will start automatically every time you boot your machine.
If you stop the service/daemon and wish to restart it without rebooting your machine, run the nserver.bat command (on Windows) or the nserver script (on UNIX-based systems). This command/script is located in the bin directory of your selected realm server.
Manual startup of the realm server
If you did not select the installation option to create the realm server as a service/daemon, you need to start the realm server manually.
Starting the realm server manually on Windows
There are several ways to start a realm server:
Method 1: For Windows operating systems, the installation procedure for Universal Messaging installs a Start Menu entry called
Start Servers > Start Universal Messaging Realm Server > Start <InstanceName> under the Universal Messaging entry, where
<InstanceName> is the name of the realm server. When you select this shortcut, the realm server starts up.
Method 2: You can open a console prompt by selecting the Start Menu entry
Tools > Universal Messaging Clients > <InstanceName> > Realm Server Command Prompt. This opens a console prompt at the
bin directory of your selected realm server. At the prompt, type
nserver, and the realm server will start up.
Starting the realm server manually on UNIX-based systems
For UNIX-based operating systems, you can start the realm by running the nserver script in the bin directory of your selected realm server.
Avoiding server stop on user logoff
If the realm server is not configured as a daemon, nserver will start the realm server in console mode, which will cause the realm server to stop when the user who started it logs off.
This server stop resulting from a user logoff can be avoided by using the nohup command to start the realm server:
nohup ./<InstallDir>/UniversalMessaging/server/<InstanceName>/bin/nserver &
Forcing console mode startup
You can force the realm server to run in a console even if you installed it as a service/daemon. To do this, open a console prompt, change your working directory to the <InstanceName>/bin directory, and use the following command:
nserverdaemon -c
Behavior of the realm server during startup
To check that the realm server has started properly, examine the realm server log file nirvana.log in the location <InstallDir>\UniversalMessaging\server\<InstanceName>\data, where <InstallDir> is the disk root location of your Universal Messaging installation, and ensure there are no errors being reported. Also check the log file for a completion message such as the following:
[Tue Apr 24 10:59:22.374 CEST 2018] ... - Startup: Realm Server Startup sequence completed
For more information about the contents of the log file, refer to the section
Universal Messaging Enterprise Manager : Logs Panel in the
Administration Guide.
Switching between Automatic startup and Manual startup
If you installed the realm server to start manually, but would now prefer it to start automatically as a service/daemon, you can register the realm server as a service/daemon. To do this, proceed as follows:
Changing from manual to automatic startup:
Windows: Ensure that you are a user with Administration rights, then run the command
registerService.bat located in the directory
<InstallDir>\UniversalMessaging\server\<InstanceName>\bin.
UNIX: Ensure that you are a user with sudo rights, then use the centralized
daemon.sh script:
<InstallDir>/common/bin/daemon.sh -f <Path>/nserverdaemon
where <Path> is <InstallDir>/UniversalMessaging/server/<InstanceName>/bin.
Changing from automatic to manual startup:
If you installed the realm server to start automatically as a service/daemon, but you want to change this setup so that you start the realm server manually, you can deregister the realm server as a service/daemon. To do this, proceed as follows:
Windows: Ensure that you are a user with Administration rights, then run the command
unregisterService.bat located in same directory as the
registerService.bat command.
UNIX: Ensure that you are a user with sudo rights, then use the centralized
daemon.sh script:
<InstallDir>/common/bin/daemon.sh -d <Path> -R
where <Path> is <InstallDir>/UniversalMessaging/server/<InstanceName>/bin.
Getting the current status of the realm service/daemon
To display the current status of the service/daemon of the realm server, proceed as follows:
Windows: Enter the following command at the command prompt:
<InstallDir>\UniversalMessaging\server\<InstanceName>\bin\nserverdaemon -q
Note:
The command requires administrator rights and needs to be run from a console that has administrator rights.
UNIX: To check if the realm server is installed as a daemon, enter the following command at the command prompt.
<InstallDir>/common/bin/daemon.sh -d <Path> -l
where <InstallDir> and <Path> are as defined above. You do not require sudo rights to run this command.