Explanation | The name of the published WSDL file must be an fully qualified, absolute, path name. |
Action | Provide an absolute path. |
Explanation | The directory into which the published WSDL file is to be placed must already exist. |
Action | Name an existing directory. |
Explanation | The only valid choices for the protocol are "http" and "https". |
Action | sSpecify either "http" or "https". |
Explanation | Port must be a positive number. |
Action | Provide a positive number. |
Explanation | The exception details should provide additional information. |
Action | The exception details should give guidance on what to do. |
Explanation | The exception details should provide additional information. |
Action | The exception details should give guidance on what to do. |
Explanation | The values in the wsdl file and the Web services Deployment Descriptor must match up. |
Action | Correct one of the files. |
Explanation | There may be a syntax error in the input WSDL file. |
Action | Check the input WSDL file for any errors. |
Explanation | Could not create output WSDL file. |
Action | The exception details should give some guidance. |
Explanation | Could not create a working directory. |
Action | The exception details should give some guidance. |
Explanation | Could not get the InputStream. |
Action | The exception details should give some guidance. |
Explanation | The ibm-webservice-bnd.dtd file of Web service enabled jar file has routeModuleName attribute whose value does not match any Web module described in the application's application.xml file. Or, a Web service enabled war file does not appear i the application's application.xml file. |
Action | Check the ibm-webservice-bnd.dtd and application.xml files. Make sure the endpointEnabler has been run on the ear file. |
Explanation | There is a mismatch between the information in the Web services Deployment Descriptor and the information in the Web services Binding file. |
Action | Make the two files consistent. |
Explanation | The exception details should provide additional information. |
Action | The exception details should give some guidance. |
Explanation | If a webservices.xml file has a reference to a WSDL file then that WSDL file must exist in the module. |
Action | Add the expected WSDL file. |
Explanation | A Web service enabled module must contain a Web services binding file. |
Action | Add the missing binding file using either the Assembly Toolkit or the endptEnabler command. |
Explanation | The resource bundle for your locale was not found. This will prevent logging of information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Web services Deployment Descriptor is not properly formed, one if its webservice-description elements does not have a wsdl-file element. |
Action | Fix the DeploymentDescriptor. |
Explanation | The Web services Deployment Descriptor is not properly formed, one if its webservice-description elements has an improperly formed portcomponent element. |
Action | Fix the DeploymentDescriptor. |
Explanation | The Web services binding file does not contain a properly formatted "routerModules" element. |
Action | Fix the bindings file. |
Explanation | Each EBJ-JAR file must have a related router WAR module. |
Action | Fix the application. |
Explanation | An IOException occurred while copying a file. |
Action | The exception details should give some guidance. |
Explanation | There is a name conflict between directory and file system name. |
Action | Remove the file. |
Explanation | The Web services Deployment Descriptor is not properly formed, one if its webservice-description elements does not have a webservice-description-name element. |
Action | Fix the DeploymentDescriptor. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is a programming error. All the modules shouldhave server names. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | This is a programming error. Assume that theMapModulesToServers task should have already validated thatthe user input has the correct syntax. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | The web.xml file contains an error. |
Action | Repair the web.xml file. |
Explanation | The web.xml file contains an error. |
Action | Repair the web.xml file. |
Explanation | The webservices.xml file contains an error. |
Action | Repair the webservices.xml file. |
Explanation | One of the WSDL files in a module is inconsistent with the Web services deployment descriptor. |
Action | remove the inconsistency, either by removing the port from the WSDL file or adding a corresponding port-component to the Deployment Descriptor. |
Explanation | The router war module is missing from the application. |
Action | Fix the application. |
Explanation | The router WAR's web.xml is not correct. |
Action | Make sure the servlet-mapping element is there and that it contains a url-pattern. |
Explanation | Older versions of Web services specification allowed the wsdl-file element of the Web services Deployment Descriptor to point anywhere in the module. The current version recommends that all WSDL files reside in or below WEB-INF/wsdl (for WAR modules) and META-INF/wsdl (for JAR modules).. In the future, WSDL files that do not reside in or below the appropriate wsdl directory will not be published to URI, or to file. |
Action | Move all WSDL files to the wsdl directory. |
Explanation | Web services deploy tool reported an error, the deployment may have failed. |
Action | Examine the error message from WSDeploy tool to determine the source of the problem. |
Explanation | Web services deploy tool reports a warning, the deployment may or may not fail. |
Action | Examine the warning message from WSDeploy to determine whether any corrective action is necessary. |
Explanation | None. |
Action | None. |
Explanation | The Web services deploy task has completed successfully. |
Action | None. |
Explanation | The Web services bindings file has incorrect information |
Action | Correct the Web services bindings file |
Explanation | For all Web services enabled EJB module, at least one router module has to be created within the same application |
Action | Run endpointEnabler to add appropriate router modules |
Explanation | All applications have to deployed into either a server or a cluster. |
Action | Correct the deployment.xml for this the application or reinstall the application. |
Explanation | The web.xml for the router war module should have one url pattern for each port component defined within webservices.xml. |
Action | Correct the web.xml for this router module. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | All Web services enabled applications should have at least one wsdl file. |
Action | If the application is Web services enabled, check to see whether wsdl files are packaged with the application. |
Explanation | The Web services endpointenabler task has completed successfully. |
Action | None. |
Explanation | Incorrect user input for EJB URL suffix |
Action | Provide correct input. |
Explanation | There is an inconsistency in the Web services client configurartion. |
Action | Ensure that the WSDL file configured for this client contains the port type. |
Explanation | Only element zero of the custom property parameters object is used. |
Action | Product code should make sure the properties configured are combined into the first parameter element. Report an error to support. |
Explanation | An problem occurred while creating a mapping of port types and the ports that could be configured for them. This information is generated from the client deployment descriptor and the WSDL file. |
Action | Ensure that Web services client in this module is probably configured and the WSDL file identified in the client deployment descriptor is in the module. |
Explanation | A Web service client preferred port must implement its port type. The client WSDL file specifies ports, bindings and port types. |
Action | Specify a preferred port that implements the port type. |
Explanation | Incorrect user input for JMS URL prefix. |
Action | Provide correct input. |
Explanation | Incorrect user input provided for Web service scope. |
Action | Provide correct input. Correct values are Application, Request, and Session. |
Explanation | Incorrect user input provided for Web service client resquest timeout. The timeout is number of milliseconds to wait for a request to complete. |
Action | Provide correct input. The value must be a positive integer, 0, or -1. |
Explanation | The user input provided for Web service client overridden endpoint URL is not a valid URL. |
Action | Provide correct input. The value must be a valid URL that represents an HTTP port, JMS port, or a local ejb. |
Explanation | The user input provided for Web service client's deployed WSDL is invalid. |
Action | Provide correct input. The deployed WSDL value must be a uri relative to the module and represent a WSDL file that is in the client's module. |
Explanation | The overridden binding namespace cannot be specified unless the overridden endpoint URL is specified or previously defined. |
Action | Provide a value for Web service client overridden endpoint URL or do not specify a value for the overridden binding namespace. |