Overview

The following wikis outline the various steps required to use an EJBsover HTTP(s) either with the legacy HTTP invoker (AS 3.x and 4.0.x) or with the unified invoker configured to use HTTP as transport (AS/EAP 4.2.x+). 

This is a common configuration where a server is behind a firewall or in a DMZ, with external clients.  The server does not have the correct hostname or Ip address available locally, because it is only available externally on the other side of the firewall.  This configuration will allow clients to use http to communicate with that server behind the firewall.

Only EJB2 beans

• If using AS 3.x or 4.0.x, please see accessing EJBs via HTTP legacy invoker

• If using AS 4.2.x+ or EAP 4.2.x+, please see accessing EJBs via Unified Invoker configured with Servlet as transport

Only EJB3 beans

• See accessing EJB3s over HTTP(s)

EJB2 beans, EJB3 beans and JNDI over HTTP and HTTPS with Unified Invoker

• If using AS 4.2.x+ or EAP 4.2.x+, please see accessing EJB2, EJB3 and JNDI via Unified Invoker configured with Servlet and SSL Servlet as transports for HTTP and HTTPS communication

• If clients are accessing via NAT firewall, see accessing EJB2, EJB3 and JNDI over HTTP/HTTPs via NAT firewall.

Referenced by: