Another approach is use servlets for public internet clients, and sticking
with http protocol between the browser clients and your server. If you need
Java on the client, you can marshall Java objects by value over http using
Java serialization and jamming the serlialized objects into the http
protocol.
Stateless protocol over the public internet is generally a good idea ;-)
-Chris.
> -----Original Message-----
> From: Jeffrey Vagg [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 19, 1999 12:48 AM
> To: [EMAIL PROTECTED]
> Subject: EJB, DMZ's, and firewalls
>
> Hi,
>
> I am not sure if this is the best alias for this. Although it is based
> around accessing EJB through a DMZ.
>
> I am working on an application that has a DMZ configuration between the
> intranet and the Internet. I am currently implementing an intranet EJB
> solution using Weblogic that has no issues with firewalls because it
> doesn't go through them. However, there is another application that I
> am starting to gather requirements for. The client from this
> application will be located on the other side of the outer DMZ firewall,
> the Internet. I am not sure if the client will be HTML or Java. The
> outer firewall only has port 80 open while the inner firewall has one or
> two ports open for this application. In the DMZ I currently have
> Netscape Enterprise Web Server.
>
> If I want to reuse some of the EJB services that I created previously,
> what would be the suggested config? Is it possible to have a Java
> client and use JNDI/EJB through a DMZ? I assume that callbacks would
> not be permitted which would disallow the use of such things as JMS. Is
> this correct? Does anyone know if Weblogic has a solution for this? I
> know that Sun's JDK does HTTP tunneling. Does Weblogic's RMI do the
> same thing and how does this apply to EJB?
>
> I am leaning towards an HTML client and use servlets/JSP. It sounds as
> if there is too many problems with RMI through the firewall. Although I
> would like a more stateful client for my customers. Also I am not sure
> if the JNDI lookup would work because the Weblogic URL is t3://....
> which does not have the http protocol in it. The web server / servlet
> engine in the DMZ can either process the request or act as a proxy
> through the inner firewall.
>
> Any comments or suggestions would be appreciated.
>
> Thanks
> Jeff Vagg
> << File: Card for Jeffrey Vagg >>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
