B
bart.syryn
Guest
Thanks for all the responses. Correct me if I'm wrong. But with the 'SESSION:CURRENT-REQUEST-INFO:ClientContextId' i know at the appserver-side the session-id of the client. So at that point I can lookup the client-principal in activate.p. With SET-DB-CLIENT(client-principal:handle), i can set the database and also the tenant ? So at login I need to set the correct tenant : client-principal
OMAIN-NAME = "tenantname". Is this correct ? In a stateless-appserver, I need to read this information everytime there's a call to the appserver (activate.p) ? Is it correct that when you use a state-reset-appserver, you only need to do this once (in the connection.p) ? If you use the session:current-request-info:clientcontextid you don't need to pass any extra handles etc. to the appserver (except at login : the username, password and domain-name (tenant)). Is the session:current-request-info:clientcontextid available in ABL ? We still use the appbuilder. I find information about the session:current-request-info in the help, but what is clientcontextid ? Kind regards Bart S.
Continue reading...
OMAIN-NAME = "tenantname". Is this correct ? In a stateless-appserver, I need to read this information everytime there's a call to the appserver (activate.p) ? Is it correct that when you use a state-reset-appserver, you only need to do this once (in the connection.p) ? If you use the session:current-request-info:clientcontextid you don't need to pass any extra handles etc. to the appserver (except at login : the username, password and domain-name (tenant)). Is the session:current-request-info:clientcontextid available in ABL ? We still use the appbuilder. I find information about the session:current-request-info in the help, but what is clientcontextid ? Kind regards Bart S.Continue reading...