WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


WSWS

WSWS2000I: {0}
Explanation None.
Action No user action is required.
WSWS2001I: Trace data will be displayed on stdout.
Explanation The requested trace data will be logged to the standard output stream.
Action No user action is required.
WSWS2002I: Please enter the name of an existing file.
Explanation These are instructions for the endpoint enabler.
Action No user action is required.
WSWS2003I: Backing up EAR file to: {0}~
Explanation The endpoint enabler is making a backup copy of the EAR file.
Action No user action is required.
WSWS2004I: IBM WebSphere Application Server Release 6
Explanation Standard IBM banner displayed by the endpoint enabler.
Action No user action is required.
WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
Explanation Standard IBM banner displayed by the endpoint enabler.
Action No user action is required.
WSWS2006I: Please enter the name of your EAR file:
Explanation These are instructions for the endpoint enabler.
Action No user action is required.
WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2004.
Explanation Standard IBM Copyright.
Action No user action is required.
WSWS2008E: Missing value for '-transport' parameter.
Explanation The '-transport' parameter was specified on the command line but the associated value was not specified.
Action Specify a value for the '-transport' parameter and re-try the command.
WSWS2009E: Missing value for '-properties' parameter.
Explanation The '-properties' parameter was specified on the command line but the associated properties filename was not specified.
Action Specify a properties filename for the '-properties' parameter and re-try the command.
WSWS2010I: Read properties from file: {0}
Explanation The endpoint enabler is reading properties from the specified file.
Action No user action is required.
WSWS2011E: ERROR: unrecognized command-line parameter found: {0}
Explanation The specified command-line parameter was encountered but is not a recognized as a valid command-line parameter.
Action Correct the command and re-try.
WSWS2012I: The endpoint enabler is using the following properties:
Explanation Properties being used by the endpoint enabler.
Action No user action is required.
WSWS2013E: Unrecognized transport: {0}
Explanation 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".
Action Ensure that only valid transport types are used on the command line and within the properties file.
WSWS2014E: 'EAR filename' parameter is missing or empty.
Explanation A null value or empty string was passed for the 'EAR filename' parameter to the EndpointEnabler.enableEarFile method.
Action Ensure that a valid EAR filename is passed.
WSWS2015E: 'props' parameter is missing.
Explanation A null value was passed for the 'props' parameter to the EndpointEnabler.enableEarFile method.
Action Ensure that a valid Properties object is passed for the 'props' parameter.
WSWS2016I: Loading EAR file: {0}
Explanation The endpoint enabler has started loading the specified EAR file into memory.
Action No user action is required.
WSWS2017I: Found EJB Module: {0}
Explanation The endpoint enabler recognized the specified EJB jar within the EAR file, and is processing the EJB jar.
Action No user action is required.
WSWS2018I: Finished processing EAR file {0}.
Explanation The endpoint enabler has finished processing the specified EAR file.
Action No user action is required.
WSWS2019I: Enabling EJB Module {0}...
Explanation The endpoint enabler has started to process the specified EJB jar module.
Action No user action is required.
WSWS2020I: Finished enabling EJB Module {0}...
Explanation The endpoint enabler has finished processing the specified EJB jar module.
Action No user action is required.
WSWS2021I: Skipping EJB Module {0} since it contains no Web services.
Explanation The specified EJB Module does not contain a JSR109 deployment descriptor. Therefore, it must not contain any Web services and does not need to be enabled.
Action No user action is required.
WSWS2022I: Skipping {0} router module for EJB Module {1} since it already contains a router for this transport.
Explanation The specified EJB Module already contains a router module for the specified transport.
Action No user action is required.
WSWS2023I: Skipping {0} router for EJB Module {1} due to 'skip' property.
Explanation The indicated router module will not be added to the EAR since the user specified a 'skip' property for the indicated EJB Module.
Action No user action is required.
WSWS2024I: Adding {0} router for EJB Module {1}.
Explanation The endpoint enabler is adding a router module for the specified transport.
Action No user action is required.
WSWS2025I: Router module name: {0}
Explanation The endpoint enabler is displaying the name of the new router module.
Action No user action is required.
WSWS2026I: Context root: {0}
Explanation The endpoint enabler is displaying the context root for the new router module.
Action No user action is required.
WSWS2027I: Listener input port: {0}
Explanation The endpoint enabler is displaying the listener port for the new router module.
Action No user action is required.
WSWS2028I: Destination type: {0}
Explanation The endpoint enabler is displaying the destination type for the new router module.
Action No user action is required.
WSWS2029I: Enter {0} router name for EJB Module {1} [{2}]:
Explanation The endpoint enabler is requesting a name for the router module.
Action Follow instructions as requested.
WSWS2030I: Enter {0} context root for EJB Module {1} [{2}]:
Explanation The endpoint enabler is requesting the context root for a router module.
Action Follow instructions as requested.
WSWS2031I: Enter {0} listener input port name for EJB Module {1} [{2}]:
Explanation The endpoint enabler is requesting the listener port name for a router module.
Action Follow instructions as requested.
WSWS2032E: Invalid destination type specified: {0}
Explanation Valid destination types include 'queue' and 'topic'.
Action Correct the destination type and re-try.
WSWS2033I: Enter {0} destination type for EJB Module {1} [{2}]:
Explanation Requesting the destination type for the router module.
Action Follow instructions as requested.
WSWS2034I: Usage syntax: endptEnabler [options] [trace options] [<ear-file-name>]

