Database Changes

Database changes can be migrated by importing the table records into the new database. This might include changes made to the Navigator, Workflow Rules table or the Role Processes table.

For example, Navigator entries exist as records in the afm_ptasks table. You will need to find which records you have created and export these to Excel. Then you can import these into the new database.

View Files and Javascript Files

To migrate changes made to axvw view files and javascript files you will first need to locate the files on the file system. If the files were created using the View Definition Wizard, then they have been created in a subfolder under the archibus/schema/per-site folder.

You will need to copy those axvw and js files to the new server.

Using the Package and Deploy Wizard to Migrate Changes

There is a view called the Package and Deploy Wizard which will let you select which applications you want migrated to a new server. For example, if you have modified Capital Projects / Projects and you want to bring those changes to the new server, you will go to the Deploy and Package Wizard and use this to package up the Projects application.

Open the Package and Deploy Wizard found under System / System Administrator / Package and Deploy Wizard . Under the second tab "Specify Deployment Type", select "Enterprise Deployment" and indicate that this is the staging server. Under "Specify Update Type", select the application domain, in this case, Capital Projects. The wizard will zip up the entire Capital Projects folder to an archive file and then tell you where they have created this file for you.

Go to the file system and copy that zip or war file to the new server. On the new server, run the Package Deploy Wizard to remove the old archived Capital Projects folder and replace it with the new archived file. Under Specify Deployment Type, select "Enterprise Deployment" and indicate that this is the production server.