You acquire the RMI-IIOP stubs and interfaces of J2EE applications that are imported into the J2EE server.

The RMI-IIOP stubs and interfaces of J2EE applications that are imported into the J2EE server cannot be acquired if the J2EE application has not been started even once.

Moreover, if Enterprise Beans containing the remote interface do not exist in the J2EE application, acquiring the RMI-IIOP stubs and interfaces results in an error.

Execute the following command to acquire the RMI-IIOP stubs and interfaces:

Execution format

cjgetstubsjar [server-name] [-nameserver provider-URL] -name application-name -d storage-path-of-RMI-IIOP-stubs-and-interfaces

Example of execution

cjgetstubsjar MyServer -name App1 -d temp

Note:

• You can use this functionality only if the following conditions are fulfilled:
  
  • If Application Server version 06-50 or later is upgraded when the J2EE applications created with an earlier version exist on the J2EE server
  • If the name is not changed with the cjrenameapp command
• You cannot acquire the RMI-IIOP stubs and interfaces based on index.html in the following cases:
  
  • If either the J2EE applications with runtime information or J2EE applications without runtime information are imported
  • If a new J2EE application is created in an environment of version 06-50 or later
  • If the name is changed with the cjrenameapp command.
• When you change the name of the application for which application.xml is omitted, an application.xml is created. Therefore, the J2EE application for which the application name is changed will be same as the application with application.xml.

For details on the cjgetstubsjar command, see cjgetstubsjar (Acquiring RMI-IIOP stubs and interfaces of applications) in the uCosminexus Application Server Command Reference Guide.