Define our migration through properties
Rather than specifying individual parameters on migration commands, we can specify the -properties file_name.properties parameter to input a properties file containing properties that define our migration. By defining our migration settings in a properties file, we can make our migration process easily repeatable. The properties file can contain the following types of properties:
Property Description Migration Equivalent to the parameters specified for the migration commands. Not every command-line parameter can be specified as a parameter property; limitations are noted in the template migration.properties file. General Control tracing and debugging when the migration commands call external tools. For example, we can enable or disable trace and specify trace strings and locations.
Properties defined in the properties file take precedence over system properties, but parameters specified on the command line take precedence over those defined in the properties file.
Tip: Use the same file for all profile and migration types because any properties that do not apply are ignored.
Tasks
- Create the properties file.
A template migration.properties file is located in...
app_server_root/properties
The template contains instructions for defining properties and examples of the default values for the command-line properties. Copy the template migration.properties file to a new location, then modify the file to suit our migration.bprac
Alternatively, we can create our own properties file without using the template.
Define properties using the following formats:
- Parameter properties for all commands
- com.ibm.ws.migration.parameter.parm_name=value
For example:
com.ibm.ws.migration.parameter.traceString=*=info:Migration.SSPI=fine:Migration.Flow=finer
- Parameter properties for specific commands
- com.ibm.ws.migration.command_name.parameter.parm_name=value com.ibm.ws.migration.WASPostUpgrade.parameter.includeApps=true
- General tracing and debugging properties
- Tracing and debugging property definitions vary based on the command run, but use the following general format:
com.ibm.ws.command_family.command_name.parm_name
For example:
com.ibm.ws.migration.backupConfig.trace=true
com.ibm.ws.migration.backupConfig.logfile=C:\logs\myBackupLog.log
com.ibm.ws.scripting.traceString=com.ibm.ws.management.*=all:com.ibm.websphere.management.*=all- When we run a migration command, input the properties file on the -properties file_name.properties parameter.
For example:
/WebSphere/AppServer90/bin/WASPreUpgrade.sh /70backupDirectory /WebSphere/AppServer70 -properties /my90migration.properties
Properties that do not apply to the command are ignored.
Related:
Overview of migration, coexistence, and interoperability Use the migration tools WASPreUpgrade command WASPostUpgrade command WASMigrationAppInstaller command manageprofiles command backupConfig command restoreConfig command