CentralCommand Technical
Intro The upgrade to CentralCommand 2.0 will soon be released and will represent a significant change for your users. The upgrade will also present some technical changes and in this article I’d like to highlight a few of the most important changes. More information on the upgrade for AGRESSO can be found in the technical guidelines document at http://techguide.agresso.com. Upgrading The upgrade to CentralCommand 2.0 will also require upgrading to AGRESSO Business World (ABW) 5.5 service pack 1. This will make the process more complex than the last few upgrades of CentralCommand which have all required ABW 54 SP4. Fortunately, the upgrade scripts are for the most part run via several upgrade GUIs to make that part easier. Here are a few other things to note about the upgrade to ABW 5.5 SP1 and CentralCommand 2.0 There are significant changes being made at the database level. This will mean that the actual upgrade of the database will take more time than past upgrades. It also will require careful testing of any custom reports as the underlying database structure may have changed thus requiring the reports to be updated. The upgrade will require a separate test server and test workstations. It is not possible to have both ABW 54 SP4 and 55 SP1 installed at the same time, so the test environment will required a dedicated test server. Likewise, it is not possible to have both versions installed on client workstations. This includes workstations using the centrally configured client as the ABW VBA install provided with 55 SP1 is not compatible with 54 SP4. AGRESSO Online Help Help files for ABW 55 SP1 and CentralCommand 2.0 have been converted from Windows help files to an html-based solution. This will require a Windows IIS server running IIS version 5.0 or 6.0 and could be either the ABW application server or a dedicated IIS server. If Internet Explorer’s built in pop-up blocker has been enabled on client workstations, it will be necessary to add the IIS server to the exception list to allow online help for ABW to function properly. .NET Trusts The ABW 5.5 SP1 client makes use of Microsoft’s .NET Framework. For workstations running in a central configured environment, the workstation must be configured to trust the ABW assemblies. To achieve this, modifications must be done to the .NET configuration files on each workstation. There are several methods to accomplish this and those are documented in the technical guidelines document mentioned above.
|