WebSphere Release-to-Release Migration ToolingMIGR0001I: java com.ibm.websphere.migration.preupgrade.WASPreUpgrade
Explanation
This is the class name of the WASPreUpgrade command
User Response:
None
MIGR0002I: java com.ibm.websphere.migration.postupgrade.WASPostUpgrade
Explanation
This is the class name of the WASPostUpgrade command
User Response:
None
MIGR0003I: java com.ibm.websphere.migration.postupgrade.WASEditionUpgrade
Explanation
This is the name of the class for the WASEditionUpgrade command.
User Response:
None
MIGR0101W: Unable to create trace log using file {0}.
Explanation
While specifying trace parameters, the trace file was not able to be created.
User Response:
Make sure the trace file name contains valid characters for the operating system file system. The output of the trace will still be displayed on the console, it can be captured and sent to IBM Service personnel.
MIGR0102E: Invalid command line parameter.
Explanation
The command parameters have been incorrectly specified.
User Response:
Make sure all parameters have been spelled correctly and are valid parameters.
MIGR0103E: You must specify the backup directory name.
Explanation
The backup directory is used to store the configuration information to be migrated to the new release.
User Response:
Run the command again with the backup directory specified.
MIGR0104E: You must specify the currently installed WebSphere directory name.
Explanation
The currently installed WebSphere directory must be accessed to obtain the configuration information to be migrated to the new release.
User Response:
Run the command again with the currently installed WebSphere directory specified.
MIGR0105E: You must specify the primary node name.
Explanation
The primary node name is used to call XMLConfig to obtain configuration information for the current release.
User Response:
Run the command again with the primary node name specified.
MIGR0106E: Illegal argument {0} specified.
Explanation
The specified parameter is not supported by the command.
User Response:
Check the spelling of the parameter and run the command again.
MIGR0107E: There must be an even number of optional parameters.
Explanation
Optional parameters are specified by first entering the name of the parameter followed by the value of the parameter.
User Response:
Run the command again with the correct format for optional parameters.
MIGR0108E: The specified WebSphere directory does not contain a WebSphere version that can be upgraded.
Explanation
Migration support is provided for releases 3.5.1 through 4.1.
User Response:
If you are attempting to migrate a supported release, verify that the directory name is correct and rerun the command.
MIGR0110E: The currently installed version of WebSphere is not supported by this command.
Explanation
The WASPostUpgrade command is running against a version of WebSphere that it does not support.
User Response:
The WASPostUpgrade command that was invoked may not be using the current version WebSphere directories. Specifically invoke the command in the current WebSphere directory structure. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0111E: The specified backup directory cannot be used because it is a file.
Explanation
A directory must be specified so that files containing the configuration information for the current release can be saved.
User Response:
Run the command again with the name of a directory specified.
MIGR0112E: The specified backup directory cannot be used because it is not writeable.
Explanation
A writeable directory must be specified so that files containing the configuration information for the current release can be saved.
User Response:
Run the command again with the name of a writeable directory specified.
MIGR0113E: The specified backup directory cannot be used because it cannot be created.
Explanation
The system was unable to create a directory with the name you specified.
User Response:
Determine why the directory could not be created and run the command again.
MIGR0114E: The setupCmdLine setting {0} cannot be found.
Explanation
A property in an IBM supplied file could not be found.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0115E: Unable to execute: {0}.
Explanation
During migration processing an attempt was made to call another WebSphere program, the call could not be completed successfully.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0116E: The backup directory does not contain the required xml data file {0}.
Explanation
The call to WASPostUpgrade was specified without using the -import keyword to specify a particular xml file. A file called websphere_backup.xml in the backup directory will be used.
User Response:
Rerun the WASPostUpgrade command using the -import keyword to specify an xml file created using the XMLConfig command on a prior WebSphere version.
MIGR0117E: The specified WebSphere directory does not contain a valid product file {0}.
Explanation
The directory specified on the migration command does not contain a valid properties/com/ibm/websphere/product.xml file.
User Response:
Rerun the command with a valid WebSphere directory name.
MIGR0118E: The WebSphere directory does not contain a readable product file {0}.
Explanation
The directory specified on the migration command does not contain a readable product.xml file.
User Response:
Rerun the command with a valid WebSphere directory name.
MIGR0119E: The XML file {0} used for import is not valid.
Explanation
A file was specified using the -import keyword that was not valid
User Response:
Rerun the command using an valid xml file.
MIGR0120E: The DTD file {0} does not exist.
Explanation
An internal error has occurred. The specified file is expected to be in the new WebSphere version bin/migration subdirectory.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0121E: Unable to read import XML document {0}, exception {1}.
Explanation
An error occurred while reading the xml file to import during migration.
User Response:
Rerun the command with a valid xml import file. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0122E: Unable to read configuration file {0}.
Explanation
The specified configuration file could not be read.
User Response:
If the file is part of the current WebSphere configuration then restore the configuration from a previous backup and rerun the command. WASPostUpgrade saves backups of all configuration files it attempts to modify in the same directory structure with a timestamp as part of its name.
MIGR0123E: Unable to import object {0} of type {1}, exception {2}.
Explanation
During WASPostUpgrade processing, an error occurred while importing the specified object.
User Response:
See the following errors in the migration log for further details. Correct the problem and rerun the command or use the WebSphere administration interfaces to complete configuring the specified object.
MIGR0124E: Unable to import XML data file {0}.
Explanation
An attempt to read the specified file failed.
User Response:
Make sure that the file exists and rerun the command.
MIGR0125E: The call to XMLConfig was not successful {0}.
Explanation
The call to XMLConfig to obtain the configuration information for the current release failed.
User Response:
Check the log created by the command for details and rerun the command.
MIGR0126E: The call to XMLConfig was not successful. Caught exception {0}.
Explanation
The call to XMLConfig to obtain the configuration information for the current release failed.
User Response:
Check the log created by the command for details and rerun the command.
MIGR0128E: Unable to read XMLConfig data tag definition file.
Explanation
The DTD file is expected to be in the new WebSphere version bin/migration subdirectory.
User Response:
If the file is missing restore it if possible, also verify that the userid used to run the migration command has sufficient file system authority. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0201I: Initialized Log File {0}.
Explanation
The specified log file has been initialized, a new log file will be created for each invocation of the migration commands.
User Response:
None
MIGR0202W: Unable to initialize log file {0}.
Explanation
The specified log file could not be initialized, no data will be saved in a log file but output will still be routed to the console.
User Response:
The migration should continue normally and output can be viewed on the console. The user file permissions should be checked before the command is run again.
MIGR0203I: Working with configuration from release {0}.
Explanation
This message logs the WebSphere version number of the backup configuration.
User Response:
None
MIGR0204I: Calling XMLConfig {0}.
Explanation
A call is being made to the XMLConfig program, this is used to create an xml file that will be used to migration to the new WebSphere version.
User Response:
None
MIGR0205W: Unable to capture output of {0}.
Explanation
An attempt was made to capture the output while calling another program during migration. This could not be done but the migration command should still function normally.
User Response:
Check the migration log file for information on whether the command completed normally.
MIGR0206W: Unable to copy directory. The source {0} does not exist.
Explanation
An expected directory could not be found and could not copied. This may affect the resulting migration.
User Response:
If the source file would have been used while creating an enterprise application then use a development environment to add the file to the appropriate location in the enterprise application.
MIGR0207W: Unable to copy directory {0}.
Explanation
The directory could not be copied. This may affect the resulting migration.
User Response:
If the directory would have been used while creating an enterprise application then use a development environment to add the files from that directory to the appropriate location in the enterprise application.
MIGR0208W: Unable to install datasource {0} into JDBC driver name {1}.
Explanation
The specified datasource could not be added to the JDBC driver.
User Response:
After migration has completed use the system administration interfaces to add the datasource. This needs to be done before applications servers that have deployed applications that depend on that datasource can be started.
MIGR0210I: Creating directory {0}.
Explanation
The directory was created during normal processing.
User Response:
None
MIGR0211I: Copying directory {0}.
Explanation
The process of copying a directory and its contents has started.
User Response:
None
MIGR0212E: Unable to create directory {0}. It already exists as a file.
Explanation
An unexpected failure occurred while creating a directory.
User Response:
Delete the directory and rerun the migration command.
MIGR0213E: Unable to create directory {0}.
Explanation
An unexpected failure occurred while creating a directory.
User Response:
Verify that the userid used to run the migration command has sufficient file system authority. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0214W: Unable to copy file. Source {0} does not exist.
Explanation
An unexpected failure occurred while copying a configuration file.
User Response:
If the source file would have been used while creating an enterprise application then use a development environment to add the file to the appropriate location in the enterprise application.
MIGR0215W: Unable to copy file. Could not open destination file {0}.
Explanation
An unexpected failure occurred while copying a configuration file.
User Response:
Verify that the userid used to run the migration program has appropriate file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0216W: Unable to copy file. Could not transfer from source {0} to destination {1}.
Explanation
An unexpected failure occurred while copying a configuration file.
User Response:
Verify that the userid used to run the migration program has appropriate file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0217W: Could not close file {0}.
Explanation
An unexpected failure occurred while closing a configuration file.
User Response:
Verify that the userid used to run the migration program has appropriate file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0218I: Starting to import {0}, action {1}.
Explanation
The specified object is being imported into the new WebSphere version, the action value relates to the XMLConfig action associated with the object in the xml file.
User Response:
None
MIGR0219I: Starting to import {0}.
Explanation
The specified object is being imported into the new WebSphere version.
User Response:
None
MIGR0220W: Ignoring object {0} of type {1} because action was not create, createclone, update or locate.
Explanation
The action on the specified object in the input xml file was not supported for migrating objects. This could action including delete, export, start, stop, ping, associateclone, or disassociateclone.
User Response:
If the object needs to be created in the new configuration then either use a different input xml file, modify the input xml file and rerun migration or use the WebSphere system administration interfaces to create the object.
MIGR0221I: Reading the previously saved configuration file {0}.
Explanation
The specified configuration file from a previous WebSphere version is being read. This will be the source for importing objects into the new WebSphere configuration.
User Response:
None
MIGR0222W: Unable to locate object while importing object {0} of type {1}.
Explanation
The specified object in the configuration file could not be located in the new WebSphere configuration.
User Response:
This problem usually occurs for configurations with multiple nodes in the same input xml file and the specified object is not on the node being migrated. If this is the case the message can be ignored, if not verify if the object needs to be added to the configuration and use the WebSphere system administration interfaces to create the object.
MIGR0223I: Adding {0} entry {1} to the model.
Explanation
The specified object is being added to the configuration of the new WebSphere version.
User Response:
None
MIGR0224W: Ignoring Node entry {0}, it is for a node other than this one.
Explanation
The specified node entry is being ignored because it does not match the node being migrated.
User Response:
This problem usually occurs for configurations with multiple nodes in the same input xml file and the specified object is not on the node being migrated. If this is the case the message can be ignored, if not verify if the object needs to be added to the configuration and use the WebSphere system administration interfaces to create the object.
MIGR0227W: Unable to make a backup of configuration file {0}, caught exception {1}.
Explanation
An unexpected failure occurred while copying a configuration file.
User Response:
Migration should have occurred normally, a backup of the previous configuration file is not available. Verify that the userid used while running the migration command has appropriate file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0228E: Unable to save configuration files. Caught exception {0}.
Explanation
An unexpected error occurred while trying to save the migrated configuration.
User Response:
verify that the userid used to run the migration command has sufficient file system authority. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0229I: Updating attributes of {0} entry {1}, it is already defined in the existing model.
Explanation
The specified entry already exists in the configuration of the new WebSphere version, it's attributes will be updated.
User Response:
None
MIGR0230I: Ignoring attributes of {0} entry {1}. Objects owned by this object will be mapped to the one object allowed by this product.
Explanation
The specified entry is being ignored since it does not directly map into the model of the new WebSphere configuration, however any objects that are owned by that entry will be added.
User Response:
None
MIGR0231E: Unable to deploy object {0} of type {1}.
Explanation
An unexpected error occurred while deploying the specified object.
User Response:
Verify that the object exists in the backed up environment. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0232I: No object of type {0} to import.
Explanation
No objects of the type specified exist to import.
User Response:
None
MIGR0233W: Unable to import object {0} of type {1}, JSP level 0.91 is not supported.
Explanation
A servlet using JSP 0.91 interfaces was detected. This JSP level is not supported on the new WebSphere version and the servlet will not be migrated to the new configuration.
User Response:
Use a development environment to convert the servlet to use the supported JSP levels and add it to the appropriate enterprise application.
MIGR0234W: Unable to locate object {0} of type {1}.
Explanation
Migration was unable to locate the object of the type specified when attempting to migrate it.
User Response:
Verify that the object exists in the backed up environment. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
Explanation
The configuration from the prior WebSphere version has been successfully imported into the new WebSphere version.
User Response:
Inspect the WASPostUpgrade log to verify the results.
MIGR0237I: Read configuration file {0}.
Explanation
The configuration file was successfully read.
User Response:
None
Explanation
This message follows another message in the log that shows another program that is being called during migration, this message displays the results of that call.
User Response:
None
MIGR0243I: Datasource {0} already installed in JDBC driver name {1}.
Explanation
The specified datasource was already installed in the JDBC driver.
User Response:
None
MIGR0244I: Ignoring attributes of {0} entry {1}, it is already defined in the existing model.
Explanation
The specified entry is being ignored since it does not directly map into the model of the new WebSphere configuration.
User Response:
None
MIGR0245I: Ignoring {0} model entry, only clones of Application Servers are allowed.
Explanation
The specified object does not map directly into the new WebSphere model as a clone, only Application Servers are mapped to cluster members in the new configuration model.
User Response:
None
MIGR0246I: Creating object {0} of type {1} because standalone ejbs and/or web apps exist.
Explanation
WASPostUpgrade created an ear file because ejbs and/or web applications exist on the application server that are not part of an enterprise application.
User Response:
None
MIGR0248W: Level 1.0 and 1.1 JSPs will be run with level 1.2 JSP Servlet.
Explanation
Any level 1.0 or 1.1 JSPs will be run with the level 1.2 JSP Servlet.
User Response:
The Level 1.0 and 1.1 JSPs will run without source code changes.
MIGR0249E: Error while updating the plugin-cfg.xml file, caught exception {0}.
Explanation
An error occurred while calling the GenPlugInCfg command at the end of migration. Migration completed normally.
User Response:
Run the GenPlugInCfg command manually. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0250W: Document Root file limit of {0} exceeded. The file {1} was the first file not copied to WebApplication {2}'s war file.
Explanation
The number of files found under the web-application's document-root have exceeded the limit specified. Any additional files above the limit have not been copied to the web application's war file.
User Response:
Rerun the migration from the command line specifying a higher document-root limit using the -documentRootLimit attribute or manually copy any files not copied into the war file from the document-root.
MIGR0251I: Will not be migrating object {0} of type {1}, it is a sample.
Explanation
No samples are migrated during WASPostUpgrade.
User Response:
None
MIGR0252W: Unable to restore a configuration file {0}, caught exception {1}.
Explanation
While attempting to restore the specified file an unexpected error occurred.
User Response:
The configuration file may not match the rest of the configuration. If possible use one of the backup files with the same name to restore the configuration.
MIGR0253E: The backup directory {0} does not exist.
Explanation
The backup directory specified on the command line does not exist.
User Response:
Rerun the command with a valid backup directory created by the WASPreUpgrade command.
MIGR0255E: Invalid substitution value {0}.
Explanation
Substitution values can be replaced in the input xml file during migration. These are specified on the WASPostUpgrade command.
User Response:
Rerun the migration command using a valid substitution value.
MIGR0256W: LTPA AuthMechanism is not supported by this WebSphere edition. The SWAM AuthMechanism will be used.
Explanation
The LTPA Authentication Mechanism is not supported by this edition. The SWAM Authentication Mechanism supported by this edition has been set as the active Authentication Mechanism.
User Response:
The SWAM Authentication Mechanism has been configured during migration and will work in a non-distributed environment.
MIGR0257E: Environment variable {0} was not set.
Explanation
An internal error occurred, the specified environment variable must be set for proper execution of the migration command.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
Explanation
The specified file is being copied
User Response:
None
MIGR0259I: Completed successfully.
Explanation
The migration has completed with no warning or error messages.
User Response:
None
MIGR0260W: {0}{1} has been added to the configuration but it's classpath parameter may need to be updated if its prerequisite has changed.
Explanation
The resource provider has been successfully added to the configuration but it's classpath information may be incorrect if a prereq change was required for the new WebSphere version.
User Response:
Use the WebSphere system administration interfaces to update the classpath value of the specified resource provider.
MIGR0261I: There were no files located under the {0} to copy to the war file {1}.
Explanation
There were no files located under the web-application's classpath or document-root to copy to the war file.
User Response:
Verify that there are no files located under the web-application's classpath or document-root. If there are files under the classpath or document-root, manually copy them to the war file.
MIGR0263W: Security password settings have not been saved correctly. Update them in the backup file or by using the administration interfaces.
Explanation
The security passwords have not been saved as {xor} or clear text passwords.
User Response:
The security passwords found in the websphere_backup.xml file must be updated before running WASPostUpgrade.
MIGR0264I: There is no data source to map for EJB {0}.
Explanation
No data source was found to map to the specified EJB.
User Response:
Verify that there is no data source configured for the specified EJB in the websphere_backup.xml file.
MIGR0265I: Will not be migrating {0} and any associated security.
Explanation
The admin application and any security defined on it is not migrated during WASPostUpgrade.
User Response:
None
MIGR0266W: Unable to deploy jar file {0} containing the ejb {1}.
Explanation
An unexpected error occurred when attempting to deploy the specified jar file using the ejbdeploy tool.
User Response:
Attempt to run the ejbdeploy tool from the command line. If successful, add the jar file to the applicable ear file. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0268W: Failure while updating the server configuration, exception {0}.
Explanation
An unexpected error occurred while updating the server configuration.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0269E: The call to get configuration settings was not successful {0}.
Explanation
An unexpected error occurred while calling an internal program.
User Response:
Verify that the userid used to run the migration program has sufficient file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0270E: Call to compute administration settings failed: {0}.
Explanation
The call to automatically determine you administration server name and port failed.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0271W: Completed with warnings.
Explanation
The migration completed with some warning messages but no errors occurred.
User Response:
Check the log file created by the migration command in the logs directory for further information and correct the problems if required.
MIGR0272E: Unable to complete the command.
Explanation
The migration command failed.
User Response:
Check the log file created by the migration command in the logs directory for further information and correct the problems if required.
MIGR0273I: A web module named {0} has already been added to the enterpriseApp. Only one web module of the same name is allowed.
Explanation
A web module with the same name has already been added to the ear file.
User Response:
Rename the web module and use AAT to add the module to the ear file.
MIGR0274W: A web module with a context root of {0} has already been installed. Web Module {1} will not be added to the ear file: {2}.
Explanation
A web module with the specified context root has already been installed and will not be added to the ear file.
User Response:
Modify the web module's context root and use AAT to add the module to the ear file.
MIGR0275I: {0} was not configured for this node and will not be installed
Explanation
The object specified was not configured for the node that has been migrated and was not installed.
User Response:
If the object should be installed on the current node. Configure and install the object using the WebSphere administration interfaces.
MIGR0276E: The -import parameter is not supported for this release and version.
Explanation
The -import parameter cannot be used when configuration information is stored in a database.
User Response:
Run the command again without the -import parameter.
MIGR0277E: Use the -import parameter to specify the name of your XML file.
Explanation
The default XML configuration file server-cfg.xml was not found.
User Response:
Run the command again using the -import parameter to specify the name of you configuration file.
MIGR0278W: {0} applications require source code changes and will need to be manually migrated.
Explanation
Applications that require source code changes cannot be automatically migrated.
User Response:
Implement the source code changes and install the applications. See the Info Center for details.
MIGR0279W: {0} disabled because the required Enterprise Edition feature is not installed.
Explanation
The Enterprise Edition Other Services feature must be installed in order to run the specified service.
User Response:
Install the feature and rerun the command.
MIGR0280W: Application {0} removed because the required Enterprise Edition feature is not installed.
Explanation
The Enterprise Edition Business Rule Beans feature must be installed in order to run Business Rule Beans applications.
User Response:
Install the feature and rerun the command.
MIGR0281W: All CORBA servers will be disabled because the corresponding Enterprise Edition feature is not installed.
Explanation
The Enterprise Edition CORBA C++ SDK must be installed in order to run CORBA applications.
User Response:
Install the feature and rerun the command.
MIGR0282W: All CORBA servers that have been defined will need to be re-registered.
Explanation
CORBA servers could not be automatically migrated.
User Response:
Run the CORBA server registration command for each server you wish to migrate.
MIGR0283E: Unable to read backup options file {0}, exception {1}.
Explanation
An unexpected error occurred while trying to read the specified file.
User Response:
Verify that the userid used to run the migration program has sufficient file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0284E: The version of WebSphere in the specified backup directory is not supported by this command.
Explanation
A backup directory as specified that was created for a version of WebSphere that is not supported.
User Response:
Rerun the migration command with a valid backup directory created by the WASPreUpgrade command.
MIGR0285E: An unexpected internal error occurred, exception {0}.
Explanation
An unexpected error occurred.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0286E: Completed with errors.
Explanation
The migration completed with some errors.
User Response:
Check the log file created by the migration command in the logs directory for further information and correct the problems if required.
MIGR0287I: Created configuration file {0} successfully.
Explanation
The specified configuration file did not previously exist in the new WebSphere configuration and was successfully created.
User Response:
None
MIGR0288I: Saved configuration file {0} successfully.
Explanation
The specified configuration file was saved.
User Response:
None
MIGR0289E: Entry {0} in entry {1} does not exist.
Explanation
The specified entry in the configuration file does not exist as expected.
User Response:
This configuration file is not valid, either restore a valid backup from a previous configuration or use the WebSphere system administration interfaces to fix the settings in the file.
MIGR0290W: Unable to convert CustomTransport, there is no equivalant transport type.
Explanation
Custom Transports are not supported in the new WebSphere version.
User Response:
Use the WebSphere system administration interfaces to define an HTTP transport port in the application server desired if the port needs to be configured, otherwise ignore the message.
MIGR0291W: Will not be migrating object {0} of type {1}.
Explanation
The specified object was not migrated because it is not supported by this edition.
User Response:
If security is not configured for any other objects in the enterprise application, security will have to be configured on another object in the enterprise application.
MIGR0293I: The application {0} was deployed on server {1} successfully.
Explanation
The specified application was deployed on the specified server successfully.
User Response:
None
MIGR0294E: The server {0} to deploy the application {1} on was not found.
Explanation
The server to the deploy the specified application on was not found.
User Response:
Check to see if the server exists in the migrated configuration. If it does, install the application using the WebSphere administration interfaces. If it does not, create the server and install the application using the WebSphere administration interfaces.
MIGR0295E: You cannot specify more than {0} positional parameters.
Explanation
The command that you entered specified more than the maximum number of positional parameters.
User Response:
Check the parameters specified on the command and run it again.
MIGR0296I: Initial Heap Size setting will not be mapped because they may not be valid for this release.
Explanation
The heap size specified in the previous version of WebSphere does not directly map into the new WebSphere model because the servers all run in different java virtual machines. The value will be ignored.
User Response:
Inspect the value specified for the previous version and determine if the heap sizes need to be updated in the servers of the new configuration.
MIGR0297I: Maximum Heap Size setting will not be mapped because they may not be valid for this release.
Explanation
The heap size specified in the previous version of WebSphere does not directly map into the new WebSphere model because the servers all run in different java virtual machines. The value will be ignored.
User Response:
Inspect the value specified for the previous version and determine if the heap sizes need to be updated in the servers of the new configuration.
MIGR0298W: Unable to locate the document-root {0}.
Explanation
The document-root specified for the web-application in the websphere_backup.xml file was not found.
User Response:
Verify that the specified document-root does not exist. If the document-root exists, manually copy any files found under the document-root to the war file.
MIGR0299W: Unable to locate the classpath {0}.
Explanation
The classpath specified for the web-application in the websphere_backup.xml file was not found.
User Response:
Verify that the specified classpath does not exist. If the classpath exists, manually copy any files found under the classpath to the war file.
MIGR0300I: Starting to save existing WebSphere environment.
Explanation
The series of steps needed to save the existing configuration information is starting.
User Response:
None
MIGR0301I: Exporting existing configuration.
Explanation
Configuration information is being read from the database.
User Response:
None
MIGR0302I: Saving existing files.
Explanation
Files needed to restore your configuration on the new release are being copied to the backup directory.
User Response:
None
MIGR0303I: Completed saving of the existing WebSphere environment.
Explanation
The process of backing up your previous configuration is complete.
User Response:
None
MIGR0304I: Starting to restore previous WebSphere environment.
Explanation
A series of steps will be performed to restore the previous WebSphere environment into the configuration of the new WebSphere version.
User Response:
None
MIGR0305I: Importing previous configuration.
Explanation
The configuration from the previous WebSphere version is being imported.
User Response:
None
MIGR0307I: Completed restoring of the previous WebSphere environment.
Explanation
The last step has been completed in restoring the previous WebSphere configuration.
User Response:
Display the WASPostUpgrade log and verify the results. The message previous to this one indicates success, warning or error.
MIGR0310E: Invalid value specified for {0}: {1}.
Explanation
The specified value is incorrect.
User Response:
Rerun the command with a correct value.
MIGR0311E: Directory {0} does not exist.
Explanation
The specified directory does not exist.
User Response:
Create the directory and rerun the migration command.
MIGR0312E: {0} is not a directory.
Explanation
The specified value is not a directory.
User Response:
Rerun the command with a valid directory name.
MIGR0313E: More than one {0} directory exists, please specify one using the {1} parameter.
Explanation
More than one directory exists in the WebSphere configuration.
User Response:
Rerun the command specifying the requested directory name using the noted parameter.
MIGR0314I: Importing previous Enterprise Extensions configuration.
Explanation
Importing Enterprise Extensions configuration information from the previous release has started.
User Response:
None
MIGR0315I: Processing bootstrap port settings.
Explanation
The bootstrap port setting of the previous WebSphere version will be processed.
User Response:
None
MIGR0316I: Updating bootstrap port setting to {0}.
Explanation
The bootstrap setting of the name server associated with the default server will be updated to use the same value as was used in the previous version of WebSphere.
User Response:
None
MIGR0317I: Not updating bootstrap port settings, prior release value was the default value.
Explanation
No bootstrap port setting was specified in the previous version of WebSphere, the current value will not be changed.
User Response:
None
MIGR0318I: Adding naming context {0} for earfile {1} for interoperability.
Explanation
The specified naming context has been added to the namebindings.xml file.
User Response:
None
MIGR0319E: This node has already been federated into a cell manager configuration.
Explanation
This node has already been added to the cell manager configuration. Migration will not be run because the configuration is controlled by the cell manager.
User Response:
If migration is desired then remove the node from the cell manager configuration and rerun the command. However this should be done with caution because the configuration is already being managed.
MIGR0320I: The application {0} has already been deployed on server {1}.
Explanation
The specified application has already been deployed on the specified server successfully.
User Response:
None
MIGR0321W: The enterprise bean being migrated contains RunAs system identity. You may want to change it to RunAs role.
Explanation
The enterprise beans that were migrated contain RunAs system identity.
User Response:
The RunAs system identity can be changed to RunAs role by modifying the application using the WebSphere administration interfaces.
MIGR0322I: Adding security role {0} to the application {1}.
Explanation
The specified security role has been added to the application's binding file.
User Response:
None
MIGR0323I: Enabling {0} in configuration file {1}.
Explanation
The specified value is being enabled in the configuration file, it was previously disabled.
User Response:
None
MIGR0324E: Unable to enable {0} in configuration file {1}.
Explanation
The specified configuration file could not be enabled.
User Response:
Verify that the userid used to run the migration program has sufficient file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0325I: Converting {0} to {1} in {2}.
Explanation
The specified object is being converted in the specified file.
User Response:
None
Explanation
The specified object is being added to the noted configuration file.
User Response:
None
Explanation
An unexpected error occurred.
User Response:
Verify that the userid used to run the migration program has sufficient file system authorities. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0329W: Creating was.policy file for the ear file {0} that grants all Java 2 security permissions to the ear file.
Explanation
The enterprise application has been granted java.security.AllPermission.
User Response:
The Java 2 Security policy for the enterprise application can be changed by editing the was.policy file. For syntax of was.policy, please refer to the Dynamic Policy section of documentation in Info Center.
MIGR0330I: {0} the authorization table in the ear file {1}.
Explanation
The authorization table in the specified ear file has been created or updated based on information found in the websphere_backup.xml file.
User Response:
None
MIGR0331W: Port {0} in server {1} has been migrated but is already assigned in file {2}, this may result in port conflicts.
Explanation
The specified port was already in use in the reported file. The port assignment has been migrated anyway.
User Response:
The port assignment may cause a conflict if both ports are started at the same time. Use the WebSphere system administration interfaces to assign unique port values if this occurs.
MIGR0332I: Updating attributes of the {0} AuthMechanism.
Explanation
The attributes of the specified authentication mechanism have been updated.
User Response:
None
MIGR0333W: If enabled, security has been disabled. LTPA keys must be generated before security can be enabled.
Explanation
LTPA keys must be generated before global security can be enabled. Therefore, if enabled, global security has been disabled during migration.
User Response:
Generate the LTPA keys using the WebSphere administration interfaces. If needed, see the Info Center for details.
MIGR0334W: If enabled, security has been disabled. The LTPA AuthMechanism must be configured before security can be enabled.
Explanation
The Authentication Mechanism configured in the previous release is not supported by this release. Therefore, if enabled, global security has been disabled during migration. The only authentication Mechanism supported is LTPA.
User Response:
To enable security, the LTPA authentication mechanism must be configured using the WebSphere administration interfaces. See the Info Center for details.
MIGR0335I: Updating attributes of the {0} UserRegistry to reflect the information for serverId {1}.
Explanation
The attributes of the specified user registry have been updated to reflect the information for the specified serverId.
User Response:
None
MIGR0336I: Ignoring attributes of servlet {0}. The {1} attribute in the ibm-web-ext.xmi file has been set to true.
Explanation
The specified servlet has not been migrated, since the specified attribute has been enabled in the web module's ibm-web-ext.xmi file.
User Response:
None
MIGR0337W: Updating the servlet-class attribute of servlet {0} to {1}.
Explanation
The specified servlet's servlet-class attribute has been updated to reflect the package that contains the servlet for this release.
User Response:
Source code changes may be required to reflect the specified servlet's new package.
MIGR0338E: No server was found on which to deploy the application {0}.
Explanation
No servers were found in the migrated configuration to deploy the specified application on.
User Response:
Check the migration log file to find out whether any servers were migrated successfully. If the correct server exists to install the application on, install the application using the WebSphere administration interfaces. Consult the IBM WebSphere Application Server Support website if this does not resolve the problem.
MIGR0339I: Using wsadmin to deploy the application {0}.
Explanation
Migration used wsadmin to deploy the specified application.
User Response:
None.
MIGR0340E: Unable to deploy the application {0}.
Explanation
The call to wsadmin failed and the specified application was not deployed.
User Response:
Check the wsadmin.traceout file found in the logs directory of new version install root to determine why the call to wsadmin failed.
MIGR0341W: The application {0} was not installed. The application was part of a model or server group configuration.
Explanation
The specified application was not installed on this WebSphere edition because it was part of a model or server group configuration that was migrated.
User Response:
See the Info Center for details.
MIGR0342W: Manual migration required for file {0}.
Explanation
Automated migration is not supported for the file.
User Response:
See the Info Center for details on how to manually migrate the file.
MIGR0343I: Starting to process configuration directory {0}.
Explanation
Automated migration is starting for the directory.
User Response:
None.
MIGR0344I: Starting to process configuration file {0}.
Explanation
Automated migration is starting for the file.
User Response:
None.
MIGR0900E: java com.ibm.websphere.migration.clientupgrade.ClientUpgrade: Invalid command line:
Explanation
This is usually caused by parameters being misspelled or parameters missing.
User Response:
Make sure all parameters have been spelled correctly and are valid parameters. Type the command without parameters or arguments to get correct syntax of the command.
MIGR0901W: -traceString is mandatory if traceFile is present.
Explanation
If you have specified a trace file specify the level of detail to be written out to trace through the use of -traceString.
User Response:
Add the parameter -traceString. ex: -traceString "*=all=enabled" (include quotes).
MIGR0903W: Missing value for attribute {0}.
Explanation
There was no argument given for the specified attribute. For example you did '-traceFile' and it should have been '-traceFile /some/path/to/log/file.txt'.
User Response:
Supply an argument to the specified parameter.
MIGR0904W: Invalid Ear file {0}.
Explanation
Ear that was supplied is either not an ear file or the contents and/or structure of the ear does not follow the J2EE specification.
User Response:
Verify that path has been spelled correctly and there is a valid ear in that location.
MIGR0905W: Invalid parameter specified {0}.
Explanation
A parameter has been specified that is not recognized as a valid parameter.
User Response:
Verify spelling and/or run the command alone without any parameters or arguments to get the correct syntax of the command.
MIGR0906W: You must specify the ear file location.
Explanation
No ear file has been specified. This is the first argument you pass in after the command. ex: clientUpgrade /ear/file/location/earfile.ear.
User Response:
Rerun the command with an ear file as the first argument.
MIGR0907W: Ear file {0} does not exist.
Explanation
The ear file that was specified can not be found in the given location.
User Response:
Verify that the path is spelled correctly and that there is a ear in that location.
MIGR0908W: Ear file {0} is a directory.
Explanation
Ear file that was specified is a directory.
User Response:
Verify that ear file that was specified is not a directory but an ear file.
MIGR0909W: No client jars found by the name {0}.
Explanation
The ear file does not contain any client jars by the specified name.
User Response:
Verify that the ear file contains the client jar that was specified.
MIGR0910W: No client jars found.
Explanation
The ear file does not contain any client jars.
User Response:
If the ear file that was specified was expected to contain client jars then correct the ear file and try the command again.
MIGR0911I: Running client jar migration on all client jars.
Explanation
No specific client jar was specified for migration so all client jars will be migrated if it is needed.
User Response:
None
MIGR0912I: Running client jar migration on {0}.
Explanation
This is the current client jar that is in the process of being migrated.
User Response:
None
MIGR0913E: Undefined error occurred during the client upgrade process.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0914E: Error during trace setup.
Explanation
Trace could not be setup properly. Trace may or may not be working because of this.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MIGR0915I: The jar file {0} has been previously migrated and will not be modified.
Explanation
Client jar has been migrated. This will occur when you try to migrate an ear/jar that has already been migrated by this tool.
User Response:
None