|
Note: LiveCycle ES3 is the last release to support BAM. If
you wish to continue using BAM with LiveCycle ES3, skip this section.
If you do not wish to continue using BAM, it is recommended that
you uninstall it by performing the steps described in the section below.
When you uninstall your existing LiveCycle installation, BAM
will be removed along with it. Because some folders might not be
removed during uninstallation, you should ensure that BAM has been
cleanly uninstalled before you attempt to reinstall BAM.
Important: If you wish to continue using BAM with
LiveCycle ES3, do not perform the steps below.
Uninstall BAM Server:Stop BAM
Server.
Undeploy the BAM Server EAR file by doing one of the following: (JBoss only) Removing Lava_Adobe.ear from [bam root]/server/<profile_name>/deploy
directory.
(WebLogic only) Undeploy and delete the old BAM Server
EAR file using WebLogic Server Administration Console
(WebSphere only) Undeploy the BAM Server EAR file
using WebSphere Administrative Console.
(JBoss only) Remove the following files:
Delete all the files from the recovery log directory and
logging directory that have names similar to the following patterns:
filestore*.dat
DEFAULTRECOVERYLOGGER_*
chkpoint*
Review the contents of the [bam root]\bin folder and,
if any chkpoint* files exist, delete them.
Use your database management tools to drop the database tables
that store the BAM Server metadata.
UNCOMMITTED_TID
ALLOCATED_UID
METADATA_OBJECTS
|
|
|
