Follow this procedure only if you are upgrading from an ALBPM WE (WorkSpace Extensions) 5.7
environment and want to use ALI Collaboration as the back-end storage for ALBPM
processes attachments.
Important:
The first time you start an upgraded Process Execution Engine in 6.0 it will
migrate its database structure. Before running this attachments migration
procedure, make sure your newly upgraded Engine has been started at least once in
the new ALBPM 6.0 environment.
Important:
To prevent data corruption, the Process Execution Engine must be stopped while
running this procedure.
The migration of existing ALBPM WE 5.7 attachments to the new ALBPM 6.0
installation is automated with Ant scripts. You must install Apache Ant version 1.6.5
in order to run the migration script. Refer to the ALBPM Ant Tasks for
details own using Ant with ALBPM.
- Make sure Ant is configured and running on your environment.
- Create a build.xml script file like the following
example (you may also download it from http://edocs.bea.com/albsi/docs60/resources/upgradeguide/build.xml).
Make sure you change all property values in the script to match your
environment. Refer to the ALBPM Ant Tasks for
details about the <fuego:migrateWE57to60> task.
<project name="ALBPM WE Migration" default="Migration573_60_we"
basedir="." xmlns:fuego="antlib:fuego.tools.ant.enterprise">
<description>
Example script for migrating ALBPM 5.7 WE attachments to ALBPM 6.0.
</description>
<!-- Change these properties to match your environment -->
<property name="bea.home" value="C:/bea/albpm6.0"/>
<property name="fuego.basedir" value="C:/bea/albpm6.0/enterprise"/>
<property name="engine.name" value="engineStandalone"/>
<target name="Migration573_60_we">
<fuego:migrateWE57to60 action="migrate_mappings" engineId="${engine.name}"
directoryFile="${fuego.basedir}/conf/directory.xml">
<!-- Change these connection properties to your MS-SQLServer database with ALBPM WE
5.7 attachments -->
<msSqlServerConfiguration host="we-standalone" port="1433"
user="processdbinstalluser" password="password"
database="processdbInstall"/>
<!-- For Oracle, use the following instead of <msSqlServerConfiguration>:
<oracleConfiguration
host="hostname" port="1433"
user="processdb" password="password"
sid="sidname" schema="processdb"/>
-->
</fuego:migrateWE57to60>
<fuego:migrateWE57to60 action="migrate_attachments" engineId="${engine.name}"
directoryFile="${fuego.basedir}/conf/directory.xml">
<!-- Change these connection properties to your MS-SQLServer database with ALBPM WE
5.7 attachments -->
<msSqlServerConfiguration host="we-standalone" port="1433"
user="processdbinstalluser" password="password"
database="processdbInstall"/>
<!-- For Oracle, use the following instead of <msSqlServerConfiguration>:
<oracleConfiguration
host="hostname" port="1433"
user="processdb" password="password"
sid="sidname" schema="processdb"/>
-->
</fuego:migrateWE57to60>
</target>
</project>
- Open a command-line session and run the migration script using Ant.
Example on Windows:
C:\>cd folder_containing_script
C:\>ant -lib c:\bea\albpm6.0\enterprise\ext -lib c:\bea\albpm6.0\enterprise\lib
Example on Unix:
$ cd directory_containing_script
$ ant -lib /bea/albpm6.0/enterprise/ext:/bea/albpm6.0/enterprise/lib
The script will output informational messages about its progress. Example
output:
C:\migration>ant -lib C:\bea\albpm6.0\enterprise\lib -lib C:\bea\albpm6.0\enterprise\ext
Buildfile: build.xml
Migration573_60_we:
[fuego:migrateWE57to60] fuego base dir [C:\bea\albpm6.0\enterprise]
[fuego:migrateWE57to60] setting bea.home [C:\bea\albpm6.0]
############## Product: AquaLogic Business Process Management
############## Application: BEA AquaLogic(TM) BPM Enterprise Standalone
############## Component: enterprise
############## Release: 6.0
### bea.home: C:\bea\albpm6.0
[fuego:migrateWE57to60] Starting ALBPM WE Migration - 5.7 to 6.0 -
[fuego:migrateWE57to60] IMPORTANT: Migration task migrates Attachment data from ALBPM WE 5.7 ProcessDB to ALBPM WE 6.0 Engine DB.
[fuego:migrateWE57to60] IMPORTANT: ALBPM Engine DB must have been migrated to 6.0 before executing this task!
[fuego:migrateWE57to60] Directory file has been specified: C:\bea\albpm6.0\enterprise\conf\directory.xml
[fuego:migrateWE57to60] Migrating to Engine 'engineStandalone'
[fuego:migrateWE57to60] Action = 'migrate_mappings'
Creating connector [ProcessDBConfiguration:SQL]
Creating connector [fuego:SQL]
Creating connector [organization:HYDROGEN]
OpenLog: verbosity level = 2
Creating connector [engineStandalone_ENGINE_DB_FUEGOLABS_ARG:SQL]
[fuego:migrateWE57to60] Migrating 1 Process-to-Project Mappings. Duplicate Process-to-Project Mappings will be overwritten.
[fuego:migrateWE57to60] Migration Task completed successfully.
[fuego:migrateWE57to60] Starting ALBPM WE Migration - 5.7 to 6.0 -
[fuego:migrateWE57to60] IMPORTANT: Migration task migrates Attachment data from
ALBPM WE 5.7 ProcessDB to ALBPM WE 6.0 Engine DB.
[fuego:migrateWE57to60] IMPORTANT: ALBPM Engine DB must have been migrated to 6.
0 before executing this task!
[fuego:migrateWE57to60] Directory file has been specified: C:\bea\albpm6.0\enter
prise\conf\directory.xml
[fuego:migrateWE57to60] Migrating to Engine 'engineStandalone'
[fuego:migrateWE57to60] Action = 'migrate_attachments'
Creating connector [ProcessDBConfiguration:SQL]
Creating connector [fuego:SQL]
Creating connector [organization:HYDROGEN]
OpenLog: verbosity level = 2
Creating connector [engineStandalone_ENGINE_DB_FUEGOLABS_ARG:SQL]
[fuego:migrateWE57to60] Migrating 2 instance properties.
[fuego:migrateWE57to60] Migrating 4 attachments.
[fuego:migrateWE57to60] Migration Task completed successfully.
BUILD SUCCESSFUL
Total time: 36 seconds
Note:
You may pass an additional -v (verbose) argument
to the ant command to get more detailed output,
including information about each attachment being migrated.
After running the script successfully, all attachments from your 5.7 WE
environment are now available on your new ALBPM 6.0 installation. You may now
re-start your Engine and login to ALBPM WorkSpace to verify your process instances
contain the old attachments.