Viewing Documents Using OpenDocument SAP BusinessObjects Business Intelligence platform 4.0 Support Package 2

Transcription

1 Viewing Documents Using OpenDocument SAP BusinessObjects Business Intelligence platform 4.0 Support Package 2

2 Copyright 2011 SAP AG. All rights reserved.sap, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.all other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.these materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

3 Contents Chapter Getting started...5 About this documentation...5 Who should use this documentation?...5 About OpenDocument...5 What's new in SAP BusinessObjects Business Intelligence platform Migrating your links...6 Changes to the default URL path...6 Deprecated parameters...7 Chapter OpenDocument syntax...9 Basic URL syntax...9 URL syntax considerations...9 Chapter Session management...11 Serialized sessions...11 Logon tokens...12 User sessions...12 Chapter Parameter reference...15 Session management parameters...17 serses...17 token...18 Document identifier parameters...19 idocid...19 sdocname...19 sidtype...20 sinstance...21 Input parameters...21 lsc...21 lsm[name]...22 lsr[name]...23 lss[name]

4 Contents spartcontext...25 srefresh...25 sreportmode...26 sreportname...27 sreportpart...27 Output parameters...28 NAII...28 soutputformat...28 sviewer...29 Appendix A More Information...31 Index 33 4

5 Getting started Getting started 1.1 About this documentation This documentation provides you with information for constructing parameterized URLs with the OpenDocument syntax. OpenDocument URLs link to Business Intelligence (BI) documents in an SAP BusinessObjects Business Intelligence platform installation. A parameter reference, including syntax and usage examples, is provided for each OpenDocument URL parameter. For information about deploying the OpenDocument web application after the installation of the BI platform, see the SAP BusinessObjects Business Intelligence platform Web Application Deployment Guide Who should use this documentation? This documentation is for anyone creating URLs to BI documents with the OpenDocument syntax. We recommend consulting this guide if you are: Providing end users with hyperlinks to a document through or other direct means. Embedding hyperlinks in one document to another. Programmatically generating hyperlinks to documents in your custom application. Familiarity with the management and organization of objects in your BI platform installation is beneficial About OpenDocument OpenDocument is one of many deployed web applications within a BI platform installation. It processes incoming URL requests for documents and any other viewable object type in the Central Management Server (CMS), and delivers the correct document to the end user in the appropriate viewer. This allows you to send users direct links to a document and avoid having them navigate through a folder hierarchy, such as in BI launch pad. The OpenDocument syntax and its parameters allow you to construct URLs that link to these documents. For example, consider the following URL: Type=CUID 5

6 Getting started Replace <servername>:<port> with the name and port number of your web server where OpenDocument is deployed. This URL accesses the object in the CMS with the CUID value of Aa6GrrM79cRAmaOSMGoadKI. If this is a Crystal report, for example, then the report is rendered to the user in a default SAP Crystal Reports viewer. In this example, idocid is one of many URL parameters. These parameters specify how to access a particular document in the CMS, or determine how to display the document to the user. You can link to many viewable object types with the OpenDocument syntax. Some examples include: Crystal reports Web Intelligence documents Analysis workspaces BI launch pad workspaces Dashboard Design objects (formerly Xcelsius) Some of the designers for these BI document types provide GUI-based URL builders to help you embed opendocument URLs into your documents. Consult their respective product documentation for information on these features. 1.2 What's new in SAP BusinessObjects Business Intelligence platform 4.0 serses parameter The serses parameter can now be used to pass a serialized Enterprise session to an OpenDocument URL. Use this parameter so users avoid encountering additional logon prompts in your custom application. For more information on the serses parameter and managing user sessions, see Session management and serses. 1.3 Migrating your links Changes to the default URL path 6

