So here is the situation:
We have to embbed an AS400 application in a specific tab on the View 360 of a PCSi-based application. And we're doing this by using an iFrame linked to an URL allowing connecting to Convertigo, a software which is"webizing" AS400 applications.
Doing this we have to manage Convertigo "sessions". Such a session is created when the iFrame is displayed, unless there is an already existing and idle one for the current user. When we stop using a session we have to turn it idle (so it is reusable) AND we have to "reset" it. Finally when the operator is logging out, we have to close all existing sessions.
And now here is the issue:
As described, a session is created when displaying a iFrame containing a reference to a Convertigo URL. That is to say, the session is created from the browser on the client side (and not from a rule running on the Pega server side). This is fundamental as Convertigo sessions are basically identified using the JSession ID cookie.
For this reason, when it comes to resetting or closing a Convertigo session, we have to call HTTP-based web services and we have to call them from the client side browser. We cannot use Connect-HTTP rules as these rules will be running on the server and will not be using the same JSession ID that is corresponding to the browser instance from which the initial call creating the Convertigo session was made.
Thanks for your help.
***Updated by moderator: Lochan. Removed user added #helpme tag. Apologies for confusion, shouldn't have been an end-user option.
Unfortunatly that is the initial solution we implemented and it's not working.
The Activity and the Connect-HTTP rule that is called from there are running server-side. So the JSessionID that is used is by definition different from the one that has been used when initially creating the Convertigo session as this Convertigo session has been created by a call from a browser instance on the client PC.