this database has two purposes firstly it holds the relation between usernames and passwords so that users can be validated secondly it holds the relation between validated usernames and the software files they are allowed to request from the lms this allows the same lms to serve different java applications to different users depending on their licensed software group the database can be relational in format and may contain at least a user and a file table an example for which is provided in fig4 in step 6 above the username is validated against the password in the user table the correct licensed software group found and associated with the network connection by the lms and finally the command file name address is located from the file table for the users licensed software group there should be only one command file per licensed software group this could change if each users 39 settings are stored on the lms and this strictly means that there should be a separate license software group command file join table between the user and file tables but for simplicity a flag is used in the file table here to mark the file that contains the clc interpretable commands for a licensed software group once the lms has validated the user identified their licensed software group and located the command file for that group the lms reads the correct command file and sends it through the secure connection back.