OLAP Reporting Application

S

swathi

Hi group,

Iam really new to this topic and i have already posted a
message that i need to build an OLAP Reporting Application, and i got
a reply saying that there are already some posts in the group about
that topic thanks Alvin, but before that only i read an article about
"Build an OLAP Reporting App in ASP.NET Using SQL Server 2000 Analysis
Services and Office XP" and i got lots and lots of doubts about that
article, if anyone could clarify my doubts it would be great and the
help would be highly appreciated.

I need to do this in just 2 days so please friends help me!!!!!

First thing was that iam using my school system which has Windows NT,
SQL Server 2000 and visual studio .NET 2003 and i have installed OWC
Version 10 on that machine. I read somewhere that OWC 10 is for
Windows XP and not for Windows NT, if thats the case what should i do
then the application will not run on NT???

Second thing is that if it works....
then i have some doubts in that article.
*************
I did not understand the below part

Configuring the OLAP Source for HTTP Access

Before we can begin building the Web-based OLAP reporting application,
we must configure the Analysis Services data source for access by
Microsoft Internet Information Services (IIS). The IIS Web site must
be set up on the same server where Analysis Services is installed, and
it must contain a single file called msolap.asp. This file provides
the bridge between requests coming over an HTTP port and the Analysis
Services data source. The file is located under the path \Program Files
\Microsoft Analysis Services\bin. We recommend that you configure the
data source for access over a secure connection (HTTPS) using a Secure
Sockets Layer (SSL) certificate. This step requires that you purchase
an SSL certificate for the Analysis Services server. You can also use
a nonsecure (HTTP) connection to access the data source, but we don't
recommend this approach.

Once IIS is installed on the Analysis Services server, you can
configure a new Web site for HTTPS access. First create a new Web site
directory outside of the default Web root directory (\Inetpub\wwwroot
\). We recommend that you stop the default Web site for security
purposes. In addition, you should close port 80 on your firewall and
open port 443 for HTTPS access once the SSL certificate is installed.

Copy the msolap.asp file from the \Program Files\Microsoft Analysis
Services\bin directory into the new Web site directory, and use IIS
Manager to configure the new Web site directory as a Web Application
and add a Host Header Name for the Web site (for example,
olap.mycompany.com).

Purchase and install the SSL certificate on the server. The Web site
must already be accessible over port 80 during the purchase
verification process. Once the certificate is installed, you can close
port 80 and open port 443 on your firewall. Use IIS Manager to set
Directory Security so that Anonymous Access is disabled and Basic
Authentication is enabled. Finally, reset IIS to apply the changes.

Once HTTPS access has been set up, you must update the OLE DB
connection string that points to the OLAP data source. The format of
the connection string is as follows:

Provider=MSOLAP;user id=Domain\Username;password=Password;Data
Source=https://ServerName;Initial Catalog=OLAPDataSourceName

For more details, consult the Knowledge Base article 279489, "How to
Connect to Analysis Server 2000 By Using HTTP Connection".



OLAP Security Access

Security credentials are essential once your OLAP data source becomes
accessible over HTTPS because your data source is now potentially
available to anyone who can browse your Web site. For example, a
remote user can open Excel and connect a PivotTable to your OLAP data
source simply by providing the URL for the Analysis Server and the
name of the Initial Catalog.

Analysis Services implements cube security roles based on Windows NT®
user accounts. Basically, you create one or more local Windows NT user
accounts on the server and assign them to a SQL Server database role.
You then assign the database role to a cube role and assign it to the
specific cube. The cube role essentially inherits the Windows NT user
ID and password credentials. You can then add the user ID and password
credentials to the OLAP data source connection string.

Note that one OLAP data source may contain multiple cubes. You can
connect to a specific cube by setting the OWC PivotTable control's
<DataMember> XML tag value to a valid cube name (explained in the next
section). This cube must be assigned to a role that corresponds to the
credentials in the OLAP data source connection string.
**************************
I did not understand this part how to do this....

and when i saw the code for the application

then i found DHTML behavior file called webservice.htc whats this do
we need to code that file or it is taken from somewhere or is it
generated by the application???

Please Friends help me out with this topic, iam really new to this
topic and iam not getting anything into my mind, if any one can
explain the step by step process about how to set up a connection, how
to access a cube data, drill up and drill down operations, that would
be great

Thank You in advance
KSR
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top