<ear-file-name> represents the name of the EAR file to be processed.
If not specified, the user will be 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 contained in
     <properties-file-name>.
-transport <transports-list>
-t <transports-list>
     The comma-separated default list of transports for
     which router modules should be created.
     The currently-supported transports include http and jms.
-enableHttpRouterSecurity
     Each HTTP router module created by endptEnabler will be protected if the EJBs
     in the corresponding EJB jar are also protected.
     Note that if this option is not specified, then no security information
     will be added to the HTTP router module, even if the corresponding EJB jar
     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
Explanation This message explains how to invoke the endptEnabler command.
Action No user action is required.
WSWS2035E: Error loading the JSR 109 deployment descriptor {0} for EJB Module {1}.
Explanation The endpoint enabler was unable to read the specified deployment descriptor file. This is possibly due to some unexpected or invalid structure within.
Action Please check for and correct any errors the specified file may contain.
WSWS2036I: Saving EAR file {0}...
Explanation The endpoint enabler tool is saving the EAR file to disk.
Action No user action is required.
WSWS2037I: Finished saving the EAR file.
Explanation The endpoint enabler has finished saving the EAR file to disk.
Action No user action is required.
WSWS2038I: Trace has been enabled for the following components: {0}
Explanation This message tells the user that tracing has been enabled for one or more components.
Action No user action is required.
WSWS2039I: Trace data will be logged in file: {0}
Explanation The requested trace data will be logged into the specified file.
Action No user action is required.
WSWS2040W: EJB jar {0} contains protected EJBs,
yet the -enableHttpRouterSecurity option was not specified, so the resulting
HTTP router module, {1}, will not include security information.
Explanation This is simply a warning which indicates security information will not be added to the HTTP router module since the -enableHttpRouterSecurity option was not specified on the command line. If you would like the HTTP router module to be protected, simply specify the -enableHttpRouterSecurity option.
Action No user action is required.
WSWS2041W: The -enableHttpRouterSecurity option was specified,
yet the EJB jar {0} contains at least one unprotected EJB or the existing
security information is incomplete. Therefore, security information will not be added
to the {1} HTTP router module.
Explanation This is simply a warning which indicates that security information will not be added to the HTTP router module since the EJB jar does not contain complete security information. If you would like the HTTP router module to be protected, make sure that the EJB jar contains complete security information.
Action No user action is required.
WSWS2042E: Listener input port {0} is already configured for JMS router module {1}.
Explanation A listener input port that is configured with a queue cannot be used with more than one JMS router module. The Web service implementations contained within a particular enterprise bean jar module share a listener input port and the associated queue, but the listener input port cannot be shared with another enterprise bean jar module.
Action Create a new listener input port and associate it with one of the JMS router modules.
WSWS2043I: Activation spec JNDI name: {0}
Explanation The endpoint enabler is displaying the activation spec JNDI name for the new router module.
Action No user action is required.
WSWS2044I: Enter {0} Activation spec JNDI name for EJB module {1} [{2}]:
Explanation The endpoint enabler is requesting the Activation spec JNDI name for a router module.
Action Follow instructions as requested.
WSWS2045I: EndpointEnabler failed with error:
{0}
Explanation The endpoint enabler encountered an error and did not succeed.
Action Correct the error and invoke the endpoint enabler command again.
Reference topic    

Terms of Use | Feedback

Last updated: Apr 23, 2009 7:19:30 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webservices.enabler.resources.enablerMessages.html

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