MIGR

MIGR0001I: WASPreUpgrade command syntax:
MIGR0002I: WASPostUpgrade command syntax:
MIGR0102E: An unsupported command line parameter was used.
MIGR0103E: You must specify the backup directory name.
MIGR0104E: You must specify the currently installed Application Server directory name.
MIGR0106E: The illegal argument {0} is specified.
MIGR0108E: The {0} directory does not contain a product version that can be upgraded. Verify that the directory name is correct, and rerun the command.
MIGR0110E: The currently installed version of Application Server is not supported by this command.
MIGR0111E: The migration function cannot use the specified backup directory because it is a file.
MIGR0112E: The specified backup directory cannot be used because it is not writable.
MIGR0113E: The specified backup directory cannot be used because it cannot be created.
MIGR0114E: The migration function cannot find the setupCmdLine setting {0}
MIGR0115E: The migration function cannot run program: {0}
MIGR0117E: The specified Application Server directory does not contain a valid product file {0}.
MIGR0122E: The migration function cannot read configuration file {0}
MIGR0201I: The migration function initialized log file {0}
MIGR0202W: The migration function is unable to initialize log file {0}
MIGR0206W: The migration function cannot copy the directory. The source file {0} does not exist.
MIGR0207W: The migration function cannot copy the directory {0}
MIGR0210I: The migration function is creating a directory {0}
MIGR0211I: The migration function is copying a directory {0}
MIGR0212E: The migration function cannot create the directory {0}. A file with this name already exists.
MIGR0213E: The migration function cannot create a directory {0}
MIGR0214W: The migration function cannot copy the file. Source {0} does not exist.
MIGR0215W: The migration function cannot copy the file and open the destination file {0}
MIGR0217W: The migration function cannot close file {0}
MIGR0223I: The migration function is adding {0} entry {1} to the model.
MIGR0227W: The migration function cannot make a backup copy of configuration file {0}; exception {1} occurred.
MIGR0228E: The migration function cannot save configuration files; exception {0} occurred.
MIGR0229I: The migration function is updating the attributes of {0} entry {1}. This entry is already defined in the existing model.
MIGR0234W: The migration function cannot locate object {0} of type {1}
MIGR0237I: The migration function read configuration file {0} successfully.
MIGR0241I: Output of {0}
MIGR0251I: The migration does not include object {0} of type {1}; it is a Sample.
MIGR0253E: The backup directory {0} does not exist.
MIGR0257E: The environment variable {0} was not set.
MIGR0259I: The migration has successfully completed.
MIGR0271W: Migration completed successfully, with one or more warnings.
MIGR0272E: The migration function cannot complete the command.
MIGR0280W: Application {0} is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0281W: All CORBA servers are disabled because the corresponding IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0283E: The migration function cannot read backup options file {0}, exception {1}
MIGR0284E: The version of WebSphere {0} in the specified backup directory cannot be migrated to profile {1}
MIGR0285E: An unexpected internal error occurred with exception {0}
MIGR0286E: The migration failed to complete.
MIGR0287I: The migration function successfully created configuration file {0}
MIGR0288I: Configuration file {0} ready to be saved.
MIGR0302I: The existing files are being saved.
MIGR0303I: The existing Application Server environment is saved.
MIGR0304I: The {0} profile in the previous application server environment is being migrated into the {1} profile.
MIGR0307I: The restoration of the previous Application Server environment is complete.
MIGR0310E: A value that is specified for {0} is not valid: {1}
MIGR0319E: This node is already federated into a cell manager configuration.
MIGR0332I: The attributes of the {0} authentication mechanism are updating.
MIGR0335I: Attributes of the {0} user registry are updating to reflect the information for server ID {1}
MIGR0339I: Application {0} is deploying using the wsadmin command.
MIGR0340W: Application {0} did not deploy.
MIGR0341W: Application installation directory has been updated to {0}
MIGR0344I: Processing configuration file {0}
MIGR0345E: The migration backup directory is not compatible with this Application Server version.
MIGR0346I: Object {0} of type {1} is not migrating; it is an administrative application.
MIGR0349E: The migration function cannot access the configuration directory.
MIGR0350W: Synchronization with the deployment manager using the {0} protocol failed.
MIGR0351I: The migration function is attempting to synchronize with the deployment manager using the {0} protocol.
MIGR0352I: The synchronization with the deployment manager is successful.
MIGR0353E: The migration function cannot create configuration file {0}
MIGR0357W: The extended messaging service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0360W: The staff service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0363W: The IBM WebSphere Business Integration adapter service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0365W: The member manager service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0366W: The business process container is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0367I: Backing up the current Application Server environment.
MIGR0371I: The name-value pairs that existed in the old file are not found in the new file.
MIGR0372I: Migrated grant permissions follow.
MIGR0378E: The node name of the new configuration must be the same as the old configuration: {0} for this environment.
MIGR0379W: Do not use the existing deployment manager in the old configuration. It has been disabled.
MIGR0380E: The JMX connection is not established with the deployment manager node {0}, using connector type of {1} on port {2}. The WASPostMigration program is now closing. No changes are made to the local Application Server environment.
MIGR0385I: Starting to save profile {0}
MIGR0386E: Profile {0} is not found in the currently installed Application Server.
MIGR0387E: The backup directory does not contain profile {0}
MIGR0389I: Applications will not be migrated, the -includeApps attribute was set to false.
MIGR0391E: You must specify the name of the source profile by using the -oldProfile option.
MIGR0394W: IBM WebSphere Web Service Reference service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0395W: IBM WebSphere Application Event service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0396W: IBM WebSphere Business Context Data service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0397W: Service Integration Bus migration failed.
MIGR0400I: Server {0} is added to the default core group.
MIGR0402I: Existing transports are migrating into the transport channel service; see the information center for further information.
MIGR0403I: The transport with a port address of {0} is migrating to channel {1} and belongs to the {2} ThreadPool.
MIGR0404W: Do not use the node agent in the old configuration. It has been disabled.
MIGR0410W: Unable to add server {0} to the default coregroup
MIGR0411E: You must specify the name of the target profile by using the -profileName option.
MIGR0415E: The cell name {0} from the old configuration does not match the cell name {1} in the target profile. No migration can occur.
MIGR0417I: Node {0} is added to the default node group.
MIGR0419I: The -useMetaDataFromBinary attribute is set to false for application {0}. The local changes are added to the repository.
MIGR0420I: The first step of migration completed successfully.
MIGR0421W: The first step of migration completed with warnings.
MIGR0425I: A deployment manager migration is detected. Before continuing with the WASPostUpgrade process, run the backupConfig command on your federated nodes.
MIGR0426E: {0} command not supported on z/OS for direct invocation from the Unix shell. Use z/OS Migration Management Tool under WebSphere Customization Tools instead.
MIGR0427W: Node {0} has been migrated, but may not be manageable in current release.
MIGR0428E: Incorrect Deployment Manager connection established.
MIGR0431E: Federated node {0} already exists in current configuration. Migration cannot continue.
MIGR0432W: Found server {0} to be of type {1} which is unsupported in current product version. {0} will not be migrated.
MIGR0433E: Conflicting parameters, -keepAppDirectory true and -appInstallDirectory, have both been specified. If -appInstallDirectory is specified, -keepAppDirectory must be false.
MIGR0434I: Will not be migrating object {0} of type {1}, it is already installed.
MIGR0435W: Could not resolve variable {0}
MIGR0436W: Could not process resource {0} due to variable issues.
MIGR0437E: Detected current version of deployment manager running while -keepDMgrEnabled attribute set.
MIGR0438W: Not copying file or directory {0} because a version of the file or directory already exists in current version.
MIGR0439E: Can not initialize trace services.
MIGR0440W: The migration of one or more applications terminated unexpectedly.
MIGR0444W: Cell-level documents are not merged. Any changes that you make to the stand-alone cell-level documents before using the WASPostUpgrade command must be repeated on the new cell. For example, virtual hosts.
MIGR0445W: The JDBC provider, {0}, is no longer a valid. You will not be able to create any new data sources for this provider until you either use the WebSphereConnectJDBCDriverConversion tool or create a new JDBC provider.
MIGR0450W: Some files were copied directly without being processed by migration, review MIGR0451W messages in the log file.
MIGR0451W: Migration copied file originally located at {0} to local path {1}
MIGR0452W: Migration could not locate a file matching {0} when migrating {1}. The reference has not been modified.
MIGR0453W: Not migrating DB2 for zOS Local JDBC Provider (RRS) JDBC Provider. This JDBC Provider will be copied over as-is but will be disabled at runtime. In order for this JDBC Provider to function at runtime it will need to be migrated to a DB2 Universal JDBC Driver Provider using the DB2 Universal Driver. This can be done manually or by using the IBM Application Server JDBC Migration Utility for DB2 on z/OS, available as a web download. Contact IBM support for details.
MIGR0454I: The {0} setting in file {1} is deprecated.
MIGR0455W: WebSphere Connect JDBC driver support has been removed. Data source {0} will need to be modified to make use of either Microsoft SQL Server JDBC Driver or DataDirect Connect JDBC driver.
MIGR0456W: Do not use the existing deployment manager in the old configuration.
MIGR0457W: Do not use the node agent in the old configuration.
MIGR0458E: Security is enabled in your prior configuration. -username and -password are required arguments.
MIGR0459I: Application Server configuration files are being migrated.
MIGR0460E: Application Server migration is not supported in this configuration.
MIGR0461I: Application Server has already been migrated.
MIGR0462I: Application Server factor is saving base configuration files.
MIGR0463I: Nothing to migrate at this time. The current profile has already been migrated with all information from enabled features.
MIGR0464E: Failed to stop prior release nodeagent.
MIGR0465E: Error in command line after {0}, found unexpected text {1}. All optional parameters must be prefixed by a label escaped by a leading - character.
MIGR0466E: No value was found for the argument {0}. This argument requires a value {1}
MIGR0478E: The port value for the endpoint {0} in of the server {1} is invalid or missing.
MIGR0479E: The host value for the endpoint {0} in of the server {1} is invalid or missing.
MIGR0482E: You must specify the <backupDirectoryName> and <currentWebSphereDirectory>.
MIGR0483W: Variable {0} at {1} scope has been defined with an emtpy value. This variable has also been defined at a broader scope. The broader scoped variable value will be hidden.
MIGR0484E: No profiles or instances found with name {0}
MIGR0485W: Process count exceeds the maximum recommended limit of {0} processes per coregroup.
MIGR0486I: The {0} setting in file {1} is deprecated.
MIGR0489E: The migration backup directory profile is of type {0} which is not compatible with this profile type {1}
MIGR0490I: Changing the {0} setting from {1} to {2} in the file {3} to meet performance requirements.
MIGR0491W: The migration function cannot continue because there are too many open files.
MIGR0492W: The SOAP port has changed from {0} to {1}, you must manually synchronize the managed nodes with the Deployment Manager.
MIGR0493E: The profile name {0} does not match the target profile {1}, the profile names must match for this migration.
MIGR0494E: An unexpected error occured during communication with the Deployment Manager, the migration cannot continue. Resolve the error and rerun the WASPreUpgrade tool to create a new backup directory.
MIGR0495E: The migration function cannot use the specified backup directory, it is invalid.
MIGR0496W: The migration of {0} terminated unexpectedly.
MIGR0497E: The migration function cannot save files to the backup directory, it is an invalid location.
MIGR0498E: Derby database lock file detected. Cannot migrate Derby database {0} while in use.
MIGR0499I: Application {0} successfully deployed using the wsadmin command.
MIGR0506E: Deregistration from old admin agent unsuccessful, make sure old admin agent process is running and the soap port is correct
MIGR0507E: Registration with new admin agent unsuccessful, manually register the migrated appserver to the new admin agent and job managers if applicable
MIGR0508I: Deregistering from old admin agent
MIGR0509I: Registering with new admin agent, make sure new admin agent process is running
MIGR0510E: Security is enabled in your managed application server. -oldAdminAgentUsername, -oldAdminAgentPassword, -newAdminAgentUsername, -newAdminAgentPassword are required arguments.
MIGR0511E: Admin Agent information for the new release is invalid.
MIGR0512E: Admin Agent information for the old release is invalid.
MIGR0513W: A cross machine migration detected. However, the source and target hostnames are identical - hostname={0} You will need to validate the host name setting of your endpoints.
MIGR0514I: Cross machine migration detected. You will need to manually disable the {0} server on the source machine.
MIGR0515W: Cannot validate if the source hostname ({0}) has the same IP address as the target hostname ({1}). Hostname changes were made to one or more of the server''s endpoints. You must validate these changes.
MIGR0519I: The certificate exchange related messages can be ignored.
MIGR0520E: The migration function cannot exchange the signer certificates. Run the retrieveSigners command to exchange the certificates manually.
MIGR0521W: Not migrating variable {0} for zOS. The default value will be used in the target profile.
MIGR0522W: The migration function cannot write the destination file {0}
MIGR0523I: The following security provider(s) were renumbered due to migration. Duplicate entries were removed.
MIGR0524I: The migration function cannot create the destination file {0}. It already existed. The source file {1} cannot be migrated.
MIGR0525W: The migration function cannot create the destination file {0}. The source file {1} cannot be migrated.
MIGR0526W: The migration function cannot migrate the java.security file because the contents are not compatible between the source and target.
MIGR0527I: The java.security file was migrated. Review the contents of the file to ensure the desired behavior. Additional changes may be needed.
MIGR0528E: Unable to read file {0}
MIGR0529I: WASPostUpgradeBLAHelper command syntax:
MIGR0530E: Unable to run command {0}
MIGR0531E: Unable to run jython file {0}
MIGR0532I: The commands have been saved.
MIGR0533E: Commands not saved {0}
MIGR0534E: The {0} option must be specified when using the remote version of the WASPreUpgrade command.
MIGR0535E: Machine change is not supported for flexible management profile {0}
MIGR0536E: The profileRegistry.xml file was not found in the following location: {0}
MIGR0539W: The {0} path {1} was change to {2} during migration due to path or variable resolution issues.
MIGR0540W: An additional java.security file was detected, but not migrated. If needed, migrate the java.security file manually. The java.security file is found under: {0}
MIGR0541W: A machine change migration has been detected. There are resources registered with the job manager function associated with the previous deployment manager. Update the job manager URL for the registered resources after WASPostUpgrade.
MIGR0542W: A machine change migration has been detected. The previous deployment manager could not be contacted to determine whether there are resources registered with the associated job manager function. If there are registered resources, update the job manager URL for the registered resources after WASPostUpgrade.
MIGR0543W: The migration function cannot copy into the read-only target directory {0}
MIGR0544W: The migration function cannot compress an empty directory {0}
MIGR0545I: The WebSphere Application Server installation configuration file {0} was migrated successfully. However, the changes should be reviewed and updated if necessary.
MIGR0546E: The WebSphere Application Server migration function failed to rename the cell with the following message: {0}
MIGR0547W: The output of {0} cannot be read: {1}
MIGR0548I: Assets, business-level assets, and composition units are being installed.
MIGR0549W: The following command did not install the application server assets, business-level assets, and composition units: {0}. See the {1} log file for more information.
MIGR0550E: The following command did not back up the target profile: {0}. See the {1} log file for more information.
MIGR0551I: The deployment manager is being started.
MIGR0552I: The deployment manager is being stopped.
MIGR0553W: The following command did not start the deployment manager: {0}. See the {1} log file for more information.
MIGR0554E: The following command did not stop the deployment manager: {0}. See the {1} log file for more information.
MIGR0555I: The web server plug-in configuration file is being generated for the following context: {0}
MIGR0556W: The following command did not generate the web server plug-in configuration file: {0}. See the {1} log file for more information.
MIGR0557W: The following command did not change the ownership of the {0} file to the {1} user: {2}
MIGR0558W: The following command did not complete successfully: {0}
MIGR0559W: The port values in the endpoint addresses for the service maps and local mapping service were not updated. Review the port values and verify that they are correct.
MIGR0560E: The old installation root directory cannot be determined from the {0} properties file. Ensure that the file exists and has the proper file permissions.
MIGR0561E: The currentWebSphereDirectory parameter specifies a profile, {0}, that does not match the profile name that was provided with the -oldProfile parameter, {1}
MIGR0562E: The {0} currentWebSphereDirectory parameter value does not reference a valid profile.
MIGR0563E: The {0} currentWebSphereDirectory parameter value does not reference an installation or profile root directory.
MIGR0564E: The migration cannot continue because the following required directory cannot be found: {0}
MIGR0565E: The {0} property that corresponds to the {1} command-line parameter is specified in the following properties file: {2}. Remove the property from the properties file and specify it on the command line.
MIGR0566E: Properties that must be specified from the command line are specified in the properties file. Remove the properties from the properties file and specify them on the command line.
MIGR0567E: A property for an unsupported parameter is specified in the properties file. Remove all unsupported parameters from the properties file, and run the command again.
MIGR0568E: An unsupported property that corresponds to the {0} command-line parameter is specified in the following properties file: {1}. Remove the property from the properties file, and run the command again.
MIGR0569W: Automatic repository checkpoints are now disabled in the Extended Repository Service. The checkpoints must be manually re-enabled.
MIGR0570E: The profile registry in the following file does not contain any registered profiles: {0}
MIGR0571W: The file or directory was not migrated because a variable in the following path cannot be resolved: {0}. This path is referenced in the {1} file.
MIGR0572W: The file or directory was not migrated because the following path refers to a system root directory: {0}. This path is referenced in the {1} file.
MIGR0573W: The file or directory was not migrated because it was not found at the following path: {0}. This path is referenced in the {1} file.
MIGR0574W: The following file or directory was not migrated: {0}. This path is referenced in the {1} file.
MIGR0575W: The following directory was not migrated to avoid corrupting the new application server installation or target profile: {0}. This path is referenced in the {1} file.
MIGR0576W: The file or directory cannot be migrated because the current user ID cannot write to the following target directory: {2}. The following configuration path was not migrated: {0}. This path is referenced in the {1} file.
MIGR0577W: The default value of the web server plug-in PostBufferSize property was changed during migration from 64 to 0 to prevent the web server plug-in from retrying HTTP POST requests. Review this change and adjust the setting if necessary.
MIGR0578W: The default value of the web server PostBufferSize property is non-zero. In WebSphere Application Server Version 8.5.5, the default value was changed to 0 to prevent the web server plug-in from retrying HTTP POST requests. If you do not want the web server plug-in to retry HTTP POST requests, change this setting to 0.
MIGR0579W: The migration process detected a cluster address endpoint in {0}. After the migration completes, verify that the endpoint is still valid and functional.
MIGR0580W: The {0} node was migrated using the following options: -machineChange false, -setPorts useOld, and com.ibm.ws.migration.postupgrade.keepNodeEnabled was set to true in the migration.properties file. With this configuration, the old node can be managed by the new deployment manager, resulting in possible data corruption.
MIGR0581E: The {0} argument is replaced. Use the {1} argument instead.
MIGR0582I: The -setPorts argument was specified with a starting port number, which automatically resolves port conflicts. Therefore, the -resolvePortConflicts argument will be ignored.
MIGR0583E: The specified value of {1} is out of range for the {0} argument. Specify a value from {2} to {3}
MIGR0584E: The {0} file exists but is not readable. Verify that you have the necessary file permissions.
MIGR0585W: The following applications were not installed in the new profile: {0}. Check the {1} directory for the application installation logs. If you are seeing this message as part of the WASPostUpgrade process, it does not mean that the WASPostUpgrade process failed. After you resolve any application installation issues, you can run the following command to install the remaining applications in your new profile: {2}
MIGR0586I: The {0} application is already installed, so the wsadmin command to install it was skipped.
MIGR0587W: In WebSphere Application Server Version 9.0, the default value for the ESIEnable webserver plug-in property changed to "false". The property value of "true" from your old configuration will be migrated forward. To use the new default behavior, manually set the property to "false".
MIGR0588I: The migration process added the {0} endpoint to the {1} server and assigned it a port number of {2}. You can change the port setting in the serverindex.xml file.
MIGR0589W: CEA was enabled on the {0} profile, but is not available in this version of the product. Applications that depend on this feature will not function.
MIGR0590I: The web module deployment descriptor in the {0} module of the {1} application was updated to version {2} so that it can be deployed in a mixed-cell environment.
MIGR0591E: The WASPreUpgrade command was unable to locate any valid registered profiles. To find profiles, use the manageprofiles -listProfiles and -validateRegistry options.
MIGR0592I: The migration tool detected JPA applications that are incompatible with the supported level of OpenJPA. For compatibility, the openjpa.Compatibility="UseListAttributeForArrays=true" JVM property was set on the following server: {0}
MIGR0593W: The file handle limit is less than the optimum limit of {0}. If you do not change the file handle limit to {0} or higher, then the migration might fail.
MIGR0594I: The {0} custom property was added to support the default CoreGroup wire protocol for this release in a mixed-cell environment.
MIGR0595I: The value of the {0} custom property was changed from {1} to {2} to support changes in how the core group member selects the default protocol for this release.
MIGR0596W: The migration tool was unable to migrate the Compute Grid job logs for the following deployment target: {0}.
MIGR0597I: WASMigrationAppInstaller command syntax:
MIGR0598I: The {0} application successfully deployed by using the wsadmin command with Java EE compatibility set to {1}
MIGR0599I: The application deployment descriptor of the {0} application was updated to version {1} so that it can be deployed in a mixed-cell environment.
MIGR0600E: For clone migrations on the same machine, new ports must be generated. To generate the ports, specify either the -setPorts generateNew or -setPorts <startingPort> parameter.
MIGR0601E: Clone migrations are not supported for WebSphere Application Server for z/OS.
MIGR0602E: Clone migrations are not supported for job managers or managed application servers.
MIGR0603I: The clone option was used to migrate this deployment manager. When you migrate the federated nodes, provide the following connection information on the WASPostUpgrade command: -clone true -newDmgrHostname {0} -newDmgrSoapPort {1}
MIGR0604E: For clone migrations of a federated node, the new deployment manager host name is required. Specify the -newDmgrHostname <hostName> parameter.
MIGR0605E: For clone migrations of a federated node, the new deployment manager SOAP or RMI port is required. Specify either the -newDmgrSoapPort <port> or -newDmgrRmiPort <port> parameter.
MIGR0606E: When you migrate an administrative agent, new ports must be generated for the new administrative agent. To generate the ports, specify either the -setPorts generateNew or -setPorts <startingPort> parameter.
MIGR0607E: A clone migration was specified by setting the -clone parameter to true, but other migration settings are incompatible with this option. Review the other error messages and update the command parameters.
MIGR0608E: The deployment manger of this federated node was not cloned when it was migrated. Therefore, this federated node cannot be migrated using the -clone true option.
MIGR0609W: During a clone migration, the plug-in configuration for web servers is not automatically regenerated. When the new WebSphere environment is ready for web server traffic, follow the steps outlined in the document located at {0} to regenerate and propagate the plug-in configuration.
MIGR0610E: The {0} short name could not be generated by using the provided prefix of {1}.
MIGR0611E: The value of the {0} argument is not valid. This argument requires a value of{1}.
MIGR0612E: A migration is being attempted from one version of the product to the same version of the product, but the migration was not a clone.
MIGR0613E: The migration source and target profiles share the same product installation.
MIGR0614I: The value of the webAuthReq security property was changed to "persisting" in the target profile.
MIGR0615I: The clone option is enabled, so the -keepDmgrEnabled value was changed to true.
MIGR0622E: The deployment manger of this federated node was migrated using the -clone true option. Therefore, this federated node must also be migrated using the -clone true option.
MIGR0623I: The WASPostUpgrade process is rolling back changes due to a previous error. Errors that occur after this message are related to the rollback and are not the reason WASPostUpgrade failed.
MIGR0633I: The default runtime version {0} for {1} is being overridden by version {2} for all members of cluster {3} to maintain application compatibility.
MIGR0634I: The default runtime version {0} for {1} is being overridden by version {2} for server {3} to maintain application compatibility.
MIGR0635W: The default JAX-RS version was overridden for at least one cluster or server. You must reset the JAX-RS version to {0} for those clusters or servers that host an application where JAX-RS is using the Context Dependency Injection (CDI) technology.
MIGR0636I: The sslProtocol setting for the {0} repertoire was changed from SSL_TLS to SSL_TLSv2.
MIGR0637E: The deployment manager indicates that node {0} was previously cloned successfully. This node cannot be migrated a second time.
MIGR0638W: No migration to another machine occurred. No action is required if all of the unresolved variables in the path {0} are defined at a cluster scope, and the file or directory exists outside the product installation and profile directories. Otherwise, move the file or directory, or update the variable values as required in the target environment.
MIGR0639W: This stand-alone application server profile contains a server with the following customized server name: {0}. Ensure that the destination profile in the new environment contains a server with the same server name.
MIGR0640W: The target profile does not contain an application server with the same name as the {0} server in the source profile. If problems occur after migration, delete the target profile, create a destination profile that contains a server with the {0} name, and run the WASPostUpgrade command again.
MIGR0900E: The specified command is not valid.
MIGR0903W: A value for attribute {0} is missing.
MIGR0904W: The enterprise archive (EAR) file {0} is not valid.
MIGR0905W: An unacceptable parameter was specified {0}.
MIGR0906W: You must specify the enterprise archive (EAR) file location.
MIGR0907W: The enterprise archive (EAR) file {0} does not exist.
MIGR0908W: The enterprise archive (EAR) file name {0} is a directory.
MIGR0909W: No client Java archive (JAR) files are found by the name {0}.
MIGR0910W: No client Java archive (JAR) files are found.