Difference between revisions of "Upgrade Guide v2.0"

From ADF Docs
Jump to: navigation, search
(Register ADF Scripts as CommonSpot Resources)
(Register ADF Scripts as CommonSpot Resources)
Line 51: Line 51:
  
 
* To register ALL of the ADF 2.0 ThirdParty Scripts for the first time use:  
 
* To register ALL of the ADF 2.0 ThirdParty Scripts for the first time use:  
** http://{commonspot-site}/?configADF=1  ''(Any existing ADF scripts/resources will be skipped.)''
+
** http://{commonspot-site}/?configADF=1   
 +
''(Any existing ADF scripts/resources will be skipped.)''
  
 
* To update/re-register all the existing resources ADF 2.0 ThirdParty Scripts use:  
 
* To update/re-register all the existing resources ADF 2.0 ThirdParty Scripts use:  
** http://{commonspot-site}/?reconfiglADF=1 ''(Any missing ADF scripts/resources will also be added.)''
+
** http://{commonspot-site}/?reconfiglADF=1  
 +
''(Any missing ADF scripts/resources will also be added.)''
  
 
* In the case you want to only register (or re-register) a minimal set ThirdParty Scripts use these:
 
* In the case you want to only register (or re-register) a minimal set ThirdParty Scripts use these:

Revision as of 15:29, 2 March 2016

Current Version

Follow the guide below if you are upgrading to ADF v1.8.1.

Before upgrading, please review the v2.0 Release Notes

If you are upgrading from ADF v1.8.1 or earlier, then please follow the guides for previous ADF versions:

Upgrade

Follow the steps below to upgrade the ADF directory:

  1. Download the ADF v2.0 from the Community site project page.
  2. On your server, rename the "/ADF/" directory to "/ADF-1.8.x/".
  3. Create a new "/ADF/" directory. Setup any necessary security or permissions for the new "/ADF/" directory.
  4. Export the download ADF zip folder into the "/ADF/" directory.
  5. Copy the contents of the "/ADF-1.8.x/apps/" directory into the "/ADF/apps/" directory.
  6. Reset the ADF through the web browser with the following URL parameter:
    1.  ?resetADF=1

Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new.

Validate Upgrade

There are 2 methods to validate the ADF upgrade.

ADF Reset

  1. Reset the ADF through the web browser with the following URL parameter:
    1.  ?resetADF=1
  2. The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:
    1. ADF v2.0.0 has been reset successfully!
  3. Upgrade was successful and you are running the ADF v2.0.

ADF Version Output

  1. In the browser, add the following URL parameter:
    1.  ?ADFDumpVar=application.ADF.version
  2. This command with output the ADF version at the top of the page. If you see the following text:
    1. 2.0.0
  3. Upgrade was successful and you are running the ADF v2.0.


Post-Upgrade Steps

Register ADF Scripts as CommonSpot Resources

To register ADF 2.0 ThirdParty Scripts as resources in CommonSpot 10 use these URL parameters.

(Any existing ADF scripts/resources will be skipped.)

(Any missing ADF scripts/resources will also be added.)

Remember: You must be logged in to the CommonSpot site for these parameters to run.


For more information regarding the registration of ADF 2.0 ThirdParty Scripts as Resources in CommonSpot 10, please refer to the README information in the "/lib/scripts/scripts_2_0_READ_ME.txt" file.

Update Site Level Override Components

  • Any site level override ADF Lib components located in the "_cs_apps/lib/" folder will need to be renamed and the component "extends" updated to point to the latest version of the matching ADF Lib components.
Example: "_cs_apps/lib/scripts_1_1.cfc" needs to become "scripts_2_0.cfc" and the extends in the component tag
will need to point to "ADF.lib.scripts.scripts_2_0"

Update Custom App Lib Component References

  • Update any ADF Lib component references in your custom ADF Apps to the latest versions of the matching ADF 2.0 Lib components in the App's appBeanConfig.cfm file (in the root of the App directory).
Example: "addConstructorDependency(appBeanName, "scripts_1_2", "scripts"); " needs to become
"addConstructorDependency(appBeanName, "scripts_2_0", "scripts");"