Serialized session management

[Former Member]

Hello, I am having a problem with using the serialized sessions available from IEnterpriseSession. I would like to understand why this is not working and possibly get some ideas on a better approach if necessary. I am using BOE 3.1 sp5 with the java sdk.

This is a somewhat simplized example of what I am trying to do and the error I am receiving. Basically, the user logs in, does some work and logs out, then the user logs back in and does some more work, but there are session errors.

1) The user logs in to the crystal server:

     IEnterpriseSession lSession = CrystalEnterprise.getSessionMgr().logon("test", "test", "server:port", "secEnterprise");

2) get a serialized session string and save it in the application session cache:    

     String lSerializedSession = lSession.getSerializedSession();

     cachedSerializedSession = lSerializedSession;

3) Query for the CrystalReport using the cached serialized session string:

     IEnterpriseSession lSession2 = CrystalEnterprise.getSessionMgr().getSession(pSession);

     lInfoStore = getInfoStore(cachedSerializedSession);

     PagingQueryOptions lPagingQueryOptions = new PagingQueryOptions();

         lPagingQueryOptions.removeOption(PagingQueryOptions.INCLUDE_SECURITY);

     IPageResult lPageResult = lInfoStore.getPagingQuery(lPathQueryBuff.toString(), lPagingQueryOptions);

4) build up a url using openDocument.jsp, attach the cachedSerializedSession to the URL and launch the URL to a browser.

5) in a different process (i.e. closing my application) I obtain a new IEnterpriseSession by using the cachedSerializedSessionstring. cachedSerializedSession is cleared. :

     IEnterpriseSession lSession3 = CrystalEnterprise.getSessionMgr().getSession(cachedSerializedSession);

     lSession2.logoff();

     cachedSerializedSession = null;

6) The user then logs back in. since the original session was logged out.

     IEnterpriseSession lNewSession = CrystalEnterprise.getSessionMgr().logon("test", "test", "server:port", "secEnterprise");

7) get a new serialized session string and save it in the application session cache:    

     String lSerializedSession = lSession.getSerializedSession();

     cachedSerializedSession = lSerializedSession;

😎 Query for the CrystalReport using the cached serialized session string:

     IEnterpriseSession lSession2 = CrystalEnterprise.getSessionMgr().getSession(cachedSerializedSession);

     lInfoStore = getInfoStore(cachedSerializedSession);

     PagingQueryOptions lPagingQueryOptions = new PagingQueryOptions();

     lPagingQueryOptions.removeOption(PagingQueryOptions.INCLUDE_SECURITY);

     IPageResult lPageResult = lInfoStore.getPagingQuery(lPathQueryBuff.toString(), lPagingQueryOptions);

9) build up a url using openDocument.jsp, attach the cachedSerializedSession to the URL and launch the URL to a browser. openDocument prompts the user to login.

10) if the query (step 😎 is attempted again, using the same cachedSerializedSession, then the following error occurs at the getPagingQuery() call:

     com.crystaldecisions.enterprise.ocaframework.IManagedService$ManagedLogoffException

     : Unable to reconnect to the CMS cic-dev-cr01.Landacorp.local:6400. The session has been logged off or has expired. (FWM 01002)

I would expect that since the user has logged back in, there should be a new session and a new serialized session string. But this does not seem to be the case. Also, I noticed that when the logoff occurs, the connection is not completely removed from the BOE server. The SI_AUTHEN_METHOD changes from "secEnterprise" to "server-token". I'm not sure if that has anything to do with this issue.

Thanks,

Coleen

[Former Member]

Ok, I have simplified this tremendously and I still have the same issue which is...openDocument does not respect a new session after a previous session has been logged off. This looks like a bug in openDocument.

1) login to get an EntrepriseSession

2) attach the serialized session string (obtained from the EnterpriseSession) to the opendocument url and launch the url in a new browser window.

3) log off the session

4) login back in and get a new session

5) build a new opendocument url and attach the new serialized session string.

6) openDocument asks for the login name and password instead of using the new serialized session.

Why is openDocument asking for the login name and password when I have attached a new serialized session? Basically, this forces me to never log out an EnterpriseSession and just wait for a timeout and hope that all the CAL's are not used up. 

Any suggestions would be appreciated.

Thanks,

Coleen

[Former Member]

Hello Coleen,

when you logout the first BOE session, please make sure you clear cookies through java code as well. and then give a try as when using OpenDocument, cookies will be created to view report.....also try to use the fiddler utility in which you will come to know on what is happening.....

Thank You,

Amol