JProxy

JProxy is a thin J2EE client provider that delivers J2EE technology stack onto the client side with 90 KB client runtime.

JProxy is a servlet based solution and seamlessly integrates with most of Application Servers. JProxy tunnels J2EE technology stack over HTTP(S) protocol, thus letting your J2EE systems operate over any firewalls, proxies and restrictive network configurations on the Internet instanteniously.

There is no source code change required. Access J2EE technologies from any Java enabled device with no J2EE implementation required on the device itself.

Here are some key features of "JProxy":

￭ HTTP / HTTPS Tunnel for JAX-RPC, CORBA, EJB, JMS or RMI ￭ Asynchronous message delivery for JMS over HTTP / HTTPS without polling ￭ The generic provider-independent communication solution for different EJB, JMS, RMI or CORBA servers ￭ By overriding Application Layer of Open Systems Interconnect (OSI) Stack JProxy seamlessly integrates into any Java enterprise software with NO change to your code. ￭ Small client-side footprint - 90K, which enables you to utilize power of J2EE APIs from Applets running on a variety of devices - Workstations, Cellular Phones, PDA and other hardware that supports Java ￭ The only solution that allows you to employ services of EJB, RMI, JMS and CORBA remote objects via HTTP/HTTPS standard protocol in clients with no support for aforementioned technologies because they're running an older version of Java or Java Micro Edition. Such clients can be wireless devices, cell phones, PDAs and other hardware. ￭ A solution to solve scalability or failover for EJB, RMI or CORBA ￭ The EJB, RMI, JMS or CORBA support for your custom communication protocols ￭ The solution to increase communication performance by utilizing data compression and packaging of multiple independent requests ￭ J2EE Client can access all J2EE services from standard secure "sandbox"

Requirements:

￭ Java Runtime Environment 1.4.1

Limitations:

￭ At startup JProxy will print a message in the client and the server log indicating that this is an evaluation version ￭ Only 2 (two) concurrent clients can communicate with the JProxy Tunnel evaluation version. Specifically, only two physical hosts with JProxy Tunnel clients that have managed to submit their requests to JProxy Tunnel server first are served, while others will be getting an evaluation exception on the client side. ￭ The remote garbage collection is absent, so the server side's footprint will slowly grow. ￭ The Data Compression feature is absent. ￭ The Communication Timeout feature is absent. ￭ Failover feature is absent.