1. There are various online help documents which will be useful to you:
2. As Application Clusters use a Windows share for the shared disk location, you also need to be aware of the "rules" for setting up the X3 Runtime user account, as it will need access to this shared disk location.
All X3 runtime services should either run with the same Windows Active Directory (AD) account (not a local account) or with AD accounts that belong to the same AD group. Note that the AD account does NOT need to be an administrator of anything (Domain or even local administrators on the App/Runtime hosts) provided these rules are followed:
3. Each Sage X3 Apps/Runtime server MUST use the same Windows disk location for the "..\Folders" directory. i.e. if the first Apps/runtime server has the Sage folders directory located in "D:\Sage\X3ERPV12" then all Apps/Runtime servers must use this same location
4. There are several relevant fixes in the X3 Console version 2.49.2 (Discussed in https://www.sagecity.com/gb/sage-x3-uk/f/sage-x3-uk-announcements-news-and-alerts/165845/alert-console-version-2-49-2-is-now-available ) so make sure you are on this version at minimum (Latest version of the Console is always best)
5. When setting up a Network mapped drive installation on your shared disk, having low latency is important to prevent long installation times, and for ongoing processing performance. It is therefore advised to have all X3 Application/Runtime servers, database servers and disk storage servers with the shortest possible network path, in order to get highest possible throughput AND lowest possible latency. e.g. located on the same network switch or same network subnet