no.valid.servers.for.cluster=PLGC0020E: No valid server definitions are found for the server cluster No servers are found in the specified cluster. Use either the administrative console or the wsadmin tool to configure the servers within the cluster. single.server.gen=PLGC0008I: The plug-in is generating a single-server plug-in configuration file for the cell. This informational message indicates that the configuration file for the cell is generating. No user action is required. propagate.failed=PLGC0049E: The propagation of the plug-in configuration file failed for the Web server. The Application Server cannot transfer the plug-in configuration file. Verify that the IBM HTTP Server administration server is configured correctly. servertype.unknown=PLGC0054E: The plug-in is unable to get the server type for the server. The Application Server cannot determine the type of the server 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/. exception.reading.web.con=PLGC0024E: An exception occurred while getting the Web container configuration for the specified server. No configuration data is available for the Web container component of one or more of the specified servers. Use either the administrative console or the wsadmin.sh tool to configure the Web containers again. morethan.one.node=PLGC0040I: More than one node is specified in the list; only the first node is selected. You can specify only one node when multiple servers are passed as parameters. Specify only one node using either the administrative console or the wsadmin.sh tool. hostname.filter.does.not.exists.risk=PLGC0082I: There are no filters based on host names in virtualhosts.xml. The requests are not being filtered according to specific host names in virtualhosts.xml. This protects against the security exposure in which JSP source code shown by the Web server. 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. For more protection, make sure the Web server document root does not point to Application Server source files. propagate.keyring.location=PLGC0064I: The plug-in keyring file is propagated from {0} to {1} on the Web server computer. This message is for informational purposes only. No user action is required. pluginconfigservice.starterror=PLGC0058E: The plug-in cannot initialize the plug-in configuration service. The Application Server cannot start the plug-in configuration service. 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/. https.transport.exists.risk=PLGC0079I: HTTPS transport is defined between the web server {0} and the application server {1}. Communication between the web server and application server is over HTTPS which is encrypted and secure. HTTPS transport is configured. Secure communication can take place between web server and application server. No user action is required. clusteraddressendpoint.duplicates.https=PLGC0088E: The clusterAddress has more than one HTTPS transport defined. Only one HTTPS transport can be defined for the clusterAddress. Use the administrative console or the wsadmin.sh tool to fix this problem. propagate.location.failed=PLGC0063E: The propagation of the plug-in configuration file from {0} to {1} on the Web server computer failed. The Application Server cannot transfer the plug-in configuration file. Verify that the administration server for IBM HTTP Server is configured correctly. propagate.notsupported=PLGC0050W: The propagation of the plug-in configuration file is not supported for the remote Web server. The propagation of the plug-in configuration file to the remote Web server is supported for the IBM HTTP Server Web server only. No user action is required. error.reading.lotusuris=PLGC0044W: An exception occurred while getting the URI lists for Lotus workplace clusters. This message is for informational purposes only. No user action is required. no.nodes.in.cell=PLGC0030E: No nodes are defined in the cell. Nodes are not defined in the present configuration. This problem can result from a corrupted configuration. 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/. rerun.with.debug=PLGC0004E: An exception occurred while running the GenPluginCfg utility. An error occurred while the utility was running. 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/. no.def.for.pmirm=PLGC0073W: No definition is found for request metrics. This informational message indicates the program status. No user action is required. exception.parsing.cluster=PLGC0018E: An exception occurred while reading the server cluster configuration for a cluster. This error occured because of a corrupted cluster configuration file. 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. no.alias.tag.exists.risk=PLGC0086W: There are no aliases tags in the file {0}. Aliases are not defined for the virual host groups. No host aliases are defined for virtual host groups. Make sure that virtual host group definitions has some host aliases. propagate.stashfile.location.failed=PLGC0067E: The propagation of plug-in stash file from {0} to {1} on the Web server computer failed. The Application Server cannot transfer the plug-in stash file. Verify that the administration server for IBM HTTP Server is configured correctly. no.cell.name=PLGC0010E: No cell name is specified...stopping generation. A cell name is required. 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/. webserverlist.unknown=PLGC0055E: The plug-in is unable to get the list of Web servers that is defined on the node. The Application Server cannot retrieve the list of Web servers. 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/. no.clusters.or.nodes=PLGC0014E: No clusters or nodes are defined...exiting. Nodes or clusters are not defined in the present configuration. Servers are not available for which to generate a plug-in configuration. Create nodes and clusters that have servers in them using either the administrative console, or the wsadmin.sh tool. error.reading.tunneluris=PLGC0046W: An exception occurred while getting the URI lists for tunnel clusters. This message is for informational purposes only. No user action is required. nopluginproperties.found=PLGC0056E: The plug-in is unable to get the plug-in properties for the Web server. The Application Server cannot retrieve the plug-in properties. 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/. no.server.defs.for.cell=PLGC0015E: No server definitions are found for the cell. Servers are not defined in the given cell. Servers are not available for which to generate a plug-in configuration. Create servers within the nodes and clusters before running the tool, by using either the administrative console or the wsadmin.sh tool. server.name.not.set=PLGC0016E: A server name is not set for a member server in the cluster. One or more of the cluster members do not have server names. Use the administrative console or the wsadmin.sh tool to fix this problem. clusteraddressendpoint.port.zero=PLGC0090E: The clusterAddress endpoint port is zero. The clusterADdress endpoint needs a valid port defined. Use the administrative console or the wsadmin.sh tool to fix this problem. generate.started=PLGC0051I: Plug-in configuration file generation started for the Web server. This message is for informational purposes only. No user action is required. error.reading.routermodule=PLGC0035E: An exception occurred while getting the associated router module name. This exception is unexpected. The cause is not immediately known. 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/. nodesync.keyring.started=PLGC0068I: Node synchronization is started to propagate the plug-in keyring and stash file that is defined in the managed node. Node synchronization is used to move the plug-in keyring and stash file to the managed node. No user action is required. unable.to.parse.file.risk=PLGC0083E: Unable to parse the file {0}. The config file does not exist or the content is corrupted. The Application Server cannot parse the specified configuration file. Check the location of the file and make sure that it has valid contents. error.loading.tunnelcfghelper=PLGC0045W: The plug-in is unable to load the com.ibm.ws.httptunnel.channel.WSHttpTunnelPluginConfigHelper helper class. The HTTP tunnel configuration helper class did not load. 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. app.server.root.missing=PLGC0038E: The application server root must be specified in the generate method. This exception is unexpected. The cause is not immediately known. 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/. error.getting.urlpatterns=PLGC0036E: An exception occurred while getting dynamically generated servlet URL patterns for a Web services-enabled Web archive (WAR) module. This exception is unexpected. The cause is not immediately known. 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/. node.in.sync.stashfile=PLGC0075I: The node is already synchronized and the stash file is already propagated. Node synchronization has already propagated the stash file to the managed node. No user action is required. propagate.stashfile.location=PLGC0066I: The plug-in stash file is propagated from {0} to {1} on the Web server computer. This message is for informational purposes only. No user action is required. clusteraddressendpoint.duplicate.http=PLGC0087E: The clusterAddress has more than one HTTP transport defined. Only one HTTP transport can be defined for the clusterAddress. Use the administrative console or the wsadmin.sh tool to fix this problem. gen.for.cluster=PLGC0039I: The plug-in is generating a server plug-in configuration file using the cluster definition. This message is for informational purposes only. No user action is required. single.node.gen=PLGC0009I: The plug-in is generating for all the servers in the cell. This message is for informational purposes only. No user action is required. propagate.location=PLGC0062I: The plug-in configuration file is propagated from {0} to {1} on the Web server computer. This message is for informational purposes only. No user action is required. propagate.keyring.location.failed=PLGC0065E: The propagation of plug-in keyring file from {0} to {1} on the Web server computer failed. The Application Server cannot transfer the plug-in keyring file. Verify that administration server IBM HTTP Server is configured correctly. node.required=PLGC0002E: A server name is specified without a node name. Both the server name and the node name are required for single-server plug-in generation. If you specify a server name, you must specify a node name. propagate.keyring.failed=PLGC0070E: The propagation of the plug-in keyring has failed for the Web server. The Application Server cannot transfer the plug-in keyring file. Verify that the administration server for IBM HTTP Server is configured correctly. clusteraddressendpoint.host.null=PLGC0089E: The clusterAddress endpoint host is null. The clusterADdress endpoint needs a valid host defined. Use the administrative console or the wsadmin.sh tool to fix this problem. propagate.keyring.complete=PLGC0069I: The propagation of the plug-in keyring is complete for the Web server. This message is for informational purposes only. No user action is required. node.in.sync.plugincfg=PLGC0074I: The node is already synchronized and the plug-in configuration file is already propagated. Node synchronization has already propagated the plug-in configuration file to the managed node. No user action is required. exception.reading.ear=PLGC0029E: An exception occurred while reading the enterprise archive (EAR) file One or more of the applications that are deployed on the specified servers cannot be read. 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/. clusteraddressendpoint.unknown.name=PLGC0091E: The clusterAddress endpoint name is unknown, The clusterAddress endpoint name has to be HTTP_ENDPOINT or HTTPS_ENDPOINT. Use the administrative console or the wsadmin.sh tool to fix this problem. cell.required=PLGC0001E: A cell name is not specified. The cell name is a required value. You must specify a cell name. no.server.tag.exists.risk=PLGC0084W: There are no Server tags in the file {0}. The configuration file has no application server definition. The configuration has no application servers defined. Make sure that some application servers are defined and used by the web server. error.reading.web.con=PLGC0025E: The plug-in cannot get the Web container configuration for the specified server No configuration data for the Web container component is available for one or more of the specified servers. Use either the administrative console or the wsadmin.sh tool to configure the Web containers again. no.transport.exists.risk=PLGC0080W: No transports are defined between the webserver {0} and the application server {1}. Communication between the web server and application server is currently not possible. There are no HTTP nor HTTPS transports defined Web server and Application Server. 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. unknown.parameter=PLGC0003E: Unknown parameter: An unknown parameter is encountered. Review the usage information of the GenPluginCfg utility for valid parameters. no.transport.tag.exists.risk=PLGC0085W: There are no Transport tags for the application server {0} in the file {1}. The Application Server has no Transports defined in plug-in configuration. Set up HTTPS (SSL) transports between the webserver and application server, in order to have the communication between webserver and application server be encrypted. doc.output.exception=PLGC0006E: An exception occurred while outputting the document. An error occured while generating the plug-in configuration file. 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/. config.service.notAvailable=PLGC0076E: The configuration service is not available. The configuration root specified is incorrect. The plug-in configuration generator is not able to access the repository. Verify that configuration root is correctly passed to the plug-in configuration generator. root.exception=PLGC0034E: Root exception: This informational message indicates a root exception. 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/. error.reading.lotusclusters=PLGC0042W: An exception occurred while getting the Lotus workplace clusters. This message is for informational purposes only. No user action is required. no.server.index=PLGC0026E: An exception occurred while reading the server index for the server. The present configuration did not contain a server index file. This missing file can result from a corrupted configuration. Verify that the serverindex.xml file exists. If it does not exist, create the file. exception.reading.server=PLGC0023E: An exception occurred while reading the server configuration No configuration data is found for one or more of the servers that you specified. Use either the administrative console or the wsadmin.sh tool to configure your servers. generate.notcomplete=PLGC0053E: The plug-in configuration file is not created for the Web server. The Application Server cannot generate the plug-in configuration file. 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/. propagate.stashfile.failed=PLGC0072E: The propagation of the plug-in stash file has failed for the Web server. The Appplication Server cannot transfer the plug-in stash file. Verify that the administration server for IBM HTTP Server is configured correctly. error.reading.lotustransports=PLGC0043W: An exception occurred while getting the transports for Lotus workplace servers. This message is for informational purposes only. No user action is required. no.server.for.any.cluster=PLGC0021E: No valid server definitions are found for any cluster. No plugin-cfg.xml document is generated. No servers are found. No servers are available for which to generate the plug-in configuration. Use either the administrative console or the wsadmin.sh tool to configure the servers within the cluster. error.reading.nodes.in.cell=PLGC0031E: An error occurred while reading nodes in a cell. This exception is unexpected. The cause is not immediately known. 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/. no.cells.defined=PLGC0019E: No cell definitions are found. No cells are found in your existing configuration. Use the administrative console or the wsadmin.sh tool to create the cells. error.parsing.cluster=PLGC0017E: The plug-in cannot parse the server cluster configuration for the cluster. This error occurred because of a corrupted cluster configuration file. 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/. gen.for.clusters=PLGC0012I: The plug-in is generating a server plug-in configuration file using the cluster definition. This message is for informational purposes only. No user action is required. error.loading.plugincfghelper=PLGC0037E: The plug-in cannot load the com.ibm.ws.webservices.deploy.PluginCfgHelper helper class. The webservices.jar file might not be in the class path. Check the class path and include the java archive (JAR) file, if necessary. nodesync.started=PLGC0047I: Node synchronization is started to propagate the plug-in configuration file that is defined in the managed node. Node synchronization is used to move the plug-in configuration file to the managed node. No user action is required. debug.file.name=PLGC0061I: Debug log file = This informational message indicates the name of the debug log file. No user action is required. no.def.for.server=PLGC0022W: No definition is found for the specified server No configuration data is found for one or more of the servers that you specified. Use either the administrative console or the wsadmin.sh tool to configure your servers. propagate.stashfile.complete=PLGC0071I: The propagation of the plug-in stash file is complete for the Web server. This message is for informational purposes only. No user action is required. pluginconfigservice.started=PLGC0057I: The plug-in configuration service started successfully. This message is for informational purposes only. No user action is required. webserver.noapplications=PLGC0060E: No applications are mapped to the Web server. 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. Use the Application Installation wizard to map modules to the Web server. hostname.filter.exists.risk=PLGC0081W: There are filters based on host names in virtualhosts.xml. The requests are filtered according to specific host names in virtualhosts.xml, when the value specified in the host header doesn't match the filter, the web server plug-in would pass the control to webserver indicating that the Application Server will not handle the request. The web server could potentially serve the JSP source from the IHS document root. 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. 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. error.loading.lotuscfghelper=PLGC0041W: The plug-in is unable to load the com.ibm.wkplc.generator.LotusCfgHelper helper class. The Lotus Workplace server helper class did not load. 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. config.file.name=PLGC0005I: Plug-in configuration file = This informational message indicates the name of the plug-in configuration file. No user action is required. gen.for.all.cell.servers=PLGC0013I: The plug-in is generating a server plug-in configuration file for all of the servers in the cell. This message is for informational purposes only. No user action is required. pluginconfigservice.notstarted=PLGC0059I: The plug-in configuration service is not started. 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. No user action is required. propagate.complete=PLGC0048I: The propagation of the plug-in configuration file is complete for the Web server. This message is for informational purposes only. No user action is required. generate.complete=PLGC0052I: Plug-in configuration file generation is complete for the Web server. This message is for informational purposes only. No user action is required. no.webservers.in.cell.risk=PLGC0077I: There are no web servers defined in the cell {0}. No web servers are defined in the specified cell. No user action is required. exception.reading.app=PLGC0028E: An exception occurred while reading the deployed applications for the specified server. One or more of the applications that are deployed on the specified servers cannot be read. 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/. only.http.transport.exists.risk=PLGC0078I: Only HTTP transport is defined between the web server {0} and the application server {1}. Communication between the web server and application server is over HTTP which is unencrypted and in clear text. Only HTTP transport is configured. All communication between web server and application server will be in clear text. 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. doc.gen.exception=PLGC0007E: An exception occurred while generating a plug-in configuration document. An error occurred while generating the plug-in configuration file. 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/. runtime.exception.while.generating=PLGC0033E: A runtime exception occurred while generating the plug-in configuration: A problem resulted from generating the configuration file. 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/. exception.while.generating=PLGC0032E: An exception occurred while generating plug-in configuration: A problem resulted from generating the plug-in configuration file. 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/.