Agile Business Suite Release 7.0 does not include Host Builder. If you are still using Host Builder in releases prior to 3.3, you must first migrate your application to Developer, following the instructions in the EAE to Agile Business Suite Migration Guide.
You must then migrate your application from 3.3 to Agile Business Suite 7.0 following the instructions in the EAE 3.3 to Agile Business Suite Migration Guide.
Notes:
Change in naming convention – In previous products, the naming convention for the first node in the directories for the runtime software has been LINCxx and LINCxxSYS. For example, LINC17/LSS, LINC17/1/LINCSUPPORT, LINC17/WFL/ GENERATE, LINC17SYS/BLD, etc. The naming convention for these directory nodes is now NGENxx and NGENxxSYS. For example, NGEN28/LSS, NGEN28/1/ LINCSUPPORT, NGEN28/WFL/GENERATE, NGEN28SYS/BLD, etc. If you have jobs or non-EAE applications that refer to any of these files, you must change the first directory node from LINC17[SYS] to NGEN28SYS].
The naming convention for two SLs has also changed. LINCxxSERVICES is now NGENxxSERVICES. For this release it is NGEN28SERVICES. LINCxxMLSSUPPORT is now NGENxxMLSSUPPORT. For this release it is NGEN28MLSSUPPORT.
User GLI programs – If your existing user GLI programs are sending data to ispecs that have the system MAINT field present (standard ispec or a memo ispec with an automaint profile) then you must change the field name MAINT to USERMAINT.
For applications that use the Remote Access Server and are being migrated from EAE, it is necessary to disable and enable CCF after the application has been deployed from AB Suite. This ensures that the RATL view for the application reads the new LINCCNTL file.