We plan to install Payara Enterprise on Server A and conduct distributed object application
development by communicating with Server B via IIOP (Internet Inter ORB Protocol). It should be
noted that middleware other than Payara will be installed on Server B.
Server A will act as the EJB client, while Server B will serve as the EJB service provider.
We are concerned that if there are any areas where Payara has extended or modified the
functionality of IIOP communication beyond GlassFish, there may be limitations in communication
between Server A (Payara) <----> EJB invocation (IIOP) <----> Server B (non Payara).
Could you please provide information on any areas where Payara has extended or modified the
functionality of IIOP communication beyond GlassFish, if such modifications exist?
Hi @Masami,
Thank you for your question.
Could you please provide information on any areas where Payara has extended or modified the
functionality of IIOP communication beyond GlassFish, if such modifications exist?
The classic IIOP-RMI in Payara Enterprise is fully compatible with that of Glassfish. That core protocol has not been modified by Payara. What Payara Enterprise has is an additional lite and thin client that can be used to communicate via HTTP(S) instead of IIOP-RMI. You can find more about this in the relevant section of the docs.
So in your case, Payara Enterprise should work fine as the client in your setting via the traditional IIOP-RMI protocal.
1 Like