7 Getting started The default URL to the OpenDocument web application bundle has changed in SAP BusinessObjects Business Intelligence platform 4.0. New absolute OpenDocument links need to use the new default URL: If you are migrating reports with existing links from an XI 3.x release platform, resolve the issue by setting up the following redirect in your web server: Redirect:../OpenDocument/opendoc/openDocument.jsp To:../BOE/OpenDocument/opendoc/openDocument.jsp Ensure that all URL request parameters are forwarded correctly by your redirect. Refer to your web server documentation for detailed steps on implementing a redirect. SAP BusinessObjects Business Intelligence platform 4.0 only supports a Java deployment of OpenDocument. The OpenDocument web bundle is part of the BOE.war file Deprecated parameters This section lists deprecated and obsolete OpenDocument parameters as of SAP BusinessObjects Business Intelligence platform 4.0. Obsolete parameters are unsupported. Deprecated and obsolete members as of SAP BusinessObjects Enterprise XI 3.1 Service Packs are also listed for reference. Table 1-5: Deprecated Parameters Parameter Replace with sidtype=guid Deprecated in SAP BusinessObjects Enterprise XI 3.1 SP3) Specifies that a GUID is used to specify the viewable document. Use in conjunction with idocid. Use sidtype=cuid instead. sidtype=ruid Deprecated in SAP BusinessObjects Enterprise XI 3.1 SP3) Specifies that a RUID is used to specify the viewable document. Use in conjunction with idocid. Use sidtype=cuid instead. 7

8 Getting started Parameter Replace with skind Specifies the SI_KIND property of the target Desktop Intelligence document. Use idocid instead. spath The file path of the target document. Use idocid instead. spath does not support the use of localized folder names which are available in this release. Legacy documents that use spath to reference the correct folder name as stored in the CMS will continue to work while under deprecation. But it is recommended that you migrate your links to use the idocid parameter instead. stype Specifies the file type of the target document. Use idocid instead. sviewer=actx Specifies the Crystal Reports ActiveX Viewer. Use sviewer=html or sviewer=part instead. The ActiveX Viewer is deprecated as of this release. sviewer=java Specifies the Crystal Reports Java Applet Viewer. Use sviewer=html or sviewer=part instead. The Java Applet Viewer is deprecated as of this release. Table 1-6: Obsolete Parameters Parameter Replace with swindow Obsolete as of SAP BusinessObjects Enterprise XI 3.1 SP3 Indicates whether the target document will open in the current browser window or whether a new window will be launched. Use the HTML anchor's target attribute or an equivalent. For example: <a href="..." tar get="_blank">...</a> 8

9 OpenDocument syntax OpenDocument syntax 2.1 Basic URL syntax The basic syntax for an OpenDocument URL is as follows: Variables are denoted with angle brackets. You must substitute the proper value for these variables. For example, you must use the name of your BI platform server where OpenDocument is hosted in place of <servername> and you must use the correct port number in place of <port> to access the OpenDocument web application. 2.2 URL syntax considerations Accessing documents You must include the idocid or sdocname parameter in your OpenDocument URL to specify the document to be viewed. Since there may be multiple documents in the Central Management Server (CMS) with the same name, and documents can be moved or renamed, it is recommended that you use idocid to ensure uniqueness. Joining parameters Join parameters with the ampersand (&). Do not place spaces around the ampersand. For example: stype=wid&sdocname=sales2003 The ampersand is always required between parameters. Spaces and special characters in parameter values Because some browsers cannot interpret spaces, the parameters of the link cannot contain spaces or other special characters that require URL encoding. To avoid the misinterpretation of special characters, you can define a URL-encoded string in the source database to replace the special character with an escape sequence. This will allow the database to ignore the special character and correctly interpret the parameter value. Note that certain RDBMS have functions that allow you to replace one special character with another. 9

10 OpenDocument syntax By creating an escape sequence for the plus sign (+), you can instruct the database to interpret the plus sign as a space. In this case, a document title Sales Report for 2003 would be specified in the DocName parameter as: &sdocname=sales+report+for+2003& This syntax prevents the database from misinterpreting the spaces in the title. In addition, values for serialized sessions (using the serses parameter) and logon tokens (using the token parameter) must be URL-encoded by your application before being passed to the OpenDocument URL string. Trailing spaces in parameter values Trim trailing spaces at the end of parameter values and prompt names. Do not replace them with a plus sign (+). The viewer may not know whether to interpret the plus sign (+) as part of the prompt name or as a space. For example, if the prompt name displays: Select a City:_ (where _ represents a space), enter the following text in the link: lssselect+a+city:=paris where the spaces within the prompt name are replaced with the plus sign, and the trailing space is trimmed off. Capitalization All of the OpenDocument parameters and parameter values are case sensitive. URL length limit OpenDocument may add characters to your URL when it redirects to the requested document; however, encoded URLs cannot exceed the maximum character limit for the supported browsers. For example, certain versions of Internet Explorer limit the URL length to 2083 characters. Therefore, know the browser character limit to ensure your URL will be within the maximum limit. Parameter values in links to sub-reports You cannot pass parameter values to a sub-report of a target Crystal report. Opening a new window To force OpenDocument HTML links to open a new browser window, use the HTML anchor's target attribute or an equivalent. For example: <a href=" KI&sIDType=CUID" target="_blank">hyperlink text</a> 10

