Explanation | The name of the published WSDL file must be a fully qualified and absolute path name. |
Action | Provide an absolute path name for the published WSDL file. |
Explanation | The directory that the published WSDL file is to be placed must already exist. |
Action | Specify an existing directory for the published WSDL file. |
Explanation | The only valid choices for the protocol are "http" and "https". |
Action | Specify 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. |
Action | Correct either or both of the files so that they match. |
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 for the Web service enabled jar file has a routerModuleName 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 in the application's application.xml file. |
Action | Make sure that the endptEnabler command 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Web services deployment descriptor is not properly formed. One possible reason is that its Web service description elements do not have an associated WSDL file. |
Action | Correct the deployment descriptor. |
Explanation | The Web services deployment descriptor is not properly formed. One if its webservice-description elements has an improperly formed port component element. |
Action | Correct the deployment descriptor. |
Explanation | The Web services binding file does not contain a properly formatted "routerModules" element. |
Action | Correct the bindings file. |
Explanation | Each EBJ-JAR file must have a related router WAR module. |
Action | Correct 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 | Correct the deployment descriptor. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This is a programming error. All the modules should have server names. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | This is a programming error. Assume that the MapModulesToServers task should have already validated that the 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 | Correct the WEB-INF/web.xml file. |
Explanation | The WEB-INF/web.xml file contains an error. |
Action | Correct the WEB-INF/web.xml file. |
Explanation | The webservices.xml file contains an error. |
Action | Correct the WEB-INF/webservices.xml file. |
Explanation | One of the WSDL files in a module is inconsistent with the Web services deployment descriptor. |
Action | Remove the inconsistency 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 | Make sure that the endptEnabler command is run on the application and that the application contains the required router module. |
Explanation | The router WAR module'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 specifications 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). |
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 | No action required. |
Explanation | The Web services deploy task has completed successfully. |
Action | No action required. |
Explanation | The Web services bindings file has incorrect information. The supported transports for router modules include jms and http. |
Action | Correct the Web services bindings file and re-try. |
Explanation | For all Web services enabled EJB module, at least one router module has to be created within the same application |
Action | Run endptEnabler to add appropriate router modules. |
Explanation | All applications have to be deployed into either a server or a cluster environment. |
Action | Correct the deployment.xml for 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/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 | There is no action required. |
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 | Ensure that the properties configured are combined into the first parameter element. |
Explanation | A 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 | The JMS URL prefix was not formatted correctly. The JMS URL prefix must start with jms:jndi: followed by the destination JNDI name, and it must include the jndiConnectionFactoryName property. The destination and connection factory JNDI names must not contain java:comp. |
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 not valid. |
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. |
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 user entered a JMS URL prefix string which starts with "jms:/queue" or "jms:/topic" which indicates that it follows the IBM proprietary JMS URL syntax. The IBM proprietary JMS URL syntax has been deprecated in favor of the industry standard JMS URL syntax. |
Action | Change your JMS URL prefix string so that it follows the industry standard JMS URL syntax. Consult the product documentation for more information. |