WebSphere Web Services

WSWS2000I: {0}

Explanation

None.

User Response:

None.

WSWS2001I: Trace data will be displayed on stdout.

Explanation

The requested trace data will be logged to the standard output stream.

User Response:

None.

WSWS2002I: Please enter the name of an existing file.

Explanation

These are instructions for enabler tools.

User Response:

Follow instructions as requested.

WSWS2003I: Backing up EAR file to: {0}~

Explanation

The endpoint enabler tool is making a backup copy of the EAR file.

User Response:

None.

WSWS2004I: IBM WebSphere Application Server Release 5

Explanation

Standard IBM banner displayed by enabler tools.

User Response:

None.

WSWS2005I: Web Services Enterprise Archive Endpoint Enabler Tool.

Explanation

Standard IBM banner displayed by enabler tools.

User Response:

None.

WSWS2006I: Please enter the name of your EAR file:

Explanation

These are instructions for enabler tools.

User Response:

Follow instructions as requested.

WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2003.

Explanation

Standard IBM Copyright.

User Response:

None.

WSWS2008E: Missing value for '-transport' parameter.

Explanation

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 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.

User Response:

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.

User Response:

None.

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.

User Response:

Correct the command and re-try.

WSWS2012I: The endpoint enabler is using the following properties:

Explanation

Properties being used by the endpoint enabler.

User Response:

None.

WSWS2013E: Unrecognized transport: {0}

Explanation

An unrecognized transport type was specified for the '-transport' command-line parameter or within a .transports property. Valid transport types are: "http" and "jms".

User Response:

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.

User Response:

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.

User Response:

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.

User Response:

None.

WSWS2017I: Found EJB Module: {0}

Explanation

The endpoint enabler recognized the specified EJB jar within the EAR file, and is processing the EJB jar.

User Response:

None.

WSWS2018I: Finished processing EAR file {0}.

Explanation

The endpoint enabler tool has finished processing the specified EAR file.

User Response:

None.

WSWS2019I: Enabling EJB Module {0}...

Explanation

The endpoint enabler has started to process the specified EJB jar module.

User Response:

None.

WSWS2020I: Finished enabling EJB Module {0}...

Explanation

The endpoint enabler has finished processing the specified EJB jar module.

User Response:

None.

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.

User Response:

None.

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.

User Response:

None.

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.

User Response:

None.

WSWS2024I: Adding {0} router for EJB Module {1}.

Explanation

The endpoint enabler is adding a router module for the specified transport.

User Response:

None.

WSWS2025I: Router module name: {0}

Explanation

The endpoint enabler is displaying the name of the new router module.

User Response:

None.

WSWS2026I: Context root: {0}

Explanation

The endpoint enabler is displaying the context root for the new router module.

User Response:

None.

WSWS2027I: Listener Input Port: {0}

Explanation

The endpoint enabler is displaying the listener port for the new router module.

User Response:

None.

WSWS2028I: Destination type: {0}

Explanation

The endpoint enabler is displaying the destination type for the new router module.

User Response:

None.

WSWS2029I: Enter {0} router name for EJB Module {1} [{2}]:

Explanation

Requesting a name for the router module.

User Response:

Please follow instructions as requested.

WSWS2030I: Enter {0} context root for EJB Module {1} [{2}]:

Explanation

Requesting the context root for a router module.

User Response:

Please follow instructions as requested.

WSWS2031I: Enter {0} listener input port name for EJB Module {1} [{2}]:

Explanation

Requesting the listener port name for a router module.

User Response:

Please follow instructions as requested.

WSWS2032E: Invalid destination type specified: {0}

Explanation

Valid destination types include 'queue' and 'topic'.

User Response:

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.

User Response:

Please follow instructions as requested.

WSWS2034I: Usage syntax: endptEnabler [options] [trace options] [] 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 -p Load and use the properties contained in . -transport -t 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-line tool.

User Response:

None.

WSWS2035E: Error loading the JSR 109 deployment descriptor {0} for EJB Module {1}.

Explanation

The enabler tool was unable to read the specified deployment descriptor file. This is possibly due to some unexpected or invalid structure within.

User Response:

Please check for and correct any errors the reported file may contain.

WSWS2036I: Saving EAR file {0}...

Explanation

The endpoint enabler tool is saving the EAR file to disk.

User Response:

None.

WSWS2037I: Finished saving the EAR file.

Explanation

The endpoint enabler tool has finished saving the EAR file to disk.

User Response:

None.

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.

User Response:

None.

WSWS2039I: Trace data will be logged in file: {0}

Explanation

The requested trace data will be logged into the specified file.

User Response:

None.

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.

User Response:

None.

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.

User Response:

None.