Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Analytics Web Administration Guide > Working with Data and Managing the Web Catalog Using Siebel Analytics Web SOAP API > Description of Siebel Analytics Web SOAP API Methods > HtmlViewServiceThe HtmlViewService service embeds Siebel Analytics Web HTML results in third-party dynamic Web pages, such as Active Server Pages (ASP) or JavaServer Pages (JSP), and portal frameworks. The embed process merges Siebel Analytics Web content with the content of third-party Web pages. HTML methods extract fragments of HTML code that can be inserted in third-party Web pages. Table 42 describes the HTML code excerpts and desired page locations. For each returned report object, the HTML code fragment contains a callback link that is followed automatically when the Web page is loaded by the browser. The code fragment does not contain the full user interface definition of the report. While the report is being constructed by Siebel Analytics Web, the user sees the Siebel Analytics Web "Searching..." image (the default image is a spinning arrow) embedded on the third-party Web page. For smooth report transitioning, Siebel Analytics Web tracks the Analytics reports that have been added to a third-party Web page by maintaining information in an internal logical page object during the construction of the third-party Web page. The HtmlViewService service methods explicitly refer to the internal logical page by its ID. About HtmlViewService Bridging and Callback URLsTo embed a report with active drilldown links, the HtmlViewService service allows the Web browser to issue callback requests from embedded reports to the Siebel Analytics Web server. Although it is possible to route requests directly to the Siebel Analytics Web server, in many cases it is preferable to route requests through the Web server that originally serviced the third-party page. Also, in situations where Siebel Analytics Web and the third-party Web server do not belong to the same Domain Name Service (DNS) domain, users may see JavaScript errors related to browser security constraints for cross-domain scripting. To avoid these issues, use the setBridge() method to modify callback URLs to point to the third-party Web server. Be aware that a Web component executed by the third-party Web server to reroute requests to Siebel Analytics Web is not provided. This function would need to be fulfilled by the third-party application. For more information about the setBridge() method, see setBridge() Method. Table 43 shows the supported methods for the HtmlViewService. addReportToPage() MethodThe addReportToPage() method adds results to an HTML page. Signaturevoid addReportToPage(String pageID, String reportID, ReportRef report, String reportViewName, ReportParams reportParams, ReportHTMLOptions options, String sessionID);
endPage() MethodThe endPage() method destroys the Siebel Analytics Web server page object and all data associated with it. Signaturevoid endpage(String pageID, String sessionID); getCommonBodyHTML() MethodThe getCommonBodyHTML() method gets HTML to include in the <BODY> section. SignatureString getCommonBodyHTML(String pageID, String sessionID);
ReturnsReturns a string containing the HTML to include in the <BODY> section. getHeadersHTML() MethodThe getHeadersHTML() method gets HTML to include in the <HEAD> section. SignatureString getHeadersHTML(String pageID, String sessionID);
ReturnsReturns a string containing the HTML to include in the <HEAD> section. getHTMLForReport() MethodThe getHTMLForReport() method gets an HTML excerpt to display the results for a particular report. Before issuing this call, use the addReportToPage method to add the results to an HTML page. SignatureString getHTMLForReport(String pageID, String pageReportID, String sessionID);
ReturnsReturns a string containing the HTML excerpt that displays the specified report. setBridge() MethodThe setBridge() method specifies a bridge URL to receive communications. Specifying a bridge URL can be useful when the Siebel Analytics Web server and the user's Web server reside on different machines, or when you want to modify the results in your application development environment. After the setBridge() method is called, all requests from the client browser to the Siebel Analytics Web server are sent to the bridge URL, which then forwards requests to the Siebel Analytics Web server. Signaturevoid setBridge(String bridgeURL, String sessionID); UsageYou are responsible to make sure that the client browser provides a handler to the bridge URL in the form of a Java servlet, an Active Server Pages (ASP) page, a Common Gateway Interface (CGI), an Internet Server application programming interface (ISAPI), or an equivalent application. You must also perform the following tasks:
How Callback URLs Are ReplacedThe new callback URL is based on the bridge URL, with the addition of a RedirectURL argument. The value of the RedirectURL argument should be the original value of the URL, encoded using standard URL encoding rules. Internally, Siebel Analytics Web usually uses relative URLs for callback links. For example, if the original callback link is saw.dll?Go and the bridge URL is http://myserver/myapplication/sawbridge, the new callback URL is http://myserver/myapplication/sawbridge?RedirectURL=saw.dll%3fGo. startPage() MethodThe startPage() method creates a new page object and returns its ID. SignatureString startPage(StartPageParams options, String sessionID);
Returns |
![]() |
![]() ![]() |
Siebel Analytics Web Administration Guide |