4 1 3 Configuring the Communications Route Table

LANSA Communication Set Up

4.1.3 Configuring the Communications Route Table

LANSA for Linux Installer creates a basic Communications Route Table {lansa_root}/lroute.dat during installation. The table contains only one entry of LU Name *LOCAL which can be used to access the Listener of the same installation. The port number of the entry simply uses the same port number for the Listener.

For example, if you install LANSA for Linux to the directory /lansa, the file /lansa/lroute.dat will be created with the following content if you do not use the port option for the installer:

* LANSA Communication Routing Table File
* Comma Delimited, positional parameters.
* Empty parameters must have at least one space.
* Record Types (first character)
*   R   routing information
*   T   module trace information
R,*LOCAL,,Socket, ,0,4545,0,1,0,0

If you need to customize any settings for the entry after installation, you can edit the route table with a text editor. Most of the settings are simple to change by following the remarks in the route table.

If you need to add entries to the route table, you can modify the route table by copy existing entries and then customize the copied entries.

Alternatively, if you need to make extensive changes to the route table, the LANSA Communications Administrator on Windows offers some nice GUI editing capability.

You can use the LANSA Communications Administrator to create or maintain the Communications Route Table (lroute.dat) for use on the Linux Server. You must run the Administrator on a Windows Server that has the LANSA Listener installed, so that the Listener options appear in the Advanced menu.

1.  Decide on a location for the Linux Route Table. (For example, c:\lroute.dat)

2.  Open the Administrator and choose Create Route Table for Deployment from the Advanced pull-down menu. Any Host Routes you had defined for your default Route Table should disappear when you click on the Host Routes window.

3.  Configure the Communications Route Table as described in the Workstation Configuration chapter. Keep the following points in mind:

  • The Start Listener and Stop Listener button should not be used as it will attempt to start or stop the listener on the Windows Server, not the Linux Server.
  • The Number of Threads parameter should be 0 or 1. Anything else is treated as 1.

4.  Copy the new lroute.dat file to the appropriate directory on the Linux Server, usually {lansa_root}/listen.dat.

     Note: The filename lroute.dat must be specified in lower case.