Application client functions

Application client functions

Use the following table to identify the available functions in the different types of clients.

Available functions ActiveX client Applet client J2EE client Pluggable client Thin client
Provides all the benefits of a J2EE platform Yes No Yes No No
Portable across all J2EE platforms No No Yes No No
Provides the necessary run-time support for communication between a client and a server Yes Yes Yes Yes Yes
Supports the use of nicknames in the deployment descriptor files.
Note: Although one can edit deployment descriptor files, do not use the administrative console to modify them.
Yes No Yes No No
Supports use of the RMI-IIOP protocol Yes Yes Yes Yes Yes
Browser-based application No Yes No No No
Enables development of client applications that can access enterprise bean references and CORBA object references Yes Yes Yes Yes Yes
Enables the initialization of the client application run-time environment Yes No Yes No No
Supports security authentication to enterprise beans Yes Limited Yes Yes Yes
Supports security authentication to local resources Yes No Yes No No
Requires distribution of application to client machines Yes No Yes Yes Yes
Enables access to enterprise beans and other Java classes through Visual Basic, VBScript, and Active Server Pages (ASP) code Yes No No No No
Provides a lightweight client suitable for download No Yes No Yes Yes
Enables access JNDI APIs for enterprise bean resolution Yes Yes Yes Yes Yes
Runs on client machines that use the Sun Java Runtime Environment No No No Yes No
Supports CORBA services (using CORBA services can render the application client code nonportable) No No Yes No No

See Also

ActiveX application clients
Applet clients
J2EE application clients
Thin application clients
Pluggable application clients
Authentication mechanisms

Related Tasks

Configuring authentication mechanisms
Configuring global security
Configuring Java 2 security

Available functions	ActiveX client	Applet client	J2EE client	Pluggable client	Thin client
Provides all the benefits of a J2EE platform	Yes	No	Yes	No	No
Portable across all J2EE platforms	No	No	Yes	No	No
Provides the necessary run-time support for communication between a client and a server	Yes	Yes	Yes	Yes	Yes
Supports the use of nicknames in the deployment descriptor files. Note: Although one can edit deployment descriptor files, do not use the administrative console to modify them.	Yes	No	Yes	No	No
Supports use of the RMI-IIOP protocol	Yes	Yes	Yes	Yes	Yes
Browser-based application	No	Yes	No	No	No
Enables development of client applications that can access enterprise bean references and CORBA object references	Yes	Yes	Yes	Yes	Yes
Enables the initialization of the client application run-time environment	Yes	No	Yes	No	No
Supports security authentication to enterprise beans	Yes	Limited	Yes	Yes	Yes
Supports security authentication to local resources	Yes	No	Yes	No	No
Requires distribution of application to client machines	Yes	No	Yes	Yes	Yes
Enables access to enterprise beans and other Java classes through Visual Basic, VBScript, and Active Server Pages (ASP) code	Yes	No	No	No	No
Provides a lightweight client suitable for download	No	Yes	No	Yes	Yes
Enables access JNDI APIs for enterprise bean resolution	Yes	Yes	Yes	Yes	Yes
Runs on client machines that use the Sun Java Runtime Environment	No	No	No	Yes	No
Supports CORBA services (using CORBA services can render the application client code nonportable)	No	No	Yes	No	No