Before you install the Reporting Services extensions [AX 2012]

Imparted from Here

Before you install the Microsoft SQL Server Reporting Services extensions, you must complete the following procedures.

Verify that you have the required permissions to install the Reporting Services extensions

---

To install the Reporting Services extensions, you must have the required permissions. For more information, see Verify that you have the required permissions for installation.

Install prerequisites

---

On the computer where Reporting Services is installed, or where you plan to install Reporting Services, run the prerequisite validation utility to verify that system requirements have been met. For information about how to run the prerequisite validation utility, see Check prerequisites.

For more information about the hardware and software requirements for Microsoft Dynamics AX, see the system requirements.

Configure the Reporting Services instance by using the Reporting Services Configuration Manager tool

---

Use the following procedure to configure the Reporting Services instance.

Note

If you installed the Reporting Services instance in its default configuration, Reporting Services is already configured for you. We recommend that you complete this procedure to verify that the options are configured correctly.

1. Open Reporting Services Configuration Manager (Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > Reporting Services Configuration Manager).
2. Connect to your Reporting Services instance.
3. Configure the options that are described in the following table. For detailed information about each option, see the SQL Server documentation.

Click this option…	To do this…
[ServerName]\[InstanceName]	Verify that the Reporting Services instance is running. If it is not running, click Start.
Service Account	The action you should take depends on the configuration mode you selected when installing the Reporting Services instance. · If you selected the Install the native mode default configuration option, no action is required. The service account is set to the account you specified when installing the Reporting Services instance. · If you selected the Install, but do not configure the report server option, select the built-in account, Network Service, as the service account. Note When you install the Reporting Services extensions, the Business Connector proxy account will automatically be assigned as the service account for the Reporting Services instance.
Web Service URL	Create a virtual directory for the Reporting Services web service. By default, the virtual directory is named ReportServer and the URL is http://[SSRSServerName]:80/ReportServer.
Database	Create a database for the Reporting Services instance. By default, the database is named ReportServer.
Report Manager URL	Create a virtual directory for Report Manager. Report Manager is the website that reports are published to. By default, the virtual directory is named Reports and the URL is http://[SSRSServerName]:80/Reports.
E-mail Settings	This option is not required. For more information, see the SQL Server documentation.
Execution Account	Take no action. Note When you install the Reporting Services extensions, the Business Connector proxy account will automatically be assigned as the execution account for the Reporting Services instance.
Encryption Keys	This option is not required. For more information, see the SQL Server documentation.
Scale-out Deployment	This option is not required. For more information, see the SQL Server documentation.

4. Click Exit to close Reporting Services Configuration Manager.

Configure the Reporting Services instance for local administration

---

To administer an instance of the report server locally, you must complete additional configuration steps when you deploy Reporting Services on Windows Server 2008. Windows Server 2008 limits the overuse of elevated permissions by removing administrator permissions when you access applications. If you are a member of the local Administrators group, you run most applications as if you are using the Standard User account because the operating system removes permissions.

Although this practice improves the overall security of your system, it prevents you from using the predefined, built-in role assignments that Reporting Services creates for local administrators. However, by completing additional configuration steps, you can manage the report server's content and operations by using standard user permissions. For instructions, see How to: Configure a Report Server for Local Administration on Windows Vista and Windows Server 2008 on TechNet.

After you have configured the Reporting Services instance for local administration, verify that you can access the sites that are listed in the following table.

Web site	Default URL
Reporting Services web service	http://[SSRSServerName]:80/ReportServer
Report Manager	http://[SSRSServerName]:80/Reports