แก้ไข

แชร์ผ่าน

Configure a URL (Report Server Configuration Manager)

  • บทความ

Before you can use the web portal or the Report Server Web service, you must configure at least one URL for each application. Configuring the URLs is mandatory if you installed Reporting Services in "files-only" mode (that is, by selecting the Install but do not configure the server option on the Report Server Installation Options page in the Installation Wizard). If you installed Reporting Services in the default configuration, URLs are already configured for each application.

Use the Reporting Services Configuration tool to configure the URLs. All parts of the URL are defined in this tool. Unlike in earlier releases, Internet Information Services (IIS) Web sites no longer provide access to Reporting Services applications in SQL Server 2008 (10.0.x) and later versions.

Reporting Services provides default values that work well in most deployment scenarios, including side-by-side deployments with other Web services and applications. Default URLs incorporate instance names, minimizing the risk of URL conflicts if you run multiple report server instances on the same computer.

This article provides instructions for the following tasks:

  • Create a URL for the Report Server Web service.

  • Create a URL for the web portal.

  • Set advanced URL properties to define more URLs.

For more information about how URLs are stored and maintained or about interoperability issues, see About URL reservations and registration (Report Server Configuration Manager) and Install Reporting and Internet Information Services side-by-side. To review examples of URLs often used in a Reporting Services installation, see Examples of URLs in this article.

Prerequisites

Before you create or modify a URL, remember the following points:

  • You must be a member of the local Administrators group on the report server computer.

  • If IIS is installed on the same computer, check the names of virtual directories on any Web site that uses port 80. If you see any virtual directories that use the default Reporting Services virtual directory names ("Reports" and "ReportServer"), choose different virtual directory names for the Reporting Services URLs that you configure.

  • You must use the Reporting Services Configuration tool to configure the URL. Don't use a system utility. Never modify URL reservations in the URLReservations section of the RSReportServer.config file directly. You must use the Reporting Services Configuration tool to update both the underlying URL reservation that's stored internally and synchronize the URL settings stored in the RSReportServer.config file.

  • Choose a time that has low report activity. Each time the URL reservation changes, you can expect that the application domains for Report Server Web service and the web portal might be recycled.

  • For an overview of URL construction and usage in Reporting Services, see Configure report server URLs (Report Server Configuration Manager).

Configure a URL for the report server web service

  1. Start the Reporting Services Configuration tool and connect to a local report server instance.

  2. Select Web Service URL.

  3. Specify the virtual directory. The virtual directory name identifies which application receives the request. Because multiple applications can share an IP address and port, the virtual directory name specifies which application receives the request.

    This value must be unique to ensure that the request reaches its intended destination. This value is required. It's case-insensitive. There's a one-to-one correspondence between a virtual directory name and an instance of a Reporting Services application. If you create multiple URLs to the same application instance, you must use the same virtual directory name in all of the URLs you define for this application instance.

    For the Report Server Web service, the default virtual directory name is ReportServer.

  4. Specify the IP address that uniquely identifies the report server computer on the network. If you want to specify a host header or define more URLs for the same application instance, you must select Advanced. For instructions on how to set advanced properties on the URL, see the instructions later in this article. Otherwise, use the Web Service URL page to select from the following values:

    • All Assigned specifies that any of the IP addresses that are assigned to the computer can be used in a URL that points to a report server application. This value also encompasses friendly host names, such as computer names, that can be resolved by a domain name server to an IP address that's assigned to the computer. This value is the default for a Reporting Services URL.

    • All Unassigned specifies that the report server receives any request that another application doesn't handle. You should avoid this option. If you select this option, it becomes possible for another application that has a stronger URL reservation to intercept requests intended for the report server.

    • 127.0.0.1 is the IPv4 address used to access to localhost. It supports local administration on the report server computer. If you select only this value, only users who are logged on locally to the report server computer have access to the application.

    • ::1 is the loopback address in IPv6 format.

    • Specific IP addresses also appear in this list. IP addresses can be in IPv4 and IPv6 formats. Nnn.nnn.nnn.nnn is the 32-bit IPv4 address of a network adapter card on your computer. IPv6 addresses are 128-bit, with eight 4-byte fields separated by colons: \<prefix>:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn.

    If you have multiple cards or if your network supports both IPv4 and IPv6 addresses, you see multiple IP addresses. If you select only one IP address, it limits application access to the IP address and any host name that a domain name server maps to that address. You can't use localhost to access a report server, and you can't use the IP addresses of other network adapter cards that are installed on the report server computer. Typically, if you select this value, it's because you're configuring multiple URL reservations that also specify explicit IP addresses or host names. For example, you might have one for a network adapter card used for intranet connections and a second one used for extranet connections.

  5. Specify the port. Port 80 is the default because it can be shared with other applications. If you want to use a custom port number, remember that you have to always specify it in the URL used to access the report server. You can use the following techniques to find an available port:

    • From a command prompt, enter the following command to return a list of TCP ports that are being used: netstat -anp tcp

    • Review the Microsoft Support article, Information about TCP/IP port assignments, to read about TCP port assignments and the differences between Well Known Ports (0 through 1023), Registered Ports (1024 through 49151), and Dynamic or Private Ports (49152 through 65535).

    • If you're using Windows Firewall, you must open the port. For instructions, see Configure a firewall for report server access.

  6. Verify that IIS (if you installed it) doesn't have virtual directory with the same name you plan to use.

  7. If you installed a TLS/SSL certificate, you can select it now to bind the URL to the TLS/SSL certificate that's installed on your computer.

  8. Optionally, if you select a TLS/SSL certificate, you can specify a custom port. The default is 443, but you can use any port that is available.

  9. Select Apply to create the URL.

  10. Test the URL by selecting the link in the URLs section of page. The report server database must be created and configured before you can test the URL. For instructions, see Create a Native mode report server database (Report Server Configuration Manager).

