I need to know the details of using applet based application in JBOSS - the clients are connecting from NAT enviornments.
I have implementd RMI over HTTP protocol for EJB communication.
But the Client Connect address configuration which is used in Nat'ed IP scenario is to be done at startup.
Even the configuration in HTTP-invoker.sar file where we can form the URL has to be done at the start up; if I provide the NAT IP which client uses here then it binds the domain to that particular client only.
And the same domain can not be used by any other client as they might NAT to diffrent IP.
I need a solution which will allow me to form the URL's from the client end using NAT IP at the runtime; if this can be done the same JBOSS instance can be used by all clients - thos who NAT and those who do not NAT as well.
Please suggest a way out if you have come across similar issue where you need to support many clients out of the same domain and some of them NAT the IP's on client side.
Any help on this will be very much appreciated !!
The JBOSS remoting document says that the ClientConnectAddress can not be changed at the runtime.
5.4.2. Configurations affecting the invoker client
There are some configurations which will impact the invoker client. These will be communicated to the client invoker
via parameters in the Locator URI. These configurations can not be changed during runtime, so can only be
set up upon initial configuration of the server invoker on the server side. The following is a list of these and their
clientConnectPort - the port the client will use to connect to the remoting server. This would be needed in the case
that the client will be going through a router that forwards requests made externally to a different port internally.
clientConnectAddress - the ip or hostname the client will use to connect to the remoting server. This would be
needed in the case that the client will be going through a router that forwards requests made externally to a different
ip or host internally.
If no client connect address or server bind address specified, will use the local host's address (via InetAddress.