Explanation | The cell name is a required value. |
Action | You must specify a cell name. |
Explanation | Both the server name and the node name are required for single-server plug-in generation. |
Action | If you specify a server name, you must specify a node name. |
Explanation | An unknown parameter is encountered. |
Action | Review the usage information of the GenPluginCfg utility for valid parameters. |
Explanation | An error occurred while the utility was running. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example, run GenPluginCfg -debug yes. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the name of the plug-in configuration file. |
Action | No user action is required. |
Explanation | An error occured while generating the plug-in configuration file. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example run GenPluginCfg -debug yes. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while generating the plug-in configuration file. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example run GenPluginCfg -debug yes. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates that the configuration file for the cell is generating. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | A cell name is required. |
Action | Specify a cell name. Verify that the configuration data is saved in the repository. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | Nodes or clusters are not defined in the present configuration. Servers are not available for which to generate a plug-in configuration. |
Action | Create nodes and clusters that have servers in them using either the administrative console, or the wsadmin.sh tool. |
Explanation | Servers are not defined in the given cell. Servers are not available for which to generate a plug-in configuration. |
Action | Create servers within the nodes and clusters before running the tool, by using either the administrative console or the wsadmin.sh tool. |
Explanation | One or more of the cluster members do not have server names. |
Action | Use the administrative console or the wsadmin.sh tool to fix this problem. |
Explanation | This error occurred because of a corrupted cluster configuration file. |
Action | Use the administrative console to cluster your servers again. If that action fails, delete any cluster configuration that is present and try again. Make sure that the configuration data is saved in the repository. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This error occured because of a corrupted cluster configuration file. |
Action | Use the administrative console or the wsadmin.sh tool to cluster your servers again. If that action fails, delete any cluster configuration that is present and try again. |
Explanation | No cells are found in your existing configuration. |
Action | Use the administrative console or the wsadmin.sh tool to create the cells. |
Explanation | No servers are found in the specified cluster. |
Action | Use either the administrative console or the wsadmin tool to configure the servers within the cluster. |
Explanation | No servers are found. No servers are available for which to generate the plug-in configuration. |
Action | Use either the administrative console or the wsadmin.sh tool to configure the servers within the cluster. |
Explanation | No configuration data is found for one or more of the servers that you specified. |
Action | Use either the administrative console or the wsadmin.sh tool to configure your servers. |
Explanation | No configuration data is found for one or more of the servers that you specified. |
Action | Use either the administrative console or the wsadmin.sh tool to configure your servers. |
Explanation | No configuration data is available for the Web container component of one or more of the specified servers. |
Action | Use either the administrative console or the wsadmin.sh tool to configure the Web containers again. |
Explanation | No configuration data for the Web container component is available for one or more of the specified servers. |
Action | Use either the administrative console or the wsadmin.sh tool to configure the Web containers again. |
Explanation | The present configuration did not contain a server index file. This missing file can result from a corrupted configuration. |
Action | Verify that the serverindex.xml file exists. If it does not exist, create the file. |
Explanation | One or more of the applications that are deployed on the specified servers cannot be read. |
Action | Examine the exception information. Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example: run GenPluginCfg -debug yes. If the problem persists, redeploy the application. Verify that the enterprise archive (EAR) file and the Web archive (WAR) file are valid. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | One or more of the applications that are deployed on the specified servers cannot be read. |
Action | Examine the exception. Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example: run GenPluginCfg -debug yes. Make sure that the configuration data is saved in the repository. If the problem persists, redeploy the application. Verify that the enterprise archive (EAR) file and the Web archive (WAR) file are valid. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Nodes are not defined in the present configuration. This problem can result from a corrupted configuration. |
Action | Verify that the configuration data is saved in the repository. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Make sure that the configuration data is saved in the repository. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A problem resulted from generating the plug-in configuration file. |
Action | Examine the exception for nested exceptions and error codes. Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example, run the following command: GenPluginCfg -debug yes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A problem resulted from generating the configuration file. |
Action | Examine the exception for nested exceptions and error codes. Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example, run the following command: GenPluginCfg -debug yes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates a root exception. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example, run the following command: GenPluginCfg -debug yes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example, run the following command: GenPluginCfg -debug yes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes to see trace details. For example, run the following command: GenPluginCfg -debug yes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The webservices.jar file might not be in the class path. |
Action | Check the class path and include the java archive (JAR) file, if necessary. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | You can specify only one node when multiple servers are passed as parameters. |
Action | Specify only one node using either the administrative console or the wsadmin.sh tool. |
Explanation | The Lotus Workplace server helper class did not load. |
Action | No user action is required, if Lotus Workplace servers are not defined. If you define Lotus Workplace servers, verify that the class path includes the cfplugin.jar file. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The HTTP tunnel configuration helper class did not load. |
Action | No user action is required if the servers that use the HTTP tunnel are not defined. If the servers are defined using the HTTP tunnel, verify that the class path includes the cfplugin.jar file. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | Node synchronization is used to move the plug-in configuration file to the managed node. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Application Server cannot transfer the plug-in configuration file. |
Action | Verify that the IBM HTTP Server administration server is configured correctly. |
Explanation | The propagation of the plug-in configuration file to the remote Web server is supported for the IBM HTTP Server Web server only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Application Server cannot generate the plug-in configuration file. |
Action | Enable trace for the com.ibm.websphere.plugincfg.generator.* classes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Application Server cannot determine the type of the server |
Action | Enable trace for the com.ibm.websphere.plugincfg.generator.* classes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Application Server cannot retrieve the list of Web servers. |
Action | Enable trace for the com.ibm.websphere.plugincfg.generator.* classes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Application Server cannot retrieve the plug-in properties. |
Action | Enable trace for the com.ibm.websphere.plugincfg.generator.* classes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Application Server cannot start the plug-in configuration service. |
Action | Enable trace for the com.ibm.websphere.plugincfg.generator.* classes. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The plug-in configuration service is started when it is enabled only, and is run on the deployment manager server or the stand-alone Application Server. |
Action | No user action is required. |
Explanation | The plug-in configuration file for the Web server is generated based on the applications that are mapped to it. Applications are not mapped to the Web server. |
Action | Use the Application Installation wizard to map modules to the Web server. |
Explanation | This informational message indicates the name of the debug log file. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Application Server cannot transfer the plug-in configuration file. |
Action | Verify that the administration server for IBM HTTP Server is configured correctly. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Application Server cannot transfer the plug-in keyring file. |
Action | Verify that administration server IBM HTTP Server is configured correctly. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Application Server cannot transfer the plug-in stash file. |
Action | Verify that the administration server for IBM HTTP Server is configured correctly. |
Explanation | Node synchronization is used to move the plug-in keyring and stash file to the managed node. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Application Server cannot transfer the plug-in keyring file. |
Action | Verify that the administration server for IBM HTTP Server is configured correctly. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The Appplication Server cannot transfer the plug-in stash file. |
Action | Verify that the administration server for IBM HTTP Server is configured correctly. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | Node synchronization has already propagated the plug-in configuration file to the managed node. |
Action | No user action is required. |
Explanation | Node synchronization has already propagated the stash file to the managed node. |
Action | No user action is required. |
Explanation | The configuration root specified is incorrect. The plug-in configuration generator is not able to access the repository. |
Action | Verify that configuration root is correctly passed to the plug-in configuration generator. |
Explanation | No web servers are defined in the specified cell. |
Action | No user action is required. |
Explanation | Only HTTP transport is configured. All communication between web server and application server will be in clear text. |
Action | Evaluate if HTTP transport is required for your environment. If sensitive information is being transmitted between the web server and the application server, it is recommended to use HTTPS (SSL) transports between the web server and the application server. |
Explanation | HTTPS transport is configured. Secure communication can take place between web server and application server. |
Action | No user action is required. |
Explanation | There are no HTTP nor HTTPS transports defined Web server and Application Server. |
Action | Set up HTTPS (SSL) transports between the web server and application server, in order to have the communication between web server and the application server be encrypted. |
Explanation | The Web server will prevent an HTTP request from being sent to the Application Server if the value specified in host header does not exist in the filter. The request is then served by the Web server. |
Action | Make sure that the web server document root does not point to Application Server source files and change the Virtual Host Name in virtualhosts.xml to filter generic requests, for example, *:9080. |
Explanation | Requests are not being filtered. The Web server Plug-in will process all requests and forward each to an application server running the requested application. |
Action | For more protection, make sure the Web server document root does not point to Application Server source files. |
Explanation | The Application Server cannot parse the specified configuration file. |
Action | Check the location of the file and make sure that it has valid contents. |
Explanation | The configuration has no application servers defined. |
Action | Make sure that some application servers are defined and used by the web server. |
Explanation | The Application Server has no Transports defined in plug-in configuration. |
Action | Set up HTTPS (SSL) transports between the webserver and application server, in order to have the communication between webserver and application server be encrypted. |
Explanation | No host aliases are defined for virtual host groups. |
Action | Make sure that virtual host group definitions has some host aliases. |