You'll need to modify the naming service and jrmp
invoker service configurations.
I just noticed, the rmi codebase webserver doesn't
support pluggable socket implementations :-(
So, it is very difficult to configure all ejb invocation via a ssl layer.
if I can , what need I do? Or which document should I refer .
This is explained in the new documentation
($9.99 - end of chapter 8), even if some details
remains obscure (how to change the RMI+SSL domain
name for example).
It works fine for me, and it is transparent (except
for the property).
For CA and keystore, if you do not want to share
the same keystore, I recom this 'cookbook'
(so I dinot manage to run openssl under W2K but on
a linux box it works fine)