Changes

As part of All n One's efforts for ongoing service enhancement and improvement of the bxp software platform, it has come is now time for a number of extensive infrastructure improvements to be realised.

The most important part of this the process for this release is that you , the bxp user , will experience no change in any of your daily activities. This is purely a suite of back end enhancements.

For testing purposes for a limited time the service will be available through http://ww4.allnone.ie/client/client_demo/main/login.asp though some operational differences explicitly regarding the ssl SSL certificate and file references will be apparent (as ww4 is not the same as ww3, where current links point). The service will continue to use ww3, . ww4 is for testing purposes only.

The current bxp infrastructure is built on Windows Server 2003 servers. This will become end of life in 2015 ( http://support.microsoft.com/lifecycle/search/default.aspx?alpha=Windows+Server+2003+R2 ).

It also means that our infrastructure on which these OSes OS's are installed will be upgraded as well. The web tier of our infrastructure will enable virtualisation of 2 windows 2008 servers across three physical boxes. Our database server will be upgraded as well with a minimal lag mirroring server sitting immediately beside it. This reduces any impact of a motherboard failure.

As part of the security enhancements planned , all data on the database hard drives at rest will be encrypted. This is not applied to the web servers as they do not hold client data.

In previous iterations of MySQL where a date/time field type is in a table, if and not specified in the query , it could be left out. More recent itterations iterations of MySQL now require the date time field to be explicitly filled in. , e.g. Not every outcome requires a callback. Therefore the callback date and time could be left blank. Now a date time must be specified and then handled. We have been working on code to handle all examples like this throughout bxp for the last past 14 months.

A number of new security features are now possible through the heart beat. The first is an ability to auto lock out an account after 90 days if it hasn't been logged into. This ability will lock out the account on a scheduled basis but the user will remain a live user. This option will not be turned on by default for all accounts, just those clients who explicitly request it.