J
Jon Brock
Guest
We are using Dynamics with PASOE on 11.7, and are planning on going to 12.0. There are code changes you need to make within Dynamics and/or ADM2. For instance there are a few references to SESSION:CLIENT-TYPE checking for a value of "APPSERVER" and you need to add "MULTI-SESSION-AGENT" to that (see documentation.progress.com/.../index.html ) There were also some changes we made to the client side to improve support for reconnecting to the appserver. We changed our client deployment strategy with pasoe. Instead of setting up VPN's to connect to the traditional appserver, we use https without a VPN. However this seems to make the connection a bit less reliable, so we were exposing this reconnection bug more often. It looks like it was always intended to be able to recover from transient network errors, but there's a problem in afasconmgr.p connectServiceWithParams. You can change "if not valid-handle(hServer)" to "if not valid-handle(hServer) or not hServer:connected()" and it works much better! I also changed dynamics to use SESSION:CURRENT-REQUEST-INFO:ClientContextId instead of SESSION:SERVER-CONNECTION-ID as the basis of the session id (e.g. in afsesmngrp.i, but there are a number of other files as well). This is so that the session is preserved upon reconnect. But you also need to modify connectServiceWithParams to not recreate the server handle (which causes openedge to generate a new default ClientContextId) and disconnectService to not delete the server handle. An alternative which would probably be better would be to generate your own session id on the client as a guid, store it persistently (global or static class for instance) and then manually set the ClientContextId after the server handle is created. All in all it's possible to do, and at this point we're seeing improved connection stability and performance over the traditional appserver.
Continue reading...
Continue reading...