Upgrading V.17.3 and V.18.x Applications

You can use the Package and Deploy Wizard or the Deployment Packager actions to upgrade your applications from release V.17.3 or V.18.x. The Deployment Packager can include files from release V.17.3 or V.18.x in the Web archive (WAR) files; however, the packager itself only runs on the V.19.1 and later core.

The principle reasons for using the Deployment Packager to do this kind of update are:

• Standard Process. The upgrade process described below is one that ARCHIBUS uses to test its own applications for update.
• Web Archive File. If your site typically uses a staging server to merge files and test them on the V.19.1 or later release, the Deployment Packager can produce a Web Archive (WAR) file from this staging server. You can then deploy this archive to your production server using the standard procedure.

When upgrading from these earlier releases there are some manual steps you must take before creating the deployment package. The following procedure describes these manual steps, after which you can create the deployment package using the wizard, or by running the deployment packager actions directly.

The Update Process for V.17.3 and V.18.x

To create Web Archive files for earlier releases in the Deployment Packager archive:

1. Files: Copy your data and extension files:
   • Project Data. Use the operating system to copy the \projects subfolders from your V.17.3 or V.18.x production server to a V.19.1-or-later staging server. Before copying, remove this subfolder from the staging server to make certain you completely replace its contents when you copy the files to it.
   • appContext-services.xml file: When deploying project data and application extensions from a release prior to V.19,1, you need to back up the schema\ab-products\common\resource\appContext-services.xml file that is installed with V19.1. After deploying the application files, you will copy this file into the schema\ab-products\common\resource folder.
   • Per-site Data. To preserve your ad-hoc view and report definitions, use the operating system to copy the schema\per-site folder from your V.17.3 or V.18.x production server to a V.19.1-or-later staging server. Remove this subfolder from the staging server before pasting the copied files into it to ensure you completely replace the contents of the folder.
   • Extensions: Use the operating system to copy the \ab-projects subfolders from your V.17.3 or V.18.x production server to your V.19.1-or-later staging server. Remove this subfolder before copying to make certain you completely replace it.
   • Libraries: Copy the libraries, excluding the archibus-solutions-common.jar from WEB-INF\lib\archibus-*.jar to your V.19.1-or-later staging server. When you do so, replace the existing files.

Note: The archibus-solutions-common.jar from previous Web Central releases is not compatible with V.19.1 and later. When deploying project data and application extensions from a previous release to a V.19.1 or later server, do not replace the WEB-INF\lib\archibus-solutions-common.jar to the new deployment.

2. Preferences: Migrate any changes you made to the WEB-INF\config\* files or authentication files by making the corresponding edit to one of the V.19.1 or later .preferences files.
3. Packages: Create your new Web Archive package in one of the following ways:

   • From the application server, use the System Administration/System Administrator/Package and Deploy Wizard task to create your packages by running the wizard and making the selections appropriate for your deployment. See Using the Package and Deploy Wizard .

   or

   • Run the Deployment Packager actions directly:

1. Start the V.19.1-or-later application server.
2. Run the System Administration/System Administrator/Package Data action to create the mysite-data.war file.
3. Run the System Administration/System Administrator/Package Extensions actions to create the mysite-extensions.war file.

Note: Be sure to copy the appContext-services.xml file from its backup location into the schema\ab-products\common\resource folder after deploying the application files.

4. You can now use the standard Deployment Packager procedures to migrate and deploy these applications. See Deployment Packager Actions: Overview.

ARCHIBUS Workflow Rule Table (afm_wf_rules) Definitions

Newer ARCHIBUS applications use the service-style definitions in the ARCHIBUS Workflow Rules table (that is, these applications use one entry per class or service), rather than the method-style definitions (that is, using one entry per method). As such, you do not need to update your project database’s Workflow Rule definitions for the upgraded logic to work (for example, the logic in AbCommonResources).

You do need new database elements for new applications – such as Workflow Rules, Process Navigator entries, messages table entries and other application elements. To merge these into your project database, use the Database Update Wizard which handles all required elements.