Generating Stubs and Ties 

Use

You can generate IIOP support for your remote objects using the J2EE Engine’s RMIC tool. You generate the stubs and ties against the implementation class of the remote interface.

If you prefer the command-line tools, you can use the standard rmic tool that is distributed with your Java Development Kit (JDK) software as an alternative.

Procedure

To start the J2EE Engine’s RMIC tool, run the rmic script file that is located in the <SAP_install_dir>\<system_name>\<instance_name>\j2ee\deploying directory.

To generate stubs and ties for the AccountImpl implementation class, proceed as follows:

...

       1.      Choose RMI_IIOP Support to show that you are generating RMI-IIOP stubs and ties.

       2.      In the Additional Classpath field, enter the path to any JAR files, or directories containing class files that must be added to the classpath. With this option you no longer have to set in advance the path to the remote objects you generate stubs against. You can use the PathChooser pane on the right-hand side of the screen to browse to the corresponding directories. You add them to the Additional Classpath field by choosing <<.

       3.      In the Class Name field, specify the fully qualified class name of the implementation class against which stubs and skeletons are generated. As with the AccountImpl class, the value of the field must be exapmles.rmi_p4.AccountImpl.

       4.      Depending on your application and your development environment, you can choose the following additional options of the J2EE Engine’s RMIC tool:

...

                            a.      Specify the path to the directory where you want the generated Java files to be stored in the Generator Directory field. The path must be absolute. Use the PathChooser pane on the right-hand side of the screen to browse to the corresponding directoriy. You add it to the Generator Directory field by choosing <<.

If you do not specify anything in this field, the generated files are placed in the directory where the J2EE Engine’s RMIC tool resides.

                            b.      Specify the path to the directory where you want the generated Java class files to be stored in the Compiler Directory field. The path must be absolute. Use the PathChooser pane on the right-hand side of the screen to browse to the corresponding directoriy. You add it to the Compiler Directory field by choosing <<.

If you do not specify anything in this field, the generated files are placed in the directory where the J2EE Engine’s RMIC tool resides.

                            c.      If you do not want the tool to delete the files with .java extensions after it generates the stubs and skeletons, choose Keep Java Files.

                            d.      If you want the tool to generate separate stubs for each remote interface that the remote object implements, choose Additional Stubs. Otherwise, a common stub is generated for all implemented interfaces.

       5.      Choose Generate to generate the stubs and ties. They must be packaged together with the remote interfaces and their implementation classes so that you can deploy them on the J2EE Engine.