Express (Distributed operating systems), v8.0 > Reference > Messages
CWSAD
CWSAD0001E: The ServiceIndexReader class created an IOException or a SAXException error when it read the {0} file.
Explanation An IOException or SAXException error is created when the file is read. Action Ensure that the file exists and that it is usable.
CWSAD0002E: The ServiceIndexWriter class created an IOException when it writes to the {0} file.
Explanation An IOException is created when ServiceIndexWriter class writes to the file. Action Ensure that the hard disk is not full and we have the writable permission.
CWSAD0003E: The administrative command cannot find {0} application.
Explanation The application name cannot be found. Action Provide the correct application name.
CWSAD0004E: The administrative command cannot find {0} module.
Explanation The module cannot be found in the service package. Action Provide the correct module name for the service package.
CWSAD0005E: The administrative command cannot find {0} Web service.
Explanation The Web services cannot be found in the module. Action Ensure that the module has a Web service and that the service name is correct.
CWSAD0006E: The administrative command cannot find {0} logical endpoint.
Explanation The specified logical endpoint cannot be found in the serivce. Action Provide a logical endpoint name.
CWSAD0008E: The administrative command found multiple services index files for {0} service and {1} module.
Explanation Multiple services index files were found when only one service index file is expected. Action This is an internal error, no user action is required.
CWSAD0009E: There is no Web service in the {0} services index file.
Explanation The services index file has no entry for a Web service. The file might not be usable. Action If the file was manually modified, uninstall and reinstall the service. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product.
CWSAD0010E: There is no logical endpoint in {0} service.
Explanation The services index file has no entry for a logical endpoint. The file might not be usable. Action If the file was manually modified, uninstall and reinstall the service. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product.
CWSAD0011E: There is no operation for the {0} logical endpoint.
Explanation The services index file has no operation for the endpoint. The file might not be usable. Action If the file was manually modified, uninstall and reinstall the service. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product.
CWSAD0012E: The {0} file name provided cannot be used.
Explanation The file name must not contain slashes, directory or path name. Action Provide the correct file name without the slashes, directory or path name.
CWSAD0013E: The specified {0} file name cannot be found.
Explanation The specified file name cannot be located in the configuration repository. Action Provide the correct file name that can be found in the repository.
CWSAD0014E: The node has not been added because the version of the Feature Pack for Web Services that is installed on the {0} dmgr is earlier than the version that is installed on {1} node.
Explanation The version of the Feature Pack for Web Services that is installed on the dmgr node must be at the same level or higher than the version that is installed on the node. Action Install the same version or a higher version of the Feature Pack for Web Services on the dmgr node before running the addNode command.
CWSAD0015E: The node has not been added because the Feature Pack for Web Services is installed on the {0} node and not on the dmgr node.
Explanation The Feature Pack for Web Services is not installed on the dmgr node but has been installed on the managed node. Action Install the same level or a higher version of the Feature Pack for Web Services on the dmgr node before attempting to add the managed node.
CWSAD0016W: The target module {0} on node {1} cannot be reached because the module and the node require the Feature Pack for Web Services.
Explanation The module contains JAX-WS Web Services and requires the Feature Pack for Web Services. To map a Web module from an application that requires feature pack functionality even though the Web server does not have feature pack functionality, define the Web server on a node with feature pack augmentation.
Action Install the Feature Pack for Web Services on the target node.
CWSAD0017E: The node has not been added because the Feature Pack for Web Services is installed on the dmgr node and the {0} node is prior to the WebSphere 6.1 level.
Explanation The Feature Pack for Web Services is installed on the dmgr node but the managed node is prior to the WebSphere 6.1 level. Action Install the same level of the Feature Pack for Web Services on the managed node or upgrade it to the WebSphere 6.1 level before attempting to add the managed node.
CWSAD0018E: The administrative command cannot find {0} for {1} assets.
Explanation The specified asset name cannot be found. Action Provide the correct asset name.
CWSAD0019E: The parameters contain the following not valid property names: {0}.
Explanation The parameters for the administrative command or MBean operation contain one or more not valid property names. Action Provide the correct parameters.
CWSAD0020E: The command parameters contain the following not valid property values: {0}
Explanation The command parameters contain one or multiple not valid property values. Action Provide the correct command parameters.
CWSAD0021E: The command parameters contain the following conflicting properties: {0}
Explanation No more than one asset type is allowed in the query properties. Action Provide no more than one asset type.
CWSAD0022E: The logical endpoint name is missing in the parameter.
Explanation The logical endpoint name is required in the parameter for the specific MBean operation. Action Provide the logical endpoint name in the parameter.
CWSAD0023E: The queryProps parameter is null.
Explanation The query parameter should not be null. Action Provide queryProps parameter.
CWSAD0024E: The application name is missing in the parameter
Explanation Application name is required in the parameter. Action Provide the application name in the parameter.
CWSAD0025E: The module name is missing in the parameter
Explanation Module name is required in the parameter. Action Provide the module name in the parameter.
CWSAD0026E: The service name is missing in the parameter.
Explanation Service name is required in the parameter. Action Provide the service name in the parameter.
CWSAD0027E: The service or endpoint listener is already started on server {0}.
Explanation The service or endpoint listener is already started on the specific server. Action No action is needed since the service listener is already started on the specific server.
CWSAD0028E: The service or endpoint listener is already stopped on server {0}.
Explanation The service or endpoint listener is already stopped on the specific server. Action No action is needed since the endpoint listener is already stopped on the specific server.
CWSAD0029E: Cannot start the service listener on server {0} because it is a pre-7.0 server. We must start the containing asset instead.
Explanation Cannot start the service listener on a pre-7.0 server. Action Start the asset that contains the service.
CWSAD0030E: Cannot stop the service listener on server {0} because it is a pre-7.0 server. We must stop the containing asset instead.
Explanation Cannot stop the service listener on a pre-7.0 server. Action Stop the asset that contains the service.
CWSAD0031E: Cannot start the service listener on server {0} because the containing asset is not started.
Explanation Cannot start the service listener if the containing asset is not started. Action Start the asset that contains the service.
CWSAD0032E: The specified application module does not contain any web service.
Explanation The specified application module does not contain any web service. Action Provide the correct application, module, and service name.
CWSAD0033E: Cannot start the service listener on server {0} because the server is not started.
Explanation Cannot start the service listener if the server is not started. Action Start the server that is the target for the service.
CWSAD0034E: The node name is missing in the target parameter.
Explanation Node name is required in the target parameter. Action Provide the node name in the target parameter.
CWSAD0035E: The server or cluster name is missing in the target parameter.
Explanation Either server or cluster name is required in the target parameter. Action Provide the server name or the cluster name in the target parameter.
CWSAD0036E: The application is not installed on the target {0}.
Explanation The application is not installed on the specified server target or cluster target. Action Provide the correct node name and server name for the target.
CWSAD0037E: Cannot invoke MBean operation {0} because the application is either not installed on a 7.0 server or not started.
Explanation The specified MBean operation requires the application is running on a 7.0 server. Action Make sure the application is installed on a 7.0 server and is started before invoking the operation.
CWSAD0038E: Module {0} cannot not be found.
Explanation The module cannot be found in the service package. Action Provide the correct module name for the service package.
CWSAD0039W: The extended status report data from a downstream server {0} is not of expected type. The expected type is EndpointStatusReportExtendedData, but the actual type is {1}.
Explanation The extended status report data fro ma downstream server should be of EndpointStatusReportExtendedData type. Action This is an internal error.
CWSAD0040I: The application {0} is configured in the Application Server repository.
Explanation This informational message indicates the program status. Action No user action is required.
CWSAD0041E: An error occurred configuring {0} in the Application Server repository: {1}
Explanation Prior messages detail the cause of this failure. Typically, the error conditions include wrong server and node names specified as module targets during installation. Action Read the error messages and rectify the problem.
CWSAD0042E: An error occurred creating the configuration documents in the repository.
Explanation An unexpected error occurred when saving the configuration documents of the application to the WebSphere repository during application installation. This message is preceded by a more detailed message regarding the failure. Action Refer to the previous messages in the log file for a failure description. If no messages are displayed, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CWSAD0043W: The number of router modules is not consistance. The binding file of update EJB jar {0} has defined {1} router modules while the binding file of deployed EJB jar {0} has defined {2} router modules.
Explanation The number of router modules defined for the update EJB jar are not as same as the number found on the deployed EJB jar. Action Provide the correct EJB jar for update or correct the binding file.
CWSAD0044W: No matched HTTP router module {0} is found within the update EJB jar {0} binding file.
Explanation No HTTP router module is found within the update EJB jar binding while there is a HTTP router module defined in deployed EJB binding. Action Provide the correct EJB jar for update or correct the bindings.
CWSAD0045E: The binding file of update EJB jar {0} has a different HTTP router module name {1} than the deployed HTTP router module name {2}.
Explanation The binding has a new HTTP router module name than the one on deployed binding. Action Provide the correct ejb jar for update or correct the bindings.
CWSAD0046W: The binding file of update EJB jar {0} contains HTTP router module {1}, but the binding file of deployed EJB jar has no HTTP router module.
Explanation The update EJB jar bindings has an extra HTTP router module than the deployed EJB binding. Action Provide the correct ejb jar for update or correc the bindings.
CWSAD0047W: No matched JMS router module is found within the update EJB jar {0} binding file.
Explanation No JMS router module is found within update EJB jar binding while there is a JMS router module defined in deployed EJB binding. Action Provide the correct EJB jar for update or correct the bindings.
CWSAD0048E: The binding file of update EJB jar {0} has a different JMS router module name {1} than the deployed JMS router module name {2}.
Explanation The binding has a new JMS router module name than the one on deployed binding. Action Provide the correct ejb jar for update or correct the bindings.
CWSAD0049W: The binding file of update EJB jar {0} contains JMS router module {1}, but the binding file of deployed EJB jar has no JMS router module.
Explanation The update EJB jar bindings has an extra HTTP router module than the deployed EJB jar binding. Action Provide the correct ejb jar for update or correct the bindings.
CWSAD0050W: No binding information is found within the update EJB jar {0}.
Explanation The binding file is missing from the update EJB jar. Action Provide the correct ejb jar for update or correct the bindings.
CWSAD0051E: Cannot find a key within hash table for EJB JAR {0}.
Explanation The hash table does not contains the EJB JAR information from application installation operation. Error may be caused by using incorrect application or inputs parameters. Action Check with the installation inputs or scripts or provide a correct application.
CWSAD0052E: Cannot find the server string corresponding to the EJB JAR within hash table for key {0}.
Explanation The hash table does not contains the server string for a particular key. Error may be caused by using incorrect application or inputs parameters. Action Check with the installation inputs or scripts or provide a correct application.
CWSAD0053E: The unique key for router {0} cannot be found from key set of hash table.
Explanation The hash table does not contains the router module information. Error may be caused by using incorrect application or inputs parameters. Action Check with the installation inputs or scripts or provide a correct application.
CWSAD0054E: Cannot find the target server corresponding to the HTTP router WAR module within hash table for key {0}.
Explanation The hash table does not contains the server string for a particular key. Error may be caused by using incorrect inputs parameters or application. Action Check with the installation inputs or scripts or provide a correct application.
CWSAD0055E: Ejb jar and its HTTP router WAR module are not targeted to the same server. EJB JAR has the target of {0} and HTTP router WAR module has the target of {1}.
Explanation The destinations of EJB JAR and its HTTP router WAR module are not the same. Action Check with the installation inputs and scripts or provide a correct application. Sometimes, you may need to provide explicit server information for installation.
CWSAD0056E: Cannot find the target server corresponding to the JMS router JAR module with hash table for key {0}
Explanation The hash table does not contains the server string for a particular key. Error may be caused by using incorrect inputs parameters of application. Action Check with the installation inputs or scripts or provide a correct application. If all correct, contact IBM support.
CWSAD0057E: Ejb jar and its JMS router JAR module are not targeted to the same server. EJB JAR has target of {0} and JMS router JAR module has target of {1}.
Explanation The destinations of EJB JAR and its JMS router JAR module are not the same. Action Check with the installation inputs and scripts or provide a correct application. Sometimes, you may need to provide explicit server information for installation.
CWSAD0058E: Cannot find a key within hash table for the update module {0}.
Explanation The hash table does not contains the EJB JAR information from application installation operation. Error may be caused by using incorrect application or inputs parameters. Action Check with the installation inputs or scripts or provide a correct application.
CWSAD0059E: Update module {0} is not found on the deployed application.
Explanation There is not matched name application or module deployed on the server. Action Provide the correct module for update or check with the deployment inputs or scripts.
CWSAD0060E: The deployed server target {0} for module {1} is not matching to the update application server target {2} for module {3}.
Explanation The update module has server target which is different than the server target of deployed module. EJB and its related router modules cannot have different server targets. Action Provide the correct module for update, check the deployment inputs or scripts, or make sure EJB and its related router modules have the same server targets.
CWSAD0061E: No target mapping information is found on the deployed module {0}.
Explanation This could be either an user error or IBM internal error. Action Provide the correct module for update or check with the deployment inputs or scripts.
CWSAD0062E: Map modules to servers information is needed for partial or single file updated.
Explanation Cannot find map modules to servers information from user inputs. Action Add map modules to servers option with the deployment inputs or scripts.
CWSAD0063E: Update module {0} does not match to any of the router modules on the deployed application.
Explanation This could be an user error or IBM WebSphere internal error. Action Provide the correct module for update or chekc with the deployment inputs or scripts.
CWSAD0064W: The target module {0} on node {1} cannot be reached because the module requires a different node version.
Explanation The module contains JAXWS Web Services that is required for the WebSphere 7.0 and later. Action Install or upgrade the target node to WebSphere 7.0 and later.
CWSAD0066E: The router module {0} cannot be located on the deployment target of {1}.
Explanation The router modules found within the update EJB binding do not exist or cannot be found on the deployment target. Action Include a router module within the application and redo the deployment.
CWSAD0067E: Service {0} cannot be found.
Explanation The specified service cannot be found in the module. Action Ensure that the module has a service and that the service name is correct.
CWSAD0068E: Logical endpoint {0} cannot be found in service {1}.
Explanation The specified logical endpoint cannot be found in the serivce. Action Ensure that the logical endpoint name is correct.
CWSAD0069E: Failed to invoke the EndpointManager MBean operation {0} on server {1} due to exception {2}.
Explanation There is an exception when invoking the EndpointManager MBean operation on a server. Action Check the JMX connection to the server is working. If working, this is an internal error. If not working, fix the JMX connection problem.
CWSAD0070E: The target parameter should not contain both server name and cluster name.
Explanation The target parameter can contain either server name or cluster name but not both. Action Pass either server name or cluster name. We can invoke the operation twice, one for the server and one for the cluster.
CWSAD0071W: EJB {0} implemented as JAX-WS Web services bean is not an EJB 3.0.
Explanation Web service enabled EJB module should be greater than or equal to EJB 3.0. Action Change or update the EJB to a 3.0-style EJB.
CWSAD0072E: The deployed server target {0} for module {1} is not matching to the update server target {2} for module {3} on partial or single file update.
Explanation The module with partial or single file update has server target different than the server target of deployed module. EJB and its relted router modules cannot have different server targets. Action Provide the correct module for update, check the deployment inputs or scripts, or make sure EJB and its related router modules have the same server targets.
CWSAD0073E: No target mapping information is found on the deployed file or partial application {0}.
Explanation This could be either an user error or IBM internal error. Action Provide the correct file or partial application for update or check with the deployment inputs or scripts.
CWSAD0074E: No information of map modules to servers is found.
Explanation This could be either an user error or IBM internal error. Action Provide value to map modules to server property for the file or partial application update.
CWSAD0075E: The value of RepositoryContext is null.
Explanation Cannot obtain RepositoryContext. Action Contact IBM technical support.
CWSAD0076E: The value of serverStringOfUpdatedEJBModule is null.
Explanation No target is found for updated module. Action Contact IBM technical support.
CWSAD0077E: The value of serverStringOfDeployedRouterMoudule is null.
Explanation Cannot obtain server target from deployed router module. Action Contact IBM technical support.
CWSAD0078E: Access denied for resource {0}, {1} authority required.
Explanation The current user role does not have access to the resource. Action Retry the command with a higher level user.
CWSAD0079W: Unable to deploy the application {0} on the node {1} because the node version defined in the binding definition file for the application specific binding is later than the version of the target node.
Explanation The application specific binding, defined in the specified application, requires WAS v7.0 or later. Action Target the application to a node that is at WAS v7.0 or later.
CWSAD0080E: Cannot start the service listener on server {0} because the containing asset is in status {1} which is not valid to perform the operation.
Explanation The operation requires the asset in the started status and cannot be performed if the asset is in other status such as unknown, unavailable, partial start, or partial stopped. Action Start the containing asset in order to perform the operation.
CWSAD0081E: Cannot stop the service listener on server {0} because the containing asset is in status {1} which is not valid to perform the operation.
Explanation The operation requires the asset in the started status and cannot be performed if the asset is in other status such as unknown, unavailable, partial start, or partial stopped. Action Start the containing asset in order to perform the operation.
CWSAD0083E: Found {0} extension for the {1} extension point due to a missing or incorrect input parameter.
Explanation The input parameter may contain wrong or missing package name, so zero or multiple ServiceIndexManager extensions are found matching the input parameter. Action Specify the correct asset package names for the input parameter.
CWSAD0084E: The asset is not installed on the target {0}.
Explanation The asset is not installed on the specified server target or cluster target. Action Provide the correct server target or cluster target.
CWSAD0085E: Cannot start the service listener for service {0}. We must start the containing asset instead.
Explanation This service does not support the operational control at the service or endpoint level. Action Start the asset that contains the service.
CWSAD0086E: Cannot stop the service listener for service {0}. We must stop the containing asset instead.
Explanation This service does not support the operational control at the service or endpoint level. Action Stop the asset that contains the service.
CWSAD0087E: The MBean operation {0} is not supported for the service {1}.
Explanation This service does not support the operational control at the service or endpoint level. Therefore, the MBean operation is not supported. Action Do not invoke the MBean operation for the specified service.
CWSAD0088E: The input parameter {0} contains malformed sub-string {1}. It should be in the format of name=value.
Explanation A sub-string in the input parameter is not in the format of name=value. Action Provide the input parameter in the format of name pairs such as name1=value1,name2=value2.
CWSAD0089E: URLPrefixMap Validation Error: It is incorrect to use the JMS property name("{0}") for a Web Services
enabled Web module ("{1}"). The valid URL Prefix Map property name for a Web services enabled Web module is: "{2}"
Explanation In a Web services enabled Web module, you can only use //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ as a property name for the URL Prefix Map. Action Use appropriate //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ property name for a Web services enabled Web module.
CWSAD0090E: URLPrefixMap Validation Error: It is incorrect to use the Enterprise JavaBean (EJB) property name("{0}")
for a Web Services enabled web module ("{1}"). The valid URL Prefix Map property name for a Web services enabled Web module is: "{2}"
Explanation In a Web services enabled Web module, you can only use //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ as a property name for the URL Prefix Map. Action Use appropriate //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ property name for a Web services enabled Web module.
CWSAD0091E: URLPrefixMap Validation Error: Unrecognized property name "{0}", at module="{1}".
The valid URL Prefix Map property name for a Web services enabled Web module is: "{2}"
Explanation In a Web services enabled Web module, you can only use //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ as a property name for the URL Prefix Map. Action Use appropriate //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ property name for a Web services enabled Web module.
CWSAD0092E: URLPrefixMap Validation Error: Unrecognized property name "{0}", at module="{1}".
The valid URL Prefix Map property names for a Web services enabled EJB module are: "{2}", "{3}" and "{4}"
Explanation In a Web services enabled EJB module, you can only use the following property names: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ , jms, and ejb. Action Use appropriate property names for a Web services enabled EJB module.
CWSAD0093E: URLPrefixMap Validation Error: Invalid "{0}" URL fragment="{1}", at module="{2}", {3}
Explanation A malformed URL was specified. Error message indicates more details. Action See the associated error message for details regarding the errors encountered while parsing the URL fragment. Correct the URL fragment provided in the properties file.
CWSAD0094E: URLPrefixMap Validation Error: Invalid Protocol("{0}"), used in an {1} URL="{2}", at module="{3}".
Expected Protocols are:"{4}"
Explanation Invalid protocol found in supplied URL. Action Use a valid protocol.
CWSAD0095E: URLPrefixMap Validation Error: host and port values missing in HTTP URL="{0}"
Explanation The HTTP URL fragment provided is missing either the required host or port values. Action Add the necessary host and port to the specified URL.
CWSAD0096E: URLPrefixMap Validation Errors encountered. See trace file for additional details.
Explanation Validation errors were encountered. Action Look at trace file for additional details.
CWSAD0097E: URLPrefixMap Validation Error: Problems were encountered while reading the properties for the URL="{0}" at module ="{1}"
error encountered="{2}"
Explanation Problems were encountered while reading properties within specified URL. Action Ensure that properties are specified correctly.
CWSAD0098E: URLPrefixMap Validation Error: Invalid destination type: "{0}" specified within a JMS endpoint URL fragment, at module="{1}"
Explanation A proper destination type is missing in the supplied JMS endpoint URL. Action Specify proper destination and destination type.
CWSAD0099E: URLPrefixMap Validation Error: The JMS endpoint URL fragment: "{0}" at module: "{1}"
is missing the following required property: "{2}"
Explanation The required URL properties are missing in the specified JMS URL fragment. Action Specify all required and missing properties in the specified URL.
CWSAD0100E: URLPrefixMap Validation Error: Unable to construct a query from URL fragment: "{0}" at module: "{1}"
Either no properties were specified, or the ''?'' delimiter is missing from the URL fragment.
Explanation Either no properties were specified, or a delimiter is missing from the URL. Action Add necessary properties or proper delimiter (?) to indicate where to read properties from.
CWSAD0101E: URLPrefixMap Validation Error: The specified module="{0}" was not found.
Ensure correct module name has been specified. Expecting a Web services enabled web(.war) or ejb(.jar) module name.
Explanation The properties file did not contain a valid module name. Action Add correct module name to the properties file.
CWSAD0102E: URLPrefixMap Validation Error: The property that is being requested for deletion in module="{0}"
key="{1}" and value="{2}"
does not exist in current URL Prefix Map.
Current stored URL Prefix Map values are: "{3}"
Explanation The property that is requested for deletion does not exist in the current URL Prefix Map. Action Verify that the property key and value specified matches the current stored values.
CWSAD0103I: URLPrefixMap Section: module={0}
Explanation Comments in a properties file indicating what module this section corresponds to. Action This is just an informational comment. No action is required.
CWSAD0104E: URLPrefixMap Validation Error: Multiple URL prefix map sections found for module="{0}"
Remove any duplicate URL prefix map entries.
Explanation Multiple URL prefix map sections for the same module were found in the properties file. We must not configure multiple URL prefix map sections that specify the same module name. Configuring multiple URL prefix map sections that specify the same module creates ambiguity regarding which updates are requested. Action Remove duplicate entries to avoid unintended updates to the master configuration.
CWSAD0105W: The {0} target module cannot be installed on the {1} node because the module requires version {2} or later of WAS to be installed on the node.
Explanation The module contains JAX-WS web services and requires the specified minimum version of the application server. The node currently has an earlier version of this product installed. Action Install the specified minimum version of the application server on the target node.
CWSAD0106W: Unable to deploy the {0} application on the {1} node because it contains service reference attachments or attachments specified in a name-value pair format. The application requires version {2} or later of WAS to be installed on the node.
Explanation The application contains service reference attachments or attachments specified in a name-value pair format. The application requires the specified minimum version of the application server. The node currently has an earlier version of this product installed. Action Target the application to a node that is at the specified minimum version of the application server, or install the specified minimum version of the application server on the target node.
CWSAD0107W: Unable to deploy the {0} application on the {1} node because it contains configuration for WS-Policy that requires version {2} or later of WAS to be installed on the node.
Explanation The application contains configuration files that define how WS-Policy is configured. The application requires the specified minimum version of the application server. The node currently has an earlier version of this product installed. Action Target the application to a node that is at the specified minimum version of the application server, or install the specified minimum version of the application server on the target node.
CWSAD0108W: Unable to deploy the {0} application on the {1} node because it contains an attachment to a policy set that requires version {2} or later of WAS to be installed on the node.
Explanation The application contains an attachment to a policy set with a policy type that requires the specified minimum version of the application server. The node currently has an earlier version of this product installed. Action Target the application to a node that is at the specified minimum version of the application server, or install the specified minimum version of the application server on the target node.