This topic provides information about software and hardware topologies to help plan your installation of Lotus® Expeditor Server.
- Software topology
- Hardware topology examples
Use the information in this section to understand how the software components interact. For a description of how different servers might be set up to support the software topology, see Hardware topology examples .
Lotus Expeditor Server installs and runs as a collection of application servers on the WebSphere® Application Server platform. For each installation of Lotus Expeditor Server, an installation of WebSphere Application Server is required. In addition, both the Lotus Expeditor Server and WebSphere Application Server installations must reside on the same system.
Installing multiple Lotus Expeditor Server instances on a single WebSphere Application Server instance is not supported.
Hypertext Transfer Protocol (HTTP) is used as the transport protocol for the majority of the Lotus Expeditor Server services requests. Lotus Expeditor Server does not require a Web server. For a production environment, it is recommended that a remote Web Server be configured. For a clustered environment, all Lotus Expeditor Server instances can share one or more remote Web servers.
Because IBM® Lotus Expeditor administration and configuration are dependent on WebSphere Application Server, you might have to use the administrative tools that are provided with WebSphere Application Server to monitor or control activities that are related to the Lotus Expeditor Server. Additionally, if you configure an external Web server for use with Lotus Expeditor Server, you might need to use the Web server interface to administer Lotus Expeditor Server related activities.
Lotus Expeditor Server require access to a user registry. Lotus Expeditor Server supports user registries configured using WebSphere Application Server's federated repository support (Virtual Member Manager). See the WebSphere Information Center
for information on supported repositories.
Hardware topology examples
WebSphere Application Server supports a wide variety of ways to deploy in your computing environment. Commonly used topologies fall into one of the following broad categories:
- Single-system topology. The components are installed on the same system. This topology is useful for developer and proof of concept installations, but is not recommended for production environments.
- Multi-system topologies. The components (the Web server, application server, databases, and so forth) are physically separated onto different systems.
- Vertical scaling topologies. Multiple application servers running IBM Lotus Expeditor are created on a single physical system, usually by creating cluster members. Note that Lotus Expeditor Server does not support this topology.
- Horizontal scaling topologies. Members of a Lotus Expeditor Server cluster exist on multiple physical systems, effectively and efficiently distributing the workload of a single logical Lotus Expeditor Server. HTTP redirector products can also be used to implement horizontal scaling. Clustering is most effective in environments that use horizontal scaling because of the ability to build in redundancy and failover, to easily add new horizontal cluster members to increase capacity, and to improve scalability by adding heterogeneous systems into the cluster.
- HTTP server separation topologies. The Web (HTTP) server is located on a different physical system than WebSphere Application Server and Lotus Expeditor Server.
- Demilitarized zone (DMZ) topologies. Firewalls can be used to create demilitarized zones -- systems that are isolated from both the public Internet and other systems in the configuration. This improves security, especially for sensitive back-end resources, such as databases.
It is important to remember that, in any topology, many resources and settings that are defined within WebSphere Application Server, such as Global Security Settings and DataSources, are shared across all applications, including the Lotus Expeditor Server instances.
Parent topic: Planning for deployment: XPD622