Explanation | This is a restriction of the product. |
Action | Do not use this command when there are more than one node in the system configuration. |
Explanation | This is a restriction of the product. |
Action | Do not use this command where there is more than one node in the configuration archive. |
Explanation | The specified node name or server name are not valid. |
Action | Specify a valid node name and server name. |
Explanation | The importServer command creates a new server based on the server configuration from the archive. |
Action | Specify a different server name. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The specified node name does not match any node that is defined in the configuration. |
Action | Check the spelling of the node name. |
Explanation | The systemapps.xml file in the configuration archive does not contain the specified variable prefix for the application. |
Action | Make sure that <deployedApplications> entries in systemapps.xml start with ${WAS_INSTALL_ROOT}. |
Explanation | The importWasprofile command requires that the number of servers in the configuration archive and the system configuration match. |
Action | Only use this command when both system configuration and configuration archive contains the same number of the servers, except for the case that the system configuration contains no server. |
Explanation | The importWasprofile command requires that the names of servers in the configuration archive to match the names of servers in the system configuration. |
Action | Only use this command when the names of all the servers are the same between the configuration archive and the system configuration. |