11 Session management Session management Normally when using an OpenDocument link to access documents secured in the BI platform, the user will be prompted for credentials. OpenDocument provides two parameters to avoid having the user prompted for their username and password information. You can either insert a serialized session or a logon token directly into the OpenDocument URL. This gives you control over the duration of the access to the document. OpenDocument URLs can be set to different languages. 3.1 Serialized sessions Serialized sessions can be used in OpenDocument by inserting the serses parameter into the OpenDocument URL. This allows users to access files without being prompted for credentials. Creating a serialized sessions does not use up an additional licence. Serialized sessions expire if the original user's session times out or logs off. The following example uses the BI platform Java SDK to pass in a serialized session to the OpenDocument URL. For more information on the IEnterpriseSession.getSerializedSession method, see the SAP BusinessObjects Business Intelligence platform Java API Reference. String opendocumentserses() throws SDKException, UnsupportedEncodingException { IEnterpriseSession sess = CrystalEnterprise.getSessionMgr().logon ("username", "password", "<cms>:<port>", "secenterprise"); String sersession = sess.getserializedsession(); String sersesencode = URLEncoder.encode(serSession, "UTF-8"); return (" KI&sIDType=CUID&serSes=" + sersesencode); } Replace <server>:<port> with the server name and port number of your web server. Replace <cms>:<port> with the Central Management Server (CMS) name and port number. You must URL-encode the serialized session. Since an OpenDocument URL with a serialized session contains the user session, they must not be shared for security reasons. 11

12 Session management 3.2 Logon tokens Logon tokens can be used in OpenDocument by inserting the token parameter into the OpenDocument URL. Logon tokens allow users access to files secured in the BI platform without being prompted for credentials, while also giving you control on the duration of the access to the file. Creating a new logon token uses up an additional licence. The following example uses the BI platform Java SDK to pass in a logon token to the OpenDocument URL. For more information on the ILogonTokenMgr.createLogonToken method, see the SAP BusinessObjects Business Intelligence platform Java API Reference. String opendocumenttoken() throws SDKException, UnsupportedEncodingException { IEnterpriseSession sess = CrystalEnterprise.getSessionMgr().logon ("username", "password", "<cms>:</port>", "secenterprise"); String token = sess.getlogontokenmgr().createlogontoken("",120,100); String tokenencode = URLEncoder.encode(token, "UTF-8"); sess.logoff(); return (" KI&sIDType=CUID&token=" + tokenencode); } Replace <server>:<port> with the server name and port number of your web server. Replace <cms>:<port> with the Central Management Server (CMS) name and port number. The createlogontoken method allows you to specify the machine that can use the token (which can be empty to allow any user to use the token), the number of minutes the token is valid for, and the number of logons that the token can be used for as parameters. Since the newly created logon token consumes an additional session, sess.logoff is called to logoff the original session. Since an OpenDocument URL with a logon token contains the user session, they must not be shared for security reasons. 3.3 User sessions When OpenDocument is used from BI launch pad or the CMC, it will access the current user session and the user does not need to enter credentials. When a document is viewed using an OpenDocument URL, the user will be prompted for credentials except in the following cases: Vintela or Siteminder SSO is configured for the deployed OpenDocument web application. The OpenDocument URL uses a serses or a token parameter. The OpenDocument application has an existing user session for that browser session. 12

13 Session management If the existing session is different than the session in the serses or token parameter, the existing session will be closed and a new session will be created. That is, you can use serses or token parameter to over-ride an existing user session. The OpenDocument application will look for an existing user session in the Web application session and in cookies. Only one OpenDocument session can be created from a single browser session. If the new serses or token parameter is incorrect and there is an existing user session, OpenDocument will attempt to open the document using the current user session. If it can't it will then prompt the user for credentials. 13

14 Session management 14

