Handling Enterprise Session Management and other issues related with URL Reporting or OpenDocument Applies to: BusinessObjects Enterprise XI 3.1 BI 4.0 Summary URL reporting or openDocument.jsp or openDocument.aspx can be conveniently used to view crystal reports, WebI documents, full client or DeskI documents, OLAP-Analysis documents, Voyager workspaces, InfoView dashboards, Xcelsius documents published as SWF files. This document reviews the session management aspect of openDocument.jsp, frequent issues seen URL reporting which are not covered in detail in OpenDocument document. Author: Aasavari Bhave Company: SAP Americas Inc. Created on: 3 October 2011 Author Bio Aasavari works as Consultant III in Developer Support in Customer Assurance of SAP Americas Inc. She has been supporting customers on Custom SDK development for Business Objects Enterprise, Crystal Reports and BusinessObjects Web Services for over five years. The support on SDK includes, creating samples that show how to use APIs, create documentation on SDK usage and troubleshoot and track SDK related product bugs. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com © 2011 SAP AG 1 Handling Enterprise Session Management and other issues related with URL Reporting or OpenDocument Table of Contents Introduction ......................................................................................................................................................... 3 Session Management ......................................................................................................................................... 3 Methods of Bypassing logon for openDocument using Enterprise SDK ........................................................ 3 Default Token ............................................................................................................................................................... 3 CreateLogonToken ...................................................................................................................................................... 3 CreateWCAToken ........................................................................................................................................................ 4 Serialized Session ....................................................................................................................................................... 4 Single Sign-On ............................................................................................................................................................. 4 Issues with OpenDocument ................................................................................................................................ 5 No Customization ............................................................................................................................................ 5 Number of Sessions ........................................................................................................................................ 5 Closing Browser .............................................................................................................................................. 5 Timeout ........................................................................................................................................................... 5 CreateWCAToken Issue ................................................................................................................................. 5 How to logoff the session explicitly ................................................................................................................. 5 Using Same Browser Sessions or Tabs in same Browser ............................................................................. 5 Behavior in Different Service Packs, Fix Packs .............................................................................................. 5 Viewing WebI Vs Crystal Reports ................................................................................................................... 5 Viewing Crystal Reports .................................................................................................................................. 5 Limitation of OpenDocument .......................................................................................................................... 6 InfoView Preferences ...................................................................................................................................... 6 Transition from XI 3.1 to BI 4.0 ........................................................................................................................... 6 Related Content .................................................................................................................................................. 7 Copyright............................................................................................................................................................. 8 SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com © 2011 SAP AG 2 Handling Enterprise Session Management and other issues related with URL Reporting or OpenDocument Introduction URL reporting or openDocument.jsp or openDocument.aspx can be conveniently used to view Crystal Reports WebI documents full client or DeskI documents OLAP-Analysis documents Voyager workspaces InfoView dashboards Xcelsius documents published as SWF files. This document reviews the session management aspect of openDocument.jsp, frequent issues seen URL reporting which are not covered in detail in openDocument document. Session Management After launching openDocument.aspx or openDocument.jsp URL, the user is prompted to logon to CMS. To bypass the logon at this stage, pass a logon token or serialized session in the URL. This logon token or serialized session is generally created in a JSP or ASPX page using BusinessObjects Enterprise SDK. The JSP or ASPX page then redirects to openDocument. Redirect to openDocument.jsp or openDocument.aspx regardless of how the token or serialized session is created. Methods of Bypassing logon for openDocument using Enterprise SDK Default Token IEnterpriseSession es = CrystalEnterprise.getSessionMgr().logon(“<username>”,”<password>,”<cmsname>”,”<authtype>” );String token = es.getLogonTokenMgr().getDefaultToken(); response.sendRedirect("http://<servername>:<port./OpenDocument/opendoc/openDocument.jsp?< other arguments>&token=" + token); Pros Lasts for 12 hours or when the original session that created it is logged off, whatever occurs first. This token can be used to re-logon into a timed out\ expired session. Cons Every use of default token consumes one session on enterprise. CreateLogonToken IEnterpriseSession es = CrystalEnterprise.getSessionMgr().logon(“<username>”,”<password>,”<cmsname>”,”<authtype>” ); String token = es.getLogonTokenMgr().createLogonToken("",5,20); response.sendRedirect("http://<servername>:<port./OpenDocument/opendoc/openDocument.jsp?< other arguments>&token=" + token); Pros Has more flexibility, can specify client machine where it is valid or valid number of usages or valid number of minute. It can be used for whatever is specified or when the original session that created it is logged off explicitly, whatever occurs first. It is logged off, whatever occurs first. This token can be used to re-logon into a timed out\ expired session. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com © 2011 SAP AG 3 Handling Enterprise Session Management and other issues related with URL Reporting or OpenDocument Cons Every use of the token consumes one session on enterprise. CreateWCAToken IEnterpriseSession es = CrystalEnterprise.getSessionMgr().logon(“<username>”,”<password>,”<cmsname>”,”<authtype>” ); String token = es.getLogonTokenMgr().createWCAToken("",5,20); response.sendRedirect("http://<servername>:<port./OpenDocument/opendoc/openDocument.jsp?< other arguments>&token=" + token); Pros Token created this way has more flexibility; can specify client machines where it is valid or valid number of usages or valid number of minute. It can be used for whatever is specified or when the original session that created it is logged off explicitly, whatever occurs first. Every use of this token will not consume one session on enterprise. This token is really meant to be used by BO applications /InfoViewApp, /InfoViewAppActions, /CrystalReports, /Analytical Reporting for sending requests to one another so that the request can be sent out without session count increase. Cons Token created this way cannot be used to re-logon an expired or timed out session. Serialized Session IEnterpriseSession es = CrystalEnterprise.getSessionMgr().logon(“<username>”,”<password>,”<cmsname>”,”<authtype>” ); String serializedSession = es.getSerializedSession(); response.sendRedirect("servername:port/OpenDocument/opendoc/openDocument.jsp?<other arguments>&serses=" + java.net.URLEncoder.encode(serializedSession)); Pros This is a serialized session that is passed in URL, and it doesn't consume an additional enterprise session. Thus, it is a good alternative to using WCA token which is more prone to errors. It can be used to re-logon into timed out or expired session. Cons Serialized session can be used only as long as the original session that created it is not explicitly logged off.