You can invoke the Deployment Packager actions from the Package and Deploy Wizard . In this case the wizard guides you through the process. You can also invoke the Deployment Packager actions yourself from the Web Central Process Navigator if you want to control the steps more finely.
There are three separate packaging actions, because in some configurations, not all files are on the same application server.
Package Data: This action reads your data files (from the \projects subfolders) and your My Favorites and Dashboard files (from the \schema\per-site subfolders). It packages them into a distribution WAR file created inside your web application folder, for example, C:\Users\Public\ARCHIBUS\mysite-data.war.
Package Extensions: This action reads your application extensions from the \schema\ab-products and other subfolders you designate. It packages them into distribution WAR file created inside your web application folder, for example, C:\Users\Public\ARCHIBUS\mysite-extensions.war.
Package Deployment Files: This action merges your mysite-data.war and mysite-extensions.war file into the stock distribution file from ARCHIBUS – archibus.war. In doing so, it updates the stock ARCHIBUS distribution with your own data and extension files. The action also merges any changes you made to your .properties files into the archibus.war file. In this way, you can deploy this update
The procedures for using the packaging actions are different for enterprise and workgroup configurations. For more details, see:
The package actions use the folder locations listed in the application-update.properties file to determine what subfolders are packaged into each distribution WAR file. For more information on editing this file, see Editing Your Application Update Properties.
| Copyright © 1984-2014, ARCHIBUS, Inc. All rights reserved. |