Mapping Report Portal to a Virtual Directory (IIS 7.0 or higher)

IMPORTANT

Read more about Data Workbench’s End-of-life announcement.

Steps to map the Report Portal to a virtual directory (IIS 7.0 or higher).

Currently, most Managed Service clients have servers with the Windows Server 2008 operating system and the IIS 7.0 or higher web server.

Prerequisites

Make sure that ASP and ASP.Net components are installed for IIS 7.0 or higher.
Make sure the IIS Web user has Modify access to the E:\Portal\data\users.mdb file. You can change that by right-clicking on the users.mdb file and under Properties, go to the Security tab. If you do not see the IIS Web User listed or do not have the ability to add the IIS Web User to the list, simply give the Users group the Modify access.
Make sure whatever user account is being used to run the Application Pools also has Modify access to the E:\Portal\data\users.mdb and the C:\Windows\Temp\ folders.

On the machine where Report Portal is installed, start the IIS Manager:

Start > Administrative Tools > Internet Information Services (IIS) Manager.
Select Local Machine > Sites > Default Web Site.
Right-click Default Web Site and select Add Virtual Directory.
For an alias, enter Portal.
For the physical path, enter E:\Portal\PortalASP.
Click OK.

The virtual directory that you created appears under the Default Web Site.

Add the following virtual directories under the virtual directory that you just created.

Create this alias…	For this physical resource
Core	E:\Portal\PortalFiles\Core
CSS	E:\Portal\PortalFiles\CSS
Images	E:\Portal\PortalFiles\Images
Output	Physical location of the directory in which Report Server saves the output for your report sets. The output folder can be located anywhere and can be named anything. It contains a subfolder for each report set. You can delete the E:\Portal\PortalFiles\Output, but move the profiles.xml to the physical location of the Output file.

When finished, verify that IIS displays four new virtual directories. Make sure that the directory structure has one parent folder (with the same name as your portal) and four subfolders.
Click on Application Pools, then DefaultAppPool (assuming that’s the one you set up with your portal).
Click on Advanced Settings and select True for the Enable 32-Bit Applications.
To get the Portal to work, you need to convert it to an application. After setting up the virtual directories, right click on the Portal virtual directory and select Convert to Application.

You can download the Portal from Softdocs under Softdocs > Report Portal. You can simply download the ReportPortal-Release-1-0-0-7.zip.
You no longer need the ReportPortalSetup.xml, so it can be deleted.
For the sake of standardization, place the contents of this zip file into E:\Portal.
To determine the SMTP server For managed services clients, you can go look here.
Put in a request with NetOps to change the domain name entry in IIS for the report server to something friendlier - for example, reports.clientname.insight.omniture.com, so that your overall portal URL is https://reports.clientname.insight.omniture.com/Portal. Configure your email.asa file once this change has been put into place.