15 Parameter reference Parameter reference This section provides details about the available OpenDocument parameters, their specific uses, and relevant examples. The document to which an OpenDocument link points to is referred to as the target document. Table 4-1: Session Management Parameters Parameter serses Specifies a valid serialized Enterprise session. token Specifies a valid logon token for the current Enterprise session. Table 4-2: Document Identifier Parameters Parameter idocid Specifies the unique identifier of the viewable document in the CMS. Use in conjunction with sidtype. sdocname Specifies the name of the viewable document in the CMS. sidtype Specifies the type of object identifier used to specify the viewable document. Use in conjunction with idocid. sinstance Specifies the scheduled instance of the target document to open. Use in conjunction with sdocname or idocid. 15

16 Parameter reference Table 4-3: Input Parameters Parameter lsc Specifies a contextual prompt for Web Intelligence documents if there is an ambiguity during SQL generation. lsm[name] Specifies multiple values for a prompt. [NAME] is the text of the prompt. lsr[name] Specifies a range of values for a prompt. [NAME] is the text of the prompt. lss[name] Specifies a value for a single prompt. [NAME] is the text of the prompt. spartcontext Specifies the data context of a Crystal report part. Use in conjunction with sreportpart. srefresh Indicates whether a database refresh should be forced when the target document is opened. sreportmode Indicates whether the link should open the full target Crystal report or just the report part specified in. sreportname Specifies the report to open if the target document contains multiple reports. sreportpart Specifies the part of the target Crystal report to open. Table 4-4: Output Parameters Parameter NAII Indicates whether to force the display of the prompt selection page for Interactive Analysis prompts. soutputformat Specifies the format in which to open the target document. 16

17 Parameter reference Parameter sviewer Specifies the selected report viewer. 4.1 Session management parameters serses serses Specifies a valid serialized Enterprise session. A serialized string representing the current Enterprise session. Contains a serialized session of the current user session. This can be entered into an OpenDocument URL to allow users to access files without being prompted for credentials. Creating a serialized sessions does not use up an additional licence. Serialized sessions expire if the original user's session times out or logs off. The following example uses the BI platform Java SDK to pass in a serialized session to the OpenDocument URL. For more information on the IEnterpriseSession.getSerializedSession method, see the SAP BusinessObjects Business Intelligence platform Java API Reference. You can retrieve a serialized session in a similar fashion using other BI platform SDKs such as.net and Web Services. String opendocumentserses() throws SDKException, UnsupportedEncodingException { IEnterpriseSession sess = CrystalEnterprise.getSessionMgr().logon ("username", "password", "<cms>:<port>", "secenterprise"); String sersession = sess.getserializedsession(); String sersesencode = URLEncoder.encode(serSession, "UTF-8"); return (" KI&sIDType=CUID&serSes=" + sersesencode); } Replace <server>:<port> with the server name and port number of your web server. 17

18 Parameter reference Replace <cms>:<port> with the Central Management Server (CMS) name and port number. You must URL-encode the serialized session. Since an OpenDocument URL with a serialized session contains the user session, they must not be shared for security reasons token token Specifies a valid logon token for the current Enterprise session. The logon token for the current Enterprise session. Contains the logon token for the current user. This can be entered into an OpenDocument URL to allow users to access files without being prompted for credentials. Creating a new logon token uses up an additional licence. The following example uses the BI platform Java SDK to pass in a logon token to the OpenDocument URL. For more information on the ILogonTokenMgr.createLogonToken method, see the SAP BusinessObjects Business Intelligence platform Java API Reference. You can create logon tokens in a similar fashion using other BI platform SDKs such as.net and Web Services. String opendocumenttoken() throws SDKException, UnsupportedEncodingException { IEnterpriseSession sess = CrystalEnterprise.getSessionMgr().logon ("username", "password", "<cms>:<port>", "secenterprise"); String token = sess.getlogontokenmgr().createlogontoken("",120,100); String tokenencode = URLEncoder.encode(token, "UTF-8"); return (" KI&sIDType=CUID&token=" + tokenencode); } Replace <server>:<port> with the server name and port number of your web server. Replace <cms>:<port> with the Central Management Server (CMS) name and port number. The createlogontoken method allows you to specify the machine that can use the token (which can be empty to allow any user to use the token), the number of minutes the token is valid for, and the number of logons that the token can be used for as parameters. Since an OpenDocument URL with a logon token contains the user session, they must not be shared for security reasons. 18

