  RMIC Tool generates stubs and ties (skeletons) to be used in the remote client-server communication. The tool enables you to manage the
process by choosing various options in both GUI and console (non-GUI) environment.

  The usage and options of the "RMI improved compiler" dialog box are described below:
      Generator Directory - the directory where the java-files for remote communication are generated. The path is absolute, according to
the corresponding operating system. The default value is the current directory.
      Compiler Direcory - the directory where are class-files for remote communication are compiled. The path is absolute, according to
the corresponding operating system. The default value is the current directory.
      Additional classpath - directories or JAR files to be added to the classpath; with this option, you do not need to set in advance
the path to the package in the system classpath.
      Class Name - the fully qualified Java name of the remote class 
  

  Different options are provided for the specifics of the generating process:
      RMI_P4 Support - generates stubs and skeletons that enable you to use the remote object using the RMI/P4 protocolUse.
      RMI_P4 Security - related to the RMI/P4 option above. If the indicator is set, the generated skeleton encapsulates additional
security features. Each time a particular remote method is requested by a client, the security logic implemented in the skeleton verifies
whether corresponding user is authorized with access to the remote method. If not, an exception is thrown.
      RMI_IIOP Support - generation of stubs and ties is performed using the IIOP protocol.
      Additional Stubs - related to the RMI/IIOP option above. If a remote class implements more than one remote interface, separate stubs
for all implemented interfaces are generated. By default (if the indicator is not set), a common stub is generated for all implemented
interfaces.
      Keep java generated files - if you set this indicator, the generated .java files of the stubs and the skeletons are not deleted
after the .class files have been produced.