Archibus Package and Deploy Wizard Overview

The Archibus Package and Deploy Wizard (available on the Navigator at System / System Administrator / Package and Deploy Wizard ) provides an automated process for migrating your data, extensions, and settings when upgrading to a newer version of Archibus.

The Package and Deploy Wizard features offer the following advantages over manually migrating changes:

• Your back-up, prototype-to-production, and update processes can be consistent and repeatable.
• Your standard processes migrate without hand editing.
• Your data and extensions are automatically combined into Web Archive (WAR) files that can be backed up and transferred easily between computers and offices. You can then deploy these WAR files using the standard procedures supported by your application server.

Use the Package and Deploy Wizard to preserve the following when upgrading:

Component to Preserve	Description
Data	The wizard backs up your data files, such as enterprise graphic s files (.swf, .json,, etc) that reside on the application server
Extensions	The wizard merges your personalized extensions with the files provided with a new Archibus release. The wizard can migrate any applications that are coded to the Archibus best practice guidelines. See Application and Workflow Rule Guidelines.
Settings	The wizard preserves Archibus configuration and authentication preferences unique to your site are preserved, while merging them with new preferences and defaults supplied with a newer Archibus version

The Package and Deploy Wizard divides the Archibus product into groups of files that should be upgraded together. For instance, the Archibus core product contains related files, services, and third-party libraries that Archibus develops and tests as a unit. As such, you should always upgrade Archibus core files together as one unit.

Similarly, each individual domain area, such as the Space domain, has forms, reports, workflow rules, and services that support that particular domain. Again, you should always upgrade domain files as a unit.

Within reason, you can mix-and-match different portions of the product. For instance, you can keep all of your application domains as they are -- with your personalized workflow rules and forms -- and upgrade only the Archibus core. Alternately, you may wish to preserve your personalized workflow rules and forms for just one domain, Building Operations for instance, but upgrade all other portions of the product.