Read more about Data Workbench’s End-of-life announcement.
Steps to map the Report Portal to a virtual directory (IIS 6.0).
Mapping the Report Portal to a virtual directory on IIS 6.0 involves three separate tasks:
You must complete all three tasks.
On the machine where Report Portal is installed, open *PortalName*\ReportPortalSetup.xml in a text editor such as Notepad.
Use the editor’s find-and-replace feature to globally replace (Replace All) the string “VSVirtualPortalName” with the name of your portal. For example, if you want to use “VisualReportPortal” as the name of your Report Portal, you would search for “VSVirtualPortalName” and replace it with “VisualReportPortal.”
Locate the following element in this file:
<IIsWebVirtualDir Location= "/LM/W3SVC/1/Root/PortalName/Output" AccessFlags="AccessRead | AccessScript” AppFriendlyName="Output" . . . >
Set this element’s Path attribute to the physical location of the directory in which Report Server saves the output for your report sets.
The output folder can be located anywhere, can be named anything, and contains a subfolder for each report set.
This must be the same directory that you specify in the Output Root parameter in the Report.cfg file for a report set. For more information, see Configuring Report.cfg Files.
The following code sample shows how you would set the Path attribute if your reports were saved to E:\VSReport\ReportOutput:
< . . . AppIsolated="2" AppRoot="/LM/W3SVC/1/Root/PortalName/OutputFolder" DirBrowseFlags="DirBrowseShowDate | DirBrowseShowTime |... Path="E:\VSReport\ReportOutput"
It is critical that the Path attribute is set properly.
If you changed the default Path of the Output element, move the profiles.xml file from the \PortalName\PortalFiles\Output folder to the output directory that you specified in Step 4. In the example above, you would move profiles.xml to E:\VSReport\ReportOutput.
Verify that the Path attributes for all of the other IIsWebVirtualDir elements are mapped to the correct location by searching for all instances of C:\Inetpub\wwwroot and replacing each with the correct path.
Save the file. If you want to preserve the original file, you can save the configuration file using a new name.
On the machine where Report Portal is installed, start the IIS Manager using Start > Administrative Tools > Internet Information Systems (IIS) Manager.
Select (local computer) > Web Sites > Default Web Site.
Right-click Default Web Site and select New > Virtual Directory (from file).
Select the ReportPortalSetup.xml file and click Read File.
Verify that six virtual directories are listed for your Report Portal as shown in the following example.
If you do not see six virtual directories or if you receive an error message, click Cancel and examine the configuration file for errors.
Select the first virtual directory in the list (the one that is the parent of the other five) and click OK. IIS imports the mappings and add the virtual directories to the Default Web Site.
Make sure that the resulting directory structure has one parent folder (with the same name as your portal) and five sub-directories as shown in the following example.
Click each virtual directory to ensure that IIS can locate the physical directory it represents. If IIS displays an error, right-click the virtual directory name and verify that the Local Path field points to the correct physical directory.
To use Report Portal, ASPs must be enabled on IIS. (By default, ASPs are disabled when IIS 6.0 is installed.) Use the following procedure to verify that ASPs are enabled on your IIS.
In the IIS Manager window, select (local computer) > Web Service Extensions.
Verify that the Active Server Pages extension is set to Allowed.
If their Status is Prohibited, select Active Server Pages and click Allow.
Close IIS Manager.