Use this page to view or change the configuration settings
for the web server plug-in configuration service.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
If you are using a stand-alone application server, click server_name to view this administrative console page.
For a WebSphere® Application Server, Network Deployment configuration,
if you are using the deployment manager, click .
For IBM i and distributed platforms
running in a WebSphere Application Server, Network Deployment environment,
the deployment manager SystemOut log contains the status of the automatic
plug-in generation and propagation.
For IBM i
and distributed platforms running in a Base or Express® environment, the application server's
SystemOut log contains the status of the automatic plug-in generation
and propagation.
For the z/OS platform,
the TSO JOB log contains the status of the automatic plug-in generation
and propagation.
Enable automated web server configuration processing
The web server plug-in configuration service is selected by default.
The service automatically generates the plug-in configuration file
whenever the web server environment changes, with a few exceptions.
For example, the plug-in configuration file is regenerated whenever
one of the following activities occurs:
- A new application is deployed on an associated application server
- The web server definition is saved
- An application is removed from an associated application server
- A new virtual host is defined
In
WebSphere Application Server, Network Deployment configurations,
the plug-in configuration file does not regenerate when:
- A cluster member is added to a cluster.
- TCP channel settings are updated for an application server.
In a base WebSphere Application Server or WebSphere Application Server, Express configuration,
the plug-in configuration file does not regenerate when TCP channel
settings are updated for an application server.
In a base WebSphere Application Server or WebSphere Application Server, Express configuration,
whenever a virtual host definition is updated, the plug-in configuration
file is automatically regenerated for all of the web servers.
By default, this option is selected. Clear the field to disable
automated web server configuration processing.