WSWS

WSWS2000I: {0}
WSWS2001I: The trace data is displayed on the standard output stream.
WSWS2002I: Enter the name of an existing file.
WSWS2003I: Backing up the enterprise archive (EAR) file to: {0}~
WSWS2004I: IBM WebSphere Application Server Version 8.0
WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
WSWS2006I: Enter the name of your enterprise archive (EAR) file:
WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2010.
WSWS2008E: Missing value for the -transport parameter.
WSWS2009E: Missing value for the -properties parameter.
WSWS2010I: Read properties from file: {0}
WSWS2011E: An unrecognized command-line parameter was found: {0}
WSWS2012I: The endpoint enabler is using the following properties:
WSWS2013E: An unrecognized transport was specified: {0}
WSWS2014E: 'EAR filename' parameter is missing or empty.
WSWS2015E: The props parameter is missing.
WSWS2016I: Loading enterprise archive (EAR) file: {0}
WSWS2017I: Found enterprise bean module: {0}
WSWS2018I: Finished processing enterprise archive (EAR) file {0}.
WSWS2019I: Enabling enterprise bean module {0}...
WSWS2020I: Finished enabling enterprise bean module {0}...
WSWS2021I: Skipping the enterprise bean module {0} because it contains no Web services.
WSWS2022I: Skipping {0} router module for enterprise bean module {1} because it already contains a router for this transport.
WSWS2023I: Skipping {0} router for enterprise bean module {1} due to the skip property.
WSWS2024I: Adding {0} router for enterprise bean module {1}.
WSWS2025I: Router module name: {0}
WSWS2026I: Context root: {0}
WSWS2027I: Listener input port: {0}
WSWS2028I: Destination type: {0}
WSWS2029I: Enter {0} router name for enterprise bean module {1} [{2}]:
WSWS2030I: Enter {0} context root for enterprise bean module {1} [{2}]:
WSWS2031I: Enter {0} listener input port name for enterprise bean module {1} [{2}]:
WSWS2032E: The destination type that is specified: {0} is not valid.
WSWS2033I: Enter {0} destination type for enterprise bean module {1} [{2}]:
WSWS2034I: Usage syntax: endptEnabler [options] [trace options] [<ear-file-name>] <ear-file-name> represents the name of the enterprise archive (EAR) file to process. If not specified, the user is prompted for this value. Options: -help, -h, -?      Print this message and exit. -verbose, -v      Print detailed progress messages while the EAR file is      being processed. -quiet, -q      Do not print progress messages while the EAR file is      being processed. -properties <properties-file-name> -p <properties-file-name>      Load and use the properties that are contained in      <properties-file-name>. -transport <transports-list> -t <transports-list>      The comma-separated default list of transports for      which router modules to create.      The currently-supported transports include http and jms. -classpath <classpath> -cp <classpath>      Set additional directories, zip, and jar files in search path.      Separate multiple entries with the file separator character      specific to your operating system. -enableHttpRouterSecurity      Each HTTP router module that is created by endptEnabler are protected if the enterprise beans      in the corresponding enterprise bean module are also protected.      Note that if this option is not specified, no security information      is added to the HTTP router module, even if the corresponding enterprise bean module      contains security information. {0} Examples:      endptEnabler      endptEnabler myearfile.ear      endptEnabler -v myearfile.ear      endptEnabler -v -transports jms myearfile.ear      endptEnabler -q -p myenabler.props -t http myearfile.ear
WSWS2035E: An error occurred loading the JSR 109 deployment descriptor {0} for enterprise bean module {1}.
WSWS2036I: Saving the enterprise archive (EAR) file {0}...
WSWS2037I: Finished saving the enterprise archive (EAR) file.
WSWS2038I: Trace is enabled for the following components: {0}
WSWS2039I: Trace data will be logged in file: {0}
WSWS2040W: The enterprise bean module {0} contains protected enterprise beans, yet the -enableHttpRouterSecurity option was not specified, so the resulting HTTP router module, {1}, will not include security information.
WSWS2041W: The -enableHttpRouterSecurity option was specified, yet the enterprise bean module {0} contains at least one unprotected enterprise bean or the existing security information is incomplete. Therefore, security information will not be added to the {1} HTTP router module.
WSWS2042E: Listener input port {0} is already configured for JMS router module {1}.
WSWS2043I: Activation spec JNDI name: {0}
WSWS2044I: Enter {0} activation spec JNDI name for enterprise bean module {1} [{2}]:
WSWS2045I: EndpointEnabler failed with error: {0}
WSWS2046W: The {0} WAR module generated by EndpointEnabler contains multiple servlets with the same URL pattern. This must be fixed before installing the application.
WSWS2047I: URL pattern for port {0}: {1}
WSWS2048I: Missing value for the -classpath parameter.


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.enabler.resources.enablerMessages.dita
File name: com.ibm.ws.webservices.enabler.resources.enablerMessages.html