19 Parameter reference 4.2 Document identifier parameters idocid idocid Specifies the unique identifier of the viewable document in the CMS. Use in conjunction with sidtype. A numerical identifier associated with the document in the CMS. You must include the idocid or sdocname parameter in your OpenDocument URL to specify the document to be viewed. Since there may be multiple documents in the CMS with the same name, it is recommended that you use idocid to ensure uniqueness. You can see identifier values for a document within the Central Management Console (CMC) or BI launch pad applications. The properties page for each document contains the document ID and the CUID. You can also obtain the identifier programmatically using the BI platform SDK. For example, in the Java SDK the com.crystaldecisions.sdk.occa.infostore.iinfoobject interface contains getid and getcuid methods which you can pass to an OpenDocument URL. If you pass in an InfoObject ID rather than a CUID, you do not need to specify the sidtype parameter. However, InfoObject IDs are changed when migrating documents from one CMS to another. It is recommended that the CUID be used, which is preserved during migration. Type=CUID sdocname 19

20 Parameter reference sdocname Specifies the name of the viewable document in the CMS. The title of the document in the CMS. You must include the idocid or sdocname parameter in your OpenDocument URL to specify the document to be viewed. Since there may be multiple documents in the CMS with the same name, and documents can be moved or renamed, it is recommended that you use idocid to ensure uniqueness. sdocname does not support the use of localized document names. Legacy documents that use sdoc Name to reference the correct document name as stored in the CMS will continue to work. But it is recommended that you use the idocid parameter instead sidtype sidtype Specifies the type of object identifier used to specify the viewable document. Use in conjunction with ido cid. InfoObjectID ParentID CUID If you pass in an InfoObject ID as a value to idocid rather than a CUID, you do not need to specify the sidtype parameter. However, InfoObject IDs are changed when migrating documents from one CMS to another. It is recommended that the CUID be used, which is preserved during migration. Type=CUID 20

21 Parameter reference sinstance sinstance Specifies the scheduled instance of the target document to open. Use in conjunction with sdocname or ido cid. User (Latest instance owned by current user) Last (Latest instance of the document) Param (Latest instance of the document with matching parameter values. Crystal reports and Web Intelligence documents only.) Input parameters lsc lsc Specifies a contextual prompt if there is an ambiguity during SQL generation. Only supported by Web Intelligence documents. A prompt value that resolves the ambiguity in the SQL generation. 21

22 Parameter reference Type=CUID&lsC=Sales lsm[name] lsm[name] Specifies multiple values for a prompt. [NAME] is the text of the prompt. Multiple prompt values, separated by a comma. no_value (only for optional parameters) You can remove an optional parameter from the prompt by setting it to no_value in the opendocument query string. If you leave an optional parameter out of the opendocument query string, a default parameter value will be applied. Type=CUID&sRefresh=Y&lsMSelect+Cities=[Paris],[London] Type=CUID&sRefresh=Y&lsMparamStringDR=[c],[d]&lsMparamNumberDR=[3],[4]&lsMparamDate DR=[Date(2003,6,3)],[Date(2003,6,4)]&lsMparamDateTimeDR=[DateTime(2003,6,1,3,1,1)],[DateTime(2003,6,1,4,1,1)] Crystal reports If the target is a Crystal report, each value must be enclosed in square brackets. Web Intelligence documents The character? is a reserved prompt value for Web Intelligence documents in an opendocument URL. Setting the prompt value to lsm[name]=? in the URL forces the "Prompts" dialog box to appear for that particular prompt. Olap Intelligence reports If the target document is an OLAP Intelligence report (.car) you can use the IsM parameter to specify prompts. The parameters are passed in as a URL-encoded string using the unique name of the parameter set up in the OLAP Intelligence report. 22

