BMC Middleware Automation enables you to migrate or clone a WebSphere Configuration, so that you can install the generated Configuration on a target application server of a different WebSphere version. You can use the migration feature for the following objectives:
|Objective||Supported migration paths|
|Migrate a WebSphere (Network Deployment Edition) Configuration to a later version of WebSphere|
Clone a WebSphere (Network Deployment Edition) Configuration for the same version of WebSphere
For any WebSphere Application Server Configuration that you migrate or clone, you have the option of adjusting the topology in the target Configuration. For example, you might want to migrate a WebSphere Configuration from a 10-node cell to a 5-node cell. You can choose whether to migrate the following topology elements and which specific elements of each type to include in the target Configuration:
You can also migrate Configuration templates (Configurations that were created with the "Configuration Packager" wizard) using the Packaged Configuration migration mode.
You can use the Packaged Configuration migration mode starting with BMC Middleware Automation version 8.6.00.006.
You can also migrate a Configuration between different application servers. Currently, BMC Middleware Automation supports migration between WebSphere (full profile) and WebSphere Liberty Profile. For the specific use cases of such migration, see Migrating Configurations between different application servers.
Ensure that your source Configuration meets the following requirements:
The source Configuration that you want to migrate is compatible with the latest version of BMC Middleware Automation. If necessary, upgrade the Configuration.
During the migration, take into account the following considerations:
On the first page of the Migrate Configuration wizard, enter the following information and then click Next:
The source Configuration that you want to migrate or clone.
This field is populated according to the Configuration that you selected in the previous step. You can browse and select a different Configuration.
Source Server Profile
The file name and path of the Server Profile that represents the source application server.
The source Server Profile is required in the following scenarios:
Source Application Server
The version of the WebSphere application server in the original Configuration.
Target Application Server
The version of the WebSphere application server in the Configuration to generate.
|Migrate Liberty Applications||(WebSphere Liberty Profile) Select this check box if you want to migrate Liberty applications.|
On the next wizard page select the workspace folder in which to save the generated Configuration.
In addition, review the suggested name for the new Configuration and optionally specify a different name. The default name is originalConfigName_migr_to_targetAppserver.
Then click Next.
If your source Configuration is from a WebSphere Liberty Profile, skip now to step 6.
For a regular WebSphere (full profile) source Configuration, select the migration mode on the Migration Mode Selection page. Then, depending on the selected mode, use the next few wizard pages to select the specific topological elements of each type that you want to include in the Configuration:
|Mode||Elements available for selection|
|Cell migration||Nodes, clusters, servers, applications|
|Node migration||Nodes, servers, applications|
|Cluster migration||Clusters, servers, applications|
|Server migration||Servers, applications|
|Packaged Configuration migration||All elements in the specified Configuration|
Note, that 'Application' is an application element in the Configuration Snapshot, and not the actual .ear application file.
BMC Middleware Automation does not validate the applications that you include in your Configuration for compliance with any new standards that might exist in the target WebSphere version. You can use the WebSphere Application Migration toolkit to ensure that the applications are updated.
On the Migration Options page, adjust the tokenization settings (that is, select which items you want to tokenize), and then click Next.
By default, tokenization is performed on the names of all cells, nodes, node hosts, classification labels, clusters, and servers, as well as on absolute paths.
If you are performing the migration to WebSphere Liberty Profile, the Migration Options page does not display, and you proceed directly to step 6.
Within the cli subdirectory of your BMC Middleware Automation installation, execute a command that invokes the migrateConfiguration script. The following options are available for the migration operation:
Migration mode, according to the highest level topological element that you want to migrate. Choose one of the following values:
|Full path to the source Configuration file that you want to migrate.|
Full path to the Server Profile that represents the source application server.
The source Server Profile is required if you want to retrieve classification labels or if your Configuration includes applications for deployment.
The version of the WebSphere application server in the Configuration to generate. Choose one of the following values:
|Full path and name of the generated Configuration and the directory in which to store it.|
The names of the applications to migrate (a comma-separated list).
For all applications, use an asterisk *.
The names of the servers to migrate (a comma-separated list).
For all servers, use an asterisk *.
The names of the nodes to migrate (a comma-separated list).
For all nodes, use an asterisk *.
The names of the clusters to migrate (a comma-separated list).
For all clusters, use an asterisk *.
Full path to the log4j.properties file, for logging output.
If you do not provide information for use of the log4j file, the stdout and stderr files are used instead for logging output.
Path to a directory in which to store temporary data during the migration process.
If not specified, a temporary folder is created automatically.
|(Optional) Path to a directory in which to store the migration report.|
|Whether to tokenize the cell name, either |
|Whether to tokenize node names, either |
|Whether to tokenize the names of node hosts, either |
|Whether to tokenize classification labels, either |
|Whether to tokenize cluster names, either |
|Whether to tokenize server names, either |
|Whether to tokenize absolute paths, either |
The following example migrates a full Cell configuration from WebSphere 6.1 to WebSphere 8.5:
You can now install your new, migrated Configuration at the relevant target application server, as described in Installing a Configuration.
Before installing the new, migrated Configuration, ensure that the Server Profile that you will use during the installation operation contains token values for the tokens in the Configuration. Alternatively, you can synchronize the tokens during the installation operation.