9 1:Project.net Deployment Requirements

From Pnet-Community

Revision as of 22:11, 11 June 2010 by Dkassman (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Contents

[edit] Summary of Project.net Deployment Requirements

The following lists the recommended hardware and software for Project.net. A modern single-CPU system acting as both an application and database server will handle 150 to 200 users with typical usage patterns: five to ten percent of users logged in and less than a dozen simultaneous schedule recalculations.

The capacity of this system can be increased to between 450 to 500 users if it is equipped with dual CPUs, more memory and a fast hard drive. More than this requires separate application and database servers, with dual CPUs on the application server and a fast hard drive on the database server. Application server capacity can be stretched with multiple application servers, each running up to three instances of Apache Tomcat.

[edit] General Hardware and Operating System Requirements

Operating System

  • Specific operating systems are listed in each server's section below
  • Apache Tomcat performs noticeably better on systems running Linux than on those using Windows.
  • Additional memory is recommended for systems using Microsoft Windows operating systems, especially if those servers run anti-virus software, too.

System Memory

  • The amount of recommended memory is shown in the tables below
  • Please review your memory needs and the memory limits for Microsoft operating systems when selecting a Windows operating system.
  • Be aware there are limits to the Java heap size, based upon whether you are using a 32- or 64-bit operating system. This can affect Apache Tomcat performance; in general, you should select a 64-bit operating system for the Project.net application server.

Hard Drive Space

  • 5GB minimum of hard drive space free for data storage on each server (application servers may need more, depending upon document storage requirements).
  • Recommend 10,000 to 15,000 RPM hard drives or faster for database servers.

Virtual Machines

  • Project.net runs equally well on physical or virtual hardware (virtual machine), providing it meets the requirements below.
    • Note, virtual machines running Microsoft Windows operating systems seem to perform better on some virtual machine platforms than others.
    • Virtual machines running Linux perform equally well across the common virtual machine solutions.



Commonly Sized Systems (exact recommendations will depend upon # of concurrent users)
< 200 Users 200 - 500 Users
Server CPU (min) Memory CPU (min) Memory
Application or Database xeon 2.5ghz (dual core) 2 GB xeon 2.66ghz (dual core/ multiple CPU) 4 GB
Application and Database xeon 2.5ghz (dual core) 4 GB xeon 2.66ghz (dual core/ multiple CPU) 4+ GB


Larger Systems (exact recommendations will depend upon # of concurrent users)
1000 - 2000 Users 2000+ Users
Server CPU (min) Memory CPU (min) Memory
Application 2-3 dual-core CPUs running 2-3, load-balanced Apache Tomcat application servers 8 GB multiple servers running multiple load-balanced Apache Tomcat application servers 8+ GB for each server
Database dual core CPU running Oracle 10g Standard One or better 4+ GB 2-3 dual-core CPUs running Oracle 10g Standard or Enterprise 4+ GB

[edit] Web Browser

  • Tested on Linux, Windows or OS X with:
  • Microsoft IE 7.0, 8.0
  • Firefox 3.*
  • Apple Safari 4, 5
  • Should work with:
  • Firefox 2.0 or higher
  • Opera 8.0 or higher
  • Google Chrome 4.*

[edit] Application Server

  • Either operating system
  • Application Server software: Apache Tomcat 6.*
  • Java Runtime Environment (JRE or JDK) 6
  • Messaging Service software: Apache ActiveMQ 5.3 or newer
  • Linux specific
  • Should run on any Linux server distribution supported by Apache Tomcat and Oracle database.
  • Known to work on:
  • Red Hat Enterprise Linux
  • Fedora Core 2-5
  • Debian 3.1
  • Ubuntu 9.10
  • Solaris 9 (Unix)
  • File Sharing Software (NFS or Samba), if document vault storage not located on the application server machine
  • Windows specific
  • Known to work on:
  • Windows 2008 Server
  • Windows 2003 Server
  • Windows 2000 Server

[edit] Database Server

  • Either operating system
  • Oracle 10g (10.2)
  • 5GB minimum of hard drive space free for database tables
  • Recommend 10,000 to 15,000 RPM hard drive or faster
  • 2 GB RAM
  • Recommend 4 GB RAM, if system serves as both application and database server.

[edit] Web Server

  • Project.net will work well with the web server built-in to the Tomcat application server.
  • Production deployments should use a web server, such at Apache httpd or Microsoft IIS for increased performance and improved security.
  • If desired, the application can be protected using SSL. The certificates usually need to be ordered in advance and should be configured on the web server prior to installing Project.net.

[edit] Documentation Vault File Server

  • All files uploaded in the Documents module in the Project.net application get uploaded to document vault.
  • It is typical to host the document vault on the application server in the beginning. Often, it needs to be moved to another machine as the document vault grows larger.
  • If on another system, the document vault server's file share will need to be mounted so the application server can access it.

[edit] SMTP Mail Server

  • A mail server is used to send out application notifications and invitations.
  • Must have relaying enabled for application server outbound email
  • Project.net supports two methods to secure your mail relay:
  • by IP address of the application server, or
  • utilize a user name and password to log into the SMTP server.

[edit] LDAP Server (optional)

Project.net has built-in user authentication, but an external directory server can be used as long as it has LDAP v2 or v3 support

  • Any Lin*x Directory Server, such as OpenLDAP
  • Microsoft Active Directory

[edit] More Help

Personal tools