Page tree
Skip to end of metadata
Go to start of metadata

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:

ObjectiveSupported migration paths
Migrate a WebSphere (Network Deployment Edition) Configuration to a later version of WebSphere
  • WebSphere 6.1 to 7.0, 8.0, or 8.5
  • WebSphere 7.0 to 8.0 or 8.5
  • WebSphere 8.0 to 8.5

Clone a WebSphere (Network Deployment Edition) Configuration for the same version of WebSphere

  • WebSphere 6.1 to 6.1
  • WebSphere 7.0 to 7.0
  • WebSphere 8.0 to 8.0
  • WebSphere 8.5 to 8.5

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:

  • Cell
  • Node
  • Cluster
  • Server
  • Application

You can also migrate Configuration templates (Configurations that were created with the "Configuration Packager" wizard) using the Packaged Configuration migration mode.

Note

You can use the Packaged Configuration migration mode starting with BMC Middleware Automation version 8.6.00.006.

You can perform the migration either through the GUI or through the CLI.

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.

Before you begin

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.

  • The source Configuration is a full Configuration Snapshot taken from the source application server.
  • The source Configuration file does not contain the tokenized values for integer and or boolean type fields (for example, ports). Othwerwise, BMC Middleware Automation might fail to load the source Confguration file and will not be able to continue with actual migration.
  • For each node in your topology you have the classification label specified in the Server Profile file. If the source Configuration Snapshot does not have Classification labels defined, then during the Cell or Node migration modes the ServerIndex element for the regular WAS Application Server types is not captured. Since BMC Middleware Automation needs to identify on which node these servers are created, classifications identify the servers on the correct nodes.

During the migration, take into account the following considerations:

  • On a server selection screen, avoid selecting dmgr and nodeagent server types, since during installation of the migrated Configuration, the dmgr (nodeagent) server-sensitive information (ports, hosts, discovery addresses etc.) is overridden, that may result in a server failure. You may, however, choose to select those server types, if you need to have server-specific elements (AdminService, CoreGroupBridgeService, JavaProcessDef etc.) for those specific server types migrated, or you plan to make additional changes to those server types.
  • If during the Cell and Node migration modes you select dmgr and nodeagent server types, the ServerIndex elements are not created for those server types to lower the risk of the sensitive port data overrides.

To migrate a Configuration through the GUI

  1. In the Application Navigator tree, right-click the Configuration file or Snapshot that you want to migrate or clone, and select  Migrate Configuration.
  2. On the first page of the Migrate Configuration wizard, enter the following information and then click Next:

    Field

    Description

    Source Configuration

    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:

    • (WebSphere full profile) If you want to retrieve classification labels
    • (WebSphere Liberty Profile) If you want to migrate Liberty applications (as indicated by the check box at the bottom of this wizard page)

    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.
  3. 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.

    Note

    If your source Configuration is from a WebSphere Liberty Profile, skip now to step 6.

  4. 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:

    ModeElements available for selection
    Cell migrationNodes, clusters, servers, applications
    Node migrationNodes, servers, applications
    Cluster migrationClusters, servers, applications
    Server migrationServers, applications
    Application migrationApplications
    Packaged Configuration migrationAll elements in the specified Configuration

    Note

    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.

  5. 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.

    Note

    If you are performing the migration to WebSphere Liberty Profile, the Migration Options page does not display, and you proceed directly to step 6.

  6. Review the migration summary, and click Finish.
    The migration process starts running and the new Configuration is generated. When migration is complete, a migration report is displayed, and the new Configuration is opened for display.

To migrate a Configuration through the CLI

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:

OptionDescription
-mode

Migration mode, according to the highest level topological element that you want to migrate. Choose one of the following values:

  • cell (the default)
  • node
  • cluster
  • server
  • application
  • packaged
-sourceConfigFull path to the source Configuration file that you want to migrate.
-sourceProfile

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.

-targetServer

The version of the WebSphere application server in the Configuration to generate. Choose one of the following values:

  • was61
  • was70
  • was80
  • was85
  • wlp85
-targetConfigFull path and name of the generated Configuration and the directory in which to store it.
-applicationNames

The names of the applications to migrate (a comma-separated list).

For all applications, use an asterisk *.

-serverNames

The names of the servers to migrate (a comma-separated list).

For all servers, use an asterisk *.

-nodeNames

The names of the nodes to migrate (a comma-separated list).

For all nodes, use an asterisk *.

-clusterNames

The names of the clusters to migrate (a comma-separated list).

For all clusters, use an asterisk *.

-log4j

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.

-workDir

Path to a directory in which to store temporary data during the migration process.

If not specified, a temporary folder is created automatically.

-report(Optional) Path to a directory in which to store the migration report.
-tokenizeCellName Whether to tokenize the cell name, either yes or no. The default is yes.
-tokenizeNodeNamesWhether to tokenize node names, either yes or no. The default is yes.
-tokenizeNodeHostNames Whether to tokenize the names of node hosts, either yes or no. The default is yes.
-tokenizeClassificationsWhether to tokenize classification labels, either yes or no. The default is yes.
-tokenizeClusterNamesWhether to tokenize cluster names, either yes or no. The default is yes.
-tokenizeServerNames Whether to tokenize server names, either yes or no. The default is yes.
-tokenizeAbsolutePathsWhether to tokenize absolute paths, either yes or no. The default is yes.

The following example migrates a full Cell configuration from WebSphere 6.1 to WebSphere 8.5:

Example

migrateConfiguration.sh -sourceConfig /opt/configs/was61_full_cell_config.xml \
-targetConfig /opt/configs/migrated_was61_to_was85.xml -targetServer was85 \ 
-mode cell -nodeNames * -serverNames * -clusterNames * -applicationNames *

Where to go from here

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.

Related topics

Migrating Configurations between different application servers

Migration of Configurations