BOXI R2 SDK - is the user session and infoStore still valid?

[Seabrook7]

Hi All,

We have a custom app that allows our users to run as many reports as they want. Their asp.net session timeout is set very high - to 1 day.

We log them into the BO CMS with a default user ID and password. We want to let them run reports for as long as they want. (we don't have enough users to worry about performance, and we have a CPU license - so it doesn't matter how many sessions are active at a time.)

So in code, we're logging them into the CMS like this...

myEnterpriseSession = mySessionMgr.Logon(user, password, server, auth)

then creating the infoStore like this...

myEnterpriseService = myEnterpriseSession.GetService("InfoStore")
        myInfoStore = CType(myEnterpriseService, InfoStore)

And we're storing both in the session. How can I tell if the IStore is still valid when we grab it out of the session to do a BO query?

the only thing I can find that I THINK is checking is:

if (TypeName(HttpContext.Current.Session("InfoStore")) = "ISInfoStore")...

Also, how can I define the valid number of minutes for this IStore (without using a logonToken and defining it's valid number of minutes)?

Thanks!
Melissa

 

[hilfy]

In the web.config file for your application, you can set the timeout in the sessionstate tag. Here's an example from the web.config that comes with InfoView:

<sessionState mode="InProc"
              stateConnectionString="tcpip=127.0.0.1:42424" 
              sqlConnectionString="data 
              source=127.0.0.1;Trusted_Connection=yes"
              cookieless="false" 
              timeout="20" />

In our Production environment we've changed the timeout value to "999" and don't seem to be having any trouble with the users' sessions timing out. Our users login to Infoview automatically when they log in to our portal, but it may be a couple of hours before they go to the portal's Reports tab to actually use it.

-Dell


A computer only does what you actually told it to do - not what you thought you told it to do.

 

[Seabrook7]

Thanks for the reply, Dell.

The timeout in the web.config file is for the ASP.NET Infoview application itself, not for the BO session that gets created with the CMS when the user logs in, right?

So what you're saying is that the BO Session and it's InfoStore object seem to be valid as long as the users sessions are valid. They're not timing out before their ASP.NET session becomes invalid. So if the InfoStore is stored in the session, and it's still there when we call for it, then it must still be valid?

 

[hilfy]

That seems to be how it's working.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.