The WASPreUpgrade command for WebSphere® Application Server Version 8.5 saves the configuration of a previously installed version of WebSphere Application Server into a migration-specific backup directory.
The command file is located in and must be run from the Version 8.5 app_server_root/bin directory.
To run this command script, your user profile must have *ALLOBJ authority.
WASPreUpgrade backupDirectory
currentWebSphereDirectory
[-traceString trace_spec [-traceFile file_name ]]
[-workspaceRoot profile1=user_workspace_folder_name_1;profile2=user_workspace_folder_name_2]
[-username < user name >]
[-password < password >]
[-javaoption < -Xms...m > -javaoption < -Xmx...m > ]
[-requireEmbeddedDBMigration true | false]
[-keepDmgrEnabled true | false]
The command has the following parameters:
This is also the directory from which the WASPostUpgrade command reads the configuration.
If the directory does not exist, the WASPreUpgrade command script creates it.
To gather all trace information, specify "*=all=enabled" (with quotation marks).
If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.
If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.
The value "-Xms...m" is the parameter specified to indicate the starting heap size. Replace the "..." with the size in Megabytes that you intended to use. For example, if the starting heap size is to be 128 MB, specify the parameter as: -javaoption -Xms128m
The value "-Xmx...m" is the parameter specified to indicate the maximum heap size. Replace the "..." with the size in Megabytes that you intend to use. For example, if the maximum heap size is to be 1024 MB, specify the parameter as: -javaoption -Xmx1024m
If the value is specified as true, any exception that occurs when you migrate the embedded databases causes the WASPreUpgrade command to fail. If the value is specified as false, any exception that occurs when you migrate the embedded databases is logged in the trace file, and the WASPreUpgrade command continues.
The default value is true.
When WASPreUpgrade runs, Version 8.0 deployment manager profiles are stopped. By default, the deployment manager remains stopped. If the value is specified to true, WASPreUpgrade starts the deployment manager before the command finishes running.
The default value is false.
The WASPreUpgrade tool displays status to the screen while it runs. The tool also saves a more extensive set of logging information in the WASPreUpgrade.time_stamp.log file written to the backupDirectory directory, where backupDirectory is the value specified for the backupDirectory parameter. You can view the WASPreUpgrade.time_stamp.log file with a text editor.
WASPreUpgrade saves all of your resources, but it does not migrate entities in your classes directory.