 operations can be performed through the methods of the NMS user interface API. Operations include adding, modifying, moving and removing nodes in the client tree. The NMS user interface API also provides other useful user interface-related util- ity methods that can be used by application programs within the client JVM. Utility methods are related to internal frame handling, cursor handling and panel handling. In addition to creating custom views through the Java client user interface and through static entries in the tree XML file, it is possible to create and handle custom views. This way of handling custom views has advantages over others in that the cus- tom view operation can be invoked from any user interface component (menu, tool- bar, etc.) of the client. The custom view that is added is stored in the database so providing a view for all clients connected to the same server. It was mentioned above that temporary custom views could be added. These pro- vide the flexibility to create and view custom views for the desired client without dis- playing them for all connected clients. Temporary custom views can be created which are viewable in the client without a corresponding node being added in the client tree. The client can be customised. Indeed, the user can build their own client while still being able to use the product session's framework on the FE server side. The ClientFramework API is used to create connections and instantiate sessions, with the main functionalities of authenticating the user, and creating the main socket connection and instantiating the sessions. The Java client uses the utility API to create a connection to the server frame- work. Sessions will then be instantiated through main socket connection. The ClientFramework API initialises the common and generic socket connections. The constructors of this class are used to initialise the socket client. When using a cus- tom client, the ClientFramework API acts as an initialiser for client-server commu- nication. It authenticates by check