The work is on Java RMI which is mainly for the local invocation and remote invocation that is for the implementation of generic remote servers. For this, there is a need to use the invocation framework that is like the Java RMI set where there is a use of the Java Interface and Java Object Serialization Java Threat measures. (Wojciechowski et al., 2016). It includes the system with the Java TCP Networking and the multithreading methods for a proper codebase repository along with handling the generic computing architecture that is based on computing the client and the server messages. Here, there is a need to focus on the interaction contract which works for the defined Task interface which is executed through the CSMessage. The computation of the client and the server messages are set with the generic computing engine where there is an easy running of the server which has could compute the tasks with the handling of serialization object is for the computer server. There are Task Interface to call the execution of the tasks methods and then work on the system where there is a serialized object for the computing server. After receiving the computing task, there is a possibility to work on the call to getRessult() method for the display of the object. (Talukder et al., 2016). The standards are set with the FTP server that can compute the tasks based on the access from the Java class path. The standards are set with the recompiling and restarting the standard of the computer server. Reference Wojciechowski, P.T. and Siek, K., 2016, October. Atomic RMI 2: distributed transactions for Java. In Proceedings of the 6th International Workshop on Programming Based on Actors, Agents, and Decentralized Control (pp. 61-69). ACM. Talukder, A.R. and Roy, A.K., 2016. RMI Based Distributed Query Processing (Doctoral dissertation, East West University).