
>rmic -[options], ..., <Remote-Class-Name>

 The available options in the console are as follows:
  -d           - after this parameter, specify the destination directory
                 where generated stubs and skeletons are saved. The path is
                 absolute,according to the corresponding operating system.
                 The default value is the current directory.
  -dc          - add a direcorty for java-generated files of stubs and 
                 skeletons if you want to keep.
  -classpath   - adds the specified directories and JAR files to the classpath
  -nrmi_p4     - if you specify this parameter, the generated stubs and
                 skeletons do not support the RMI/P4 protocol.
  -nsecurity   - related to -nrmi_p4 option; if you choose this parameter,
                 the generated skeleton does not include additional security
                 features. By default, security features are included in
                 the generated files.
  -iiop        - with this option specified the files are generated with
                 IIOP support.
  -additional  - related to -iiop option; if you use this option, RMIC Tool
                 generates separate stubs for all remote interfaces that are
                 implemented by the remote class. By default, a single stub
                 for all interfaces is created.
  -nkeep       - if you use this option, the generated .java files are deleted,
                 after the .class files are produced. By default, the .java
                 files are stored as well.

    Note:        Specify the fully qualified Java name of the remote class
                 after the options that you have chosen to.


