[AIX Solaris HP-UX Linux Windows][IBM i]

Configuration d'IBM HTTP Server version 9.0

You can manually configure the IBM HTTP Server Version 9.0.

Avant de commencer

[IBM i] IBM HTTP Server Version 9.0 n'est pas pris en charge sur IBM® i.

[AIX Solaris HP-UX Linux Windows]The plug-in Configuration Tool (PCT) is the primary way to configure the IBM HTTP Server to load the WebSphere Application Server web server plug-in.

The Plug-in Configuration Tool (PCT) automatically configures the IBM HTTP Server. The following steps are the manual instructions for configuring the IBM HTTP Server. Vous trouverez les procédures de configuration pour les autres serveurs Web pris en charge dans la rubrique Edition des fichiers de configuration de serveur Web.

Pourquoi et quand exécuter cette tâche

Les exemples et messages sont parfois affichés sur plusieurs lignes pour une présentation plus claire. Vérifiez que chaque directive du fichier de configuration de serveur Web tient sur une ligne.

Product installation paths are examples only.

[AIX Solaris HP-UX Linux Windows]The web server Plug-in Configuration Tool (PCT) installs a dummy plugin-cfg.xml file during installation, but this file requires periodic propagation from the real file on the application server.

Procédure

  1. Determine the correct web server plug-in module to load, typically 32-bit on Windows, and 64-bit elsewhere, by determining the architecture of the web server.
    [AIX][HP-UX][Linux][Solaris]
    /opt/IBM/HTTPServer/bin/versionInfo.sh | grep Architecture
    [Windows]
    c:\IBM\HTTPServer\bin\versionInfo.bat | findstr Architecture
  2. Load the web server plug-in by appending the following line to the httpd.conf file, taking note of the architecture specified in the path. [AIX][Linux][Solaris]
    LoadModule 
         was_ap24_module /opt/IBM/WebSphere/Plugins/bin/<arch>/mod_was_ap24_http.so
    [HP-UX]
    LoadModule 
         was_ap22_module /opt/IBM/WebSphere/Plugins/bin/<arch>/mod_was_ap24_http.sl
    [Windows]
    LoadModule was_ap24_module
         c:/IBM/WebSphere/Plugins/bin/<arch>/mod_was_ap24_http.dll

    In these examples, <arch> is 32bits or 64bits depending on the web server architecture.

  3. Create the required directories and copy temporary configuration files. [AIX][Solaris][HP-UX][Linux]
          mkdir -p  /opt/IBM/WebSphere/Plugins/{logs,config}/webserver1          
          cp /opt/IBM/WebSphere/Plugins/etc/plugin-key* /opt/IBM/WebSphere/Plugins/config/webserver1/          
          cp /opt/IBM/WebSphere/Plugins/config/templates/plugin-cfg.xml /opt/IBM/WebSphere/Plugins/config/webserver1/
    [Windows]
          mkdir c:\IBM\WebSphere\Plugins\logs\webserver1          
          mkdir c:\IBM\WebSphere\Plugins\config\webserver1          
          copy c:\IBM\WebSphere\Plugins\etc\plugin-key* c:\IBM\WebSphere\Plugins\config\webserver1\          
          copy c:\IBM\WebSphere\Plugins\config\templates\plugin-cfg.xml c:\IBM\WebSphere\Plugins\config\webserver1\
  4. Register the web server with the application server.

    For the plugin-cfg.xml configuration file to be useful, it must be generated by the application server environment to reflect configured servers and deployed applications. A definition can be created in the Administration Console on a Deployment Manager or stand-alone Application Server. Voir Définition du serveur Web.

    When registered, the Administration Console can generate and propagate a plugin-cfg.xml file to the web server, replacing the initial plugin-cfg.xml file.

    For web servers that are used with WebSphere Liberty see, Configuring a web server plug-in for Liberty

  5. Append a second directive to the httpd.conf file to identify the path to the plugin-cfg.xml file.
    • Remote web servers, not co-located with any WebSphere management process, or web servers used with WebSphere Liberty:
      WebSpherePluginConfig /opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
    • Web server registered with a stand-alone traditional application server:
      WebSpherePluginConfig profile_root/standalone/config/cells/standalone/nodes/standalone/servers/webserver1/plugin-cfg.xml
    • Web server registered with a co-located Deployment Manager:
      WebSpherePluginConfig profile_root/config/cells/<var>dmgrcell</var>/nodes/managednode/servers/webserver1/plugin-cfg.xml

Résultats

This procedure results in editing and reconfiguring the IBM HTTP Server.

Que faire ensuite

The mod_was_ap24_http plug-in module requires the GSKIT Secure Sockets Layer (SSL) encryption library if the plug-in is configured to support encrypted connections to back-end WebSphere Application Servers.

L'installation des plug-ins de serveur Web installe la bibliothèque de chiffrement SSL GSKIT au niveau requis si elle n'est pas installée. If you manually copy the plug-in to a new workstation, you might not have the required GSKIT libraries for encrypting backend connections.

When a web server has been configured, you can install applications on it. See the Applications section of the knowledge center for more information.

Conseil : Pour annuler la configuration d'un serveur Web, reprenez les étapes manuelles dans l'ordre inverse et supprimez ce que vous avez ajouté manuellement au cours de cette procédure.

Icône indiquant le type de rubrique Rubrique de tâche



Icône d'horodatage Dernière mise à jour: last_date
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=tins_manualWebIHS80
Nom du fichier : tins_manualWebIHS80.html