IBM HTTP Server tasks

You must apply maintenance to your IBM HTTP Server installation. Complete one of the following based on the version of IBM HTTP Server that is installed.

Before you begin

Note: To determine your version of IBM HTTP Server, see Checking your IBM HTTP Server version.

About this task

During the instance creation process, WebSphere Commerce creates and stores the IBM HTTP Server configuration information in the following location: WC_installdir/instances/instance_name/httpconf

WindowsThe Configuration Manager also creates a Windows service that is named IBM HTTP Server for WebSphere Commerce (instance_name) for each instance that uses a IBM HTTP Server.

By default WebSphere Commerce configures the IBM HTTP Server to use SSL. This SSL configuration used the self-signed certificate that is shipped with WebSphere Commerce.

Note: The self-signed certificate key file that is provided with WebSphere Commerce is for testing purposes only.

Procedure

  1. Ensure the plug-in is specified in the WC_installdir/instances/instance_name/httpconf/httpd.conf file.
  2. Verify that the following lines exist in the httpd.conf file:
    AIXLinux
    LoadModule was_ap22_module "WAS_Plug-indir/bin/64bits/mod_was_ap22_http.so"
    Windows
    LoadModule was_ap22_module "$PLUGIN_INSTALL_DIR_VAR$\bin\32bits\mod_was_ap22_http.dll"
    For IBM i OS operating systemIBM i version 7.1
    LoadModule was_ap20_module /QSYS.LIB/WAS_Installation_Library.LIB/QSVTAP22.SRVPGM 
    For IBM i OS operating systemIBM i version 7.2 or later
    LoadModule was_ap20_module /QSYS.LIB/WAS_Installation_Library.LIB/QSVTAP24.SRVPGM
    Note: Ensure that the plug-in file exists at the designated paths on your system. For example, on a Windows environment, the .dll file might be at WAS_Plug-indir/bin/32bits/mod_was_ap22_http.dll.

    Where WAS_Installation_Library is the installation library for your instance of WebSphere Application Server.

    WebSpherePluginConfig "WAS_installdir/profiles/profile_Name/config/cells/
    WC_instance_name_cell/nodes/webserver_name_node/servers/webserver_name/
    plugin-cfg.xml"
    Where webserver_name is the name of the WebSphere Commerce web server. For example, webserver1.

    These lines might not display together. Search the file to confirm the presence of these lines. If these lines are missing, add them to the end of the file and restart the web server.

    For IBM i OS operating systemAssign a certificate to your HTTP server by using Digital Certificate Manager (DCM). For more information, see the IBM i documentation. Select your operating system version, and review the "Manage public Internet certificates for SSL communication sessions" topic.

  3. Verify that the configuration files are updated:
    1. Start your web server as described in Starting and stopping the IBM HTTP Server.
    2. Stop your web server as described in Starting and stopping the IBM HTTP Server.

What to do next

If you have a remote web server, follow the procedure in the topic Remote web server tasks.

Your web server provides a secure environment for your business transactions by using encryption technology. Encryption is the scrambling of information transactions on the Internet so that they cannot be read until they are unscrambled by the receiver. The sender uses an algorithmic pattern or key to scramble (encrypt) a transaction, and the receiver uses a decryption key. These keys are used by the Secure Sockets Layer (SSL) protocol.

Your web server uses an authentication process to verify the identity of the person with whom you are conducting business. This process involves obtaining a certificate that is signed by a trusted third party that is called a certificate authority (CA). Equifax and VeriSign Inc. are common certificate authorities. Other CAs are available as well. To create a production key file, complete the following steps:
  1. Request a secure certificate from a certifying authority.
  2. Set your production key file as the current key file.
  3. Receive the certificate and test the production key file.
Note:
  1. If you are already using a production key file that is signed by a certifying authority, you can skip these steps.
  2. Your browser might display security messages. Review the information in each message carefully and decide how to proceed.