Servers, but which does what?
Terminal Servers
The client files required to run the Agresso application are installed and maintained on terminal servers (ts-nhr-01, emerald & ts-nhr-03). This removes the need for the files to be installed on each users PC and means that, as users do not currently have permissions to install such software, the application can be controlled and centrally managed. Terminal Servers can be accessed by all campuses and all processing is carried out on the server thus not affecting the performance of the end users PC.
Business Servers
Agresso runs with two Business Servers. It is these that control the queues and a number of background functions and services for the application. The queues and services are divided across the two servers as follows:
| agrbs-nhr-01 | agrbs-nhr-01 | ||
| Default queue | AGRAPBACS | Accounts Payable BACS | |
| ACRALS | Amendment Logging Server | AGRARBACS | Accounts Receivable BACS |
| AMS | Agresso Messaging Server | AGRBACS | Spare BACS Queue |
| RESRATE | Rate Processing Server | AGRMANACC | Management Accounts |
| SCHEDULER | Scheduled Jobs Server | AGRPAYROLL | Payroll Queue |
| AINAPS | Intellagent Server | AGRPURCH | Purchasing Queue |
| ALGSPS | Sales Order Processing | DEFAULTSC | Reserve Default Queue |
| ALGIPS | Invoice Processing Server | AGRSALOMONS | Salomons Queue |
| TPS | Transaction Processing Server | SYSADMIN | System Admin Queue |
| Workflow | |||
If one of the Business Servers were to fail, the queues and services can be moved on to the other to avoid any down time.
Web Servers
Database Servers
Infrastructure of Agresso
Agresso Live - the live Agresso system is made up a number of different servers. There are two business servers, a database server and a web server.
The business servers (agrbs-nhr-01 & agrbs-nhr-02) are asynchronous processing servers which perform jobs (e.g. posting to the G/L and reports that run in Maintenance of Ordered Reports). Each business server runs it own set of services. The biggest advantage of having two business servers is that the workload is shared but if one goes down, the other is still available to process jobs. Users communicate directly with the business servers by requests which are inserted into temporary tables on the database server which are then read by the Agresso services. This enables users to continue processing whilst waiting for a job to run or an update to occur.
The database server (agrsqlcluster, which in itself it made up of two separate servers) holds the main Agresso database and all of the 'temporary' databases - one per service (see business servers above). There are no Agresso programs installed or run on the database server.
agrws-nhr-01 is currently the web server for all Agresso web applications (e.g. on-line requisitioning, employee self service). It will also soon host the ALBACS software.
Agresso Test - We also have two AGRESSO 5.5 test servers - agrtest1 and agrtest2. This is because everything mentioned above is held only on the one respective server as there is never the same demand here as in the live environment and so performance and possible failure is not as critical.