Use the WBIPostUpgrade command for WebSphere® ESB to
retrieve the profile configuration that was saved by the WBIPreUpgrade command at the backupDirectory that you had specified.
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.
Details
The WBIPostUpgrade script for WebSphere ESB reads
the configuration from the backupDirectory to migrate
to WebSphere ESB version 6.2 and adds all migrated applications into the profile_root/installedApps directory for the new installation of WebSphere ESB.
Location
The command file is located and
should be run in the install_root/bin directory.
Syntax
The syntax is as follows:
Note: The -profileName parameter is not
supported on the i5/OS platform. If it is used, an invalid parameter exception
will be thrown.
Note: The -oldProfile parameter must precede
the -profileName (new profile) paramter.
Parameters
The parameters are as follows:
- backupDirectory
- This is a required parameter. The value backupDirectory specifies the backup directory path in which the WBIPreUpgrade tool stored the saved configuration and files and from
which the WBIPostUpgrade tool reads the configuration
and files.
- -username
- This is an optional parameter that is required if administrative
security is configured in the previous version of WebSphere ESB. The
value userID specifies the administrative user
name of the current WebSphere ESB (before
migration) installation.
- -password
- This is an optional parameter that is required if administrative
security is configured in the previous version of WebSphere ESB. The
value password specifies the password for the administrative
user name of the current WebSphere ESB (before
migration) installation.
- -profileName
- The default profile name
- -scriptCompatibility
Note: This parameter is ignored for WebSphere ESB version 6.1.x to version 6.2 migrations.
This is an optional parameter used to specify
whether migration should create the following version 6.0.2.x configuration definitions: - Transport
- ProcessDef
- SSL for 6.0.2
instead of the following
version 6.2 configuration
definitions:
- Channels
- ProcessDefs
- SSL for version 6.2
The default is true.
Specify true for this parameter in order to minimize impacts
to existing administration scripts. If you have existing wsadmin scripts or programs that use third-party configuration
APIs to create or modify the version 6.0.2.x configuration definitions, for example, you might want to specify
true for this option during migration.
Note: This is
temporary until all of the nodes in the environment are at the
version 6.2 level.
When they are all at the new level, you should perform the following
actions:
- Modify your administration scripts to use all of the version 6.2 settings.
- Use the convertScriptCompatability command
to convert your configurations to match all of the version 6.2 settings.
For more information see the convertScriptCompatibility command .
- -portBlock
- This is an optional parameter. The port_starting_number value specifies the first of a block of consecutive port numbers
to assign when the command script runs.
- -replacePorts
- This optional parameter is used to specify how to map port values
for virtual hosts and web-container transport ports.
- -keepAppDirectory
Note: This parameter is ignored for WebSphere ESB version
6.1 to version 6.2 migration.
This is an optional parameter
used to specify whether to install all applications to the same directories
in which they are currently located. The default is false. If this
parameter is specified as true, each individual application retains
its location.
Restrictions: If
this parameter is specified as true, the location is shared by the
existing
WebSphere ESB and the new installation. If you keep the migrated applications
in the same locations as those of the previous version, the following
restrictions apply:
- The version 6.2 mixed-node support limitations must be followed. This means
that the following support cannot be used when evoking the wsadmin command:
- Precompile JSP
- Use Binary Configuration
- Deploy EJB
- You risk losing the migrated applications unintentionally if you
later delete applications from these locations when administering
(uninstalling for example) your previously existing installation.
- -keepDmgrEnabled
Note: This parameter is ignored for WebSphere ESB version
6.1 to version 6.2 migration.
This is an optional parameter
used to specify whether to disable the existing WebSphere ESB deployment
manager. The default is false. If this parameter is specified as
true, you can use the existing deployment manager while the migration
is completed. It is only valid when you are migrating a deployment
manager; it is ignored in all other migrations.
Caution: Use this parameter with care.
- The reason that existing WebSphere ESB deployment
manager configurations normally are stopped and disabled is to prevent
multiple deployment managers from managing the same nodes. You must
stop the existing deployment manager before you start using the new
version's deployment manager. The most likely error conditions that
will occur if this is not done are port conflicts when the second
instance of the deployment manager is started.
- Specifying true for this parameter means that any configuration
changes made in the old configuration during migration might not be
migrated.
- -appInstallDirectory
Note: This parameter is ignored for WebSphere ESB version
6.1 to version 6.2 migration.
This is an optional parameter
used to pass the directory name to use when installing all applications
during migration. The default of profile_name\installedApps is used if this parameter is not specified.Quotes must be used around the directory name if one or more blanks
are in the name.
Tip: You can include the variable ${USER_INSTALL_ROOT} in your argument. This variable expands
to <WPS HOME>\profiles\<profile name>. For
example, if WebSphere ESB, version 6.2 is installed at C:\wps\ and the target profile
is ProcSrv01, then ${USER_INSTALL_ROOT} represents C:\wps62\profiles\ProcSrv01.
- -traceString
Note: This parameter is ignored for WebSphere ESB version 6.0.2.x to version 6.2 migration.
This is an optional parameter. The value trace_spec specifies the trace information that you want
to collect.To gather all trace information, specify "*=all=enabled" (with quotation marks).
Important: If you specify this parameter, you must also specify
the -traceFile parameter. If you specify the -traceString parameter
but do not specify the -traceFile parameter, the command creates a
trace file by default and places it in the backupDirectory/logs directory.
- -traceFile
Note: This parameter is ignored for WebSphere ESB version 6.0.2.x to version 6.2 migration.
This is an optional parameter. The value file_name specifies the name of the output file for trace
information. Important: If you specify this parameter,
you must also specify the -traceString parameter. If you specify the
-traceFile parameter but do not specify the -traceString parameter,
the command uses the default trace depth, and stores the trace file
in the location you specify.
- -createTargetProfile
This optional parameter creates a new profile with the correct
configuration settings for migration purposes.