APPSERVER PRODUCT PLATFORM SUPPORT

Borland AppServer 4.5.1

The following tables show platform certification and minimum system requirements for Borland AppServer product releases.

Borland AppServer 4.5.1

Supported Platforms:

Microsoft Windows (Intel)
OPERATING SYSTEM SUPPORTED JDK(s) MINIMUM SYSTEM REQUIREMENTS

Windows NT 4.0 SP6,
Workstation and Server

  • Windows NT Service Pack 3 or NT Service Pack 5
  • Pentium II 233 MHz
  • 128 MB RAM minimum; 160 recommended
  • 75 MB disk space

Windows 2000 SP2,
Professional and Server

  • Windows 2000
  • Pentium II 233 MHz
  • 128 MB RAM minimum; 160 recommended
  • 75 MB disk space
Sun Microsystems Solaris (SPARC)
OPERATING SYSTEM SUPPORTED JDK(s) MINIMUM SYSTEM REQUIREMENTS
Solaris 8 (32 and 64 bit) 1
  • Sun Ultra 5
  • 128 MB RAM minimum; 160 recommended
  • 75 MB disk space
Solaris 2.7 (32 and 64 bit) 1
  • Sun Ultra 5
  • 128 MB RAM minimum; 160 recommended
  • 75 MB disk space
Solaris 2.6
  • Sun Ultra 5
  • 128 MB RAM minimum; 160 recommended
  • 75 MB disk space
Hewlett Packard HP-UX (PA-RISC)
OPERATING SYSTEM SUPPORTED JDK(s) MINIMUM SYSTEM REQUIREMENTS
HP-UX 11.0 (32 bit and 64 bit)3
  • PA-RISC 100MHz
  • 64 MB RAM
  • 54 MB disk space
IBM AIX (RS/6000)
OPERATING SYSTEM SUPPORTED JDK(s) MINIMUM SYSTEM REQUIREMENTS
AIX 4.3 (32 bit and 64 bit)3
  • RS/6000 PowerPC-604 200MHz
  • 64 MB RAM
  • 54 MB disk space
Red Hat Linux (Intel)
OPERATING SYSTEM SUPPORTED JDK(s) MINIMUM SYSTEM REQUIREMENTS
Red Hat Linux 7.0 7
  • Pentium II 333MHz
  • 128 MB RAM
  • 50 MB disk space
1 Works under 64-bit but does not utilize 64-bit features.
2 JDK 1.2.2 Production Release is recommended.
3 JDK 1.2.2_005 Reference Implementation is not supported.
4 JDK 1.2.2_005 Production Release is not supported.
5 JDK 1.2.2_007 has not been certified for use with Borland AppServer
6 JDK 1.3.0_02 has been certified for use with Borland AppServer; however, subsequent patches for JDK 1.3.0 have not been certified but should work properly.
7 Under JavaSoft JDK1.2.2 (up to version JDK1.2.2_007), the EJB container will not startup properly after deploying one or more beans. To workaround this problem, set the server's configuration to run with -DEJBNoScheduler. Edit the /var/servers//adm/properties/ias.config and add the line: vmprop EJBNoScheduler