view webi by openDocument : Session++

sdk development
1

hi,
i view webi by openDocument …each time i view , the session ++; please help me… how to solve it . thanks advance…

spoon (BOB member since 2009-10-22)

2

What is session ++?

Arjun (BOB member since 2008-07-28)

3

each time i view the webi by openDocument ,the number of sessions will
increase…

spoon (BOB member since 2009-10-22)

4

Can you provide the syntax for the hyperlink?

Arjun (BOB member since 2008-07-28)

5

“http://” + CMS + “:8080/OpenDocument/opendoc/openDocument.jsp?” +
“iDocID=” + webiCUID + “&sIDType=cuid&sType=wid&sWindow=Same&token=” + token;

why the number of sessions will increase…? :hb:

spoon (BOB member since 2009-10-22)

6

Check Report Linking in BO XI

Arjun (BOB member since 2008-07-28)

7

See the “token” part of your query string?

You will want to feed a WCAToken and NOT a defaultToken.

The difference? WCAToken will utilize the current session and NOT create a new one. The defaultToken WILL create a new session – of course, you won’t know for sure without trying it out.

Good luck.

Atul Chowdhury (BOB member since 2003-07-07)

8

You said a mouthful …
It’s done, You helped. Thank you

spoon (BOB member since 2009-10-22)

9

Hi DataHog,

We’re using CreateWCAToken to create a token for OpenDocument so as not to increase the session count. I have a couple fo questions:

  1. Should we craete a new token each time we launch OpenDocument from inside the same session?

  2. When we log out using EnterpriseSession.Logoff() and then try logging in again as the same user in the same browser window we now get an “Access denied” error when launching the OpenDocument URL. We’ve tried including Session.Abandon() and Response.Cookies.Clear() as part of the log off process. Not sure how to use LogonTokenMgr.ReleaseToken method though.

Do you have any suggestions or ideas that may help us?

Thanks,
Chris

ChristianKey :uk: (BOB member since 2008-09-19)

10

If you’re relaunching openDocument from within the same session, then you should be able to reuse the existing token created previously so long as the originating EnterpriseSession is still valid, as that is what’s tied to the validity of your WCAToken as well.

Typically, you’ll never want to manually release a token or abandon a session through code - let your app-web server/container do this for you.

You say subsequent logon fail in the same browser. Can you try an experiment and repeat your workflow so it fails as described on the second logon through the same browser, keep that browser open and then launch a different browser (if you’re using IE, now use FF) and see if it permits you to log on? If so, then it may not have removed the cookies correctly. Can you use Fiddler to see what it finds as far as cookies that remain after your logoff?

Also, what does your CreateWCAToken look like? Pass in an empty (“”) string in the first argument instead of the CMS name.

Atul Chowdhury (BOB member since 2003-07-07)