B.2 Configuring Web Services

You can implement the Web portal for the system across multiple hosts. When you use multiple Web services, the meeting archive repository must reside in a file system accessible to all HTTP daemons. For instance, it can reside on a NAS box or via an NFS exported file system on one of the cluster hosts. In any event, the shared file system must be accessible via /usr/local/apache2/htdocs/repository/mtgarchive on all the machines hosting the HTTP daemon. Also, you are responsible for configuring a load balancer for HTTP requests to these machines.

When configuring the external API HTTP daemons, administrative functions are performed via HTTP on the external API hosts. For added security, these hosts can be placed behind a firewall. However, the hosts assigned to run the Web portal must be able to connect to the external API hosts via port 8000 in order for the admin console to function properly.

  1. Configure Web portal hosts:

    1. Modify the portal_hname_local array to specify all the cluster hosts for Web service.

    2. Ensure that /usr/local/apache2/htdocs/repository/mtgarchive is the same shared file system for all cluster hosts in portal_hname_local.

    3. Modify the portal_ip array to include the IP addresses that the HTTP daemon should listen on for connections.

    4. Modify the portal_hname variable to define the hostname used in URLs to the Web portal.

  2. Configure external API hosts:

    1. Modify the extapi_hname_local array to specify all the cluster hosts for the external API service.

    2. Modify the extapi_portal_ip array to specify the IP addresses on which an external API HTTP daemon listens.

    3. Modify the extapi_portal_hname to specify the hostname in URLs to the external API.