System Requirements
iSeries (AS/400) Server Requirements
Disk Space Required on the iSeries Server
Disk Space Required on the PC Client
For the PC Client Module to operate correctly, the appropriate level of PTF for the HTTP server must be installed, depending on your version of OS/400.
|
PTF |
OS/400 Release |
Comments |
|
SF99502
group level 17
|
V5R2 |
Not always required. Only install these PTFs, if the message MCH3601 is returned from module SQLTR when using the Bsafe GUI or if you experience the list of users not appearing in the GUI main screen. |
|
5722SS1 - SI17551 with any co/prerequisites. |
V5R3 |
|
If after installing the appropriate PTF there appears to be a problem with the operation of the GUI client module, please contact support, support@enforcive.com
It is important that all PC's using IBM Client Access have the latest PTFs installed otherwise various problems may occur. One common example is the RMTCMD server request being made by Client Access when logging on to Telnet.
The following page on the IBM website contains reference to the latest PTFs.
www.ibm.com/servers/eserver/iseries/access/casp.html
1. IBM i AS/400 computer running OS/400 Release 5.1, or higher.
2. TCP/IP communication.
3. Active HTTP server (OS/400 or Apache)
4. A user with SECOFR authority.
The approximate System i disk space required for the Bsafe Enterprise Security program libraries is as follows:
RMTOBJ About 122MB
RMTSMP About 328MB
The size of these libraries will not change during use of the product.
Initial disk space required for the Bsafe Enterprise Security data library is as follows:
RMTFIL About 280MB
This library will grow in size due to the addition of security definitions, through logging of network traffic and through system audit logging if the system journal has been defined in this library. The following sections discuss various approaches towards keeping disk growth under control.
The full list of access control functions which are covered by the product can be seen by looking at the product main screen, then drilling down to view the sub-functions. This is covered in depth in the product help.
The degree of logging done can be controlled in several different ways. Each of the above applications can be set to log all access or rejections alone.
Additionally, each application can be set to log the first time access for a user, or every single access. This flexibility allows you to find the balance between maximum auditing on the one hand and minimum overhead on the other.
It should be remembered too that whatever the degree of network access to your iSeries and whatever degree of logging you choose to define, the log file can be purged at any time in accordance with parameters you define and can even set to automatic purging using the iSeries scheduler.
As a final consideration, normal interactive network access doesn’t generally result in a rapid growth rate of the log file. What would cause this to increase substantially is a very large number of client / server users simultaneously querying or updating the database through ODBC / Websphere or any kind of batch operation. In these cases, it would be more of a necessity to define a reduced level of logging as described above.
The other areas of disk expansion which need to be considered are the system journal and the iSeries file journals. These can be nicely managed from Bsafe/Enterprise Security but the underlying mechanism is OS/400 or i5/OS objects. This means the journal size will be the same whether managed through Bsafe or iSeries native screens.
· Operating system - Windows 2000, 2003, XP, Vista, Windows 7 or later.
· TCP/IP communication to the iSeries or AS/400.
100 Mb
Certain operations in Bsafe/Enterprise Security involve communication between two IBM i computers via DDM. These operations include remote compliance checking and replication of user profiles, passwords and definitions.