Explanation | None. |
Action | No user action is required. |
Explanation | The requested trace data will be logged to the standard output stream. |
Action | No user action is required. |
Explanation | These are instructions for the endpoint enabler. |
Action | No user action is required. |
Explanation | The endpoint enabler is making a backup copy of the EAR file. |
Action | No user action is required. |
Explanation | Standard IBM banner displayed by the endpoint enabler. |
Action | No user action is required. |
Explanation | Standard IBM banner displayed by the endpoint enabler. |
Action | No user action is required. |
Explanation | These are instructions for the endpoint enabler. |
Action | No user action is required. |
Explanation | Standard IBM Copyright. |
Action | No user action is required. |
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. |
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. |
Explanation | The endpoint enabler is reading properties from the specified file. |
Action | No user action is required. |
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. |
Explanation | Properties being used by the endpoint enabler. |
Action | No user action is required. |
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. |
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. |
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. |
Explanation | The endpoint enabler has started loading the specified EAR file into memory. |
Action | No user action is required. |
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. |
Explanation | The endpoint enabler has finished processing the specified EAR file. |
Action | No user action is required. |
Explanation | The endpoint enabler has started to process the specified EJB jar module. |
Action | No user action is required. |
Explanation | The endpoint enabler has finished processing the specified EJB jar module. |
Action | No user action is required. |
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. |
Explanation | The specified EJB Module already contains a router module for the specified transport. |
Action | No user action is required. |
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. |
Explanation | The endpoint enabler is adding a router module for the specified transport. |
Action | No user action is required. |
Explanation | The endpoint enabler is displaying the name of the new router module. |
Action | No user action is required. |
Explanation | The endpoint enabler is displaying the context root for the new router module. |
Action | No user action is required. |
Explanation | The endpoint enabler is displaying the listener port for the new router module. |
Action | No user action is required. |
Explanation | The endpoint enabler is displaying the destination type for the new router module. |
Action | No user action is required. |
Explanation | The endpoint enabler is requesting a name for the router module. |
Action | Follow instructions as requested. |
Explanation | The endpoint enabler is requesting the context root for a router module. |
Action | Follow instructions as requested. |
Explanation | The endpoint enabler is requesting the listener port name for a router module. |
Action | Follow instructions as requested. |
Explanation | Valid destination types include 'queue' and 'topic'. |
Action | Correct the destination type and re-try. |
Explanation | Requesting the destination type for the router module. |
Action | Follow instructions as requested. |
Explanation | This message explains how to invoke the endptEnabler command. |
Action | No user action is required. |
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. |
Explanation | The endpoint enabler tool is saving the EAR file to disk. |
Action | No user action is required. |
Explanation | The endpoint enabler has finished saving the EAR file to disk. |
Action | No user action is required. |
Explanation | This message tells the user that tracing has been enabled for one or more components. |
Action | No user action is required. |
Explanation | The requested trace data will be logged into the specified file. |
Action | No user action is required. |
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. |
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. |
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. |
Explanation | The endpoint enabler is displaying the activation spec JNDI name for the new router module. |
Action | No user action is required. |
Explanation | The endpoint enabler is requesting the Activation spec JNDI name for a router module. |
Action | Follow instructions as requested. |
Explanation | The endpoint enabler encountered an error and did not succeed. |
Action | Correct the error and invoke the endpoint enabler command again. |