IT Architecture Team Report:
Administrative
Distributed Computing Infrastructure
Overview
The infrastructure for Distributed
Administrative Applications consists of the desktop,
the servers and central services that
run on those servers, the network that
connects the desktops and servers, and the various Administrative
Applications that use the above resources to deliver business
solutions to administrative departments.
The architectures for distributed administrative computing
are n-tier client server based and can be broken down into 3 general
categories: ERP/Peoplesoft, J2EE,
and Fat Client. The preferred Architecture for applications developed
by Administrative
Information Services is J2EE, a cross platform, vendor neutral,
component-based architecture.
Other Architectures are acquired when we purchase commercial
packages. In addition, OIT has developed several in-house "enabling" technologies
that offer alternative methods for administrative application development
and deployment. These are described
in more detail in the Web
Access to Databases document.
Application Server/Web server (software)
For Web Servers for distributed administrative
systems, the University uses Apache and Microsoft IIS. Apache is
the preferred Web server. The University uses Microsoft IIS only
for applications that require it. Weblogic Server and Tomcat are used as the
application server.
In the case of Peoplesoft, BEA Weblogic web server is used
as the web server and BEA Tuxedo is used as the application server. Both BEA Weblogic
web server and BEA Tuxedo applications server are bundled with the Peoplesoft product.
Collaborative Tools
There are four methods (or protocols) for handling e-mail at Princeton University: Exchange-enabled (Enhanced), IMAP (Standard), POP, or WebMail. See Knowledgebase article #9815 for additional information.
Compute/File services
Compute and File services are based
on Sun Solaris and Microsoft Windows Server operating systems. Sun
Solaris is the preferred environment for production applications
except for applications that require a Microsoft Windows environment.
Database services are based on Oracle,
Sybase, and SQL Server. Oracle is the preferred database except
for applications that require Sybase or SQL Server.
The Desktop environment is Microsoft
Windows.
Directory Service is based on LDAP
and Microsoft Active Directory
The Help Desk provides essential support
for Administrative Applications.
Version Control
Merant PVCS is used for Custom Applications. Package applications currently rely on vendors for version control.
Network Services
Network Services are defined here.
Personal Productivity Tools
Personal productivity tools are primarily
based on Microsoft Office, with additional helper applications and
utilities as determined by the Desktop Systems Council.
Reporting
Reporting is provided through a number
of tools. The current reporting tool is Cognos Reportnet. Many existing reports have been developed using Crystal Reports, SQR, Cognos Tools, and Oracle Reports.
The Princeton Data Mall and the Princeton Data Warehouse are comprehensive data collections that contain detail and summary information.
Security
University applications should use one of two OIT managed services for authentication: LDAP or Windows Active Directory. Where possible, applications should utilize built-in system authentication services, such as the use of appropriate parameters in an .htaccess file for Web applications. Capturing and validating the user’s ID and password within the application through program code is strongly discouraged. Confidential data (including passwords) must be transmitted over the network in an encrypted form, using 128-bit SSL or an equivalent method when SSL is not available. Packaged applications are, where possible, required to conform to comparable standards.
System management Services
System management Services are based
primarily upon the Tivoli suite of tools.