Migrate a stand-alone server from an older version to a
newer version of WebSphere® ESB using
the command-line tools.
Before you begin
Note: When you migrate using the command-line
tools, you can migrate either a
WebSphere ESB profile
or a
WebSphere Application Server profile.
Make sure that the following conditions are met before
you start the migration process:
- Ensure that your system meets all hardware and software requirements
for installing WebSphere ESB version 6.2, and
that you have enough space (including temporary space) for your installation.
See http://www.ibm.com/support/docview.wss?uid=swg27006912 for more information.
- If you are migrating on the same physical computer system on which
the older version of WebSphere ESB resides,
you have installed the new version of WebSphere ESB side-by-side
the old version on the same system.
- The profile in the older WebSphere ESB which
you are migrating is stand-alone (not federated to a cell).
- Sufficient disk space is available for the migrated profile and
its backup. See Premigration considerations for WebSphere ESB for disk space
requirements.
Make sure that you have completed the following tasks before
you start the migration process:
- Back up the databases that support version 6.0.2.x or version 6.1.x WebSphere ESB components.
Procedure
- Log on using one of the following procedures,
depending on your operating system.
On i5/OS® platforms: Log
on with an i5/OS user
profile that has *SECOFR user class or *ALLOBJ special
authority.

On Linux® and UNIX® platforms: Log on as the
root user.
On Windows® platforms: Log
on as a member of the Administrator group.
- Stop the version 6.1.x or 6.0.2.x server if
it is running on the node to be migrated. Use the stopServer command
from the profile_dir/bin directory
for the profile of the affected server, or stop the server from the
profile's First steps console.
For more information about the stopServer command
see the stopServer command. Use
the following syntax:Note: On i5/OS platforms,
you must run the scripts under QSHELL. To start a QSHELL session,
open a CL command prompt and type QSH.
On i5/OS platforms: profile_root/bin/stopServer server_name

On Linux and UNIX platforms: profile_root/bin/stopServer.sh server_name
On Windows platforms: profile_root\bin\stopServer.bat server_name
If security is enabled, use one of the following commands instead.
The user name provided must be a member of the operator or administrator
role.
On i5/OS platforms: profile_root/bin/stopServer server_name -username user_ID -password password

On Linux and UNIX platforms: profile_root/bin/stopServer.sh server_name -username user_ID -password password
On Windows platforms: profile_root\bin\stopServer.bat server_name -username user_ID -password password
On the Windows operating system, even
if security is enabled, the -username and -password parameters do
not have to be specified if the server is running as a Windows service. In this case, the parameters
are automatically passed into the script that the Windows service uses to shut down the system.
Note: Stop the server before beginning the migrating
process. By default, all servers on the node are stopped before the
migration completes.
- Run the WBIPreUpgrade command,
specifying the migration backup directory name and the existing WebSphere ESB directory
name. The WBIPreUpgrade tool saves
selected files from the install_root and profile_root directories to
a backup directory you specify. See the WBIPreUpgrade command-line utility for
details.
- Run the WBIPostUpgrade command,
specifying the migration backup directory. The WBIPostUpgrade tool
restores the environment in the backup directory into the new WebSphere ESB stand-alone
server installation. See the WBIPostUpgrade command-line utility for details.
Important: Use the
-createTargetProfile parameter
when invoking
WBIPostUpgrade. This option creates
a matching required new target profile for migration. For more information
about target profiles, refer to
Target profile considerations.
Note: If you are migrating on an
i5/OS platform, the target profile name
must match the profile name of the source profile being migrated.
- If you are migrating from version 6.0.2 to version 6.2.x you need to create the common database.
For information, see Creating
the common database and configuring the recovery subsystem when migrating
from version 6.0.2 to version 6.2.x.
- If required, manually update the databases
used by WebSphere ESB. Some database changes required by new versions of WebSphere ESB are
made automatically. However, if you have Business Space configured,
or if the server has insufficient permissions to access the database
schema, or other database-specific requirements are not met, you must
update the database manually. For more information see Upgrading databases for migration.
Results
You have now migrated your stand-alone server.
What to do next
Verify that the migration has been successful.