Chapter 7 Migrating Persistence Data to Backing Store : Migration Utility Usage and Parameters

Migration Utility Usage and Parameters
Usage
The general syntax for running the utility at the command line is as follows:

 
be-migration {-export -bdb|-import -db} [-input input_url] [-output output_url] -ear EAR_path or repo_path [-conn connection_string] [-partition BAR_Name:partition_id] [-help]

 
Example command to export from persistence to text files:

 
-export -bdb -input C:\mydir\bdb\FraudDetection-jdb -output C:\mydir\extract\output -ear C:\mydir\FraudDetection.ear

 
Example command to import from text files to a backing store.

 
-import -db -input C:\mydir\extract\output -conn "jdbc:oracle:thin:sa/sa@dbserver:1521:MIGRATION" -ear C:\mydir\FraudDetection.ear -partition "BusinessEvents Archive:1"

 
Persistence Database Migration Utility Parameters
 
Also Used
-bdb persistence_db_dir
-bdb is the default value.
-conn connection _string
be.migration.db.connection
<jdbc>:<vendor>:<drivertype>:<user>/<password>@<host>:<port>:<database>
The connection string specifies the JDBC driver string, the user and password, and the JDBC URL.
The user must have sufficient privileges to connect, create tables and write to and read from them.
-ear project_path
repourl
be.migration.project.path
The repo URL for the deployed BusinessEvents application. The URL format depends on the deployment transport used. Supported formats for the URL are tibcr, http, https, and file.
See Determining the TIBCO Repo URL for BusinessEvents in TIBCO BusinessEvents User’s Guide for a way to determine the repo URL.
be.migration.mode=export
Use -export -bdb to export data from a persistence database to comma-separated text files.
-export is the default option if the parameter is not specified
be.migration.mode=import
Use -import -db to import data from the exported comma-separated text files into a backing store.
-input input_url
be.migration.input.path
If used in a command with -export -bdb (exporting persistence database files) then the value is the path to the persistence database files (persistence_db_dir) to be exported.
If used in a command with -import db then the value is the path to the comma-separated text files for the import (the text files that were exported in a prior command.
-output output_url
be.migration.output.path
If used in a command with -export -bdb (exporting data from a persistence database) then the value is the path to the comma-separated text files to be created. You must create this directory before executing the command.
-partition BAR_Name:partition_id
be.migration.partition.id
The value is a BAR resource name, followed by a colon, followed by a partition ID.
The partition ID is an arbitrary numeric value to identify a BusinessEvents partition. Each rule session (BAR) uses a different partition number.
This partition ID is stored in the CacheID column of the backing store database.
If you use engine properties in the TRA file, note that two properties are used to provide the two parts of the value:
The value of be.migration.bar.name is the name of the BAR resource.
The value of be.migration.partition.id is the numeric ID.
Note Ensure that you use the same partition ID for the BARs here and in the backing store configuration.