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


WBIPostUpgrade command-line utility

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.

For i5/OS operating system Important: i5/OS is supported only if you are migrating from version 6.1.x to version 6.2.
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:

For i5/OS operating system
WBIPostUpgrade backupDirectory
                     [-username userID]
                     [-password password]
                     [-scriptCompatibility true | false]
                     [-portBlock port_starting_number]
                     [-backupConfig true | false]
                     [-replacePorts true | false]
                     [-keepDmgrEnabled true | false]
                     [-keepAppDirectory true | false]
                     [-appInstallDirectory user_specified_directory]
                     [-traceString trace_spec [-traceFile file_name]]
                     [-createTargetProfile]	
Note: The -profileName parameter is not supported on the i5/OS platform. If it is used, an invalid parameter exception will be thrown.

For Linux operating systemFor UNIX operating system
WBIPostUpgrade.sh backupDirectory
                     [-username userID]
                     [-password password]
                     [-oldProfile profile_name]
                     [-profileName profile_name]
                     [-scriptCompatibility true | false]
                     [-portBlock port_starting_number]
                     [-backupConfig true | false]
                     [-replacePorts true | false]
                     [-keepAppDirectory true | false]
                     [-keepDmgrEnabled true | false]
                     [-appInstallDirectory user_specified_directory]
                     [-traceString trace_spec [-traceFile file_name]]
                     [-createTargetProfile]

For Windows operating system
WBIPostUpgrade.bat backupDirectory
                     [-username userID]
                     [-password password]
                     [-oldProfile profile_name]
                     [-profileName profile_name]
                     [-scriptCompatibility true | false]
                     [-portBlock port_starting_number]
                     [-backupConfig true | false]
                     [-replacePorts true | false]
                     [-keepAppDirectory true | false]
                     [-keepDmgrEnabled true | false]
                     [-appInstallDirectory user_specified_directory]
                     [-traceString trace_spec [-traceFile file_name]]
                     [-createTargetProfile]
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.
-oldProfile
Restriction: This parameter is not available on i5/OS platforms.
This is an optional parameter for migrating instances or profiles from previous versions. The instance or profile must already exist in the migration backup directory before running this command.

If the -oldProfile parameter is not specified, the default profile will be used. If no default profile is found, the system will report an error.

-profileName
For UNIX operating systemFor Linux operating systemFor Windows operating system
Note: This parameter is not supported on the i5/OS platform. If it is used, an invalid parameter exception will be thrown.
This is an optional parameter for migrating to specific profiles. The value profile_name specifies the name of the profile, already created in the more recent version of WebSphere ESB, to which the script migrates your configuration. You must have already created this profile before calling the WBIPostUpgrade command.

If the -profileName parameter is not specified, the default profile will be used. If no default profile is found, the system will report an error.

Note: To ensure that the correct profile is migrated, specify the profile name using this parameter and do not rely on the default.
-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:
  1. Modify your administration scripts to use all of the version 6.2 settings.
  2. 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.
  • False
    Do not replace the version 6.0.x or 6.1.x port definitions during migration.
    • The previous version's configuration is left alone – no channels are deleted.
    • The following four named channels are set to values that are equivalent to the values set for the previous release:
      • WC_adminhost
      • WC_defaulthost
      • WC_adminhost_secure
      • WC_defaulthost_secure
    • The migration process creates transports or channels, based on the -scriptCompatibility setting, for any ports in the previous release.
    • The migration process sets all non-web-container ports to the values set for the previous release.
    • Port conflicts might arise if the migration process creates a transport or channel that is the same as one defined in the web container.

    This is the default.

  • True

    Replace all virtual host alias port settings during migration with version 6.2 port definitions.

    By default, the migration process adds configuration data from the previous environment to the data in the new WebSphere ESB environment. In some cases, however, this might not be the desired behavior for these port values. For example, existing port definitions from the earlier release might have been carefully set to avoid port conflicts with other products; in such cases, it is likely that you would want to migrate these settings into the new version's configuration. Specify true for this parameter to cause any ports of matching virtual hosts to be removed from the newer version's configuration before the new values are added.
    • All transport channels associated with the web container are deleted except for the following four named channels, which are set to values that are equivalent to the values set for the previous release:
      • WC_adminhost
      • WC_defaulthost
      • WC_adminhost_secure
      • WC_defaulthost_secure
    • The migration process creates transports or channels, based on the -scriptCompatibility setting, for any ports in the previous release.
    • The migration process sets all non-web-container ports to the values set for the previous release.
-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.

Logging

The WBIPostUpgrade command displays status to the screen while running. This command also saves a more extensive set of logging information in the WBIPostUpgrade.timestamp.log file located in the backupDirectory/logs directory. You can view the WBIPostUpgrade.profileNametimestamp.log file with a text editor.


reference Reference 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/rmig_wbipostupgrade.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).