|
|
|
|
# razor version
The program will print out the version number, patch level, and release data of the product. File $RAZOR_HOME/VERSION contains similar information. Note that if you have any of the GUI's up, you will also see the version number in the bottom right footer of the display.1
Another common query is to discover where and how Razor is being utilized on your system. By entering the command...
# razor info
you will see a full breakdown of where the license manager is running, where the various database servers are running, against which databases, and an accounting of each Razor user.
To determine who is connected to the database...
# razor who
lists the user, the application (issues, versions, or threads), and the machine they are connected to.
And in case you forgot who you were, or were wondering if Razor really knew who you are, enter the command...
# razor whoami
In order for Tower Concepts to generate license keys for a customer site, we need to have the unique id for the machine that will be running the license manager. A simpler route is to enter the following command...
# razor id
The output of the above command is what must be sent back to license@tower.com to enable generation of license keys.
The Razor licensing information is held in the file $RAZOR_LICENSE_DIR/Licenses, which is a simple ASCII file. Although it's possible to enter the license keys directly to that file with a text editor, it's often preferable to employ the razor program for this task. By entering the command...
# razor license
...you will be prompted to enter the hostid and 4 keys which make up the license file. If there are already values in the file, they will be offered as defaults within brackets; hitting the return key will simply accept the default values.
The primary advantage of using this programmatic method for entering the keys (as opposed to doing a raw edit of the license file) is that the keys are immediately validated and deciphered, providing a full description of what your licensing status is. If there were any typing mistakes on entry, you'll know it immediately, instead of discovering the problem later as you try to invoke the license manager (razor_lm).
To view the license information, enter...
# razor license_info You have a 5 seat license Your license never expires Your service contract expires on 12/31/1999 IssueWeaver is enabled.
Your output will most likely be different, but it will describe what type of license you have, including the number of seats, when your service expires2, and any optional products enabled.
Once the Razor environment has been established for the associated database (by sourcing an rz_prep file), start the license manager as a background task. Refer back to "Modes" on page 39 for details on the operating modes of the license manager.
Once you have already properly utilized one of the rz_prep files associated with a database the following command will bring up the associated database server process.
# razor up
And, just as simply, to bring the related database server down again, use the command:
# razor down
When attempting to bring a database server down, you will be warned if there are already people actively using 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 through the Access_list file. For this and other operations that can be controlled, see "Access controls" on page 199.
|
|
|
|
|
(Part 3 of 12 for this section) (Generated 09/13/99 at 18:01:58) |
|||
|
Copyright Tower Concepts http://www.tower.com Voice: 315-363-8000 Fax: 315-363-7488 support@tower.com sales@tower.com |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |