|
TrapEngine scans the Common log files, forms the Trapper database (Database), locks/unlocks Internet access by criterion established in Trapper Admin, sets up starting parameters for the Database forming, automatically forming three types of daily reports, сreates users reports by requests from TrapClients.
This program has a possibility to handle information in real time. 
Requirements for the TrapEngine workstation: - Min CPU is Pentium Pro. - Windows 2000/XP/2003. - Novell Border Manager 3.0 - 3.8 and Novell Border Manager 3.9 - The last Novell Client for Windows. - Memory: • 4 MB is for the program.
• Plus, max size of your Common Log file. This parameter is setting in NWAdmin
(the Log Rollover parameter). Do not make the size of the common log file too big. • Plus, memory for the cache of two or more databases. It is set in adjustments of the
program (see the section "TrapEngine adjustment" of documentation).
- Your workstation must be in the same network where your NBM server is. - NBM HTTP Proxy with Common logging and proxy authentication enabled. - Disk size. Must be enough for allocation of the Database. Its size depends on quantity of your users and
their work in Internet. See the section "Database" of documentation for computation of the size. - NDS common user names must not keep the following sequence of symbols: “ [“(space, left square bracket).
You can use these symbols in user names, but you cannot use them in this sequence. TrapEngine will ignore log
strings with this sequence of symbols. - Full access to the Database directory ( TrapEngine/Database/ ) must be provided for the
other workstations with TrapAdmin and TrapEngine (see the section "Recommended schemes of usage
for the program" of documentation) - Network card. For a normal work you can use any network card, including wireless connections, but
there will be better performance in a case of the faster connection. - TrapEngine workstation must have the [RF] rights on the Common Log directory. - For controlling user’s Internet access you must grant the Admin rights to the TrapEngine workstation
on the following NDS objects: 1. NBM server - for installation of the AC rule with the Trapper group. 2. Container – where will be created the Trapper group and the TrapUser user. 3. Containers – where your users are. - Access for users workstations to the TrapClient port
New in the versions: v5.0.2 (31/Jan/2008)
1. Added support of TrapClient2. Refreshed some codes by the new NDK (October, 2007) 3. Changed HELP V4.0.0 (20/May/2007): 1. Added support of Novell BorderManager 3.9.
2. Removed the Restore rules button.
3. Fixed the bug: The program hung up if the selected directory did not have log files.
4. Fixed the bug: “NWDSPutChangeAndVal returned FFFFFED0”, if there was not enough a program buffer for receiving BorderManager rules.
5. Removed a link of Trapper rule to the rule list order in BorderManager.
6. Modified the NDS Thread mode: The program stopped if the database had a user, which was deleted from NDS.
7. Refreshed some codes by the new NDK (February, 2007).
8. Created the new HTML HELP
v3.3.0 (08/Mar/2006) 1. Corrected a bug in the Main Thread mode. The program was hung up when in NWAdmin Log Roller was set "Log Rollover by Time". 2. Refreshed some codes from the new NDK (Aug, 2005). 3. Added support of the additional Organization and Country objects in the "Select Context For Trapper Group" window. 4. Added the option of moving user's loadings to the next account period, if their values exceeded the values in the Limit column. 5. Changed HELP.
v3.2.1 (29/Aug/2005) 1. Corrected a bug in the NDS Thread mode. The program was hung when administrator tried to set up a context of the Trapper group while the Start Thread mode was running. 2. Added the Default limit option. 3. The operation Define name was moved to TrapAdmin. 4. Added six additional filters for the "Filters" option. 5. Refreshed some codes from the new NDK (June, 2005). 6. Changed HELP.
v3.0.3 (16/Feb/2005) 1. Corrected the bug in the filter options. The program was passing the packets with 502 HTTP code "Bad Gateway", when the option "Bad Gateway" was turned on.
v3.0.2 (10/Dec/2004) 1. Refreshed some codes from the new NDK (September, 2004). 2. Corrected the bug in NDS Thread. The program could not process the objects without NDS context. 3. Added the database caching in the Start Thread and in the Main Thread modes. This feature increased productivity of the program in five times. 4. Enhanced the algorithm of the Define Name operation for pure IP networks. 5. Added possibility of precision tuning (by time and date) start of account period. 6. Added the option allowing automatically forming three daily reports: the full daily report, the websites report visited by your user for the day and the report about Internet work of departments of your company for this day. 7. In the Restore ACL command was added the operation of database configuration cleaning. This operation will prepare necessary conditions for the NDS Thread initialization if you will want to use this mode once again. 8. Changed Help.
v2.0.3 (25/Aug/2004): This version has many differences from the previous versions (v1.x.x). I rewrote the program through and through, added many useful features and made it by more convenient in application. The program is ready for using in DHCP networks.
|
