- J2EE Clients
- Types of J2EE Clients
- Servicing Stand-alone Java Client Applications
- Servicing EJB Clients from Other J2EE/EJB Servers
- Servicing CORBA clients from CORBA Object Request Brokers
- Servicing Legacy System Clients (ERP/CRM/Mainframes)
- Servicing JMS Clients
- Servicing Windows/.Net Clients
- Servicing Web service client
- Servicing Clients from Other Environments
Servicing Stand-alone Java Client Applications
Stand-alone Java clients can access all business logic components by making use of Java RMI calls. EJBs internally use RMI over IIOP to communicate between each other, so it is possible to directly execute RMI-based remote procedural calls from stand-alone Java clients.
When EJB access is required, Java clients obtain a handle to the given EJB by making a lookup call through JNDI in the distributed directory service. After the handle is available, Java clients can directly start invoking the business logic codes. Because EJBs are distributed components, it is possible to invoke different EJBs spread across different J2EE server environments in a consistent manner.