|
|
|
|
In order to start the Razor applications, the Razor license manager and a database server must be running. The sections which follow describe how to do both. Before doing anything though, the Razor environment must be defined.
As mentioned earlier, an rz_prep and rz_prep.sh file have been created in the database directory as a result of creating a new database. You must either source or dot one of these files depending on which command shell you use.
NOTE: If RCS is selected as the archive engine for any group within a database, make sure that the user who starts the server (typically the Razor administrator) includes RCS on his search path. |
Following the example of the previous section in which the database is located in the directory /home/razoradm/razor_db/Starguide, you should do the following (remember this is only an example and names should be changed to reflect your setup).
The Razor license manager (razor_lm) is designed to run as a background task on one machine in your network as specified in your Licenses file.1
Once invoked, it runs silently, monitoring and controlling the number of Razor users on your network. Razor does not care how many databases are in use, nor does it care where or by whom2 the program is being used.
The Razor license manager must be invoked by a user account that has write privilege to the directory where the license is stored (i.e. /home/razoradm/Razor_lm/Licenses).
The license manager supports validation of the following files for remote user3 verification:
To select a mode other than the default, the license manager may be started with the desired mode parameter or the mode may be selected via the file $RAZOR_LICENSE_DIR/License.conf5.
To start the license manager using the Razor password file, enter:
To start the license manager using the local password file, enter:
Alternatively, to start the license manager using both the Razor password file and the local password file, enter:
Wait for the razor_lm to indicate "razor_lm ready to serve!" before proceeding. You only need to start the license manager one time or when the machine on which it is running is rebooted.
# razor lm_down
This command ensures that no database connections are active before terminating the license manager.
Once a database has been created and the license manager is running, you are able to invoke a database server against it. The database to be started is based on the setting of the environment parameter RAZOR_UNIVERSE_DIR. This parameter was set by sourcing (or dotting) the appropriate rz_prep file.
To start the database server, enter the following command...
# razor up
Wait for the program to indicate "rz_server ready to serve!" before proceeding. Like the license manager, the database server only needs to be started one time or whenever it is necessary to change the Attributes file6 or the machine on which the server is running is rebooted. The "razor up" command will invoke a background daemon process which will run until the machine is brought down or is terminated by the command "razor down". From this point forward, any user who has properly referenced the rz_prep file can bring up the various Razor programs.
Yes, this happens on occasion, and can prove somewhat frustrating. Here are a few tips we hope will avoid the frustrations.
If you get complaints about environment parameters not being set, go back to the beginning of the section and source the proper rz_prep file.
Also note that the rz_server program starts up another program called kid_of_server. If the rz_server is still having trouble starting, make sure that both the rz_server and kid_of_server programs are not executing. You can find this out by using the `ps' command on SunOS:
# ps -auxww | grep server
# ps -elf | grep server
and then killing the processes by specifying the process id in the `kill' command:
# kill <rz_server pid> <kid_of_server pid>
You can view server information by using the `razor info' command, which indicates the license manager mode as well as the connected processes and process id's, including the license manager. A razor info might look like:
# razor info
The license manager is running on kermit, pid = 159
Remote Clients are using Razor Password file
Connections:
------------
Database `/home/razoradm/DB/DB_PROG/RAZOR_UNIVERSE',
is active on kermit, rz_server pid = 200,
1 - herman is running Issues on machine waldorf, pid = 174
2 - herman is running Versions on machine waldorf, pid = 162
3 - bill is running Issues on machine kermit, pid = 1117
4 - bill is running Versions on machine kermit, pid = 1119
5 - ted is running Issues on machine kermit, pid = 1246
6 - ted is running Versions on machine kermit, pid = 1268
7 - ted is running Threads on machine kermit, pid = 1270
----
Database `/home/razoradm/DB/DB_CONTACTS/RAZOR_UNIVERSE',
is active on kermit, rz_server pid = 182,
1 - alice is running Issues on machine gobo, pid = 28901
2 - davis is running Issues on machine gobo, pid = 28934
There are 9 applications connected.
You can also determine the license manager process if by using the `ps' command (on SunOS):
# ps -auxww | grep razor_lm
# ps -elf | grep razor_lm
dave 159 0.0 0.1 112 160 ? S N 08:52 0:00 /home/razoradm/Razor/bin/razor_lm dave 4804 0.0 0.2 32 196 pa S 12:16 0:00 grep razor_lm
# razor down
When attempting to bring a database server down, you will be warned if there are connections to the database. If that is indeed the case, you will be given the option of abandoning or continuing with the database shutdown sequence.
You have the ability to limit who can execute the "razor down" command. The file Access_list can contain the Razor operation RAZOR_DOWN and a list of users/groups/roles that may perform that operation. See "Access controls" on page 199, for details on controlling who can do what.
Once the rz_server is running, you may start any one or all of the Razor tools. Refer to the appropriate chapters on issues, versions, and threads for specific details on how to start the tools, but in general...
# issues &
# versions &
# threads &
Although the actual implementation will vary by operating system, there are some basic approaches to take. Your System Administrator will be the best source for the proper procedure to perform an automatic Razor startup at boot time.
The best start is to create a script called start_razor and place the following lines in it. Remember to change the setting of RAZOR_PREP in our example to reflect the actual location of the rz_prep.sh file for your database. Also, the Razor database server will inherit the search path of the user that starts it, in this case, root. You may need to modify PATH to include a minimal path for the general purpose utilities that Razor uses, for example, "cp". In most cases /usr/bin on the path would be sufficient. And finally, if using RCS, you MUST update PATH to include its location.
#!/bin/sh
RAZOR_PREP=/home/razoradm/razor_dbs/rz_prep.sh
#
# If you are using RCS, set the RCS_PATH to its location
#
RCS_PATH=
if [ -f $RAZOR_PREP ]
then
#
# Be sure a minimal path is set for general purpose
# utilities,eg./usr/bin, and if using RCS, it's
# location is included in the search path.
# Check w/Sys-admin for specifics at your site.
#
if [ "$PATH" = "" ]
then
if[ "$RCS_PATH" = "" ]
then
PATH=/usr/bin
else
PATH=/usr/bin:$RCS_PATH
fi
else
if[ "$RCS_PATH" = "" ]
then
PATH=$PATH:/usr/bin
else
PATH=$PATH:/usr/bin:$RCS_PATH
fi
fi
export PATH
. $RAZOR_PREP
nohup $RAZOR_HOME/bin/razor_lm &
sleep 5
$RAZOR_HOME/bin/razor up
fi
If starting more than one database, be sure to change RAZOR_PREP to the proper database file before executing the subsequent "razor up" command. Make sure this script is readable and executable, by setting the proper permissions for the script as follows:
# chmod a+rx start_razor
At boot time, this script will be executed by root. That may or may not be desirable, as it means that your Razor License Manager process will be owned by root. Possibly not a problem, but you'll have to be root to stop the process. To avoid this situation, you may want to run this script su'd as the owner of the database. You could do this by executing the script from the initialization file as,
# su <owner_of_db> -c "/<path_to_script>/start_razor"
Your System Administrator is the best source of information on what is appropriate for your operating system.
|
|
|
|
|
(Part 8 of 12 for this section) (Generated 09/13/99 at 17:37:48) |
|||
|
Copyright Tower Concepts http://www.tower.com Voice: 315-363-8000 Fax: 315-363-7488 support@tower.com sales@tower.com |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |