- Contact information (e-mail address, phone number, and customer ID).
- A clear description of the problem and what you were doing when it happened.
- The version of Razor.
- Server OS AND Client OS (including version number of the OS). For example, instead of stating Solaris, we need the specific Solaris version (e.g. Solaris 7).
- Any other information that might be applicable.
- All error logs and outputs.
All support requests are sent to razor_support@visiblesystemscorp.com
[ top ]
Razor's tool suite consists of Issues, Versions, and Threads. Their functions are as follows:
Issues: The Issues program is the problem tracking part of the Razor tool suite. It provides a very intuitive and powerful interface to a configurable database. Although its most frequent implementation is a problem tracking system, it can actually be configured to satisfy all sorts of needs, such as managing customer contacts, managing help desk operations, etc.
Versions: Versions provides a straightforward mechanism for controlling, monitoring, and archiving changes made to files in your development environment.
Using Issues in conjunction with Versions enables users to track problems through code/document solutions.
Threads: The Threads program provides a mechanism for defining which unique combination of files (defined by file name and version number) "belong together" for the purpose of a product build or release.
Threads may be managed using Issues thus providing the ability to create or update a thread with a selected set of problem resolutions.
The combined use of Issues, Versions and Threads provides a powerful Configuration Management System.
[ top ]
IssueWeaver™ is a tool that allows users to access the Issues portion of the Razor Database via the Internet or an Intranet. With IssueWeaver™, members of your project team can read, search, write, and update project issues from any location. You can manipulate issues from any platform that can support a web browser.
[ top ]
You can introduce any type of file into Razor, including graphics. The only limitation is the amount of storage available on your server machine. Files are introduced into Razor through the Versions tool.
[ top ]
SCCS errors can be seen a few lines above the "****- 'EXITED - 1"' error in the Razor Error Output Log:
1. (de18)
"No new line at end of file ..."
The last line in the file does not end with a new line. It is illegal to input such data to the history file created earlier as a text SCCS file.
This requirement is imposed by SCCS.
Answer: Edit the file and insure it ends with a "line-feed" character. Then attempt to check it back in.
2. (ad19)
"file ... exists"
You are trying to create the named SCCS file, but it already exists.
Answer: A file already exists with that name.
3. (Line too long)
The "line too long" error is an SCCS error. Unfortunately, SCCS has a limit on line length (our engineers advise us that the limit is 512 characters) and requires an new-line at the end of the file.
Answer: You will have to go back to file and edit that line to make it shorter or possibly add a new-line or <CR> to the end of the file.
4. (ut10)
"no space!"
The file system on which the file which caused the error is being written is out of space. Very serious!! Contact someone in your local UNIX Support Group immediately!
Answer: The drive is out of space. Please see your system administrator for resolution.
[ top ]
Please note that items in brackets [ ] are optional. Items in < > should be replaced by specific names (i.e. file name, folder, group, etc.).
To Delete Files: razor -c rm -f <file> -g <group> [-i <issue[<:issue group>]>]
Deleting files with the Razor rm command does not destroy existing threads that reference those files. However, using a UNIX rm command will destroy existing threads permanently. Never use UNIX commands on Razor data.
To Delete Folders: razor -c rm_folder -f <folder> -g <group> [-i <issue[<:issue group>]>]
To Delete Threads: razor -c rm -f <thread name> -g <group>##Threads
The named files/threads are not actually being deleted from the file system. Instead, they are simply being hidden. This is done as a safety measure and allows your Razor Administrator to actually retrieve a thread later if need be.
To Delete Issues: razor -c rm_issue -f <issue[<:issue group>]> [-g <issuegroup>]
Rather than delete issues outright, some sites prefer to keep them around for quite some time. To prevent old issues from cluttering up displays, some folks add an "Obsolete" check box to the issue form and then just filter out the ones they don't have a pressing need to see. This approach also makes future deletion more orderly; you can filter to see only the Obsolete issues, sort them by date of last modification, and draw up your hit list.
[ top ]
razor -c rm_folder -f <folder/folder/folder/...> -g <group> [-i <issue[<:issue group>]>]
[ top ]
Scripts can only be run from UNIX clients, UNIX servers, and PC servers. PC clients cannot run scripts because they are considered remote clients. If you are a UNIX client and you use the "-remote" flag to access Razor's tools, you are considered remote. At this time, remote clients do not have the ability to run scripts locally.
[ top ]
- As the UID razoradm, from the machine that is running the razor license manager and database server process, source the rz_prep file for the razor database you are concerned with. After having done that, please send us the output from the following commands:
razor info
(the above command communicates to the razor license manager)
razor who
(this command communicates with the razor database server)
- If the above commands state that the razor license manager and razor database server are up, try to bring the server up in debug mode again: rz_server -debug and send us the output.
- Please send us the output from the following command:
cat $RAZOR_UNIVERSE_DIR/Server_status
- Please send us the output from the following command:
cat $RAZOR_LICENSE_DIR/License_status
- If the above 4 steps work as the user razoradm, please perform them as another user and send the output to support as well.
Additionally...
- With the database and lm down, please check for rogue license manager and database server processes.
# ps -elf | grep lm
# ps -elf | grep rz_server
You should not see any processes running. If you do, please kill them with a " kill -9 PID ."
Now try to restart the lm.
- Please send your Server platform, client platforms, and version of Razor you are running to razor_support@visiblesystemscorp.com .
[ top ]
Here's a snippet from a no lock set error. Your error log should be similar to this:
/export/home0/razoradm/db/makodexter/RAZOR_UNIVERSE/DOMAIN_01/DX3K-1_main /Archive/RZ_VCS/top_level/source/mnf/qe_chips/quadenet.c,v: no lock set by razusr for revision 1.4 + /usr/bin/rm -f /tmp/RZTMP_RAZORDB.2447/rz_vcs.18041 + exit 1 ****- 'EXITED - 1'
Notice that the error refers to a specific user (razusr). Please keep in mind that the UID in your error message will be unique.
1. Does the Versions GUI say that the file is still checked out by razusr?
2. Does the Info file indicate with a "1" that the file is checked out?
3. Does the Info file specify razusr as the owner?
Is razusr a username unique to only one person or do many people log on as razusr? If razusr is a UID that many people use, it might be the case that too many changes are taking place at the same time by the "single" user and Razor hiccups.
What do your Info, History, and Archive files have to say about all of this? Are they in agreement about the latest version number of quadenet.c,v? If not, you're going to need to edit them. Please send the 3 complete files to razor_support@visiblesystemscorp.com .
You can find the Info, History, and Archive files in the following locations:
Info-
$RAZOR_UNIVERSE/DOMAIN_01/<version_group>/Info
Archive-
If using SCCS:
$RAZOR_UNIVERSE/DOMAIN_01/<version_group>/Archive/SCCS
If using RCS:
$RAZOR_UNIVERSE/DOMAIN_01/<version_group>/Archive/RZ_VCS
History-
$RAZOR_UNIVERSE/DOMAIN_01/<version_group>/History
[ top ]
Although your license keys never expire, your maintenance contract does so on an annual basis. Your maintenance contract allows you to receive unlimited support and allows you to upgrade as frequently as you'd like. When you receive this message, please contact Razor Sales at (315) 363-8000 or e-mail them at razor_sales@visiblesystemscorp.com to extend your Service Contract.
[ top ]
Please contact our service team at (315) 363-8000 or email your request to razor_licenses@visiblesystemscorp.com . Upon receipt of your request, you will be sent a license transferal form. This form needs to be completed before the transfer is finalized. There are further instructions and an online license transferal form available here .
[ top ]
When a Razor database is brought up, it spawns several Vcs processes. Each process then goes on to create their own RZTMP_RAZORDB.pid directories. For each database that is up, there will be several of these directories. The directories are used for processing Razor actions into the database. Only after you bring down all Razor databases is it safe to manually remove any RZTMP_RAZORDB.pid directories in the /tmp area.
Razor provides a script called rz_cleanup that will clean up files from the user's home directory. Before using this script, we advise specifying the file type you intend to remove within the body of the script itself. You may also want to write a script that would remove temporary items automatically if you desire to remove them from a place other than your home directory.
Please note that rebooting the server should clean up temporary items as well.
[ top ]
You can view a file's history in the Versions GUI by highlighting the file and then choosing the Utilities drop down menu. Choose Info and the bisectional Info GUI appears. The bottom pane is the file's history.
[ top ]
We can provide support on a lot of items, but you need to make the decisions here. You have to decide what is the best organization for your data given your unique requirements. Razor will pretty much handle any organization you desire.
To give you a head start, we suggest that you review the section in the Razor Manual entitled, "Containers: Databases, Groups, and Folders" located in Chapter 8. This section discusses three important data organization methods and provides some things to consider when finalizing the structure of your database.
Some Internet resources you may want to look at:
Inputting "configuration management" in an internet search engine will generate a plethora of information as well.
[ top ]
You will need to modify either Xdefaults or Wdefaults.
Modify Xdefaults if you are working in a UNIX environment. Change Wdefaults if you are in a PC environment. If you can't find your Xdefaults or Wdefaults files, you'll have to copy them from $RAZOR_HOME/examples and into $RAZOR_UNIVERSE_DIR.
Changes made to these files should appear upon the next invocation of the tool (i.e. restarting Issues, Versions, or Threads).
[ top ]
To restore a deleted file, follow these steps.
1. Take the database down
2. cd $RAZOR_UNIVERSE_DIR/DOMAIN_01/ /Archive/Delete
3. find . -name ‘filename' -print
4. The output will look something like this:
./Info/filename.1234 ./History/filename.1234 ./Archive/filename.1234
5. These are the files to be moved back into the database. When moving the files, please remove the numerical extension (i.e. 1234).
mv ./Archive/Delete/Info/filename.1234 Info/<filename> mv ./Archive/Delete/History/filename.1234 History/<filename> mv ./Archive/Delete/Archive/SCCS/s.file.1234 Archive/SCCS/<s.filename> Note: If you are using RCS, then you will need to go to the RZ_VCS directory instead of SCCS.
[ top ]
For example, if the current file control structure is this:
folder1 file1 file2 file3
And you would like it to appear like this:
folder0 folder1 file1 file2 file3
Here's how to do it.
1. Create new folder called "folder0."
2. Rename "folder1" to be "folder0/folder1."
3. Now folder1 (and all of its contents) is in folder0.
[ top ]
To view an Issue's history, you'll actually need to go into Versions.
In the Versions GUI,
- Choose Edit, Tool Properties.
- Uncheck Hide Issue Group.
- Choose Groups, Issues, <name of your issue group>
- Click the Issue you want the history for.
- Choose Utilities, Info and the history will appear in the lower section of the GUI.
[ top ]
To view the contents of a Thread, please complete the following steps.
- Open the Threads tool.
- Double-click on the desired thread.
- The Edit Thread GUI now appears.
Files that were included in the Thread have a plus (+) sign next to them. The version of the file that was included in the thread is seen at the far right edge of the display.
[ top ]
- In the Versions GUI, choose Edit, Tool Properties.
- Uncheck Hide Thread Group.
- Choose Groups, Threads, <name of your threads group>.
- Click the thread you'd like to promote.
- Choose Utilities/Edit file props.
- The resulting GUI will now allow you to promote your Thread's blessing.
[ top ]
RCS is distributed by the GNU Project as freeware. A list of worldwide GNU ftp sites can be found at http://www.gnu.org/order/ftp.html .
- We recommend RCS version 5.7.
- GNU makes no warranties about the software it distributes.
[ top ]
/usr/home/razoradm/Razor/scripts/rz_vcs.rcs: ci: not found
This error is generally caused by either RCS or Razor not being in your path. To set your path to include these variables, please use the following instructions.
1. Find where RCS is located.
In the C shell, type the following:
# which rcs
In the Bourne shell, type the following:
# type rcs
2. Set the path.
To set the path using the C shell, type the following:
setenv PATH "/usr/local/bin:$PATH"
To set the path using the Bourne shell, type the following:
path="/usr/local/bin:$PATH" ; export PATH
[ top ]
For the PC client:
Under WINNT you will find the file Razor.ini. Edit this file to delete paths no longer used.
For the UNIX remote client:
Go to the user's home directory and find the file .razor_login. Edit this file to remove database paths no longer needed.
[ top ]
In basic terms, CVS uses RCS, an archive system that Razor actively supports. Razor has a process for injecting existing RCS files into Razor. Please take a look at the script $RAZOR_HOME/scripts/rz_inject_rcs
The process of doing the inject is described in the header of the rz_inject_rcs script and in the Razor Users Manual, Chapter 4 Using Versions.
If you import the data, you will not lose any of the history you have compiled. Razor will import all of the different versions of the RCS files and all of the associated comments into the database.
Here is an excerpt from the script that lists the steps one needs to perform to inject RCS investments.
# # Where <folder> is the name of the folder that you want your # file(s) injected into. If none is specified the files will # be injected into the top level. # # This script will create a Razor database for the specified group # from an existing RCS database. To perform this maneuver, the following # steps should be performed: # # 1. Stop the database server (using 'razor down') # # 2. Create the new group using rz_add_group. Edit the Attributes # (formerly File_attr_desc) to suit your needs. # # 3. Bring the database server back up (using 'razor up'); # # 4. Introduce the desired files (NOT the RCS files, but the files # the RCS files resolve to) into the new group using Versions. # This is used to set the proper file attributes. # # NOTE: To best ensure the history is retained for an # existing archive of a non-ASCII file, do not choose an # archival type on the Introduce dialog. # # 5. Stop the database server again (using 'razor down') # # 6. Run this script (rz_inject_rcs) with the group name and the # name of the RCS ',v' files. # # 7. Restart the database server (using 'razor up'). # # This script will then create a full history from each RCS file, # update the version in the database and copy the RCS file you # specified into the Razor database. # # Note that if your RCS database had branches in existence, the user # will be asked if they should be injected. Setting the environment # parameter RAZOR_HONOR_ALL_BRANCHES to a non-empty value will force # all branches to be injected without bothering the user for confirmation. # # If only branches from the head version are desired, setting the # environment parameter RAZOR_ONLY_HEAD_BRANCHES to 1 will enable this # behavior. #
[ top ]
Razor's customer base has sites that have achieved CMM level 5.
[ top ]
RCS and SCCS are source code control systems. Razor commonly refers to both RCS and SCCS as archival engines. Both systems contain a set of commands that aid users in tracking the changes made to source code files, or any text files for that matter. It may be helpful to think of RCS and SCCS as a friendly librarian and accountant for your files who helps you restore your files to the condition they were in at some previous time. In short, RCS and SCCS are tools to help manage a group of file.
[ top ]
Functionally, RCS and SCCS are practically equal. The most significant difference is that they each store data in different ways. We recommend using an engine that you are comfortable with and one that complies with your OS requirements.
- UNIX based machines can typically use either RCS or SCCS.
- Linux and PCs are relegated to using RCS only.
RCS stores its revisions by holding a copy of the latest version and storing backward deltas. Since RCS stores the latest version in full, it is faster than SCCS in retrieving the latest version.
SCCS uses a "merged delta" concept.
[ top ]
Yes. You can convert your RCS data to SCCS via an unsupported C-Shell script. Most users who have employed this script have had success. You can retrieve the script from the following site:
ftp://ftp.std.com/src/gnu/cvs-1.3/contrib/sccs2rcs
Please note that users wishing to convert from RCS to SCCS will have to write their own script.
[ top ]
Razor's report feature gives you a very easy method for exporting information from a Razor database. The report format would most useful in this case would be the Export File choice. This method is used primarily to export data to an ASCII file. After the data has been exported to an ASCII file, it can then be imported into another application.
Record, Field, and item separators are already set for you, but can be easily changed if necessary. Keep in mind that whenever you export between applications, platforms, etc., the data may require a little clean up in the application you are importing into.
The commands, available from the GUI's to export data are as follows:
Issues: Reports, Create/Modify, Export File or HTML
Versions: Reports, Create/Modify, Export File or HTML
Threads: Reports, Create/Modify, Export File or HTML
- Start the GUI.
- Choose Reports, Create/Modify.
- In the Report Definition dialog, choose Edit, New Filter.
- Add fields to the right side of the dialog (right window).
- Click Save As, and give the filter a name.
- Back in the Versions GUI, choose Reports, Create and Modify.
- Give the report a title, and choose Export File or HTML. If you want to change the delimiters, double click Export File or HTML. A dialog box appears allowing you to change the delimiters. Please ensure that you save any delimiter changes.
- Back in the Report Definition dialog box, choose the filter you created in Steps 3-6.
- From the File menu, choose to either Preview or Save the report.
Info, History, and Archive files are all stored in an ASCII format. It is possible to write a script that would parse through the necessary files and produce a report. Razor gives a few examples of some reports that can be created. To view these examples, please look in the file $RAZOR_HOME/examples/README.
[ top ]
The rz_compare_thread script has the ability to do this. It is available in your $RAZOR_HOME/scripts directory. It runs similarly to this:
rz_compare_thread -g (group) -f (folder of thread) -d (directory where the original files are)
[ top ]
Yes, Razor versions directories. As a matter of fact, we recommend structuring your Versions tool directory format to mimic your build hierarchy.
[ top ]
The way that you could do this would be to have a common "group" within Versions that holds all common code to your different products.
Example:
Group A - Holds all code specific to application A.
Group B - Holds all code specific to application B.
Group C - Holds all code that is used by both applications.
How do you reuse it? Well, here is where the Threads tool comes in. A thread is merely a unique combination of files that is used to build a release. Razor takes this one step further by allowing users to produce a Project. A Project is simply a thread of threads.
[ top ]
BASIC REQUIREMENTS FOR INSTALLING RAZOR:
- You need to log onto the computer with a UID and password.
- Either SCCS or RCS need to be available on the machine that will run the Razor database server.
- If you opt to use RCS as the archival engine, we recommend version 5.7.
- You also need the proper version of X11...
- If you're on a Sun using SunOS 4.1.x, you need at least X11R4.
- All others platforms need X11R5 or better.
- A bare minimum of 16Mb memory installed on each database server.
- For X Terminals, we recommend having more than 4Mb of RAM installed on the machine.
- To view reports, specifically HTML, pie/bar charts, Razor requires a Java-capable browser. We recommend Netscape 4.5 or better.
- For Internet Explorer, Razor requires version 5 or better.
For UNIX users:
We recommend creating a dedicated Razor administration account. This will become the central location for all Razor distributions and it's a great way to start organizing like a real CM pro.
To run Razor on Windows 2000 or 2003 Server, you need the following:
- Networked Windows 2002 or 2003 Server with Service Pack 2 or greater.
- You must install as Administrator with Administrative privileges.
- NTFS disk partition with enough free disk space for installation.
- NTFS disk partition(s) with enough free space to create and maintain the desired Razor databases.
Note: Installation, as well as all of the administration of Razor Windows Server, must be done via the Administrator account.
[ top ]
To locate older Razor images, please visit visit our Razor archives page or contact us at Razor support. Please include the version of Razor you need and the Operating System.
[ top ]
Here's a snippet from a "Version Mismatch" error. Your error log should be similar to this:
License Manager/Client Subscribe Error
Version mismatch - License mgr = v4.2, Client = v4.2(a)
Please update your Razor installation on ALL platforms.
Razor requires that all machines operate with the same version of Razor. For instance, if the server is Razor 4.2a.04, all clients must be version 4.2a.04. If you get this error, you'll either need to upgrade all of your machines to 4.2a.04 or retrieve an archived version of Razor via our ftp site.
[ top ]
Here's a snippet from a "Could not spawn kid" error. Your error log should be similar to this:
***** 2001/05/14,15:38:25 *****
Could not spawn kid.
USER+razor_user does not have execute permission for
//C/TowerConcepts/Razor/scripts/rz_remote_kid
This error indicates a lack of execute permissions in the Razor installation "scripts" directory. I cannot explain what happened during your installation that prevented proper permissions from being set, but this fix should get you running Razor pretty quickly.
Please run a Razor csh window; from the Start menu on the PC where the RazorNT Server is installed, select "Programs", "Razor", and "Razor csh". Next type the commands,
cd $RAZOR_HOME/scripts
ls -l
You should see a list of the files in the directory with the file permissions. Our guess is that you're NOT going to see "execute" permission listed (first column on each line should have something like "-rwxrwxrwx" listed - the important permission I'm concerned about is the "x").
If you do NOT have the "x" permission set, please run the following command,
chmod +x *
...and try starting a client again. Please let us know what the results are.
FYI, the "Could not spawn kid" failure indicates a "time-out" problem, for a variety of reasons, when a remote client (like the Razor PC Client) is started.
[ top ]
Once you have installed Razor, here's how to correctly install a Razor database on a PC.
- In the Razor Admin GUI, go to Database/New.
- Database Location: should be similar to D:\TowerConcepts\<database_name>
- File Group name: (enter a logical name if you plan to use the file version control tool known as Versions).
- User: EXACTLY the SAME as the login ID you used to get on your computer. Generally, the UID is Administrator.
- Password: EXACTLY the SAME as the password you used to login to your computer.
- Confirm Password: confirm above password
- Now a database will have been created in the right area for Razor to access.
- You should see its service added to the Service Panel. The service will be listed as RazorDB_<database_name>. If not, reboot again.
- To start the new db, go to the Razor Admin GUI, start the License Manager and then enter the database's path correctly and choose start.
[ top ]
Here's a snippet from a common Host/Port error. Your error log should be similar to this:
The Host/Port you are trying to connect to does not appear to be running the RAZOR license server program.
Please contact your RAZOR Administrator.
This type of error is generally related to incorrect path statements. Here's how paths should look.
In the Razor Admin GUI, the path should be formatted as such...
D:\TowerConcepts\Razor\EMG\RAZOR_UNIVERSE
*Note- \Backslashes\, CAPITAL drive letter, and sYnTAx.
In the Issues/Versions/Threads log in screen on the Razor Desktop, the path should look like this...
//D/TowerConcepts/Razor/EMG/RAZOR_UNIVERSE
*Note- //forward slashes//, CAPITAL drive letter, NO colon, and sYnTAx.
[ top ]
License keys are subject to exact syntax. Even the smallest errors will result in key rejection. You can only use license keys for the machine they were requested for. If you try installing them on a different machine, the keys will not take.
All demo users need to enter "DEMO" for their Razor ID when entering their license keys.
The following instructions assume that a demo user is installing their keys for the first time.
UNIX Users:
1. First, tell Razor where the Razor license manager resides. Setting the environment variable RAZOR_LICENSE_DIR does this.
C shell:
# setenv RAZOR_LICENSE_DIR /home/razoradm/Razor_lm
Bourne/Korn shell:
# RAZOR_LICENSE_DIR=/home/razoradm/Razor_lm
2. Now invoke the license manager and enter the keys given to you.
# /home/razoradm/Razor/bin/razor license Enter id: DEMO Enter key 1: xxxxxxxx Enter key 2: xxxxxxxx Enter key 3: xxxxxxxx Enter key 4: xxxxxxxx
NT Users:
1. Go to the Razor Admin GUI (Start/Programs/Razor/Razor Admin).
2. Enter keys by going to the License Manager pull down menu and choose Keys.
3. In the resulting GUI, enter your license keys. Make sure you enter DEMO in the ID field.
[ top ]
No. The only time you need new license keys generated is when you move the Razor database installation or purchase more seats.
[ top ]
It appears that the database was created without file control groups. When creating a new database, the script 'rz_new_database' asks the user if the database will be used for file control. If you chose "N" during installation, you won't be able to use threads. To enable threads, you may create file control groups at any time by running the script 'rz_add_group'.
[ top ]
PC's running Windows operating systems can only use RCS. This is a limitation imposed by the OS and not Razor. We recommend deleting the SCCS database and installing a new database using RCS.
[ top ]
This is a known bug within Razor 4.2. The problem is that the IRIX64 directory is missing. Consequently, the rz_db_exec file in that directory is gone too.
The fix is to make the IRIX64 directory in $RAZOR_UNIVERSE_DIR/bin and copy the rz_db_exec file into the new IRIX64 dir.
[ top ]
If Add/Remove Programs is unsuccessful, you can follow these 5 steps to completely remove Razor from your computer. Before proceeding, please ensure that all databases and the license manager are down.
- Remove the Tower Concepts folder from the partition that you installed on.
- In the registry, under HKEY_LOCAL_MACHINE/software, remove the Softway Systems and Tower Concepts Registry files.
- Search the registry for other keys that are installed.
- Do a find on Razor in the registry. You shouldn't find anything related to Razor. If you do, please remove them as well.
- Keep in mind that any legacy keys will not be removable. This will not cause you any problems.
[ top ]
Limited e-mail functionality is available in our current release of Razor for Windows 2000 and 2003 servers. A new script, rz_sendmail_nt, allows you to send e-mail on State change and e-mail to razor_support@visiblesystemscorp.com. E-mail functionality in Windows requires that either Outlook or Outlook Express be set up as the default mail client on the database server. It also requires setting up an e-mail account for the user running the database service.
The rz_sendmail_nt script works in conjunction only with Outlook or Outlook Express. Razor will use the e-mail account of the user running the database service. To verify which log on name is running the service for the database, open the Services Window (Start -> Programs -> Razor -> Shortcut to Services). Right click the necessary database and choose Properties. When the Properties dialog box appears, click the Log On tab. You may then need assistance from your SysAdmin or Mail Admin to set up the mail account for this Log On (user) name.
To send e-mail on State changes, specify the e-mail address for the intended recipient(s) in the e-mail field in the Permissions file. To change the Permissions file, bring up the Razor Admin tool (Start -> Programs -> Razor -> Razor Admin). When the Admin Tool appears, select your database (making sure it is not running) and then open the Editor (Database -> Editor). From the tree view, expand the Issues group that you would like to send e-mail on state changes from. Then open the corresponding Attributes file by double-clicking on Attributes. When the Attributes GUI appears, highlight the State field and click Modify. This will open a GUI with five tabs. Select the Permissions tab (fifth tab). Click the necessary State, and then click Modify. In the Permission Settings GUI, specify the e-mail addresses for the intended recipient(s).
You can also make direct modifications to the Permissions file from vi. You can run vi from a csh terminal (Start -> Programs -> Razor -> Razor csh). For more information on setting this up, see the Razor User Manual, Chapter 8, Customization and Personalization, E-mail notification on state changes.
Note: In Outlook and Outlook Express, you will need to click the Send/Recv button, or the e-mail that Razor generates will remain in the Outbox.
Limitations: Razor 2000 or 2003 Server does not yet support database synchronization, e-mail issue submittal, and e-mail query (remote access via e-mail).
[ top ] |
