PSNext Architecture
Project management requirements have developed and expanded considerably since the start of the 1980s, moving from simple project scheduling to the establishment of genuine data-sharing tools including timesheets, forums and document management. Anyone involved in a project is now included in the company's project management software. This extreme change in demand has resulted in a complete overhaul of the IT architecture used in order to meet the following requirements:
Simple, universal, secure access
Corporate networks are often many, varied and independent, based as they are on a departmental approach and sometimes being separated geographically. PSNext meets this challenge by depending solely on the HTTP and HTTPS protocols , which are now both widespread and secure.
Automatic deployment
The more a system is used within a company, the more automated its deployment needs to be in order to reduce roll-out costs. This point becomes even more crucial in a situation where simultaneous upgrades are required. Users can run PSNext from any compatible web browser, or launch it over the web as a Java Web Start application. Either way, PSNext automatically upgrades itself on all client workstations when you upgrade it on your server.
Standard, scalable, shared architecture
As reorganizations occur, companies' requirements can change radically. Working with a standard, scalable and shared architecture means expertise and investment can be shared and maintenance costs reduced.
PSNext is a J2EE application
PSNext is based on a three-tier architecture. Each level of this architecture is itself based on tried and tested standards. PSNext is built from 10 components, each of which corresponds to a Java component that can be used within a browser or as a standalone application. Each component is automatically installed - and upgraded if need be - on client workstations, in accordance with the defined usage rights. Communication between the clients and the application server takes place by means of the HTTP or HTTPS channel.
Work offline
PSNext provides users the ability to check-in/check-out projects and work with them offline while disconnected from the PSNext server.
An example of usage by domain
- One PSNext server can support different and completely separate databases.
- More than one version of PSNext may also coexist on a single application server and point to a test database, before live implementation.
An example of scalability
- The management of scalability within PSNext is totally transparent. Simply add application servers in parallel, which will automatically handle the balancing of workload across the servers (load balancing).
