Starting the
Realm Server
Starting the Nirvana Realm server depends on the installation
operating system.
For win32 operating systems, the installer installs
a shortcut called ‘Start Nirvana Realm Server’.
Furthermore, the server command prompt can be used to
open a console window and the server can be started
by typing nserver.
Alternatively you can register the Realm as an NT service
and control operation through the service control panel.
For Linux/Solaris/Generic Unix operating systems, starting
the Realm can be done using the softlink inside the
‘Server’ directory:
[marvin@my-Channels.com]$ cd /home/my-Channels/Nirvana_3_0_0000/links/Server/Nirvana
[marvin@my-Channels.com]$ nohup Start_Nirvana_Realm_Server
&
For the personal Java installation simply click the
server link in the pjbin or the evbin, depending on
the Personal Java JRE of your choice.
At this point the server should have started and is
now ready for operation. To confirm this it is easy
to check the Realm Server log file and ensure there
are no errors being reported.
[Mon Dec 06 17:00:55 EET 2004],Log,Startup: Started
schedule entry mySchedule
[Mon Dec 06 17:00:55 EET 2004],Log,================================================
[Mon Dec 06 17:00:55 EET 2004],Log, Copyright ©
my-Channels. All rights reserved
[Mon Dec 06 17:00:55 EET 2004],Log,Start date = Mon
Dec 06 17:00:55 EET 2004
[Mon Dec 06 17:00:55 EET 2004],Log,
[Mon Dec 06 17:00:55 EET 2004],Log,Realm Server Details
:
[Mon Dec 06 17:00:55 EET 2004],Log, Realm Server name
= nirvana1
[Mon Dec 06 17:00:55 EET 2004],Log, Realm Server version
= $Name: $ - $Revision: 1.2 $
[Mon Dec 06 17:00:55 EET 2004],Log, Build Number = 0000
[Mon Dec 06 17:00:55 EET 2004],Log, Build Date = 06-Dec-2004
[Mon Dec 06 17:00:55 EET 2004],Log, Data Directory =
/home/my-Channels/Nirvana_3_0_0000/server/nirvana1/data
[Mon Dec 06 17:00:55 EET 2004],Log, Realm(s) Reloaded
= 2
[Mon Dec 06 17:00:55 EET 2004],Log, Channels Reloaded
= 14
[Mon Dec 06 17:00:55 EET 2004],Log, Queues Reloaded
= 2
[Mon Dec 06 17:00:55 EET 2004],Log, Interfaces Reloaded
= 1
[Mon Dec 06 17:00:55 EET 2004],Log,
[Mon Dec 06 17:00:55 EET 2004],Log,Operating System
Environment :
[Mon Dec 06 17:00:55 EET 2004],Log, OS Name = Windows
XP
[Mon Dec 06 17:00:55 EET 2004],Log, OS Version = 5.1
[Mon Dec 06 17:00:55 EET 2004],Log, OS Architecture
= x86
[Mon Dec 06 17:00:55 EET 2004],Log,
[Mon Dec 06 17:00:55 EET 2004],Log,Java Environment
:
[Mon Dec 06 17:00:55 EET 2004],Log, Java Vendor = Sun
Microsystems Inc.
[Mon Dec 06 17:00:55 EET 2004],Log, Java Vendor URL
= http://Java.sun.com/
[Mon Dec 06 17:00:55 EET 2004],Log, Java Version = 1.4.2_03
[Mon Dec 06 17:00:55 EET 2004],Log, Memory Allocation
= 512 MB
[Mon Dec 06 17:00:55 EET 2004],Log, Memory Warning =
435 MB
[Mon Dec 06 17:00:55 EET 2004],Log, Memory Emergency
= 481 MB
[Mon Dec 06 17:00:55 EET 2004],Log, Clock Adjustment
= 0ms
[Mon Dec 06 17:00:55 EET 2004],Log, Time Zone = Eastern
European Time
[Mon Dec 06 17:00:55 EET 2004],Log, Security Provider
0 = SUN version 1.42
[Mon Dec 06 17:00:55 EET 2004],Log, Security Provider
1 = SunJSSE version 1.42
[Mon Dec 06 17:00:55 EET 2004],Log, Security Provider
2 = SunRsaSign version 1.42
[Mon Dec 06 17:00:55 EET 2004],Log, Security Provider
3 = SunJCE version 1.42
[Mon Dec 06 17:00:55 EET 2004],Log, Security Provider
4 = SunJGSS version 1.0
[Mon Dec 06 17:00:55 EET 2004],Log,================================================
[Mon Dec 06 17:00:55 EET 2004],Log,Startup: Realm Server
Startup sequence completed
[Mon Dec 06 17:00:55 EET 2004],Log,Startup: Starting
Realm status monitoring
As the Realm Server starts up it reports the current
log level settings, currently set to 1000000 characters
and a log level of 4. The log level was set during the
installation, a level of 0 reports every action the
server does and can roll log files every minute on a
busy realm.
The Realm Server then reports the JRE environment and
the currently installed security providers. These are
important if running SSL and cause the majority of configuration
problems. After this the server then reloads all the
configuration parameters, channels and topics and then
is ready to accept connections.
If there are any problems binding to a port or creating
an SSL instance these exceptions are reported into the
Realm Server log file with as much detail as the server
can produce.
To test that the Realm Server is up and ready to accept
connections a simple test is to request information
about the realm itself. To do this you need to open
a client command prompt, and then issue the command
ngetrealms.
To open a client command prompt on a Win32 installation,
click on the Command Prompt shortcut in your Start Menu.
To open a client command prompt on a Linux/Solaris/Generic
Unix installation, open a console and source the Command
Prompt script as follows:
[marvin@my-Channels.com]$ cd /home/my-Channels/Nirvana_3_0_0000/links/Client/Nirvana
[marvin@my-Channels.com]$ . ./Command_Prompt
This will set up your environment so that you can communicate
with your Realm server. Following that, issue the ngetrealms
command:
[marvin@my-Channels.com]$ ngetrealms
Getting all known realms
Returned 1 realms
Realm Name = nirvana1
Realm Mount = / nirvana1
Protocol 0) = nsp://0.0.0.0:9000/
|
