Configuring RMI using Spring Remoting
The Spring approach to HTTP Remoting allows clients to communicate with the Spring-hosted server code via HTTP without the client code requiring any knowledge of HTTP being used. All the RPC calls are handled by Spring Remoting in case of Direct RMI port block.
 |
• From Java version 9 and above, JDK has terminated support for RMI over HTTP tunneling.
• For general information about how Windchill and RMI interact, see Windchill Runtime Environment.
• The information in this section is relevant to both HTTP and HTTPS.
|
RMI over HTTP tunneling for Windchill client is not supported as the sun.rmi.transport.proxy package is removed for Java 11 and later. However, a similar functionality is supported for Java 9 and later using Spring Remoting. Spring Remoting has RMI mechanism to communicate Java serialized object between client and server. If Java 11 or later is used and RMI port is blocked, the flow goes to Spring Remoting. Sprint Remoting uses HTTP post request to transmit Java serialized object.