(dist)(iseries)

Configure a web server and an application server profile on the same machine

WebSphere Application Server provides web server plug-ins that we can configure to communicate with a particular brand of web server. Learn how to install the web server, its web server plug-in for WebSphere Application Server, and the application server on the same machine.

(iseries) When multiple profiles exist, we can select the profile that the Web Server Plug-ins Configuration Tool configures. See Plug-ins configuration for a description of the flow of logic that determines how to select the profile to configure.

(dist) When multiple profiles exist, we can select the profile that the Web Server Plug-ins Configuration Tool configures. See Plug-ins configuration for a description of the flow of logic that determines how to select the profile to configure.

If the WAS product family supports a particular brand of web server, such as IBM HTTP Server or Microsoft Internet Information Services (IIS), the WAS product provides a binary plug-in for the web server that install.

If the WAS product family does not provide a binary plug-in for a particular brand of web server, then the web server is not supported. The purpose of the binary plug-in is to provide the communication protocol between the web server and the application server.

(dist) Suppose that you create a new profile and you also want to use a web server. We must install a new web server for the new profile, install the Web Server Plug-ins, and use the Web Server Plug-ins Configuration Tool to configure both the web server and the application server.

If the web server is not already installed, we can still install the Web Server Plug-ins for future use.

This procedure configures the application server profile that is the default profile on the machine. A one-to-one relationship exists between a web server and the application server.

However, a standalone application server profile and a managed profile can each have multiple web servers defined, each in a separate web server definition.

This article describes how to create the following topology:

Nonroot installation for the plug-in component is only supported if the application server was also installed by the same nonroot user. Otherwise, the web server configuration scripts will fail to run against the application server installation.

This topic references one or more of the application server log files. As a recommended alternative, we 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. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

The Web Server Plug-ins Configuration Tool configures the plug-in for the supported web server after collecting the following information:

The Web Server Plug-ins Configuration Tool edits the configuration file or files for a web server by creating directives that point to the location of the binary plug-in module and the plug-in configuration file.

The name of the binary plug-in module varies per web server type. The plug-in configuration file is always the plugin-cfg.xml file. The Web Server Plug-ins Configuration Tool creates a web server definition in the configuration of the application server unless one already exists.

We can use the console to manage the web server configuration. For example, when you install an application on the application server, we can also choose to install it on the web server definition. If so, the updated plugin-cfg.xml file shows that the new application is available. When the web server reads the updated plug-in configuration file, the web server becomes aware of the new application that it can serve to web clients.

If we choose not to install the new application on the web server definition, the application is not added to the plug-in configuration file. The web server is not aware of the application and cannot serve it to web clients.

Alternatively to using the Web Server Plug-ins Configuration Tool, we can use the pct command-line tool with a response file to configure a web server. Read Configure a web server plug-in using the pct tool for more information.

Use this procedure to install the web server plug-in, configure the web server, and create a web server definition in the default application server profile.


Results

The installation of the Web Server Plug-ins results in the creation of the Plugins directory and several subdirectories. The following directories are among those created on a Linux system, for example:

The Web Server Plug-ins Configuration Tool creates a web server definition within the application server profile unless one already exists.

The Web Server Plug-ins Configuration Tool configures the web server to use the profile_root/plugin-cfg.xml file.

The application server regenerates the web server plug-in configuration file, plugin-cfg.xml whenever an event occurs that affects the file. Such events include the addition or removal of an application, server, or virtual host. The standalone application server regenerates the file in the following location:

profile_root
   /config/cells/cell_name/nodes/
   web_server_name_node/servers/
   web_server_name/plugin-cfg.xml

On a federated node, the creation or removal of clusters and cluster members also causes file regeneration. The deployment manager regenerates the file for a federated application server in the following location:

profile_root
   /config/cells/cell_name/nodes/
   node_of_AppServer/servers/
   web_server_name/plugin-cfg.xml


What to do next

We can start a standalone application server and the web server immediately after configuring the plug-in for the local web server. Open the console of the application server after you start the server and save the changed configuration.

After configuring the plug-in for the local web server, we can start a federated application server and the web server after running the script that completes the configuration. Open the console of the deployment manager. Wait for node synchronization to occur. Save the changed configuration that includes the new web server definition.

See Select a web server topology diagram and roadmap for an overview of the installation procedure.

See (dist)(iseries) Plug-ins configuration for information about the location of the plug-in configuration file.

See Web server configuration for information about the files involved in configuring a web server.

See Edit web server configuration files for information about how the Web Server Plug-ins Configuration Tool configures supported web servers.

See Configure web server plug-ins for information about other installation scenarios for installing web server plug-ins.


Related concepts

  • Plug-ins configuration
  • Web server configuration


    Related tasks

  • Configure web server plug-ins

    Configure a web server plug-in using the pct tool