Explanation | This informational message indicates the program status. |
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 instructions are 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 | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | These instructions are 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 try the command again. |
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. |
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 recognized as a valid command-line parameter. |
Action | Correct the command and try again. |
Explanation | This informational message indicates the program status. |
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 | Use only valid transport types 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 | Make sure that a valid enterprise archive (EAR) file name is passed. |
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. |
Explanation | The endpoint enabler started loading the specified EAR file into memory. |
Action | No user action is required. |
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. |
Explanation | The endpoint enabler has finished processing the specified EAR file. |
Action | No user action is required. |
Explanation | The endpoint enabler started to process the specified EJB module. |
Action | No user action is required. |
Explanation | The endpoint enabler finished processing the specified EJB module. |
Action | No user action is required. |
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. |
Explanation | The specified enterprise bean 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 enterprise archive (EAR) file because the user has specified a skip property for the indicated enterprise bean 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 input 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 try again. |
Explanation | The endpoint enabler is 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 is unable to read the specified deployment descriptor file. |
Action | Check for and correct any errors that the specified file might contain. |
Explanation | The endpoint enabler tool is saving the EAR file to disk. |
Action | No user action is required. |
Explanation | The endpoint enabler finished saving the EAR file to disk. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
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 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. |
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. |
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. |
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. |