PLGC

PLGC0001E: A cell name is not specified.
PLGC0002E: A server name is specified without a node name.
PLGC0003E: Unknown parameter:
PLGC0004E: An exception occurred while running the GenPluginCfg utility.
PLGC0005I: Plug-in configuration file =
PLGC0006E: An exception occurred while outputting the document.
PLGC0007E: An exception occurred while generating a plug-in configuration document.
PLGC0008I: The plug-in is generating a single-server plug-in configuration file for the cell.
PLGC0009I: The plug-in is generating for all the servers in the cell.
PLGC0010E: No cell name is specified...stopping generation.
PLGC0012I: The plug-in is generating a server plug-in configuration file using the cluster definition.
PLGC0013I: The plug-in is generating a server plug-in configuration file for all of the servers in the cell.
PLGC0014E: No clusters or nodes are defined...exiting.
PLGC0015E: No server definitions are found for the cell.
PLGC0016E: A server name is not set for a member server in the cluster.
PLGC0017E: The plug-in cannot parse the server cluster configuration for the cluster.
PLGC0018E: An exception occurred while reading the server cluster configuration for a cluster.
PLGC0019E: No cell definitions are found.
PLGC0020E: No valid server definitions are found for the server cluster
PLGC0021E: No valid server definitions are found for any cluster. No plugin-cfg.xml document is generated.
PLGC0022W: No definition is found for the specified server
PLGC0023E: An exception occurred while reading the server configuration
PLGC0024E: An exception occurred while getting the Web container configuration for the specified server.
PLGC0025E: The plug-in cannot get the Web container configuration for the specified server
PLGC0026E: An exception occurred while reading the server index for the server.
PLGC0028E: An exception occurred while reading the deployed applications for the specified server.
PLGC0029E: An exception occurred while reading the enterprise archive (EAR) file
PLGC0030E: No nodes are defined in the cell.
PLGC0031E: An error occurred while reading nodes in a cell.
PLGC0032E: An exception occurred while generating plug-in configuration:
PLGC0033E: A runtime exception occurred while generating the plug-in configuration:
PLGC0034E: Root exception:
PLGC0035E: An exception occurred while getting the associated router module name.
PLGC0036E: An exception occurred while getting dynamically generated servlet URL patterns for a Web services-enabled Web archive (WAR) module.
PLGC0037E: The plug-in cannot load the com.ibm.ws.webservices.deploy.PluginCfgHelper helper class.
PLGC0038E: The application server root must be specified in the generate method.
PLGC0039I: The plug-in is generating a server plug-in configuration file using the cluster definition.
PLGC0040I: More than one node is specified in the list; only the first node is selected.
PLGC0041W: The plug-in is unable to load the com.ibm.wkplc.generator.LotusCfgHelper helper class.
PLGC0042W: An exception occurred while getting the Lotus workplace clusters.
PLGC0043W: An exception occurred while getting the transports for Lotus workplace servers.
PLGC0044W: An exception occurred while getting the URI lists for Lotus workplace clusters.
PLGC0045W: The plug-in is unable to load the com.ibm.ws.httptunnel.channel.WSHttpTunnelPluginConfigHelper helper class.
PLGC0046W: An exception occurred while getting the URI lists for tunnel clusters.
PLGC0047I: Node synchronization is started to propagate the plug-in configuration file that is defined in the managed node.
PLGC0048I: The propagation of the plug-in configuration file is complete for the Web server.
PLGC0049E: The propagation of the plug-in configuration file failed for the Web server.
PLGC0050W: The propagation of the plug-in configuration file is not supported for the remote Web server.
PLGC0051I: Plug-in configuration file generation started for the Web server.
PLGC0052I: Plug-in configuration file generation is complete for the Web server.
PLGC0053E: The plug-in configuration file is not created for the Web server.
PLGC0054E: The plug-in is unable to get the server type for the server.
PLGC0055E: The plug-in is unable to get the list of Web servers that is defined on the node.
PLGC0056E: The plug-in is unable to get the plug-in properties for the Web server.
PLGC0057I: The plug-in configuration service started successfully.
PLGC0058E: The plug-in cannot initialize the plug-in configuration service.
PLGC0059I: The plug-in configuration service is not started.
PLGC0060E: No applications are mapped to the Web server.
PLGC0061I: Debug log file =
PLGC0062I: The plug-in configuration file is propagated from {0} to {1} on the Web server computer.
PLGC0063E: The propagation of the plug-in configuration file from {0} to {1} on the Web server computer failed.
PLGC0064I: The plug-in keyring file is propagated from {0} to {1} on the Web server computer.
PLGC0065E: The propagation of plug-in keyring file from {0} to {1} on the Web server computer failed.
PLGC0066I: The plug-in stash file is propagated from {0} to {1} on the Web server computer.
PLGC0067E: The propagation of plug-in stash file from {0} to {1} on the Web server computer failed.
PLGC0068I: Node synchronization is started to propagate the plug-in keyring and stash file that is defined in the managed node.
PLGC0069I: The propagation of the plug-in keyring is complete for the Web server.
PLGC0070E: The propagation of the plug-in keyring has failed for the Web server.
PLGC0071I: The propagation of the plug-in stash file is complete for the Web server.
PLGC0072E: The propagation of the plug-in stash file has failed for the Web server.
PLGC0073W: No definition is found for request metrics.
PLGC0074I: The node is already synchronized and the plug-in configuration file is already propagated.
PLGC0075I: The node is already synchronized and the stash file is already propagated.
PLGC0076E: The configuration service is not available.
PLGC0077I: There are no web servers defined in the cell {0}.
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.
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.
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.
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.
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.
PLGC0083E: Unable to parse the file {0}. The config file does not exist or the content is corrupted.
PLGC0084W: There are no Server tags in the file {0}. The configuration file has no application server definition.
PLGC0085W: There are no Transport tags for the application server {0} in the file {1}.
PLGC0086W: There are no aliases tags in the file {0}. Aliases are not defined for the virual host groups.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.websphere.plugincfg.generator.PluginConfigGeneratorNLS.dita
File name: com.ibm.websphere.plugincfg.generator.PluginConfigGeneratorNLS.html