23 Parameter reference Setting a memberset parameter MADC216EA-D9A5-42B5-AE%2C21%2C84%2CA9%2CF9%2C6E%2C31%2C7=[%5BCustomers%5D.%5BCountry%5D.%26%5BMexi co%5d],[%5bcustomers%5d.%5bcountry%5d.%26%5bcanada%5d] This example opens up an OLAP Intelligence report with a memberset parameter to Customers > Country > Mexico and Customers > Country > Canada in the view lsr[name] lsr[name] Specifies a range of values for a prompt. [NAME] is the text of the prompt. Not supported by OLAP Intelligence reports. A range of values for the prompt, separated by a double period (..). no_value (only for optional parameters) You can remove an optional parameter from the prompt by setting it to no_value in the opendocument query string. If you leave an optional parameter out of the opendocument query string, a default parameter value will be applied. Type=CUID&sRefresh=Y&lsRTime+Period:=[ ) Type=CUID&sRefresh=Y&lsRparamStringDR=[h..i]&lsRparamNumberDR=[7..8]&lsRparamCurrencyDR=[3..4]&lsRparamDat edr=[date(2003,6,7)..date(2003,6,8)]&lsrparamdatetimedr=[datetime(2003,6,1,7,1,1)..date Time(2003,6,1,8,1,1)]&lsRparamTimeDR=[Time(1,1,7)..Time(1,1,8)]&lsRparamUnbound1=(..6)&lsRpara munbound2=[6..)&lsrparamstringr=[a..d]&lsrparamnumberr=[1..3]&lsrparamcurrencyr=[1..3]&lsrparam DateR=[Date(2003,6,1)..Date(2003,6,3)]&lsRparamDateTimeR=[DateTime(2003,6,1,1,1,1)..Date Time(2003,6,1,3,1,1)]&lsRparamTimeR=[Time(1,1,1)..Time(3,1,1)] Crystal reports If the target is a Crystal report, the range must be enclosed in square brackets and/or parentheses (use a square bracket next to a value to include it in the range, and parentheses to exclude it). 23

24 Parameter reference lss[name] lss[name] Specifies a value for a single prompt. [NAME] is the text of the prompt. A single prompt value. no_value (only for optional parameters) You can remove an optional parameter from the prompt by setting it to no_value in the OpenDocument URL. If you leave an optional parameter out of the OpenDocument URL, a default parameter value will be applied. Type=CUID&sRefresh=Y&lsSparamString=h&lsSparamNumber=1& lssparamcurrency=121&lssparamdate=date(2003,6,11)& lssparamdatetime=datetime(2003,6,11,14,38,37)&lssparamboolean=false& lssparamtime=time(12,39,2)&lssparamstringdr=a&lssparamdatedr=date(2003,6,1) Web Intelligence documents The character? is a reserved prompt value for Web Intelligence documents in an opendocument URL. Setting the prompt value to lss[name]=? in the URL forces the "Prompts" dialog box to appear for that particular prompt. OLAP Intelligence reports If the target document is an OLAP Intelligence report (.car) you can use the IsS parameter to specify prompts. The parameters are passed in as a URL-encoded string using the unique name of the parameter set up in the OLAP Intelligence report. Opening an OLAP report to a specific page If 23CAA3C1-8DBB-4CF3-BA%2CB8%2CD7%2CF0%2C68%2CEF%2C9C%2C6F is the URL-encoded unique name for the page parameter in the OLAP Intelligence report, you would use the following URL to open the OLAP Intelligence report to page 2: ject&stype=car&lss23caa3c1-8dbb-4cf3-ba%2cb8%2cd7%2cf0%2c68%2cef%2c9c%2c6f=2 24

25 Parameter reference Setting a cube parameter If C-9B1D B%2C5E%2CD9%2C1F%2C20%2CF8%2C1%2C62 is the URL-encoded unique name for the cube parameter opening the warehouse cube in the catalogue FoodMart 2000 on MSAS, you would use the following URL to open this cube parameter: ject&stype=car&lss c-9b1d b%2c5e%2cd9%2c1f%2c20%2cf8%2c1%2c62=catalog%3dfood Mart%202000,CUBE%3Dwarehouse spartcontext spartcontext Specifies the data context of a report part. Use in conjunction with sre portpart. Only supported by Crystal reports. The name of the report part data context. Only mandatory if a value is specified for sreportpart. Type=CUID&sReportPart=Part1&sPartContext=0-4-0 The sreportpart and spartcontext parameters are only supported with the DHML parts viewer (sviewer=part) srefresh 25

