Upgrading Only Specific Web Central Applications

Note: This topic describes how to use the deployment packager actions to upgrade only specific Web Central applications. You can also accomplish this using the Package and Deploy Wizard by selecting the applications you want to update on the Specify Update Type tab. See. Using the Package and Deploy Wizard .

You might need to upgrade only specific Web Central applications. This occurs when you have changes to just one of the applications of a domain (for example, On Demand Work), yet want to update or add a newer version of another application in the same domain (for example, Preventive Maintenance).

To upgrade only specific Web Central applications:

1. On a staging server, install the newer version of the stock ARCHIBUS.
2. Use a file comparison program to show which files are new, existing, or unchanged between your files and the stock ARCHIBUS files within the domain subfolder.

   Note: Tools such as Araxis Merge enable you to see file by file which files are new, old, or unchanged. These tools also enable you to identify the specific changes in altered files, and copy each change over using the mouse. Araxis Merge is found at
   http://www.araxis.com/merge/ .

   Do the comparison on the Domain subfolder as a whole (for example, ab-products\bldgops\*), because there are some dependencies on common views and on common workflow rules within each domain.

   • Move files that are unique to your deployment into the subfolder.
   • Merge files that are changed.
3. If any files are workflow rules, recompile the rules.
4. Retest your changes and any stock ARCHIBUS features affected by your changes.
5. Package the extensions from this staging server.
6. Redeploy the extensions on your production server.