Java开发网 - 最近出的IBM Websphere App Server Client是个什么咚咚？

Java开发网

您没有登录

» Java开发网 » Application Server » WebSphere

打印话题 寄给朋友 订阅主题

作者	最近出的IBM Websphere App Server Client是个什么咚咚？
jjohn 发贴: 0 积分: 0	于 2003-12-21 15:16 我觉得像一个客户端的"App server“。请各位大虾指点一二。 • 请求JAVA学习方向？？？？？

作者	Re:最近出的IBM Websphere App Server Client是个什么咚咚？ [Re:jjohn]
why 問題兒童总版主发贴: 4629 积分: 388	于 2003-12-22 00:04 小的也想清楚知道那是什么咚咚啦。初看见这个题目，想答那是WAS-EE其中一片光碟，安装Applet ActiveX, CORBA等client。 • SWT Designer v1.2.3 Released!

作者

Re:最近出的IBM Websphere App Server Client是个什么咚咚？ [Re:jjohn]

davidself

猫哥

CJSDN高级会员

发贴: 1506
积分: 333

于 2003-12-22 10:59

说明书上是这样写的

In a traditional client server environment, the client requests a service and the server fulfills the request. Multiple clients use a single server. Clients can also access several different servers. This model persists for Java clients except now these requests make use of a client run-time environment.

In this model, the client application requires a servlet to communicate with the enterprise bean, and the servlet must reside on the same machine as the WebSphere Application Server.

With WebSphere Application Server Version 5, application clients now consist of the following models:
v ActiveX application client
v Applet client
v J2EE application client
v Pluggable application client
v Thin application client

The ActiveX application client model, uses the Java Native Interface (JNI) architecture to programmatically access the Java virtual machine (JVM) API. Therefore the JVM code exists in the same process space as the ActiveX application (Visual Basic, VBScript, or Active Server Pages (ASP)) and remains attached to the process until that process terminates.

In the Applet client model, a Java applet embeds in a HyperText Markup Language (HTML) document residing on a remote client machine from the WebSphere Application Server. With this type of client, the user accesses an enterprise bean in the WebSphere Application Server through the Java applet in the HTML document.

The J2EE application client is a Java application program that accesses enterprise beans, Java Database Connectivity (JDBC), and Java Message Service message queues. The J2EE application client program runs on client machines. This program follows the same Java programming model as other Java programs; however, the J2EE application client depends on the application client run time to configure its execution environment, and uses the Java Naming and Directory Interface (JNDI) name space to access resources.

The Pluggable and thin application clients provide a lightweight Java client programming model. These clients are best suited in situations where a Java client application exists but the application needs enhancements to use enterprise beans, or where the client application requires a thinner, more lightweight environment than the one offered by the J2EE application client. The difference between the thin application client and the pluggable application client is that the thin application client includes a Java virtual machine (JVM) API, and the pluggable application client requires the user to provide this code. The pluggable application client uses the Sun Java Development Kit, and the thin application client uses the IBM Developer Kit For the Java Platform.

The J2EE application client programming model provides the benefits of the J2EE platform for the Java client application. The J2EE application client offers the ability to seamlessly develop, assemble, deploy and launch a client application. The tooling provided with the WebSphere platform supports the seamless integration of these stages to help the developer create a client application from start to finish.

When you develop a client application using and adhering to the J2EE platform, you can put the client application code from one J2EE platform implementation to another. The client application package can require redeployment using each J2EE platform deployment tool, but the code that comprises the client application does not change.

The application client run time supplies a container that provides access to system services for the client application code. The client application code must contain a main method. The application client run time invokes this main method after the environment initializes and runs until the Java virtual machine code terminates.

The J2EE platform allows the application client to use nicknames or short names, defined within the client application deployment descriptor. These deployment descriptors identify enterprise beans or local resources (JDBC, Java Message Service (JMS), JavaMail and URL APIs) for simplified resolution through JNDI use. This simplified resolution to the enterprise bean reference and local resource reference also eliminates changes to the client application code, when the underlying object or resource either changes or moves to a different server. When these changes occur, the application client can require redeployment. Although you can edit deployment descriptor files, do not use the administrative console to modify them.

The application client also provides initialization of the run-time environment for the client application. The deployment descriptor defines this unique initialization for each client application. The application client run time also provides support for security authentication to the enterprise beans and local resources.

The application client uses the RMI-IIOP protocol. Using this protocol enables the client application to access enterprise bean references and to use CORBA services provided by the J2EE platform implementation. Use of the RMI-IIOP protocol and the accessibility of CORBA services assist users in developing a client application that requires access to both enterprise bean references and CORBA object references.

When you combine the J2EE and CORBA environments or programming models in one client application, you must understand the differences between the two programming models to use and manage each appropriately.

View the Samples gallery for more information about application clients. Before you run the basicCalculator Sample, ensure the JMS Server is started.

--108的上铺--
davidself@twitter

• CJSDNer6月14日北京聚会花絮

作者

Re:最近出的IBM Websphere App Server Client是个什么咚咚？ [Re:jjohn]

davidself

猫哥

CJSDN高级会员

发贴: 1506
积分: 333

于 2003-12-22 11:01

定制安装有这样的功能部件中文说明：

J2EE 客户机／Java 瘦客户机支持使用 J2EE 应用程序编程模型或通过轻量级非 J2EE 编程模型访问 IBM WebSphere Application Server EJB、JDBC 数据库和 Java 消息服务消息队列。

Java 消息服务支持通过 JMS 编程接口与 IBM WebSphere Application Server 软件组件的通信。

Applet 客户机允许客户机通过使用 HTML 中包含的 java applet 访问 WebSphere Application Server 中的 EJB。

ActiveX 到 EJB 网桥允许在如 Microsoft Visual Basic、Active Server Pages 和 VBScript 环境中开发的程序利用 WebSphere J2EE 资源和服务（如，企业 Java Bean、Java 命名和目录接口、JavaMail 和 Java 消息服务）。

可插入应用程序客户机支持使用您现有的 Sun Java 运行时环境（JRE），通过轻量级非 J2EE 编程模型访问 IBM WebSphere Application Server EJB。

--108的上铺--
davidself@twitter

• Windows环境下的tomcat + apache配置(绝对实践操作版)

已读帖子

新的帖子

被删除的帖子