26 Parameter reference srefresh Indicates whether a database refresh should be forced when the target document is opened. Y N Certain documents can contain saved settings to specify that a database refresh must occur when the document is opened in a viewer. These document settings will override srefresh=n. Type=CUID&sRefresh=Y Crystal reports The srefresh parameter is only supported with the html and part Crystal report viewers, and not the actx and java viewers sreportmode sreportmode Indicates whether the link should open the full target Crystal report or just the report part specified in sre portpart. Only supported by Crystal reports. Full Part Defaults to Full if this parameter is not specified. Only applies if a value is specified for sreportpart. Type=CUID&sReportPart=Part1&sReportMode=Part 26

27 Parameter reference sreportname sreportname Specifies the report to open if the target document contains multiple reports. The report name for Web Intelligence documents and page name for OLAP Intelligence reports. Defaults to the first report if this parameter is not specified. Type=CUID&sReportName=First+Report+Tab sreportpart sreportpart Specifies the part of the target Crystal report to open. Only supported by Crystal reports. Name of the Crystal report part. Type=CUID&sReportPart=Part1 The sreportpart and spartcontext parameters are only supported with the DHML parts viewer (sviewer=part). 27

28 Parameter reference 4.4 Output parameters NAII NAII Indicates whether to force the display of the prompt selection page. Only supported by Web Intelligence documents. Y (prompt values that are passed with lss, lsm, or lsr in the URL are applied and not displayed in the "Prompts" dialog box) NAII=Y raises the "Prompts" dialog box for any values not specified in the URL. Prompts created with default values are still displayed in the "Prompts" dialog box. If all prompt values are specified in the URL, the prompt window does not appear even if NAII=Y is specified. This example assumes there are two prompts in the Web Intelligence document: Year and Country. NAII=Y forces the "Prompts" dialog box to appear and allows the user to specify a value for the Country prompt. The Year prompt is already set to a value of FY1999 in the URL using the lss parameter and therefore is not prompted for. Type=CUID&lsSYear=FY1999&NAII=Y&sRefresh=Y soutputformat 28

29 Parameter reference soutputformat Specifies the format in which to open the target document. H (HTML) P (PDF) E (Microsoft Excel ( ) - Crystal reports only) W (Rich Text Format (RTF) - Crystal reports only) Defaults to HTML if this parameter is not specified. Type=CUID&sOutputFormat=E sviewer sviewer Specifies the selected report viewer. html part (Crystal reports only) Type=CUID&sViewer=html 29

30 Parameter reference 30

31 More Information More Information Information Resource SAP BusinessObjects product information Location Navigate to and on the "SAP BusinessObjects Overview" side panel click All Products. SAP Help Portal You can access the most up-to-date documentation covering all SAP BusinessObjects products and their deployment at the SAP Help Portal. You can download PDF versions or installable HTML libraries. Certain guides are stored on the SAP Service Marketplace and are not available from the SAP Help Portal. These guides are listed on the Help Portal accompanied by a link to the SAP Service Marketplace. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. SAP Service Marketplace > Documentation Installation guides: Release notes: The SAP Service Marketplace stores certain installation guides, upgrade and migration guides, deployment guides, release notes and Supported Platforms documents. Customers with a maintenance agreement have an authorized user ID to access this site. Contact your customer support representative to obtain an ID. If you are redirected to the SAP Service Marketplace from the SAP Help Portal, use the menu in the navigation pane on the left to locate the category containing the documentation you want to access. Docupedia Docupedia provides additional documentation resources, a collaborative authoring environment, and an interactive feedback channel. Developer resources

32 More Information Information Resource SAP BusinessObjects articles on the SAP Community Network Location These articles were formerly known as technical papers. Notes Forums on the SAP Community Network These notes were formerly known as Knowledge Base articles. Training From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. Online customer support The SAP Support Portal contains information about Customer Support programs and services. It also has links to a wide range of technical information and downloads. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. Consulting Consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in topics such as relational and multidimensional databases, connectivity, database design tools, and customized embedding technology. 32

33 Index I idocid 19 L logon tokens 12 lsc 21 lsm 22 lsr 23 lss 24 M migration 6 N NAII 28 P parameters deprecated 7 list of 15 obsolete 7 S sdocname 19 serialized sessions 11 serses 17 session management 11 sidtype 20 sinstance 21 soutputformat 28 spartcontext 25 srefresh 25 sreportmode 26 sreportname 27 sreportpart 27 sviewer 29 syntax 9 T token 18 U user sessions 12 W what's new 6 33

34 Index 34