![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
Plug-ins configuration
The Web Server Plug-ins Configuration Tool configures an application server for a web server type and creates a web server definition in the configuration of the application server. Become familiar with the different processing paths that the Web Server Plug-ins Configuration Tool can use.
This article describes the two ways that the Web Server Plug-ins Configuration Tool can configure a web server and create the plugin-cfg.xml file, which is the plug-in configuration file.
지원된 구성: 이 도구는 AIX®,
Linux 및 Windows에서만
지원됩니다. As an alternative to using the Web Server Plug-ins
Configuration Tool, you can use the pct command-line tool with a response
file to configure a web server. For more information, read Configuring
a web server plug-in using the pct tool.sptcfgIn addition, the default httpd.conf configuration file must stay within the <IHS_HOME>/conf directory, and you must run setupadm manually after the administration configuration.
지원된 구성: The Web Server Plug-ins Configuration
Tool is intended for use with the full WebSphere® Application Server profile; it
is not required or supported for use in generating a web server plug-in
for the Liberty profile. For information on generating a web server
plug-in for the Liberty profile, read Configuring the Liberty
profile with a web server plug-in.sptcfgConfiguration flows
The Web Server Plug-ins Configuration Tool resolves all configurations of the web server and WebSphere Application Server to two scenarios: remote plug-in configuration and local plug-in configuration. The logic implemented in determining which scenario applies to a configuration is shown in the following diagram.

- The installation type is either remote or local.
When the Web server and application server are not on the same computer, choose the remote scenario. When both the web server and application server are on the same computer, choose the local scenario.
- If the product is installed but the profile is accidentally deleted or otherwise missing, the scenario is considered to be a remote installation. Create a profile before running the script.
- If the profile has an existing web server definition, the installation is considered a remote plug-in configuration. You cannot have more than one web server definition in a standalone application server.
Scenario A. Local standalone plug-in configuration
In this scenario, the Web Server Plug-ins Configuration Tool creates a web server definition within the application server profile directly, without the use of a script.
The Web Server Plug-ins Configuration Tool configures the web server to use the plugin-cfg.xml file that is within the application server profile. The application server regenerates the plugin-cfg.xml file in the profile_root/config/cells/ cell_name/nodes/ web_server_name_node/servers/ web_server_name directory. Regeneration occurs whenever a change occurs in the application server configuration that affects deployed applications.
| Profile type | Automatic creation of web server definition? | Web server already defined in application server configuration? |
|---|---|---|
| Application server | Yes | No |
A application server profile that has an existing web server definition should be processed as a remote plug-in configuration. An application server can have just one web server definition.
See Scenario B for a description of this type of node.
The following overview shows the procedure for verifying the web server configuration:
The Web Server Plug-ins Configuration Tool does not automatically create a web server definition within the distributed profile on a remote machine. The tool creates the configureweb_server_name script instead.
The Web Server Plug-ins Configuration Tool configures the web server to use the plugin-cfg.xml file that is maintained on the web server machine in the plugins_root/config/web_server_name directory. This file requires periodic propagation. Propagation is copying the current plugin-cfg.xml file from the application server machine to replace the plugins_root/config/web_server_name/plugin-cfg.xml file.
| Profile type | Creation of web server definition? | Web server already defined in application server configuration? |
|---|---|---|
| Any profile anywhere if you select a remote installation type in the Web Server Plug-ins Configuration Tool | By script | N/A |
| No profile | By script | N/A |
| Standalone application server profile with an existing web server definition | By script | Yes |
The following overview shows the procedure for verifying the temporary plugins_root/config/web_server_name/plugin-cfg.xml file.
The web server communicates with the remote application server using the temporary plugin-cfg.xml file.
If the application server has an HTTP Transport port assignment other than 9080, the test is not successful. Continue to the next section to create the web server definition on the application server and to complete your test of the configuration.
To summarize, two scenarios exist for Web Server Plug-ins. Each scenario revolves around a unique location for the plug-in configuration file, plugin-cfg.xml.
The application server generates the plug-in configuration file. The purpose of the file is to publish the location of all of the application server objects that are relevant to a web server and to control binary plug-in configuration options. The file identifies objects such as applications and virtual hosts for serving applications.
If the web server cannot access the file on the application server machine, you must copy the file to the web server. That process is called propagation. Propagation is reserved for the remote plug-in configuration scenario, which is Scenario B in this article.
In the local scenario, the web server can access the plugin-cfg.xml file because the web server is on the same machine as the file.
All Scenario A configurations have the web server definition within its own web server node.
Limited management options do not let you create or delete the one web server definition in the administrative console of a standalone application server. The inability of a standalone application server to create a web server definition is the basis for the configuration scripts created by the Web Server Plug-ins Configuration Tool. Without the scripts, you could not easily create a web server definition on a standalone application server node.
| Scenario | Profile type | Location of the plugin-cfg.xml file | |
|---|---|---|---|
| plugins_root | profile_root: within the web server node | ||
| A | Application server profile | X | |
| B | Any profile anywhere if you select a remote installation type in the Web Server Plug-ins Configuration Tool | X | |
| No profile | X | ||
| Application server profile with an existing web server definition | X | ||
plugins_root/config/web_server_name/plugin-cfg.xmlprofile_root/config/cells/cell_name/nodes/web_server_name_node/servers/web_server_name/plugin-cfg.xml
![[AIX]](../images/aixlogo.gif)
![[HP-UX]](../images/hpux.gif)
![[Linux]](../images/linux.gif)
![[Solaris]](../images/solaris.gif)
IHS_root
참조 주제