Originally posted by newman huang: i know it can. but i do not know how to.
First of all, You don't need to know how it is done, this is developers' responsibility.
Second, read your assignment carefully. The CUSTOMER need to communicate with you application using SSL. It is not said anything about the travel agent.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ First of all, You don't need to know how it is done, this is developers' responsibility.
[Comment], I don't agree. I think it's the right responsibility of architect for the remote secure access. Using RMI over HTTPS tunnel for public network (Internet) access is not a good practice. That's the reason HTTP as a black horse in 1995 led ahead than COBRA and DCOM.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Second, read your assignment carefully. The CUSTOMER need to communicate with you application using SSL. It is not said anything about the travel agent. [Comment], Agree, be careful to read it. Agents are assumed to keep using the existing private network which was used for 3270 terminal access. [ August 18, 2006: Message edited by: tony clare ]
Second, read your assignment carefully. The CUSTOMER need to communicate with you application using SSL. It is not said anything about the travel agent.
Good point!
Many people simply assumed that the travel agents are on the intranet.
Regards, Dan
William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.
Yep - I agree that the travel agent app network traffic does not need to be encrypted.
However, encrypted RMI traffic is possible. A good? option with Weblogic is to use their encrypted T3 protocol T3s. It performs much better than tunneling RMI over HTTP(s).
HTH Tom
Tom
What are you saying? I thought you said that Santa gave you that. And this tiny ad: