4.4 Export and backup Business Activity Monitoring metadata

Note: Do not perform the procedure described in this section if you wish to continue using BAM and the old BAM database with LiveCycle ES3. If you wish to use a new database for BAM with LiveCycle ES3, perform the procedure and reinstall BAM using LiveCycle ES or LiveCycle ES2 installation media after upgrading to LiveCycle ES3.
This task is required only if you wish to reuse an existing Business Activity Monitoring installation.

Before you begin, export the metadata so that the customized BAM objects are available to be imported into LiveCycle ES3. This applies customized objects only - do not export auto-generated objects. If you installed BAM Server manually, you must uninstall it manually as well.

    4.4.1 Export the BAM Server metadata

    1. In a browser, type http://[hostname]:[BAM port]/bam/workbench and log in to BAM Workbench.

    2. Click Application Workbench > Event.

    3. Select all events except for VC_SYSTEM_EVENTS, VC_TASK_EVENTS and your customized events.

    4. Click Delete Event(s) and then click Delete Dependencies when prompted.

    5. Delete all views except for VC_SYSTEM_VIEW, VC_TASK_VIEW and your customized views.

    6. Click Delete View(s) and then click Delete Dependencies when prompted.

    7. Repeat steps 5 and 6 for Contexts, Dimensions and Cubes, substituting the appropriate VC_SYSTEM_<>, VC_TASK_<> objects.

    8. Delete all JAR files except for your customized JAR files. Click Delete This Jar... and then click Delete Dependencies when prompted.

    9. Click the Administration Console tab and click Import/Export.

    10. When prompted, choose Export Metadata to a JAR file on the server, enter the server location and click OK.

      Note: Save the exported JAR file to a location available to the LiveCycle ES2 installer.

    11. Stop the application server and delete the 3 tables in BAM metadata database.

    // Ethnio survey code removed