Table of Contents
Advertisement
Recommended approach to testing
A recommended approach to using the On-Line Transaction Testing program is:
1.
Set all of the important server functions to Security Level 1, Log All. This will log all
requests without affecting any users. Set your Future Server settings or use the pre-
loaded recommended values.
Turn off logging on the non-critical servers to limit logging.
2.
Collect your requests and print out the Security Report by User from the Network
Transaction Analysis Reports Menu. Select Historical Review.
3.
Set up your User to Server and User to Object, SQL, FTP, CL, etc. tables if you wish to
go to Security Level 4.
4.
You can use several tools provided with SafeNet/400 to test your security settings. Use
the Security Report by User or the on-line version, PCTESTR. These can be run to test
the collected transactions against the current or future server settings. (Use Future
Setting)
5.
Use 'Show only Rejections' on PCTESTR and 'Print only Rejections' on the batch
report. If your settings are correct for the Security Levels being tested, you should receive
messages only for transactions that would be rejected.
If any of the requests are rejected, check the message description and make the
appropriate corrections to the SafeNet/400 settings. Try the transaction again.
Note: If you request Level 4, you may only get a security check to Level 3 since some servers
support only up to Level 3. This is noted on each record in the On-Line Transaction
Testing as "Level Requested", "Level Checked" and "Max Level".
SafeNet/400 Reference Guide
© Copyright 2008 MP Associates of Westchester, Inc.
V8.50 - May 2008
7.9
Advertisement
Table of Contents
