In addition to evaluating the differences in software and hardware requirements, you can decide whether to install a Gateway Appliance or a Gateway Service by evaluating the minor functional differences between the two.
The Access Gateway can be installed as an appliance (the operating system is installed with the Access Gateway software) or as a service (the Access Gateway software is installed on a machine with an existing operating system). For information on the differences between Access Gateway Appliance 3.1 SP4 and Access Gateway Appliance 3.2, see Section D.0, Feature Comparison of Different Types of Access Gateways.
These Access Gateways have the following requirements:
The Access Gateway Appliance runs on SLES 11 SP2 or SP3, 64-bit operating system on x86-64 hardware. You install it on a separate machine because it clears the hard drive and sets up a soft appliance environment.
The Access Gateway Appliance requires the following hardware:
Minimum 4 GB RAM and recommended is 8 GB RAM.
Dual CPU or Core (3.0 GHz or comparable chip).
100 GB hard disk.
This amount is recommended to ensure ample space for logging in a production environment. This disk space must be local and not remote.
A static IP address for your Access Gateway server and an assigned DNS name (host name and domain name)
For a list of hardware that is supported by SLES 11 SP2 or SP3 for x86-64 hardware, open the YES CERTIFIED Bulletin, select Service Pack 1, Service Pack 2 or Service Pack 3 for SUSE SLES 11 SP2 or SP3 in NetIQ Product, and search for your other hardware requirements.
The Access Gateway Appliance has no software requirements. The installation program re-images the hard drive, embeds the Linux operating system, then configures the embedded operating system for optimal performance.
For installation instructions, see Section 5.0, Installing the Access Gateway Appliance.
The Access Gateway Service is installed on an existing Linux system. This machine must meet the following requirements:
SLES 11 SP2 or SP3 64-bit operating system or RHEL versions 6.4 or 6.5 64-bit.
NOTE:For the SLES 11 SP2 or SP3 platform, make sure you have the latest security patches and openssl. To confirm the version of openssl in your system, run the rpm -qa | grep openssl command.
Because of library update conflicts, you cannot install Access Manager on a Linux User Management machine.
Minimum 4 GB RAM and recommended is 8 GB RAM.
Dual CPU or Core (3.0 GHz or comparable chip).
2 to10 GB per reverse proxy that requires caching and for log files. The amount varies with rollover options and logging level that you configure.
Configured with a static IP address and a DNS name. The ActiveMQ module of the Access Gateway Service must be able to resolve the machine’s IP address to a DNS name. If the module can’t resolve the IP address, the module fails to start.
Other Access Manager components should not be installed on the same machine.
Ensure that the following rpms or higher versions are installed if you have installed Access Gateway Service on RHEL:
apr-1.3.9-3.el6.x86_64
apr-util-1.3.9-3.el6_0.1.x86_64
libtool-ltdl-2.2.6-15.5.e16.x86_64
unixODBC-2.2.14-11.el6.x86_64
db4-4.7.25-16.el6.x86_64
glibc-2.12-1.25.el6_1.3.i686
libesmtp-1.0.4-15.el6.x86_64
nss-softokn-freebl-3.12.9-3.el6.i686
NOTE:For more information about dependent RPMs and how to install these, see Installing Packages and Dependent RPMs on RHEL for Access Manager.
(Only for SLES) Ensure that the following rpms or higher versions are installed:
libapr-util1-1.3.4-12.22.21.2.x86_64.rpm
libapr1-1.3.3-11.18.17.1.x86_64.rpm
unixODBC-2.2.12-198.17.x86_64.rpm
The Windows Access Gateway Service is installed on an existing Windows system. This machine must meet the following requirements:
Windows 2008 R2 Server, 64-bit operating system, in either Standard or Enterprise Edition, with the latest patches applied.
Minimum 4 GB RAM and recommended is 8 GB RAM.
Dual CPU or Core (3.0 GHz or comparable chip).
2 to10 GB per reverse proxy that requires caching and for log files. The amount varies with rollover options and logging level that you configure.
Configured with a static IP address and a DNS name. The ActiveMQ module of the Access Gateway Service must be able to resolve the machine’s IP address to a DNS name. If the module can’t resolve the IP address, the module fails to start.
Other Access Manager components should not be installed on the same machine.
Clients can use any browser or operating system when accessing resources protected by the Access Gateway.
NOTE:For information on the differences between Linux Access Gateway Appliance, Access Gateway Appliance, and Access Gateway Service, see Section D.0, Feature Comparison of Different Types of Access Gateways.