Upgrading Enterprise Deployments Using the Deployment Packager Actions

Enterprise deployments are distinguished from single-user or workgroup deployments in the following ways.

Enterprise deployments:

• Use a different application server than the default JEE server (for example, Tomcat, WebSphere, or WebLogic).
• Have the application server and database server on different machines.
• Have separate backup procedures and schedule for the database server.
• Use a prototyping or staging server to test changes to extension files before putting them into production.

These differences affect the upgrade process in the following ways:

• You Package Extensions on the staging server where you have unit tested them before putting them into production.
• You copy the mysite-extensions.war archive file to the production server using the operating system.
• You run the Package Data action on the production server where the live data, such as users’ ad-hoc views, My Favorites views, and dashboards exist.
• Most staging servers have preferences and locations identical to the production servers to facilitate deployment. When these differ, the preference entries to use are those of the production server, as these would be the settings in the final deployment file.

If you are a workgroup deployment, see Upgrading a Workgroup Deployment to a Newer Version of Web Central.

To view a flowchart of the enterprise upgrade process, see Running the Package and Deploy Wizard for Enterprise Deployments.

Using the Deployment Packager Actions to Upgrade

Note: The following procedure is for advanced users who prefer to directly edit the application-update.properties file and to run the deployment packager actions, rather than using the Package and Deploy Wizard. Using the wizard is the simplest way to upgrade. See Using the Package and Deploy Wizard.

To upgrade an enterprise deployment:

1. Delete the old ARCHIBUS. Remove the previous version of ARCHIBUS from your application server. 
   • On Tomcat or Jetty, remove the webapps\ARCHIBUS files except for the archibus.war file.
   • On WebSphere, use the administrator console to remove the previous WAR deployment.
   • On WebLogic, use the administrator console to remove the previous EAR deployment.
2. Back up the server: Run your usual backups on your application server and database data to guard against any errors in creating the packager preferences or in compressing the Web Archive (WAR) files.
3. Edit the application-update.properties file: On the staging server, edit this file to reflect the location of your extensions and project data. See Editing Your Application Update Properties.

   Note: To facilitate deployment, most staging servers have preferences and locations identical to the production servers. However, if these preferences differ, enter the .preferences of the production server, as those preferences would be the settings in the final deployment file.

4. On the Staging Server, run the Package Extensions action: This action creates the mysite-extensions.war file.
5. Copy the mysite-extensions.war file from the staging server to the production server using the operating system.
6. On the Production Server, run the Package Data action. This action backs up your database and data files to mysite-data.war file.
7. On the production server, use the operating system to copy the stock archibus.war file from your upgrade DVD to the \webapps\archibus subfolder.
8. On the production server, copy the license file: If you have been issued a new license file (afm-licenses.xml), copy it to your \webapps\archibus\config subfolder to ensure that it is part of your new deployment file.
9. On the Production Server, run the Package Deployment File action. This action merges the mysite-data.war and the mysite-extensions.war into the stock archibus.war file. This updated archibus.war file contains all the files needed to re-establish your application server.
10. Redeploy the new ARCHIBUS:
    1. On Tomcat or Jetty, use the WinZip program to unzip the new archibus.war file beneath the \archibus folder.
    2. On WebSphere, use the administrator console to deploy the new WAR deployment.
    3. On WebLogic, use the standard ARCHIBUS installation steps to create an EAR file. Then use the administrator console to deploy this new EAR deployment.
11. Reload the database:
    1. For Sybase and MS SQL Server databases, move the .db or .mdf file included in the backup from the \database-backups folder to the \databases folder.
    2. For Oracle databases, restore the .dmp file.

Deploying to Clustered Servers or Instances

You may have multiple instances of the ARCHIBUS applications deployed to different servers, or to different Java instances running on the same server, but perhaps with dedicated processor or memory space. In this case, use the final archibus.war file to deploy the identical set of files to each server or instance.

Deploying Your Extensions from a Staging Server to a Production Server

If you have developed and tested your extensions (new or altered views and workflow rules) on the development or staging server, and need to deploy them to the production server, without losing the production user data (user favorites, and graphics files) that are already created on that production server, use the procedure above to do so. You simply use your existing stock archibus.war file rather than a new one.

Deployment Packager Use Cases for Enterprise Deployments

For advanced users who prefer running the deployment packager actions without using the wizard the following use cases are provided:

Upgrading Only Specific Web Central Domains

Upgrading Only Specific Web Central Applications

See Also

Migrating Nonstandard Configuration Files

Identifying Duplicate Files