Scenario: ISV, Multiple Unknown Servers

Scenario: ISV development, application allows connection to multiple unknown servers.

Example: XYZ software develop and sell an insurance agent package. It is designed to work using many different IBM i or Window 2000 computer as its back end servers. Typically the servers are located in different cities and most agents require access to two or more of the servers.         

Recommendation: 

Ship a set of "almost ready to run" servers so that in most situations end-user involvement is minimized. Allow end-users to define new servers in exceptional circumstances:

• Deploy a Framework VF_Sy001_Servers.XML with a predefined set of servers in it.

• Use non-committal generic names for the servers (e.g. SERVER1, SERVER2, SERVER3).  

• Deploy a LANSA Communications Administrator LROUTE.DAT file containing all the predefined server details (except for the IP addresses). 

• End-users should initially use UF_ADMIN to delete server definitions that are not required (leaving their definitions in LROUTE.DAT will do no harm) and to specify the caption details for the servers that are required. 

• End-users then need to use the LANSA Communications Administrator to alter the "Fully Qualified Name of the Host (Address)" of the servers that they do need to use.

• End-users may need to use the UF_ADMIN and LANSA Communications Administrator facility to define additional servers in exceptional circumstances.