How Are Multiple Endpoints Used in Landmark?

Multiple endpoints are used in Landmark to construct a network that includes internal- and external-facing web applications. In other words, some web applications are deployed outside a firewall and others are deployed over an internal network. Each deployment requires its own access and security configuration and setup.

For example, assume that your Landmark application includes a Supplier web application that is deployed externally for internet access and a Buyer application that is deployed internally for intranet use. This is a simple deployment example that illustrates the concepts and steps involved in creating multiple end points.

The configuration used for a basic distributed application setup is shown in the following illustration.

Illustration: Basic distributed application setup
Server designation Description
appsrv

The Landmark Environment and WebSphere application server are installed on the application server host.

This WebSphere application server instance hosts the Landmark applications, the Infor Lawson System Foundation Environment, and the Lawson applications.
intwebsrv The remote web server that is exposed only behind the firewall. This machine will be used to serve as the front-end to the Buyer web application.
extwebsrv The remote web server that is exposed outside the firewall. This machine will be used to serve as the front-end to the Supplier web application.

In a Landmark enterprise application, each web application is modeled as a Landmark service, and each HTTP endpoint is meant to model a web server. In order to successfully deploy and execute in this scenario, there are three configuration steps you must perform.

  1. Connect remote web servers to the internal application server.

    At installation time, you define and configure remote web server instances to communicate with the application server.

  2. Define and map the applications to end points in the Landmark system.

    These steps are outlined in Configuring Network Endpoints.

  3. Map the modules to the appropriate web and application servers.

    This mapping can be used to partition which web applications inside an enterprise application are exposed on which web servers.

    These steps are provided in Deploying and Mapping Landmark Environment and Application Modules.

  4. Assign the endpoints to the appropriate SSO Domains.

    A procedure is provided in Adding HTTP Endpoints and Assigning to SSO Domains. You can find more detailed information on SSO Domains in the Infor Landmark Technology User Setup and Security guide.

Multiple endpoints can also be configured for both environments in a system where both the Infor Lawson System Foundation and the Landmark environments use multiple endpoints. For more information, see Configuring Multiple Endpoints for Federated Infor Lawson System Foundation and Landmark Environments.