I've been questioned several times recently about AOS load balancing in Dynamics AX, and there seems to be quite a bit of confusion about how to properly configure AX for AOS load balancing, as well as high availability. Here are a few clarifications that apply to Dynamics AX version 4.0, AX 2009 and AX 2012:
Cody, I wonder if you could comment on the options, pros/cons and best strategy for locating the application files that the AOS must access. When you have multiple AOS instances it seems the most obvious options are :
- hosting a single copy of the application files on one of the AOS instances;
- having multiple copes on >1 AOS server with some sort or replication / sync mechanism;
- putting the applciation files on a seperate high availability file share.
I think might be good idear to make it clear about AX client now talks also directly to SSRS and WCF.
AOS 2012 LB no longer covers reports, and customer must LB SSRS.
The most common implementation I've seen is to have a single copy of the application folder hosted on one of the AOS instances or a separate file server.
The problem with having multiple application folders is maintenance and the risk of having them out of sync. I am not aware of any replication or sync mechanism, as you mention, but I'm sure if you do your due diligence you could pull it off. YOu would just have to ask yourself if it is worth the trouble/risk.
Hosting the files on a clustered file server may have a limited benefit since the AOS service would not support automatic failover. You'd have to restart the AOS and client sessions would be lost. It might help you reduce downtime, though.
In AX 2012, the application files are in the database, so it is a moot point.