P
Peter Judge
Guest
Some of the Dynamics managers have been changed to add checks for the SESSION:CLIENT-TYPE. The bootstrap mechanism (afxmlcfgp.p) considers the MS agent an Appserver (not a webspeed-server). The rest of the places that the Dynamics code checks the SESSION:CLIENT-TYPE largely use is to determine whether we’re running on a server (below) , and this will continue to work just fine IF NOT ( SESSION : REMOTE OR SESSION : CLIENT-TYPE = "WEBSPEED" :U) One thing to note is that if you want to use PASOE for the Dynamics AppServer and the Dynamics WebSpeed replacement, you’ll have to do some (more) work Set up 2 ABL applications in the instance. This is because Dynamics specifies the type of session via the -icfparam switch (read-only in the session), and the agent command-line (parameters) is done per ABL application. If there’s code that checks for CLIENT-TYPE = WEBSPEED only, it’ll have to change to CLIENT-TYPE= MULTI-SESSION-AGENT AND SESSION:CURRENT-REQUEST-INFO:ADAPTER-TYPE EQ Progress.ApplicationServer.AdapterTypes:WEB The work to use a client-principal for authentication has not been done so you’d have to change that yourself. Hth, --peter
Continue reading...
Continue reading...