Show TOC Start of Content Area

Procedure documentation Generating Stubs and Skeletons  Locate the document in its SAP Library structure

Use

You generate stubs and skeletons to provide communication support to your remote objects. You use the RMIC tool to generate them against the implementation class of the remote interface.

You need this tool only if you do not use dynamic stubs and skeletons for your remote objects. For more information about the types of RMI-P4 stubs and skeletons, see Remote Objects Communication in RMI-P4.

Procedure

...

       1.      To start the RMIC tool, run the rmic script file located in the \usr\sap\<system_id>\<instance_name>\j2ee\deploying directory.

       2.      To generate RMI-P4 stubs and skeletons, select RMI_P4 Support.

       3.      In the Additional Classpath field, specify the path to any JAR files or individual class files that must be added to the classpath.

You can use the PathChooser screen area to browse to the corresponding directories. You add them to the Additional Classpath field by choosing <<.

       4.      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 examples.rmi_p4.AccountImpl.

       5.      Set any of the following additional options of the RMIC tool if you want to change their defaults:

                            a.      In the Generator Directory field, specify the path to the directory where you want the generated Java files to be stored. The path must be absolute.

You can use the PathChooser screen area to browse to the corresponding directory. You add it to the Generator Directory field by choosing <<.

Note

By default, the generated files are placed in the directory where the RMIC tool resides.

                            b.      In the Compiler Directory field, specify the path to the directory where you want the generated Java class files to be stored. The path must be absolute.

Use the PathChooser screen area to browse to the corresponding directory. You add it to the Compiler Directory field by choosing <<.

Note

By default, the generated files are placed in the directory where the RMIC tool resides.

                            c.      To provide additional security functions to the generated skeleton, select Use RMI-P4 Security.

This type of skeleton checks whether the client requesting the remote method is authorized to execute this method. If it is not authorized, no access to the remote method is granted by the system.

                            d.      To store additional information about the application in the ThreadContext, select Apply Execution Context.

                            e.      To prevent the tool from deleting the files with .java extensions after it generates the stubs and skeletons, select Keep Java Files.

       6.      Choose Generate to generate the stubs and skeletons.

 

End of Content Area