Scenario: In House Development, Well Known Servers
Scenario: In house development applications, only allow connection to a set of well known servers.
Example: ACME engineering develops their own Framework based applications in house. They deploy them to their own PCs, which utilize one of three different System i backend servers located in different offices and manufacturing plants around the country.
Recommendation:
Ship "ready to run" so that end-users do not have to be involved in any server definition at all:
- Deploy a Framework VF_Sy001_Servers.XML.
- Deploy a LANSA Communications Administrator LROUTE.DAT file containing the predefined server details.
- Do not allow end-users to alter the shipped details.
- Include appropriate icons into server definitions (often location based).