WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Target profile considerations

Before you begin the process of migrating to a new version of WebSphere® ESB, you should be aware of these target profile considerations.

Creating the correct target profile for migration is an important part the migration process. It is strongly recommend that you created new target profiles when migrating your profiles. When you create a migration target profile, you must create it with the same node name, cell name, and augmentation levels as the WebSphere ESB version 6.0.x or 6.1.x profile or WebSphere Application Server profile, and if possible, the same host name.
Tip: If you have created your target profile beforehand, do not make any cell-level changes to the new version 6.2 node before migration, such as changes to virtual-host information, because these changes will be lost during migration. Instead, wait until after the node has been migrated before making any such changes. Otherwise, you will have to use the administrative console running on the deployment manager to manually remake all of the changes to the new cell after migration, such as any changes to the virtual-host and host-alias information.

The migration wizard and the command-line tools both contain built-in options to facilitate the creation of new target profiles.

Migration wizard

If you are using the migration wizard, regardless of what type of profiles you are migrating from, always choose the Create new profile option on the migration wizard panel to create a new profile in WebSphere ESB version 6.2 for migration. This option creates a new profile with the correct configuration settings for migration purposes.
Note: The migration wizard does not support migrating WebSphere Application Server profiles. You must use the command-line tools when migrating WebSphere Application Server profiles in full WebSphere ESB installations or in WebSphere ESB client installations.
Note: The migration wizard cannot run in a non-graphical environment. Examples of non-graphical environments include the i5/OS platform or telnet sessions. If you want to run migration in a non-graphical environment, use the command-line tools.

Command-line tools

If you are using the migration command-line tools, regardless of what type of profiles you are migrating from, use -createTargetProfile when invoking WBIPostUpgrade to create a new profile in the WebSphere ESB version 6.2 installation for migration purposes. For a full description of the migration command-line tools, refer to WBIPreUpgrade command-line utility and WBIPostUpgrade command-line utility.
Note: You can optionally use the manageprofiles command if you want to create target profiles for migration outside of the migration framework. An example is if you are preparing target profiles when a migration task is running.
For i5/OS operating system Note: If you are migrating on an i5/OS platform, you should be aware of the following considerations:
  • The target profile name must match the profile name of the source profile being migrated.
  • If you specify -createTargetProfile on the WBIPostUpgrade script, you may invoke the install_root/bin/enableJVM script to set the target profile JVM type to the desired value after the target profile has been migrated. The WBIPostUpgrade script ensures that the target profile is generated with the same JVM type as the source profile for the migration process.
  • If you manually generate the target profile using manageprofiles, you must ensure that the target profile JVM type matches the source profile JVM type. This can be done by invoking the install_root/bin/enableJVM script to set the target profile JVM type before invoking the WBIPostUpgrade script.
  • The [-profile target_profile_name] option of the enableJVM command must be used to prevent switching all profiles in the product install to the specified type.

Examples of profiles created using command-line tools

Note: In the following examples, use one of the following parameters for -templatePath, depending on the type of profile you are creating:
  • WebSphere ESB stand-alone server: <WAS_HOME>/profileTemplates/default.wbiserver
  • WebSphere ESB deployment manager: <WAS_HOME>/profileTemplates/dmgr.wbiserver
  • WebSphere ESB custom nodes: <WAS_HOME>/profileTemplates/managed.wbiserver
  • WebSphere Application Server stand-alone server: <WAS_HOME>/profileTemplates/default
  • WebSphere Application Server custom nodes: <WAS_HOME>/profileTemplates/managed

Example: Creating WebSphere Process Server profiles

Example: Creating WebSphere Application Server profiles


concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cmig_vtv_pre_target_profiles.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).