locked
Install PDS on the same server with SSRS and MOSS RRS feed

  • Question

  • I have to install ProClarity Dashboard Server on the same server with SSRS and MOSS and according to a paragraph from the Dashboard setup guide

     

    - Installing ProClarity Dashboard on the same computer as either Microsoft SQL Server Reporting Services or Microsoft SharePoint Portal Server requires additional configuration.

     

    So does anyone know about the additional configuration?

     

    Thank you in advance.

    Monday, February 25, 2008 10:21 AM

Answers

  • Hello Naruepon,

    The fundamental concern with running these applications on the same server is that SharePoint likes to take control of the default website, where both PAS and the Dashboard install by default.  The order in which you install them will be important, so I would recommed installing SQL first, then Reporting Services, then the ProClarity Analytics Server, then the ProClarity Dashboard Server.  Here are some guidelines for installing with this configuration in mind:

     

    Microsoft Reporting Services 2005

    Installing Reporting Services does not configure the server, but it does install a Reporting Services Configuration utility. This utility is used to configure the Reporting Services IIS settings and database.

    During configuration, two IIS virtual directories are created as follows:

    1. The “Reports” virtual directory. The Report Manager application uses this. 
    2. The “ReportServices” virtual directory. All the Web services provided by Reporting Services are accessed through this URL.
    3. Using the Reporting Services configuration utility, create “ReportServicesPool” for Reporting Services to run in (Figure 3). This application pool uses ASP.NET 2.0 by default.  The default Web site, the default application pool, and the Reporting Services application pool is set to run ASP.NET 2.0.

    Test

    1. Open a browser and go to the Web site http://localhost/reports. Report manager should come up and be working. 
    2. Run visual studio and create a Reporting Services report and deploy the report. 
    3. Run the report manager again and the newly created report should show.

    ProClarity Analytics Server

    During the ProClarity Analytics Server (PAS) installation, the following are created or installed:

    ·         Two virtual directories under the default Web site. The default application pool is used for the virtual directories.

    1.    The first virtual directory by default is named “PAS.” The PAS standard client is accessed via this virtual directory.

    2.    The second virtual directory is by default is named “PASUpLoads.” This virtual directory is used only by the PAS Administration tool.

    ·         An ISAPI filter in the default Web site. This filter facilitates the file publishing feature of the PAS repository. 

    Test

    At this point, the PAS and Reporting Services Report Manager virtual directories should be working. Test the Reporting Services Web site as describe above, and test the PAS Web site by accessing the Web Standard client (example http://localhost/pas ). The default Web site and the PAS virtual directory should be using the default application pool. The ASP.NET version for the default application pool and the Reporting Services application pool should be set to version 2.0.52727.

    ProClarity Dashboard Server

    Installing ProClarity Dashboard Server (PDS) is a two-step process. The first step is to install the dashboard. The second step is to create a new application pool and a new Web site. The second step prepares for the installation of the SharePoint portal.

    Step 1: Install the Dashboard

    Install the dashboard using the default settings and configuration.

    ·         When prompted to either create a new database or use an existing one, create a new database.

    ·         When editing the “web.config” and “data.config” files, use the defaults provided. 

    Step 1 Test

    Browse to http://localhost/dashboard, download Dashboard Studio, and create a dashboard.

    Step 2: Create a new application pool and Web site

    1. Create a new application pool named “PDSPool.”
    2. Create a new Web site named “PDS.” 
    3. Assign a non-default port number (for example, 81) to the Web site.
    4. Point this Web site source directory to the ProClarity Dashboard directory. The default location for the Dashboard directory is C:\Program Files\ProClarity\ProClarity Dashboard Server. 
    5. Select the PDSPool application pool for the Web site.
    6. Enable anonymous access.  This sets up this Web site so that Forms authentication can be used on the dashboard. This is the default authentication mode for the dashboard. To set up Windows integratated authentication, see the ProClarity Dashboard Setup Guide.

    Step 2 Test

    Test the configuration by entering http://localhost:81 into the browser address. Log on to the dashboard, then run Dashboard Studio. At this point, the security and the providers can be configured.

     

    Microsoft SharePoint Services

    During the Microsoft SharePoint Services installation, the following are created or installed:

    ·         Two new application pools

    1.    STSAppPool1

    2.    STSAdminAppPool

    ·         A new virtual server: SharePoint Central Administration

    ·         An ISAPI filter (stsfltr.dll) to the default Web site. This filter redirects requests to the SharePoint ASP.NET handler.

    All requests directed to the default Web site are directed to SharePoint. This breaks the previously working Web sites of Reporting Services, ProClarity Dashboard Server, and ProClarity Analytics Server. Both the Microsoft SharePoint Services filter and the ProClarity Analytics Server ISAPI filters are running on the default Web site.

    All of the HTTP requests are routed through the SharePoint filter and are either sent to the ASP.NET SharePoint Web page or to extended Web site pages. The extended pages may be Web Parts, documents in the SharePoint repository, or other pages that SharePoint manages.

    (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_SP2003_ta/html/ODC_WSSArchitecture.asp)

     

    Because of this, a virtual directory under a SharePoint Web site will never see any of its requests. Requests bound for PAS, PDS, or Reporting Services will not pass down to their virtual directories. However, SharePoint Services has a command line administration utility (STSADM.EXE) that can be used to allow specific URLs to pass through the filter and then be routed to a virtual directory. The utility does a lot more, but this particular feature allows SharePoint, PAS, and Reporting Services to coexist in the default Web site. The utility is located as follows:

    c:\program files\common files\microsoft shared\web server extensions\60\bin

    The following command tells the SharePoint filter to let requests bound for http://localhost/pas to pass through to the virtual directory.

    STSADM.EXE -o addpath -url http://localhost/pas -type exclusion

    STSADM.EXE -o addpath -url http://localhost/pasuploads -type exclusion

    ProClarity Dashboard Server must also have a pass-through set up. The following command lets requests bound for the dashboard to pass through.

    STSADM.EXE -o addpath -url http://localhost/dashboard -type exclusion

    SharePoint Services and Reporting Services can also coexist if the SharePoint ISAPI filter knows about Reporting Services virtual directories. Run the following command to allow the requests for Reporting Services to pass through the SharePoint ISAPI filter:

    STSADM.EXE -o addpath -url http://localhost/reports -type exclusion

    STSADM.EXE -o addpath -url http://localhost/reportservices -type exclusion

    Notice that the instance name is part of the URL.

    Test

    To test the installation, browse to the default Web site (example http://localhost).

    Also, use the STSADM.EXE utility and run each of the above commands to test that requests bound for PAS, PDS, and Reporting Services are passing through their respective virtual directories.

    This last section is for installing with SPS, but should be similar with MOSS, just exclude the Reporting Services, PAS, and PDS virtual directories.

    Hope this helps,

     

    Bob

     

     

     

     

     

    Monday, February 25, 2008 5:57 PM

All replies

  • Hello Naruepon,

    The fundamental concern with running these applications on the same server is that SharePoint likes to take control of the default website, where both PAS and the Dashboard install by default.  The order in which you install them will be important, so I would recommed installing SQL first, then Reporting Services, then the ProClarity Analytics Server, then the ProClarity Dashboard Server.  Here are some guidelines for installing with this configuration in mind:

     

    Microsoft Reporting Services 2005

    Installing Reporting Services does not configure the server, but it does install a Reporting Services Configuration utility. This utility is used to configure the Reporting Services IIS settings and database.

    During configuration, two IIS virtual directories are created as follows:

    1. The “Reports” virtual directory. The Report Manager application uses this. 
    2. The “ReportServices” virtual directory. All the Web services provided by Reporting Services are accessed through this URL.
    3. Using the Reporting Services configuration utility, create “ReportServicesPool” for Reporting Services to run in (Figure 3). This application pool uses ASP.NET 2.0 by default.  The default Web site, the default application pool, and the Reporting Services application pool is set to run ASP.NET 2.0.

    Test

    1. Open a browser and go to the Web site http://localhost/reports. Report manager should come up and be working. 
    2. Run visual studio and create a Reporting Services report and deploy the report. 
    3. Run the report manager again and the newly created report should show.

    ProClarity Analytics Server

    During the ProClarity Analytics Server (PAS) installation, the following are created or installed:

    ·         Two virtual directories under the default Web site. The default application pool is used for the virtual directories.

    1.    The first virtual directory by default is named “PAS.” The PAS standard client is accessed via this virtual directory.

    2.    The second virtual directory is by default is named “PASUpLoads.” This virtual directory is used only by the PAS Administration tool.

    ·         An ISAPI filter in the default Web site. This filter facilitates the file publishing feature of the PAS repository. 

    Test

    At this point, the PAS and Reporting Services Report Manager virtual directories should be working. Test the Reporting Services Web site as describe above, and test the PAS Web site by accessing the Web Standard client (example http://localhost/pas ). The default Web site and the PAS virtual directory should be using the default application pool. The ASP.NET version for the default application pool and the Reporting Services application pool should be set to version 2.0.52727.

    ProClarity Dashboard Server

    Installing ProClarity Dashboard Server (PDS) is a two-step process. The first step is to install the dashboard. The second step is to create a new application pool and a new Web site. The second step prepares for the installation of the SharePoint portal.

    Step 1: Install the Dashboard

    Install the dashboard using the default settings and configuration.

    ·         When prompted to either create a new database or use an existing one, create a new database.

    ·         When editing the “web.config” and “data.config” files, use the defaults provided. 

    Step 1 Test

    Browse to http://localhost/dashboard, download Dashboard Studio, and create a dashboard.

    Step 2: Create a new application pool and Web site

    1. Create a new application pool named “PDSPool.”
    2. Create a new Web site named “PDS.” 
    3. Assign a non-default port number (for example, 81) to the Web site.
    4. Point this Web site source directory to the ProClarity Dashboard directory. The default location for the Dashboard directory is C:\Program Files\ProClarity\ProClarity Dashboard Server. 
    5. Select the PDSPool application pool for the Web site.
    6. Enable anonymous access.  This sets up this Web site so that Forms authentication can be used on the dashboard. This is the default authentication mode for the dashboard. To set up Windows integratated authentication, see the ProClarity Dashboard Setup Guide.

    Step 2 Test

    Test the configuration by entering http://localhost:81 into the browser address. Log on to the dashboard, then run Dashboard Studio. At this point, the security and the providers can be configured.

     

    Microsoft SharePoint Services

    During the Microsoft SharePoint Services installation, the following are created or installed:

    ·         Two new application pools

    1.    STSAppPool1

    2.    STSAdminAppPool

    ·         A new virtual server: SharePoint Central Administration

    ·         An ISAPI filter (stsfltr.dll) to the default Web site. This filter redirects requests to the SharePoint ASP.NET handler.

    All requests directed to the default Web site are directed to SharePoint. This breaks the previously working Web sites of Reporting Services, ProClarity Dashboard Server, and ProClarity Analytics Server. Both the Microsoft SharePoint Services filter and the ProClarity Analytics Server ISAPI filters are running on the default Web site.

    All of the HTTP requests are routed through the SharePoint filter and are either sent to the ASP.NET SharePoint Web page or to extended Web site pages. The extended pages may be Web Parts, documents in the SharePoint repository, or other pages that SharePoint manages.

    (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_SP2003_ta/html/ODC_WSSArchitecture.asp)

     

    Because of this, a virtual directory under a SharePoint Web site will never see any of its requests. Requests bound for PAS, PDS, or Reporting Services will not pass down to their virtual directories. However, SharePoint Services has a command line administration utility (STSADM.EXE) that can be used to allow specific URLs to pass through the filter and then be routed to a virtual directory. The utility does a lot more, but this particular feature allows SharePoint, PAS, and Reporting Services to coexist in the default Web site. The utility is located as follows:

    c:\program files\common files\microsoft shared\web server extensions\60\bin

    The following command tells the SharePoint filter to let requests bound for http://localhost/pas to pass through to the virtual directory.

    STSADM.EXE -o addpath -url http://localhost/pas -type exclusion

    STSADM.EXE -o addpath -url http://localhost/pasuploads -type exclusion

    ProClarity Dashboard Server must also have a pass-through set up. The following command lets requests bound for the dashboard to pass through.

    STSADM.EXE -o addpath -url http://localhost/dashboard -type exclusion

    SharePoint Services and Reporting Services can also coexist if the SharePoint ISAPI filter knows about Reporting Services virtual directories. Run the following command to allow the requests for Reporting Services to pass through the SharePoint ISAPI filter:

    STSADM.EXE -o addpath -url http://localhost/reports -type exclusion

    STSADM.EXE -o addpath -url http://localhost/reportservices -type exclusion

    Notice that the instance name is part of the URL.

    Test

    To test the installation, browse to the default Web site (example http://localhost).

    Also, use the STSADM.EXE utility and run each of the above commands to test that requests bound for PAS, PDS, and Reporting Services are passing through their respective virtual directories.

    This last section is for installing with SPS, but should be similar with MOSS, just exclude the Reporting Services, PAS, and PDS virtual directories.

    Hope this helps,

     

    Bob

     

     

     

     

     

    Monday, February 25, 2008 5:57 PM
  • Thank you for your guideline Bob, this is very helpful for me.

     

    Naruepon

    Tuesday, February 26, 2008 8:06 AM