Note

If you have existing TLS Bindings and URL Reservations and you want to change the TLS Binding, such as a different certificate or hostheader, then you should complete the following steps in order, using Reporting Services Configuration Manager:

  1. First remove all URL Reservations.
  2. Then remove all TLS Bindings.
  3. Then recreate the URLs and the TLS bindings.

Microsoft Windows supports one binding for each IP address to Port combination. If you configure a report server to use a specific hostheader value and the certificate on the Port to IP address combination is also issued to a different hostheader value, you will see in your browser, a warning indicating the certificate does not match the URL that is being used.

To correct the issue, delete all bindings and then create new bindings with unique settings or configure the Reporting Services URL registrations with wildcards.

Create a URL reservation for the web portal

  1. Start the Reporting Services Configuration tool and connect to the report server instance.

  2. Select Web Portal URL.

  3. Specify the virtual directory. The web portal listens on the same IP address and port as the Report Server Web service. If you configured the web portal to point to a different Report Server Web service, you must modify the web portal URL settings in the RSReportServer.config file.

  4. If you installed a TLS/SSL certificate, you can select it to require that all requests to the web portal are routed over HTTPS.

    Optionally, if you select a TLS/SSL certificate, you can specify a custom port. The default is 443 but you can use any port that is available.

  5. Select Apply to create the URL.

  6. Test the URL by selecting the link in the URLs section of page.

Set advanced properties to specify other URLs

You can reserve multiple URLs for the Report Server Web service or the web portal by specifying different ports or host names. You can specify either an IP address or a host header name that a domain name server can resolve to an IP address assigned to the computer. By creating multiple URLs, you can set up different access paths to the same report server instance. For example, to enable intranet and extranet access to a report server, you might use the default URL for access across the intranet, and another fully qualified host name for extranet access:

  • https://myserver01/reportserver

  • https://www.adventure-works.com/reportserver

You can't set multiple virtual directory names for the same application instance. Each Reporting Services application instance is mapped to a single virtual directory name. If you have multiple instances of Reporting Services on the same computer, the virtual directory name for an application should include the instance name to ensure that each request reaches its intended target.

Host Header If you already have a host header defined on a domain name server that resolves to your computer, you can specify that host header in a URL that you configure for report server access.

A host header is a unique name that allows multiple Web sites to share a single IP address and port. Host header names are easier to remember and enter than IP address and port numbers. An example of a host header name might be www.adventure-works.com.

SSL Port Specifies the port for TLS/SSL connections. The default port for TLS is 443.

SSL Certificate Specifies the certificate name of a TLS/SSL certificate that you installed on this computer. If the certificate maps to a wildcard, you can use it for a report server connection.

Specifies the fully qualified computer name for which the certificate is registered. The name that you specify must be identical to the name for which the certificate is registered.

You must have a certificate installed to use this option. You must also modify the UrlRoot configuration setting in the RSReportServer.config file so that it specifies the fully qualified name of the computer for which the certificate is registered. For more information, see Configure TLS connections on a Native mode report server.

Set advanced properties on a URL

  1. On either the Web Service URL or Web Portal URL page, select Advanced.

  2. Select Add.

  3. Select IP Address or Host Header Name. If you specify a host header, be sure to specify a name that the DNS service can resolve. If you're specifying publicly available domain name, include the whole URL, including https://www.

  4. Specify the port. If you specify a custom port, the URL to the application must always include the port number.

  5. Select OK.

  6. Test the URL by opening a browser window and entering the URL.

URLs for multiple report server instances on the same computer

If you're reserving URLs for multiple instances of Reporting Services, you should follow naming conventions so that you can avoid naming conflicts. For more information, see URL reservations for multi-instance report server deployments (Report Server Configuration Manager).

Examples of URL configurations

The following list shows some examples of what a report server URL might resemble:

  • https://localhost/reportserver

  • https://localhost/reportserver_SQLEXPRESS

  • https://sales01/reportserver

  • https://sales01:8080/reportserver

  • https://sales.adventure-works.com/reportserver

  • https://www.adventure-works.com:8080/reportserver01

URLs that you use to access the web portal share a similar format and are typically created under the same Web site that hosts the report server. The only difference is the virtual directory name (in this case, it's reports, but you can configure it to use whatever name that you want):

  • https://localhost/reports

  • https://localhost/reports_SQLEXPRESS

  • https://sales01/reports

  • https://sales01:8080/reports

  • https://sales.adventure-works.com/reports

  • https://www.adventure-works.com:8080/reports

Related content