Agresso Business World – Performance Tuning

An Agresso Business World customer had an issue with performance. Once a week several hundred users would all do their timesheet entry into Agresso on the same day. Users frequently complained that the system sometimes ran slow, was sluggish and hung while they were entering their timesheet details. However, this behaviour was intermittent and the issue wasn’t always evident.

So, several hundred users all doing timesheet entry into Agresso in a small time frame were experiencing performance issues.

  • “Is it the Agresso Web Server that is under too much load and is struggling with the number of connections?”
  • “Could additional indexes on the timesheet tables help?”
  • “Is there database blocking going on which is forcing users to wait?”

It was actually none of the above.

The web server was under little load. The connections for the timesheet entry were doing very few reads and there was no sign of blocking.

The issue was traced to a large number of server side processes which were using all of the database servers resources and maxing out the disk and memory.

Server side processes definition in this instance: –  scheduled jobs and services running on the Agresso Application server.

If users connected to Agresso to do their timesheets while one of these large server side processes was occurring, SQL Server had few resources available to service them. This meant that rather than taking milliseconds to process the timesheet entry, it was taking a few seconds.

An unexpected few seconds delay at the application side seems like a long time to the end users.

Basic and some more advanced techniques were used to sort out the long running server side queries. This alleviated the load on the disk I/O subsystem and memory on the database server and enabled it to deliver a fast service to timesheet entry users.

Further ongoing performance monitoring is in place to identify other badly running queries.
 
 
 
 


April Update

Welcome to our  April Update
It’s been a busy month and here are just some of the Agresso services we have provide in April.

  • A Live M4 Upgrade
  • A Live Milestone 5 Upgrade
  • Interface Consultancy
  • An Agresso Technical Health Check
  • A new M5 Installation at a green site
  • A Test Milestone 5 upgrade
  • And several Technical Training days

Agresso Milestone 5 – Supported Platforms

Windows-2008-R2

 

 

 

 

 

A lot of organisations running Agresso Business World are probably aware that Milestone 5 is available. And a certain number will be thinking about upgrading to M5 for either the benefit of new functionality or bug fixes.

It’s useful to be aware in the early stages of planning that Milestone 5 does not support Windows 2008 and 2008 R2 Server, nor does it support SQL Server 2008 and 2008 R2.

For new installations this isn’t really an issue as by default most organisations are rolling out new systems are running Windows 2012 R2 Server and SQL Server 2012 / 2014. But for existing customers who may be planning to use their existing test and live environments that are 2008 based a bit more consideration will be required


Agresso Web Client – Turning on HTTPS

Agresso-SSLThe Agresso Web client can either be run under HTTP or HTTPS. The HTTPS mode provides greater security as the data that is transmitted between the Agresso Web Client and the Agresso Web Server is encrypted.

Report Engine (Excelerator) and Web Services (ipad connections etc) also use the same method to connect to the server.

HTTPS is the recommended method and is strongly recommended for any environments where data will be transmitted over the internet.

HTTPS uses an SSL Certificate which can either be self generated or purchased from a third party certificate authority such as Thawte, RapidSSL, Comodo, VeriSign (now Symantec) etc. Self generated certificates are free, but we would recommend purchasing one from a certificate authority.

Once you have the certificate it requires loading onto the server via the certificate root console. How to obtain and load the certificate is documented by the certificate authority when you purchase the certificate so won’t cover that here. But once it’s loaded onto the server it needs adding into IIS.

Start IIS and go to the Default Web Site and then click on the Bindings menu in the right hand pane.

agresso-ssl1
From the Bindings menu add the HTTPS protocol and select the SSL certificate that you have just loaded onto the server.
agresso-bindings

 
 
 
 
 
 
 
 

 

 

On the Agresso web server launch the Agresso management console and navigate to the following menu
agresso-menu

 
 
 
 
 
 
 

 

 

Expand the menu node and go to the Protocol option. If the HTTPS is not already there then add it in. Remove the HTTP entry so it looks something like this. Do this step for the Web Services and the Report Engine (and if applicable Web Classic – Milestone 4 only)

agresso-protocol
 
 
Then go to the Publish option and in here you will see that it is currently published using HTTP.

agresso-uri

 

 

 

 

Withdraw this and then Publish it using the HTTPS option. Do this for the Report Engine and if applicable Web Classic.
agresso-publish
 
 
Please note that when you first withdraw the web service that it may likely just be the hostname of the server. In this instance the server is called agressoweb and Fully Qualified Domain Name (FQDN) of the company name is intersect.co.uk. SSL Certificates would have been normally purchased specifically for this server agressoweb.intersect.co.uk or they would be wildcard certificates which you can install on any server which has a FQDN ending in intersect.co.uk.

Because the certificates are only valid for the exact hostname, after withdrawing the HTTP://agressoweb you would publish the https to HTTPS://agressoweb.intersect.co.uk.

If the FQDN is omitted then the hostname won’t match the name on the SSL certificate and this will give a warning message and a red cross in the menu bar in your browser.

So the URL to the web client that would previously have been http://agressoweb/agresso would now be https://agressoweb.intersect.co.uk/agresso


Thinking of upgrading to Agresso Milestone 5?

Have you also considered moving the Agresso platform to the cloud as part of an upgrade?

Hosting and managing Agresso systems in a data centre and deploying the client to customer sites is nothing new and has been around for many years now. However, with virtualisation technologies maturing into stable platforms and faster and cheaper network links between office and data centre, the trend to move to cloud hosting is growing.
But would you benefit from it?

Firstly, the Agresso upgrade process is streamlined as there is no need to purchase new hardware and software licenses, or no need to upgrade existing servers to Windows 2012 and SQL Server 2012.

With the servers already in place we can very quickly carry out the Agresso upgrade at a time that suits you. For some organisations having the system offline is an issue during the live upgrade process, to accommodate this we can start the upgrade on Friday evening and return the system Saturday PM.

Having a more efficient Agresso upgrade is then further enhanced by your environment being managed by Agresso technical specialists. This is a comprehensive technical service which also includes in depth performance tuning which is sometimes required after upgrading.

For further information please contact us enquiry@intersect.co.uk