Express (Distributed operating systems), v8.0 > Reference > Messages
WSWS
WSWS2000I: {0}
Explanation This informational message indicates the program status. Action No user action is required.
WSWS2001I: The trace data is displayed on the standard output stream.
Explanation The requested trace data will be logged to the standard output stream. Action No user action is required.
WSWS2002I: Enter the name of an existing file.
Explanation These instructions are for the endpoint enabler. Action No user action is required.
WSWS2003I: Backing up the 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 WAS v8.0
Explanation This informational message indicates the program status. Action No user action is required.
WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
Explanation This informational message indicates the program status. Action No user action is required.
WSWS2006I: Enter the name of your EAR file:
Explanation These instructions are for the endpoint enabler. Action No user action is required.
WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2010.
Explanation Standard IBM Copyright. Action No user action is required.
WSWS2008E: Missing value for the -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 try the command again.
WSWS2009E: Missing value for the -properties parameter.
Explanation The -properties parameter was specified on the command line, but the associated properties file name was not specified. Action Specify a properties file name for the -properties parameter and try the command again.
WSWS2010I: Read properties from file: {0}
Explanation The endpoint enabler is reading properties from the specified file. Action No user action is required.
WSWS2011E: An unrecognized command-line parameter was found: {0}
Explanation The specified command-line parameter was encountered but is not recognized as a valid command-line parameter. Action Correct the command and try again.
WSWS2012I: The endpoint enabler is using the following properties:
Explanation This informational message indicates the program status. Action No user action is required.
WSWS2013E: An unrecognized transport was specified: {0}
Explanation An unrecognized transport type was specified for the -transport command-line parameter or within a <ejbjarname>.transports property. Valid transport types are: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ and jms. Action Use only valid transport types 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 Make sure that a valid EAR file name is passed.
WSWS2015E: The props parameter is missing.
Explanation A null value was passed for the props parameter to the EndpointEnabler.enableEarFile method. Action Make sure that a valid Properties object is passed for the props parameter.
WSWS2016I: Loading EAR file: {0}
Explanation The endpoint enabler started loading the specified EAR file into memory. Action No user action is required.
WSWS2017I: Found enterprise bean module: {0}
Explanation The endpoint enabler recognized the specified enterprise bean module within the EAR file, and is processing this module. 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 enterprise bean module {0}...
Explanation The endpoint enabler started to process the specified EJB module. Action No user action is required.
WSWS2020I: Finished enabling enterprise bean module {0}...
Explanation The endpoint enabler finished processing the specified EJB module. Action No user action is required.
WSWS2021I: Skipping the enterprise bean module {0} because it contains no Web services.
Explanation 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. Action No user action is required.
WSWS2022I: Skipping {0} router module for enterprise bean module {1} because it already contains a router for this transport.
Explanation The specified enterprise bean module already contains a router module for the specified transport. Action No user action is required.
WSWS2023I: Skipping {0} router for enterprise bean module {1} due to the skip property.
Explanation The indicated router module will not be added to the EAR file because the user has specified a skip property for the indicated enterprise bean module. Action No user action is required.
WSWS2024I: Adding {0} router for enterprise bean 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 input 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 enterprise bean 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 enterprise bean 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 enterprise bean module {1} [{2}]:
Explanation The endpoint enabler is requesting the listener port name for a router module. Action Follow instructions as requested.
WSWS2032E: The destination type specified: {0} is not valid.
Explanation Valid destination types include queue and topic. Action Correct the destination type and try again.
WSWS2033I: Enter {0} destination type for enterprise bean module {1} [{2}]:
Explanation The endpoint enabler is 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 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 //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ 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 //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ myearfile.ear
Explanation This message explains how to invoke the endptEnabler command. Action No user action is required.
WSWS2035E: An error occurred loading the JSR 109 deployment descriptor {0} for enterprise bean module {1}.
Explanation The endpoint enabler is unable to read the specified deployment descriptor file. Action Check for and correct any errors that the specified file might contain.
WSWS2036I: Saving the 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 finished saving the EAR file to disk. Action No user action is required.
WSWS2038I: Trace is enabled for the following components: {0}
Explanation This informational message indicates the program status. 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: 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.
Explanation 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. Action 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.
Explanation 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. 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 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. 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 enterprise bean 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.
WSWS2046W: The {0} WAR module generated by EndpointEnabler contains multiple servlets with the same URL pattern. This must be fixed before installing the application.
Explanation The endpoint enabler tool generated a WAR module which contains multiple servlets that are mapped to the same url pattern. The application cannot be successfully installed until this is corrected. Action Either update the web.xml in the WAR module or run EndpointEnabler with a properties file specifying custom url patterns for each port.
WSWS2047I: URL pattern for port {0}: {1}
Explanation The endpoint enabler tool has set the specified URL pattern for the indicated WSDL port within the generated HTTP router module. Action No user action is required.
WSWS2048I: Missing value for the -classpath parameter.
Explanation The -classpath parameter was specified on the command line, but the value was not given. Action Specify a value with the -classpath parameter and try the command again.