CWSAD

CWSAD0001E: The ServiceIndexReader class created an IOException or a SAXException error when it read the {0} file.
CWSAD0002E: The ServiceIndexWriter class created an IOException when it writes to the {0} file.
CWSAD0003E: The administrative command cannot find {0} application.
CWSAD0004E: The administrative command cannot find {0} module.
CWSAD0005E: The administrative command cannot find {0} Web service.
CWSAD0006E: The administrative command cannot find {0} logical endpoint.
CWSAD0008E: The administrative command found multiple services index files for {0} service and {1} module.
CWSAD0009E: There is no Web service in the {0} services index file.
CWSAD0010E: There is no logical endpoint in {0} service.
CWSAD0011E: There is no operation for the {0} logical endpoint.
CWSAD0012E: The {0} file name that is provided cannot be used.
CWSAD0013E: The specified {0} file name cannot be found.
CWSAD0014E: The node has not been added because the version of the Feature Pack for Web Services that is installed on the {0} deployment manager is earlier than the version that is installed on {1} node.
CWSAD0015E: The node has not been added because the Feature Pack for Web Services is installed on the {0} node and not on the deployment manager 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.
CWSAD0017E: The node has not been added because the Feature Pack for Web Services is installed on the deployment manager node and the {0} node is prior to the WebSphere 6.1 level.
CWSAD0018E: The administrative command cannot find {0} for {1} assets.
CWSAD0019E: The parameters contain the following not valid property names: {0}.
CWSAD0020E: The command parameters contain the following not valid property values: {0}
CWSAD0021E: The command parameters contain the following conflicting properties: {0}
CWSAD0022E: The logical endpoint name is missing in the parameter.
CWSAD0023E: The queryProps parameter is null.
CWSAD0024E: The application name is missing in the parameter
CWSAD0025E: The module name is missing in the parameter
CWSAD0026E: The service name is missing in the parameter.
CWSAD0027E: The service or endpoint listener is already started on server {0}.
CWSAD0028E: The service or endpoint listener is already stopped on server {0}.
CWSAD0029E: Cannot start the service listener on server {0} because it is a pre-7.0 server. You must start the containing asset instead.
CWSAD0030E: Cannot stop the service listener on server {0} because it is a pre-7.0 server. You must stop the containing asset instead.
CWSAD0031E: Cannot start the service listener on server {0} because the containing asset is not started.
CWSAD0032E: The specified application module does not contain any web service.
CWSAD0033E: Cannot start the service listener on server {0} because the server is not started.
CWSAD0034E: The node name is missing in the target parameter.
CWSAD0035E: The server or cluster name is missing in the target parameter.
CWSAD0036E: The application is not installed on the target {0}.
CWSAD0037E: Cannot invoke MBean operation {0} because the application is either not installed on a 7.0 server or not started.
CWSAD0038E: Module {0} cannot not be found.
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}.
CWSAD0040I: The application {0} is configured in the Application Server repository.
CWSAD0041E: An error occurred configuring {0} in the Application Server repository: {1}
CWSAD0042E: An error occurred creating the configuration documents in the repository.
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.
CWSAD0044W: No matched HTTP router module {0} is found within the update EJB jar {0} binding file.
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}.
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.
CWSAD0047W: No matched JMS router module is found within the update EJB jar {0} binding file.
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}.
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.
CWSAD0050W: No binding information is found within the update EJB jar {0}.
CWSAD0051E: Cannot find a key within hash table for EJB JAR {0}.
CWSAD0052E: Cannot find the server string corresponding to the EJB JAR within hash table for key {0}.
CWSAD0053E: The unique key for router {0} cannot be found from key set of hash table.
CWSAD0054E: Cannot find the target server corresponding to the HTTP router WAR module within hash table for key {0}.
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}.
CWSAD0056E: Cannot find the target server corresponding to the JMS router JAR module with hash table for key {0}
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}.
CWSAD0058E: Cannot find a key within hash table for the update module {0}.
CWSAD0059E: Update module {0} is not found on the deployed application.
CWSAD0060E: The deployed server target {0} for module {1} is not matching to the update application server target {2} for module {3}.
CWSAD0061E: No target mapping information is found on the deployed module {0}.
CWSAD0062E: Map modules to servers information is needed for partial or single file updated.
CWSAD0063E: Update module {0} does not match to any of the router modules on the deployed application.
CWSAD0064W: The target module {0} on node {1} cannot be reached because the module requires a different node version.
CWSAD0066E: The router module {0} cannot be located on the deployment target of {1}.
CWSAD0067E: Service {0} cannot be found.
CWSAD0068E: Logical endpoint {0} cannot be found in service {1}.
CWSAD0069E: Failed to invoke the EndpointManager MBean operation {0} on server {1} due to exception {2}.
CWSAD0070E: The target parameter should not contain both server name and cluster name.
CWSAD0071W: EJB {0} implemented as JAX-WS Web services bean is not an EJB 3.0.
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.
CWSAD0073E: No target mapping information is found on the deployed file or partial application {0}.
CWSAD0074E: No information of map modules to servers is found.
CWSAD0075E: The value of RepositoryContext is null.
CWSAD0076E: The value of serverStringOfUpdatedEJBModule is null.
CWSAD0077E: The value of serverStringOfDeployedRouterMoudule is null.
CWSAD0078E: Access denied for resource {0}, {1} authority required.
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.
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.
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.
CWSAD0083E: Found {0} extension for the {1} extension point due to a missing or incorrect input parameter.
CWSAD0084E: The asset is not installed on the target {0}.
CWSAD0085E: Cannot start the service listener for service {0}. You must start the containing asset instead.
CWSAD0086E: Cannot stop the service listener for service {0}. You must stop the containing asset instead.
CWSAD0087E: The MBean operation {0} is not supported for the service {1}.
CWSAD0088E: The input parameter {0} contains malformed sub-string {1}. It should be in the format of name=value.
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}"
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}"
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}"
CWSAD0092E: URLPrefixMap Validation Error: Unrecognized property name "{0}", at module="{1}". The valid URL Prefix Map property names for a Web services enabled Enterprise JavaBeans (EJB) module are: "{2}", "{3}" and "{4}"
CWSAD0093E: URLPrefixMap Validation Error: Invalid "{0}" URL fragment="{1}", at module="{2}", {3}
CWSAD0094E: URLPrefixMap Validation Error: Invalid Protocol("{0}"), used in an {1} URL="{2}", at module="{3}". Expected Protocols are:"{4}"
CWSAD0095E: URLPrefixMap Validation Error: host and port values missing in HTTP URL="{0}"
CWSAD0096E: URLPrefixMap Validation Errors encountered. See 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}"
CWSAD0098E: URLPrefixMap Validation Error: Invalid destination type: "{0}" specified within a JMS endpoint URL fragment, at module="{1}"
CWSAD0099E: URLPrefixMap Validation Error: The JMS endpoint URL fragment: "{0}" at module: "{1}" is missing the following required property: "{2}"
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.
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.
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}"
CWSAD0103I: URLPrefixMap Section: module={0}
CWSAD0104E: URLPrefixMap Validation Error: Multiple URL prefix map sections found for module="{0}" Remove any duplicate URL prefix map entries.
CWSAD0105W: The {0} target module cannot be installed on the {1} node because the module requires version {2} or later of WebSphere Application Server to be installed on the node.
CWSAD0106W: Unable to deploy the {0} application on the {1} node because it contains service reference attachments or attachments that are specified in a name-value pair format. The application requires version {2} or later of WebSphere Application Server to be installed on the 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 WebSphere Application Server to be installed on the 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 WebSphere Application Server to be installed on the node.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.webservices.admin.resources.websvcsAdmin.dita
File name: com.ibm.ws.webservices.admin.resources.websvcsAdmin.html