与后端服务器IBM工作灯会话控制 [英] IBM Worklight session control with back-end server

问题描述

IBM得到了服务器工作灯上的问题，在此先感谢关于这个问题的任何意见。

Got a question on IBM worklight server, thanks in advance for any comments on this subject.

用户 - >工作灯服务器 - >后端​​服务器

User --> WorkLight Server --> Back-end Server

（1）设计与IBM工作灯工作室移动应用并部署到服务器工作灯

(1) Designed a mobile application with IBM worklight studio and deployed to worklight server.

（2）必须（通过工作灯服务器用户认证通过LDAP）用于第一入口点工作灯服务器

(2) Must use worklight server for the first entry point (user authentication by LDAP via worklight server)

（3）移动应用设计的下载/上传大文件大小（10MB到1GB）的工作灯服务器后面的后端服务器（指工作流程PLS）。

(3) This mobile application designed for downloading/uploading huge file size (10mb to 1gb) to the backend server behind the worklight server (refer to the workflow pls.)

（1）如何会话共享可以在工作灯服务器与后端服务器之间完成？

(1) How session sharing can be done in between worklight server and the back-end server?

（2）如果会话共享不能做，什么是移动应用程序下载/上传文件到后端服务器提供应用程序和后端服务器不跳过知道它同样验证交易的最安全方法工作灯服务器？

(2) If session sharing cannot be done, what's the safest way that mobile application download/upload the files to the back-end server given that the application and back-end server do not know its the same authenticated transaction by skipping worklight server?

（3）难道我误解了从工作灯服务器架构什么？据我所知，工作灯服务器只是一种网关，并通过其框架部署移动应用presentation层。沉重和复杂的计算逻辑应该由其他后端服务器来处理。只要工作灯服务器网络IO是用于文件传输足够宽，它不应该是为工作灯服务器作为在这种情况下，一个网关的一个问题。对于文件传输，它不应该是针对CPU进行计算的负担，因为它只是简单地进出从用户设备到后端服务器（如工作灯一中间人）。

(3) Did I misunderstood anything from the worklight server architecture? as far as I know worklight server is just kind of gateway and presentation layer for deploying mobile application by its framework. Heavy and complex computation logic should be handled by other backend server. As long as the worklight server network IO is wide enough for file transfer, it shouldn't be a problem for the worklight server act as a gateway in this case. For file transfer, it shouldn't be a burden for CPU for computation as it is just simply in and out from the user device to the backend server (worklight as a middle man).

感谢您在百忙之中冗长的问题。

Thank you and sorry for the lengthy question.

推荐答案

（1）如何会话共享可以在工作灯服务器与后端服务器之间完成？

我可以让你将使用工作灯适配器才能做你的文件传输的假设？在这种情况下，一个会话适配器和客户端之间将被创建。更具体一点，如果我有存储在我的适配器一个全局变量和我修改基于来自所述客户端的适配器呼叫的变量，变量的状态将在随后的请求被保持，并且该变量的状态将只有到调用客户端可见。 （只是注意，这并不总是在集群环境中，客户端可以调用单独的工作灯服务器适配器真）

Can I make the assumption that you will be using a worklight adapter in order to do your file transfers? In that case, a "session" between the adapter and the client will be created. To be a bit more specific, if I have a global variable stored in my adapter and I modify the variable based on the adapter call from the client, the state of the variable will be maintained upon subsequent requests, and the state of that variable will only be visible to the calling client. (Just a note, this is not always true in clustered environments, where the client may be calling adapters on separate worklight servers)

（2）如果会话共享不能做，什么是移动应用程序下载/上传文件到后端服务器提供应用程序和后端服务器不知道它的同一认证的最安全的方式通过跳过工作灯服务器的事务？

如上所述，这可以通过适配器实现。由于适配器可以通过认证保护，它知道在客户端通过相同的认证事务调用。

As stated above, this can be achieved through adapters. Since adapters can be protected through authentication, it knows that the client is calling through the same authenticated transaction.

（3）难道我误解了从工作灯服务器架构什么？据我所知，工作灯服务器只是一种网关，并通过其框架部署移动应用presentation层。沉重和复杂的计算逻辑应该由其他后端服务器来处理。只要工作灯服务器网络IO是用于文件传输足够宽，它不应该是为工作灯服务器作为在这种情况下，一个网关的一个问题。对于文件传输，它不应该是针对CPU进行计算的负担，因为它只是简单地进出从用户设备到后端服务器（如工作灯一中间人）。

您击中了要害。我还没有亲自做过具有高量工作灯服务器上的计算任何性能测试，但如果被简单地使用它作为一个直通那么你应该罚款。该工作灯服务器已经知道能够处理的并发呼叫转接的金额相对较高，因此，我相信你会被罚款与您的设置。

You hit the nail on the head. I haven't personally done any performance testing with a high amount of computations on the worklight server, but if it is being used simply as a passthrough then you should be fine. The worklight server has been known to be able to process a relatively high amount of concurrent adapter calls, so I believe you will be fine with your setup.

这篇关于与后端服务器IBM工作灯会话控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！