1 2 Before You Begin Checklist

ü

Step

Comments / Further Actions

1.    Create a Minimum Supported Configuration document (MSC) defining the minimum configuration your solution will viably support. This includes what servers, client platforms and web browsers your application will need. Consider:

• Hardware requirements

• Software requirements

• Supported screen resolutions

• Networking capabilities

• Maximum Data volumes.

A formal Minimum Supported Configuration (MSC) Document will:

• Inform decisions about the overall solution cost

• Establish the environment required to test the deployment of the solution or any patch/hotfix made to it.

• Raise management's awareness of the risk of implementing a "sub-MSC" solution.

Note - Any other application running on this "end-user" environment must also be considered when sizing your machine.

2.    Install and configure the latest version of LANSA on the Linux Server.

SuperServer clients must not have a newer version of LANSA installed than the version of LANSA on the Linux Server.

3.    Request and install the appropriate licenses on the Linux Server.

Refer to the LANSA website for information.

4.    Follow the instructions in the LANSA Communications Setup Guide to configure communications for the client and server machines

The Client and Server can only communicate via TCP/IP.

5.    Verify the clients can communicate with the Server via TCP/IP.

On the client, use the PING command specifying the name or IP address of the server system. Wait until the PING command gives a good return code indicating it could successfully communicate with the server system.

6.    Before you deploy your own application, test your configuration of the clients and LANSA on Linux with the DEM partition and sample code.

Refer to 1.3 Test with the Verification and Sample Applications for details.