WebSphere Process Server messages     Operating Systems: All supported

WSWS

WSWS2000I: {0}
Problem This informational message indicates the program status.
User response No user action is required.
WSWS2001I: The trace data is displayed on the standard output stream.
Problem The requested trace data will be logged to the standard output stream.
User response No user action is required.
WSWS2002I: Enter the name of an existing file.
Problem These instructions are for the endpoint enabler.
User response No user action is required.
WSWS2003I: Backing up the enterprise archive (EAR) file to: {0}~
Problem The endpoint enabler is making a backup copy of the EAR file.
User response No user action is required.
WSWS2004I: IBM WebSphere Application Server Version 6.1
Problem This informational message indicates the program status.
User response No user action is required.
WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
Problem This informational message indicates the program status.
User response No user action is required.
WSWS2006I: Enter the name of your enterprise archive (EAR) file:
Problem These instructions are for the endpoint enabler.
User response No user action is required.
WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2006.
Problem Standard IBM Copyright.
User response No user action is required.
WSWS2008E: Missing value for the -transport parameter.
Problem The -transport parameter was specified on the command line, but the associated value was not specified.
User response Specify a value for the -transport parameter and try the command again.
WSWS2009E: Missing value for the -properties parameter.
Problem The -properties parameter was specified on the command line, but the associated properties file name was not specified.
User response Specify a properties file name for the -properties parameter and try the command again.
WSWS2010I: Read properties from file: {0}
Problem The endpoint enabler is reading properties from the specified file.
User response No user action is required.
WSWS2011E: An unrecognized command-line parameter was found: {0}
Problem The specified command-line parameter was encountered but is not recognized as a valid command-line parameter.
User response Correct the command and try again.
WSWS2012I: The endpoint enabler is using the following properties:
Problem This informational message indicates the program status.
User response No user action is required.
WSWS2013E: An unrecognized transport was specified: {0}
Problem An unrecognized transport type was specified for the -transport command-line parameter or within a <ejbjarname>.transports property. Valid transport types are: http and jms.
User response Use only valid transport types on the command line and within the properties file.
WSWS2014E: 'EAR filename' parameter is missing or empty.
Problem A null value or empty string was passed for the EAR filename parameter to the EndpointEnabler.enableEarFile method.
User response Make sure that a valid enterprise archive (EAR) file name is passed.
WSWS2015E: The props parameter is missing.
Problem A null value was passed for the props parameter to the EndpointEnabler.enableEarFile method.
User response Make sure that a valid Properties object is passed for the props parameter.
WSWS2016I: Loading enterprise archive (EAR) file: {0}
Problem The endpoint enabler started loading the specified EAR file into memory.
User response No user action is required.
WSWS2017I: Found enterprise bean module: {0}
Problem The endpoint enabler recognized the specified enterprise bean module within the EAR file, and is processing this module.
User response No user action is required.
WSWS2018I: Finished processing enterprise archive (EAR) file {0}.
Problem The endpoint enabler has finished processing the specified EAR file.
User response No user action is required.
WSWS2019I: Enabling enterprise bean module {0}...
Problem The endpoint enabler started to process the specified EJB module.
User response No user action is required.
WSWS2020I: Finished enabling enterprise bean module {0}...
Problem The endpoint enabler finished processing the specified EJB module.
User response No user action is required.
WSWS2021I: Skipping the enterprise bean module {0} because it contains no Web services.
Problem The specified enterprise bean module does not contain a JSR109 deployment descriptor. Therefore, this module does not contain any Web services and does not need enabling.
User response No user action is required.
WSWS2022I: Skipping {0} router module for enterprise bean module {1} because it already contains a router for this transport.
Problem The specified enterprise bean module already contains a router module for the specified transport.
User response No user action is required.
WSWS2023I: Skipping {0} router for enterprise bean module {1} due to the skip property.
Problem The indicated router module will not be added to the enterprise archive (EAR) file because the user has specified a skip property for the indicated enterprise bean module.
User response No user action is required.
WSWS2024I: Adding {0} router for enterprise bean module {1}.
Problem The endpoint enabler is adding a router module for the specified transport.
User response No user action is required.
WSWS2025I: Router module name: {0}
Problem The endpoint enabler is displaying the name of the new router module.
User response No user action is required.
WSWS2026I: Context root: {0}
Problem The endpoint enabler is displaying the context root for the new router module.
User response No user action is required.
WSWS2027I: Listener input port: {0}
Problem The endpoint enabler is displaying the listener input port for the new router module.
User response No user action is required.
WSWS2028I: Destination type: {0}
Problem The endpoint enabler is displaying the destination type for the new router module.
User response No user action is required.
WSWS2029I: Enter {0} router name for enterprise bean module {1} [{2}]:
Problem The endpoint enabler is requesting a name for the router module.
User response Follow instructions as requested.
WSWS2030I: Enter {0} context root for enterprise bean module {1} [{2}]:
Problem The endpoint enabler is requesting the context root for a router module.
User response Follow instructions as requested.
WSWS2031I: Enter {0} listener input port name for enterprise bean module {1} [{2}]:
Problem The endpoint enabler is requesting the listener port name for a router module.
User response Follow instructions as requested.
WSWS2032E: The destination type that is specified: {0} is not valid.
Problem Valid destination types include queue and topic.
User response Correct the destination type and try again.
WSWS2033I: Enter {0} destination type for enterprise bean module {1} [{2}]:
Problem The endpoint enabler is requesting the destination type for the router module.
User response Follow instructions as requested.
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. -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
Problem This message explains how to invoke the endptEnabler command.
User response No user action is required.
WSWS2035E: An error occurred loading the JSR 109 deployment descriptor {0} for enterprise bean module {1}.
Problem The endpoint enabler is unable to read the specified deployment descriptor file.
User response Check for and correct any errors that the specified file might contain.
WSWS2036I: Saving the enterprise archive (EAR) file {0}...
Problem The endpoint enabler tool is saving the EAR file to disk.
User response No user action is required.
WSWS2037I: Finished saving the enterprise archive (EAR) file.
Problem The endpoint enabler finished saving the EAR file to disk.
User response No user action is required.
WSWS2038I: Trace is enabled for the following components: {0}
Problem This informational message indicates the program status.
User response No user action is required.
WSWS2039I: Trace data will be logged in file: {0}
Problem The requested trace data will be logged into the specified file.
User response No user action is required.
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.
Problem This warning indicates that security information will not be added to the HTTP router module because the -enableHttpRouterSecurity option was not specified on the command line. If you want the HTTP router module to be protected, specify the -enableHttpRouterSecurity option.
User response No user action is required.
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.
Problem This warning indicates that security information will not be added to the HTTP router module because the enterprise bean module does not contain complete security information. If you want the HTTP router module to be protected, make sure that the enterprise bean module contains complete security information.
User response No user action is required.
WSWS2042E: Listener input port {0} is already configured for JMS router module {1}.
Problem A listener input port that is configured with a queue cannot be used with more than one JMS router module. The Web service implementations that are contained within a particular enterprise bean module share a listener input port and the associated queue, but the listener input port cannot be shared with another enterprise bean module.
User response Create a new listener input port and associate it with one of the JMS router modules.
WSWS2043I: Activation spec JNDI name: {0}
Problem The endpoint enabler is displaying the activation spec JNDI name for the new router module.
User response No user action is required.
WSWS2044I: Enter {0} activation spec JNDI name for enterprise bean module {1} [{2}]:
Problem The endpoint enabler is requesting the Activation spec JNDI name for a router module.
User response Follow instructions as requested.
WSWS2045I: EndpointEnabler failed with error: {0}
Problem The endpoint enabler encountered an error and did not succeed.
User response Correct the error and invoke the endpoint enabler command again.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webservices.enabler.resources.enablerMessages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)