構(gòu)建基于 web 的分析系統(tǒng)外文翻譯

1、<p><b>　　外 文 翻 譯</b></p><p>　　原文1：Building a Web-Based Analysis System Part1</p><p>　　譯文1： 構(gòu)建基于 Web 的分析系統(tǒng) 第一部分 </p><p>　　原文2：Building a Web-Based Analysis Sy

2、stem Part2</p><p>　　譯文2： 構(gòu)建基于 Web 的分析系統(tǒng) 第二部分 </p><p><b>　　原文1</b></p><p>　　Building a Web-Based Analysis System Part 1</p><p>　　A real-world look

3、at using the Analysis Services Thin Web Client Browser</p><p>　　Mark Scott, John Lynn</p><p>　　Using OWC to Deploy Office on the Web</p><p>　　When working with analytical databases,

4、 analysts organize data into common groups and try to determine what would happen if things were different.</p><p>　　For example, would increasing a product's price—which would increase profit per unit b

5、ut probably reduce number of units sold—yield a higher or lower overall profit? Or how would a drop in the federal discount rate affect the yield of real estate loans? To help analysts make educated projections based on

6、historical trends, Microsoft provides Analysis Services in SQL Server 2000 and OLAP Services in SQL Server 7.0. These services provide OLAP capability and can process data stored in SQL Server (</p><p>　　For

7、 example, real estate investors use cash-flow modeling to isolate a group of loans that have common characteristics (e.g., types of properties, geographic area, range of interest rates) and project the effects of differe

8、nt kinds of events. What will happen if loans mature more rapidly than expected or if the borrowers default? And how might such unpredictable events affect the yield of bonds that the loans secure?</p><p>　　

9、Selecting from lists that can include hundreds of loans and isolating the loans that have the characteristic that you're analyzing can be tricky. Analysis Services and OLAP Services can help correlate these groups of

10、 loans so that analysts can model loan assumptions. To help a client's real estate analysts project the performance of commercial mortgage-backed securities, our development team needed to devise a system that simpli

11、fied the grouping of loans in different ways—such as by their intere</p><p>　　Having settled on a back-end technology, the development team began working on a plan for implementing the front-end interface. M

12、ost financial analysts use Microsoft Excel and are familiar and comfortable with its interface. Excel includes PivotTable Service, which lets analysts connect to Analysis Services databases. Excel's drag-and-drop int

13、erface provides simple, intuitive access to multidimensional data without requiring users to have extensive training. And by using Excel's graphing capabil</p><p>　　Excel would have been a fine choice—if

14、 all the client's users worked together in the same building and could access the Analysis server through the same LAN. But because the users needed to share the application from a variety of organizations whose offi

15、ces are scattered around the world, the team needed a component similar to Excel that users could access through the Internet. The team found the solution to this challenge in Office Web Components. OWC is a set of Activ

16、eX controls that you can u</p><p>　　PivotTable can retrieve multidimensional data from an Analysis server and present the data in an interactive, drag-and-drop interface. Users who have Microsoft Internet Ex

17、plorer (IE) 4.01 or later can use OWC to analyze Analysis Services data without installing additional component software. Figure 2 shows the OWC PivotTable client interface, which looks and works like the familiar Excel

18、interface. The OWC PivotTable also provides intelligent caching, which improves performance by reducing the n</p><p>　　Although OWC provided everything our development team's project needed, we encounter

19、ed problems when we tried to deploy OWC across the Internet. The first problem was the platform that OWC runs on. The Office XP version of OWC requires Microsoft Data Access Components (MDAC) 2.6 or later. Many of the se

20、rvice subscribers use Windows NT Workstation 4.0 as their OS, and to install MDAC 2.6, they also had to install Service Pack 6 (SP6). One of the primary attractions of using OWC was that we though</p><p>　　T

21、he second problem that our team encountered was connectivity. OWC requires a direct connection to the Analysis Services data source. OWC communicates directly with the Analysis server through the default port, 2725, whic

22、h is a problem for organizations with firewalls. (For details about connecting to Analysis Services, see the Microsoft article "INF: TCP Ports Used by OLAP Services when Connecting Through a Firewall" at http:/

23、/support.microsoft.com/default.aspx?scid=kb;en-us;q301</p><p><b>　　901.)</b></p><p>　　First, we tried to solve the connectivity problem by using an HTTP connection to connect to the

24、server through port 80. This connection provides access through the same port that the Web browser uses. For added security, Analysis Services can alternatively connect through port 443 by using Secure Sockets Layer (SSL

25、). Most organizations open both port 80 and port 443 to let users access the Internet. (For more information about using HTTP, see the Microsoft article "INF: How to Connect to Analysi</p><p>　　However,

26、 the implementation of HTTP connectivity created some insurmountable obstacles. Connections through port 80 were significantly slower than direct connections in our tests. Because the multidimensional cube has to provide

27、 large amounts of data to the client, the performance degradation made using OWC impractical.</p><p>　　Looking for Alternatives </p><p>　　Next, our team considered using ADO-MD and MDX queries t

28、o create a custom interface. You can query the Analysis Services cube directly through the OPENROWSET command. (For information about querying Analysis Services, see the Microsoft article "HOWTO: SQL Server 7 Distri

29、buted Query with OLAP Server" at http://support.microsoft.com/ default.aspx? scid=kb;en-us;q218592.) OPENROWSET lets you query data from any OLE DB source, including Analysis Services. This flexibility would let us

30、use ADO to que</p><p>　　The team also investigated several third-party solutions. Many third-party solutions help users build a query and execute it to see the results. Such an approach uses system resources

31、 efficiently but isn't as interactive as the Excel and OWC drag-and-drop interfaces. So although these solutions offered unique advantages, none met the exact requirements of the project. When our team added custom d

32、evelopment costs to the overall cost of the third-party software, we decided to look elsewhere.</p><p><b>　　譯文1</b></p><p>　　作者：Mark Scott(美), John Lynn(美)</p><p><b&

33、gt;　　國籍：美國</b></p><p>　　出處：http://msdn.microsoft.com/en-us/library/aa224834(SQL.80).aspx </p><p>　　構(gòu)建基于 Web 的分析系統(tǒng) 第一部分</p><p>　　使用分析服務(wù) Web 瘦客戶端瀏覽器的現(xiàn)實看法 </p><p>　　

34、Mark Scott, John Lynn </p><p>　　使用 OWC 在 Web 上部署 Office </p><p>　　在選定了后端技術(shù)后，開發(fā)小組開始制訂實現(xiàn)前端界面的計劃。多數(shù)金融分析人員使用 Microsoft Excel，他們對其界面比較熟悉，感覺也很舒服。Excel 包括數(shù)據(jù)透視表服務(wù)，能夠允許分析人員連接到分析服務(wù)數(shù)據(jù)庫。Excel 的拖放界面提供了對多維數(shù)據(jù)的

35、簡單和直觀的訪問，并不要求用戶進行深入的培訓。而且，通過使用 Excel 的制圖功能，用戶能夠以圖和表的形式表示數(shù)據(jù)。所以，對于前端界面，小組的首選是 Microsoft Office XP 中的 Excel 2002。圖 1 顯示了 Excel 數(shù)據(jù)透視表服務(wù)瀏覽一個分析服務(wù) OLAP 多維數(shù)據(jù)集的情形。</p><p>　　如果所有的客戶端用戶在同一幢大樓內(nèi)一起工作，并通過同一個局域網(wǎng)訪問分析服務(wù)器，Exce

36、l 會是不錯的選擇。但用戶需要和辦公地點散布于世界各地的不同組織共享應(yīng)用程序，因此開發(fā)小組需要一個用戶可以通過 Internet 訪問且類似于 Excel 的組件。該小組發(fā)現(xiàn) Office Web 組件 (OWC) 能夠滿足這一需要。OWC 是一組能夠在 Web 頁上使用并提供 Office 功能的 ActiveX 控件。OWC 數(shù)據(jù)透視表組件是 Excel 中數(shù)據(jù)透視表服務(wù)的 Web 版本；數(shù)據(jù)透視表使用數(shù)據(jù)透視表服務(wù)，并要求在運行前

37、安裝數(shù)據(jù)透視表服務(wù)。但沒有 Excel，OWC 數(shù)據(jù)透視表也能工作。</p><p>　　數(shù)據(jù)透視表能夠從分析服務(wù)器上檢索多維數(shù)據(jù)并將這些數(shù)據(jù)顯示在一個交互的拖放界面上。已安裝 Microsoft Internet Explorer (IE) 4.01 或以上版本的用戶可以使用 OWC 對分析服務(wù)數(shù)據(jù)進行分析，而不必安裝額外的組件軟件。圖 2顯示了外觀和操作都類似于熟悉的 Excel 界面的 OWC 數(shù)據(jù)透視表客

38、戶端界面。OWC 數(shù)據(jù)透視表也提供了智能緩存，通過減少數(shù)據(jù)透視表從網(wǎng)絡(luò)到服務(wù)器的往返行程次數(shù)而提高性能。所以，通過有效使用分析服務(wù)，數(shù)據(jù)透視表能夠減少數(shù)據(jù)傳輸并提高效率。</p><p>　　雖然 OWC 提供了我們開發(fā)小組的項目需要的全部東西，但當我們試圖在 Internet 上部署 OWC 時，我們遇到了難題。首先是 OWC 的運行平臺問題。Office XP 版的 OWC 要求使用 Microsoft Da

39、ta Access Components (MDAC) 2.6 或以上版本。而許多服務(wù)訂戶使用 Windows NT Workstation 4.0 作為其操作系統(tǒng)，如果要安裝 MDAC 2.6，還必須安裝 Service Pack 6 (SP6)。使用 OWC 的一個主要吸引力在于我們認為它能夠?qū)崿F(xiàn)無縫的部署。我們發(fā)現(xiàn)雖然能夠自動處理安裝 Service Pack，但該過程需要重新啟動，非常麻煩。以后，Microsoft 提供了一個使

40、用 SP4 的 OWC 組件修訂版本，但我們同時也在開發(fā)自己的應(yīng)用程序，在金融機構(gòu)嚴格控制的客戶端網(wǎng)絡(luò)上部署 Service Pack 是一個很大的困難。因此，需要在操作系統(tǒng)上使用特定 Service Pack 的解決方案是不可行的。</p><p>　　其次，我們小組遇到了連接問題。OWC 要求直接連接分析服務(wù)數(shù)據(jù)源。OWC 使用默認的 2725 端口直接和分析服務(wù)器通信，對于使用防火墻的機構(gòu)來說，這是個問題。

41、（有關(guān)連接分析服務(wù)的詳細信息，參見位于 http://support.microsoft.com/default. aspx?scid=kb;en-us;q301901 的 Microsoft 文章 "INF:TCP Ports Used by OLAP Services when Connecting Through a Firewall"。）</p><p>　　首先，我們試圖使用 HT

42、TP 連接和服務(wù)器通過 80 端口進行連接以解決連接問題。該連接通過 Web 瀏覽器使用的同一個端口來提供訪問。對于額外的安全性，分析服務(wù)還能夠使用安全套接字層 (SSL)，通過 443 端口進行連接。大多數(shù)組織同時打開 80 端口和 443 端口以便用戶訪問 Internet。（有關(guān)使用 HTTP 的更多信息，參見位于 http://support.microsoft.com/default.aspx?scid=kb;en-us;q2

43、79489 的 Microsoft 文章 "INF: How to Connect to Analysis Service 2000 By Using HTTP Conection"。）圖 3說明了使用 OWC 連接到分析服務(wù)器涉及的問題。</p><p>　　然而，HTTP 連接的執(zhí)行產(chǎn)生了一些難以克服的困難。我們測試顯示，通過 80 端口進行連接要明顯慢于直接連接。因為多維數(shù)據(jù)集需要向客戶

44、端提供大量的數(shù)據(jù)，性能的降低使 OWC 的使用很不現(xiàn)實。</p><p><b>　　尋找替代方案</b></p><p>　　接下來，我們的小組考慮使用 ADO-MD 和 MDX 查詢創(chuàng)建自定義界面。您可使用 OPENROWSET 命令直接查詢分析服務(wù)多維數(shù)據(jù)集。（有關(guān)查詢分析服務(wù)的信息，參見位于 http://support.microsoft.com/defau

45、lt.aspx?scid=kb;en-us;q218592 的 Microsoft 文章 "HOWTO:SQL Server 7 Distributed Query with OLAP Server"。）OPENROWSET 允許您從包括分析服務(wù)在內(nèi)的任何 OLE DB 源上查詢數(shù)據(jù)。這種靈活性能夠讓我們使用 ADO 查詢分析服務(wù)。分析服務(wù)使用的 OLE DB 提供程序 MSOLAP 將多維數(shù)據(jù)轉(zhuǎn)換成 ADO 能夠用

46、來同前端的應(yīng)用程序進行數(shù)據(jù)通信的標準行集。這種自定義解決方案的問題在于創(chuàng)建具有 OWC 和 Excel 外觀的直觀而且互動的界面是一件非常復雜的工作。雖然開發(fā)小組能夠創(chuàng)建這樣的界面，但所花時間長、費用高，且需要不斷進行維護，因此該解決方案不具備可行性。</p><p>　　開發(fā)小組也研究了幾個第三方的解決方案。很多第三方解決方案是幫助用戶生成一個查詢，然后執(zhí)行它來查看結(jié)果。這種方式雖然有效地利用了系統(tǒng)資源，但達不

47、到 Excel 和 OWC 的拖放界面同樣的交互式效果。所以，雖然這些解決方案各具優(yōu)勢，但沒有一個能夠完全滿足本項目的要求。在我們小組將自定義開發(fā)成本加入第三方軟件的總成本考慮時，我們決定重新尋找替代方案。</p><p><b>　　原文2</b></p><p>　　Building a Web-Based Analysis System Part 2</p

48、><p>　　Using the Thin Web Client to Access Multidimensional Data </p><p>　　The development team members finally went to the Microsoft SQL Server Resource Kit and found the solution to our dilemma:

49、the Analysis Services Thin Web Client Browser. (To access the Thin Web Client on the resource kit CD-ROM, see the reference in chapter 39 of the resource kit at http://www.microsoft.com/resources/documentation/sql/2000/a

50、ll/ reskit/en-us/part11/c3961.mspx.) The Thin Web Client uses Active Server Pages (ASP) to connect to the Analysis server, converts the multidimensional data </p><p>　　The Thin Web Client requires IE 5.0 or

51、later. Because the client doesn't connect directly to the Analysis Services computer, the client doesn't need MDAC 2.6. Most of our client's subscribers have IE 5.0, so we didn't have to deploy service pa

52、cks to the subscribers' PCs. Figure 5 shows the architecture that the Thin Web Client uses. The Thin Web Client uses ASP to query the cube from the Microsoft IIS server rather than from the client. The Thin Web Clien

53、t comes with ASP pages, which you can dep</p><p>　　The Thin Web Client puts the queried data in a gridlike HTML table structure and sends the data to the browser. The user interacts with the data through Jav

54、aScript. By using transparent layers, users can drag dimensions into the cube to manipulate the data, drill down through dimensions, and display and analyze the data they need.</p><p>　　Using the Thin Web Cl

55、ient requires some compromises, as most design decisions do. Because a trust relationship can't exist between the Web server domain and the back-end domain, you can't extend Active Directory (AD) as your authenti

56、cation service through the system. Such a trust relationship could provide a means for an intruder to violate security on the back-end domain. So the system must set up one anonymous user to access the data on the Analys

57、is server. If access to the data depends on the</p><p>　　The Thin Web Client also has other drawbacks. OWC uses PivotTable's intelligent caching to minimize trips from the Web browser to the OLAP Web ser

58、ver to get more data. But the Thin Web Client draws data from the server side, and because data isn't cached at the Web browser, each change to the data requires the browser to make a new request from the Web server.

59、 When you're working with large amounts of data, this process can be sluggish. Also, OWC has a rich object model against which you can pro</p><p>　　Choosing the Right Client for the Task </p><

60、p>　　The lessons our development team learned from this project can provide a valuable guide for deploying OLAP solutions in an enterprise. Excel provides a capable, familiar client that you can deploy in a LAN but req

61、uires realtime connectivity to the OLAP server. OWC works well for deploying an Analysis Services client in an intranet because you can easily control the client platform and open ports securely in an intranet. The Thin

62、Web Client provides a good Internet solution when firewalls are in </p><p><b>　　譯文2</b></p><p>　　作者：Mark Scott(美), John Lynn(美)</p><p><b>　　國籍：美國</b></p&g

63、t;<p>　　出處：http://msdn.microsoft.com/en-us/library/aa224834(SQL.80).aspx</p><p>　　構(gòu)建基于 Web 的分析系統(tǒng) 第二部分</p><p>　　使用 Web 瘦客戶端訪問多維數(shù)據(jù)</p><p>　　開發(fā)小組成員最后選用 Microsoft SQL Server Reso

64、urce Kit，為我們的難題找到了解決方案：分析服務(wù) Web 瘦客戶端瀏覽器。（要在資源工具箱 CD-ROM 上訪問 Web 瘦客戶端，參見資源工具箱第 39 章的參考信息，該信息位于 http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/reskit/sql2000/part11/c3961.asp。）Web 瘦客戶端使用

65、 Active Server Page (ASP) 連接到分析服務(wù)器、將多維數(shù)據(jù)轉(zhuǎn)換成 HTML，并將數(shù)據(jù)傳遞給客戶端。圖 4說明了 Web 瘦客戶端顯示貸款數(shù)據(jù)子集的情況。</p><p>　　Web 瘦客戶端需要 IE 5.0 或以上版本。因為客戶端不直接連接到分析服務(wù)計算機，所以客戶端不需要 MDAC 2.6。由于多數(shù)客戶端訂戶具有 IE 5.0，所以我們不必在訂戶的個人計算機上部署 Service Pac

66、k。圖 5顯示了 Web 瘦客戶端使用的結(jié)構(gòu)。Web 瘦客戶端使用 ASP 從 Microsoft IIS 服務(wù)器 — 而不是客戶端 — 來查詢多維數(shù)據(jù)集。Web 瘦客戶端帶有 ASP 頁，使得您能夠在 IIS 服務(wù)器上部署。因為只有運行 ASP 的 IIS 服務(wù)器才能夠連接到分析服務(wù)數(shù)據(jù)庫，所以，您能夠使用一個連接來保證通過防火墻進行的多維數(shù)據(jù)集訪問，并且可以將該連接局限于 Web 服務(wù)器和數(shù)據(jù)庫服務(wù)器。這種安排創(chuàng)建了一個高效和易于保

67、護的連接。對客戶端的唯一連接是標準的 HTML 連接，這能夠減少防火墻的影響。</p><p>　　Web 瘦客戶端將查詢的數(shù)據(jù)放到一個網(wǎng)格狀的 HTML 表結(jié)構(gòu)中，并將數(shù)據(jù)發(fā)送到瀏覽器。用戶通過 JavaScript 和數(shù)據(jù)進行交互。通過使用透明層，用戶可以將維拖到多維數(shù)據(jù)集中進行數(shù)據(jù)操作、通過維向下追溯并顯示和分析其需要的數(shù)據(jù)。</p><p>　　如多數(shù)設(shè)計決策那樣，使用 Web 瘦

68、客戶端需要做出某些折衷。因為在 Web 服務(wù)器域和后端域之間不存在信任關(guān)系。您不能在系統(tǒng)中擴展 Active Directory (AD) 作為其驗證服務(wù)。這樣的信任關(guān)系會給入侵者提供一種破壞后端域安全的方法。因此，系統(tǒng)必須建立一個匿名用戶來訪問分析服務(wù)器上的數(shù)據(jù)。如果對數(shù)據(jù)的訪問取決于用戶，則不能使用基于分析服務(wù)的角色安全性來控制對數(shù)據(jù)的訪問。然而，如果系統(tǒng)允許所有用戶通過一個安全上下文進行數(shù)據(jù)訪問，則使用 Web 瘦客戶端是安全的，

69、而且容易部署。</p><p>　　Web 瘦客戶端也有其他缺點。OWC 通過使用數(shù)據(jù)透視表的智能緩存把從 Web 瀏覽器到 OLAP Web 服務(wù)器的往返行程數(shù)減少到最小來獲取更多的數(shù)據(jù)。但 Web 瘦客戶端是從服務(wù)器端提取數(shù)據(jù)的，因為數(shù)據(jù)在 Web 瀏覽器中并不緩存，所以每次對數(shù)據(jù)的更改都要求瀏覽器向 Web 服務(wù)器提出新的請求。當處理的數(shù)據(jù)量很大時，這個進程會很緩慢。OWC 還具有豐富的對象模型，您可以對之

70、編寫自定義代碼。而 Web 瘦客戶端使用 JavaScript，很難自定義。因為 Web 瘦客戶端是資源工具箱內(nèi)包含的“自由代碼”，所以 Microsoft 并不像支持 Excel 或 OWC 那樣對 Web 瘦客戶端提供相同程度的支持。而且，Web 瘦客戶端要求客戶端腳本，如果 Web 瀏覽器已經(jīng)更新或更改，它會產(chǎn)生錯誤。此外，Web 瘦客戶端不直接支持對服務(wù)器的回寫。幸好，我們小組的應(yīng)用程序不要求回寫， 所以，這個缺失的功能并不妨礙

71、我們使用 Web 瘦客戶端。在對其優(yōu)點和缺點進行評估后，我們決定部署 Web 瘦客戶端。這個解決方案在生產(chǎn)環(huán)境中使用效果不錯，并得到了用戶的廣泛認可。</p><p>　　為任務(wù)選擇合適的客戶端</p><p>　　我們的開發(fā)小組在本項目中得到的經(jīng)驗教訓能夠為在企業(yè)中部署 OLAP 解決方案提供有價值的指導。Excel 提供了功能強大而且熟悉的客戶端，您可以在局域網(wǎng)中進行部署，但需要實時連

72、接 OLAP 服務(wù)器。在 Intranet 內(nèi)部署分析服務(wù)客戶端時，OWC 的使用效果不錯，因為您可以輕松控制客戶端平臺，并且能夠在 Intranet 內(nèi)安全地打開端口。當存在防火墻，并且您希望盡可能減少對用戶操作系統(tǒng)的影響時，Web 瘦客戶端是一個很好的 Internet 解決方案。對于任何開發(fā)項目，需要理解所開發(fā)產(chǎn)品的使用者的業(yè)務(wù)要求和需要。通過概括要求并權(quán)衡所有選擇，可以發(fā)現(xiàn)能夠滿足客戶要求的正確解決方案。</p>