IM E. Installation and Deployment Guide: Power Xpert Reporting Version 3.0

Transcription

1 IM E Installation and Deployment Guide: Power Xpert Reporting Version 3.0

2

3 InstallationandDeploymentGuide: PowerXpertReportingVersion3.0 IM E

4 InstallationandDeploymentGuide:PowerXpertReportingVersion3.0:IM E Publication date December 2011 Copyright 2011 by Eaton Corporation. All rights reserved. Specifications contained herein are subject to change without notice. Power Xpert and PowerVision are registered trademarks of Eaton Corporation. EATON CORPORATION - CONFIDENTIAL AND PROPRIETARY NOTICE TO PERSONS RECEIVING THIS DOCUMENT AND/OR TECHNICAL INFORMATION THIS DOCUMENT, INCLUDING THE DRAWING AND INFORMATION CONTAINED THEREON, IS CONFIDENTIAL AND IS THE EXCLUSIVE PROPERTY OF EATON CORPORATION, AND IS MERELY ON LOAN AND SUBJECT TO RECALL BY EATON AT ANY TIME. BY TAKING POSSESSION OF THIS DOCUMENT, THE RECIPIENT ACKNOWLEDGES AND AGREES THAT THIS DOCUMENT CANNOT BE USED IN ANY MANNER ADVERSE TO THE INTERESTS OF EATON, AND THAT NO PORTION OF THIS DOCUMENT MAY BE COPIED OR OTHERWISE REPRODUCED WITHOUT THE PRIOR WRITTEN CONSENT OF EATON. IN THE CASE OF CONFLICTING CONTRACTUAL PROVISIONS, THIS NOTICE SHALL GOVERN THE STATUS OF THIS DOCUMENT. DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY The information, recommendations, descriptions and safety notations in this document are based on Eaton Corporation s ( Eaton ) experience and judgment and may not cover all contingencies. If further information is required, an Eaton sales office should be consulted. Sale of the product shown in this literature is subject to the terms and conditions outlined in appropriate Eaton selling policies or other contractual agreement between Eaton and the purchaser. THERE ARE NO UNDER- STANDINGS, AGREEMENTS, WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING WARRANTIES OF FITNESS FOR A PAR- TICULAR PURPOSE OR MERCHANTABILITY, OTHER THAN THOSE SPECIFICALLY SET OUT IN ANY EXISTING CONTRACT BETWEEN THE PARTIES. ANY SUCH CONTRACT STATES THE ENTIRE OBLIGATION OF EATON. THE CONTENTS OF THIS DOCUMENT SHALL NOT BECOME PART OF OR MODIFY ANY CONTRACT BETWEEN THE PARTIES. In no event will Eaton be responsible to the purchaser or user in contract, in tort (including negligence), strict liability or otherwise for any special, indirect, incidental or consequential damage or loss whatsoever, including but not limited to damage or loss of use of equipment, plant or power system, cost of capital, loss of power, additional expenses in the use of existing power facilities, or claims against the purchaser or user by its customers resulting from the use of the information, recommendations and descriptions contained herein.

5 About this Manual... v 1. Installation... 1 Components of a PXR System... 1 Installation Scenarios... 1 Installation Prerequisites... 3 Hardware Prerequisites... 3 Software Prerequisites... 3 Installing SQL Server on Windows Server Maximum Memory Setting for SQL Server... 5 PXR Component Installation Overview of the Deployment Utility... 9 Running the Deployment Utility After Installation... 9 Connection Credentials Required by PXR... 9 Accounts Required to Configure PXR Working With the Deployment Utility SQL Server Settings Database Setup Report Deployment Redeploying/Upgrading Reports Report Server Settings Power Xpert Reporting Web Site Credentials Providing Report Privileges to User Accounts User Access in a Windows Authentication Scheme User Access in a SQL Server Authentication Scheme Customizing the Report Menu Removing Reports From the List Adding Custom Reports to the List Setting up Trust Delegation for PXS and PXR Background Prerequisite Setting Up Trusted Delegation Accessing PXR Via HTTPS Localization... 31

6 iv

7 AboutthisManual This guide provides information concerning: Prerequisites for Power Xpert Reporting (PXR). Scenarios for installing on a single server or multiple servers. PXR installation. PXR database and reports deployment. Configuring access to a mail server. Authentication schemes and required accounts. System verification. This manual is intended for an audience of system administrators and database analysts. It assumes that you are familiar with Microsoft server operating systems, Microsoft SQL Server, Microsoft SQL Server Reporting Services, and IIS administration. While step-by-step instructions are provided for PXR related tasks, you should refer to the instructions for Microsoft Products for details about administration tasks. At the completion of the tasks in this guide, you will be ready to run the Administration Utility to connect PXR to PXS or Foreseer data sources. The tasks in this guide cover setting up necessary accounts for PXR, connecting to SQL Server, deploying reports to SQL Server Reporting Services, configuring access from PXR to a mail server, and configuring access to the SQL Server Reporting Services web site. The companion PXR Administrator's Guide discusses how to connect to data sources within PXS or Foreseer and to create the reporting hierarchy from devices attached to your PXS or Foreseer system. The reporting hierarchy provides the data required to generate PXR reports.

8 vi

9 Chapter 1. Installation This chapter covers: Deployment scenarios with one or multiple servers. Installation prerequisites. Installation of Power Xpert Reporting (PXR) components. ComponentsofaPXRSystem A typical PXR system includes: Power Xpert Software (PXS) 2.1 (or later) or Foreseer system, aggregating data for the reports from various electrical devices. Microsoft SQL Server (Standard or Enterprise edition), warehousing data for the reports. Microsoft SQL Server Reporting Services, which handles the actual report generation. Microsoft IIS, which is the web server for PXR. PXR utilities, which provide administrative interfaces for deploying the reporting database and the reports, as well as for administering the PXR system. InstallationScenarios There are two basic installation/deployment scenarios: Single Server Implementation Multi-Server Implementation In this scenario, PXS (or Foreseer), PXR, Microsoft SQL Server, Microsoft SQL Reporting Services, and IIS are all resident on the same server class machine. This is the simplest scenario to implement as there are almost no account authentication issues to deal with between servers (you must still create an account for scheduled reports). Installation and deployment is straightforward. In this scenario, PXS (or Foreseer) reside on one server and, PXR, Microsoft SQL Server, Reporting Services, and IIS reside on one or more separate servers. This is the preferred method in installations that have an existing SQL Server installation. This scenario requires that you ensure that all required accounts have been created and have the proper privileges for inter-server communication. There are two schemes for creating these accounts: as Windows accounts within Active Directory or as SQL Server accounts. IMPORTANT All of the servers must be within the same domain (for Foreseer, the same domain or Windows Workgroup).

10 Installation Scenarios This applies to a single-server PXS/PXR scenario as well. Microsoft Active Directory and Windows Accounts are required for PXS. Also, the SQL Job agent must be run under an account that has access to the PXS database. Note If you install PXR on the same server as Power Xpert Software (PXS), be aware that PXS may have installed an instance of Microsoft SQL Server Express. Be careful that you select the correct SQL Server instance when deploying PXR as the deployment application will detect instances from SQL Server Express as well as from SQL Server. Figure 1.1. PXR Installation Scenarios 2 Version December

11 Installation Prerequisites InstallationPrerequisites HardwarePrerequisites The following configuration is considered the requirements for installing PXR. PC with a 2.8 GHz dual core processor x 1024, 16-Bit Color Super VGA Monitor. 2 GB of RAM (4 GB if running on the same server as PXS or Foreseer). Add an additional GB of memory if running within a virtual machine. DVD-ROM Drive. SoftwarePrerequisites In either the single server or multi-server installation scenarios, the following software must be installed and properly configured before attempting to install and deploy PXR. If you are connecting to a PXS system, it must be version 2.1 or later. Microsoft Windows Server 2008 SP2 (32 & 64 bit, but only IE 32 bit is supported), Standard and Enterprise; Microsoft Windows Server 2008, R2 (only IE 32 bit is supported), Standard and Enterprise; Microsoft Windows Server 2008, R2 SP1 (only IE 32 bit is supported), Standard and Enterprise; Microsoft Windows Server 2003, SP2 (32 bit); Microsoft Windows Server 2003 R2, SP2 (32 bit). Note the German and Spanish editions are supported for Microsoft Windows Server 2008, R2 (only IE 32 bit is supported), Standard and Enterprise. IIS version 5.0 or later for Server 2003 or XP, IIS 7 for Server This must be installed before SQL Server, otherwise SQL Server Reporting Services and the website won't install with SQL Server. (For Server 2008, IIS is only required to ensure that SQL Server Reporting Services is installed). Microsoft SQL Server 2005 Standard or Enterprise edition (Service Pack 4), 2008 SP2 Standard or Enterprise edition, 2008 R2 Standard, Enterprise, or Small Business edition, 2008 R2 SP1 Standard, Enterprise, or Small Business edition. You must install the SQL Server Reporting Services component as well. If you will be making a connection to a remote instance of SQL Server, ensure that SQL Browser is running. IMPORTANT In SQL Server Reporting Services, do not rename the Power Xpert Software Reports folder. PXR requires this folder name to properly function. PXR supports installation of client components on the Microsoft Windows 7 operating system. Client components include the Deployment Utility, Administration Utility, report source, and documentation. Only 32-bit versions of IE are supported under 64-bit versions of Windows 7. Failure to have these properly installed and configured will result in an incomplete PXR deployment. On Windows Server 2008, you must activate ASP.NET and add the Server Role for IIS. You must also add a number of features to IIS. Version December

12 Installing SQL Server on Windows Server 2008 Failure to add these features will result in SQL Server Reporting Services not being installed. InstallingSQLServeronWindowsServer2008 PXR requires that SQL Server Reporting Services be installed as a component of SQL Server. During SQL Server installation, if ASP.NET and IIS are not enabled (and IIS is not properly configured), then the SQL Server Reporting Services option will not be available. If you're not experienced in SQL Server installation, it's quite easy to miss that as you progress through the installation dialog boxes. The following procedure ensures that ASP.NET and IIS are enabled and that IIS is configured. For more information, refer to Microsoft KB at support.microsoft.com/kb/ While this knowledge base article is specific to installing SQL Server version 2005 on Windows Server 2008, Eaton has encountered problems in installing SQL Server 2008 as well if these steps are not followed. To enable ASP.NET and IIS, you must set the server role to Web Server (IIS). To select the role for the server: 1. Launch the Server Manager by selecting Start > Administrative Tools > Server Manager. 2. Click Roles under Server Manager in the tree. 3. Click Add Roles under the Roles Summary group. 4. If the Before You Begin page is active, click Next. 5. Select the Web Server (IIS) role, then click Install. 6. After completing the role installation wizard, scroll down the Roles page and view the Role Services group. 7. Click Add Services. 8. In the Select Role Services page select the following services: Common HTTP Features Static Content Default Document Directory Browsing Directory Browsing HTTP Errors HTTP Redirection Application Development ASP 4 Version December

13 Maximum Memory Setting for SQL Server Security Windows Authentication Management Tools IIS 6 Management Capability IIS Metabase Compatibility IIS 6 WMI Compatibility IIS 6 Scripting Tools IIS 6 Management Console 9. After selecting all of the required services, click Next and then Install. IMPORTANT Verify that the IIS service is set to start automatically. Also, make sure that the SQL Server Agent service is set to start automatically. You can access the service application through Start > Administrative Tools > Services. The IIS service is called World Wide Web Publishing Service. MaximumMemorySettingforSQLServer When PXR initially populates its data warehouse SQL server memory consumption can reach 100% of the available memory on the server. To prevent this, you should limit the maximum server memory for SQL server to less than 80% of the available system memory. For more information, see msdn.microsoft.com/en-us/library/ms aspx PXRComponentInstallation PXR components are shipped on DVD and will (if you have autorun enabled for your DVD drive) automatically launch the installation application after the DVD is inserted in the drive. The following procedure provides step-by-step installation instructions. To Install PXR: 1. Place the PXR distribution DVD into the drive. If you have autorun enabled for that drive, the installation utility will automatically start. If not, double-click setup.exe in the root folder of the distribution DVD. The following dialog box may appear, and if so, click Run. Version December

14 PXR Component Installation 2. Click Next. 3. In the Power Xpert Reporting Setup dialog box, if the Microsoft.NET Framework 3.5 is not installed, you'll be asked if you wish to install it (the.net Framework 3.5 is required by PXR). You can scroll through the End User License Agreement or print it. If you choose to continue with installation, click Accept. You'll see a status box listing the actions during the.net Framework installation. After the.net Framework installation, you'll see another status box as the Setup application configures the PXR installation components. Note In Server 2008,.NET Framework 3.5 is installed but not enabled. The PXR installation will automatically enable it. 4. In the Eaton Power Xpert Reporting Setup dialog box, click the Next button. 5. Review the PXR EULA and, if you choose to continue installation, select the I accept... box and then click Next. 6 Version December

15 PXR Component Installation 6. In the Choose Setup Type dialog box, choose either Custom or Complete. In most cases, you'll choose Complete; however, if you are installing PXR components on separate servers you'll need to use Custom. The following provides some reasons that you may want to use Custom: The Complete option installs the full PXR website, and you may wish to host the PXR website on another machine. You may wish to install only the client components on a target machine. The client components, which you may also install on a Windows 7 machine, include the Administration Utility, the Deployment Utility, the report source, and the documentation. You may wish to install only the PXR database on a target machine. Figure 1.2. Custom Setup Dialog Box 7. After selecting Complete or Custom (and selecting the components you wish to install), click Next. Version December

16 PXR Component Installation 8. Click Install. 9. When installation completes, click Finish. If Run the Deployment Utility is checked (and the utility is installed), it will launch automatically. 8 Version December

17 Chapter 2. Overviewofthe DeploymentUtility The Deployment Utility provides a single application to manage: SQL Server settings Power Xpert Reporting (PXR) database creation and updates PXR report deployment SQL Server Reporting Services setup (for report subscriptions) PXR web site setup The Deployment Utility must be run after PXR installation so that you can set up the initial SQL Server Settings, create the PXR database, etc. Typically, the steps you'll follow are: 1. Specify the PXR reporting database server and SQL Server Report Server. This is done/verified each time you run the Deployment Utility. 2. Verify that the required SQL Server settings are correct and, if not, use the SQL Server Settings control to enable them. This is a simple task as the Deployment Utility handles most of the work for you. 3. Create the PXR database. 4. Configure the SQL Server Reporting Services settings. While these settings are used by PXR, they are also used for all reports from SQL Server Reporting Services. 5. Configure the PXR web site. In addition, you can also apply updates from Eaton to the PXR database and redeploy the reports (if necessary). Beyond providing a convenient way to perform these tasks, the Deployment Utility serves as a troubleshooting tool, quickly pointing out problems that may have occurred with SQL Server or the SQL Server Reporting Services. RunningtheDeploymentUtilityAfterInstallation You can run the Deployment Utility automatically from the Completed... dialog box at the end of installation. You can also run the Deployment Utility from the Windows Start menu, under Eaton Power Xpert Reporting. Before attempting to deploy reports, take a look at the follow section concerning accounts that you may need to create. ConnectionCredentialsRequiredbyPXR PXR itself needs various accounts to access different components: PXR Report Data Source PXR uses this account to retrieve data from the database. These credentials must be stored

18 Accounts Required to Configure PXR securely with SQL Server so that they can be used for scheduled reports. While this account can use Windows authentication, the best approach is to use SQL Server authentication. By creating this account in SQL Server you can set its password not to expire. Since most organizations require periodic changes in passwords for Windows accounts, setting up a Windows account with a permanent password can be difficult. The password should be permanent because each time the account password is changed you must also come back to the Deployment Utility and change it there. Information for this account is entered into the Deployment Utility on the Power Xpert Report Deployment page. PXR Website Connection to PXR Database PXR requires this account in order for the PXR website to connect to the database. This can be the same account as is used to connect to the report data source. AccountsRequiredtoConfigurePXR Information about this account is entered into the Deployment Utility on the Power Xpert Report Web Site page. IMPORTANT You must have sysadmin privileges in SQL Server and your account must be mapped to the System Administrator role in SQL Server Reporting Services to run the Deployment Utility. If you are running the Deployment Utility from another machine, you must configure your account in SQL Server accordingly (with administrative privileges) and you must enable remote access Before you can use the Deployment Utility, you must first establish the connections to the PXR database and to the SQL Server Report Server. You do that through the Connection Credentials screen, which appears when you run the Deployment Utility. You'll need to set the connection parameters the first time you run the utility; however, after the first time you run the utility it will retain the settings. You'll still see the Connection Credentials screen, but if nothing has changed you can just click the Connect button to launch the utility. 10 Version December

19 Accounts Required to Configure PXR Figure 2.1. Connection Credentials Dialog Box for Deployment Utility To create a connection: 1. Under Power Xpert Reporting Database, in the Server Name field type the name of the server\instance that will house the PXR database. This is the machine running the instance of Microsoft SQL Server that you'll use to manage the reporting database. 2. In the Authentication drop down list, select either Windows Authentication or SQL Server Authentication. Normally, you'll want to use Windows Authentication, otherwise you'll need to maintain the user and password in SQL Server. Note By default, mixed log-ins are not available in SQL Server. You must specifically enable this if you wish to use SQL accounts. This is covered in the section called Configuring SQL Server to Use Mixed Windows/SQL Server Authentication [23]. 3. Under SQL Server Report Server, in the Server Name field type the name of the server running SQL Server Reporting Services or the IP address of that server. Again, the machine name is generally preferable. 4. Beside the Instance field, click the Refresh List button. 5. Select the instance from the list. Version December

20 Working With the Deployment Utility Note If you are installing PXR on the same server that has PXS, you'll discover an instance of SQL Server Express (SQLEXPRESS). Do not use this instance for PXR. 6. Click the Connect button. If the connection information is correct, the Deployment Utility will connect to both SQL Server instances. If not, double check that you have the correct server and instance names and that you have administrative privilege both on the server and for the database instances. IMPORTANT You may see the following error message after clicking the Connect button. If the SQL Server machine is running under Windows Server 2008, SQL Server Reporting Services was not installed because IIS was not correctly configured. See the section called Installing SQL Server on Windows Server 2008 [4] and make sure that SQL Server Reporting Services is installed and that IIS is installed and properly configured. Figure 2.2. WorkingWiththeDeploymentUtility The Deployment Utility has a series of task buttons along the left that, when clicked, provide the various controls for each task in the pane to the right of the window. Figure 2.3. Deployment Utility Task Buttons The icons to the left of each button show the current state of each of the various parts of the system. The goal is to have all green checks (or at least no red X's). 12 Version December

21 SQL Server Settings When initially setting up PXR, they also guide you to what tasks still remain. The following must have a status of Configured before your PXR system will be functional: Power Xpert Reporting Database Setup Power Xpert Report Deployment (this could have a status of Recommended and be fully functional) Power Xpert Reporting Web Site SQL Server Settings The Report Server Settings must be Configured if you will be issuing scheduled reports via . Otherwise, it can be left unconfigured. The following figure shows the various possible states: Figure 2.4. Status Icons SQLServerSettings Your first task when setting up the initial database deployment is to verify the current SQL Server Settings. This icon should be a green check. If not, click the SQL Server Settings button and check the status of CLR Integration, Ad Hoc Remote Query, and SQL Agent. If any of these are not green checks, click the associated Enable or Start button. If this fails, double-check that you have administrative privileges for SQL Server and the server machine itself. Version December

22 SQL Server Settings Figure 2.5. SQL Server Settings - All Green The Deployment Utility will automatically check for the maximum server memory setting for SQL server and compare this value to the available memory on the machine itself. If the SQL server maximum is 80% or more, you are strongly advised to change this before proceeding. When PXR initially populates its data warehouse, SQL Server will consume all memory allocated to it, and if this is 80% or higher performance on the server itself will severely degrade. Note If you are installing SQL Server 2005 on Windows Server 2008, you may see the following dialog box after enabling CLR. If so, you must restart SQL Server. 14 Version December

23 Database Setup Figure 2.6. CLR Integration Alert Box DatabaseSetup After installation and connecting to database instances, you must create the Power Xpert Reporting (PXR) database. To create the PXR database: 1. Click Power Xpert Reporting Database Setup. 2. Under Database Creation, click Create Database. If the database is successfully created, the Database Creation icon will turn to a green check and the status message will be The Power Xpert Reporting database has been created. If the database isn't successfully created, click the View Log File button to review the log. Most failures are due to your user account having insufficient privileges on either the server machine or SQL Server. Note SQLCMD is required to remotely deploy the database. Version December

24 Report Deployment Figure 2.7. Database Setup Settings ReportDeployment After establishing connections to SQL Server and the SQL Server Reporting Services, and then creating the PXR database, you must next deploy the reports to SQL Server Reporting Services. To deploy reports: 1. Click the Power Xpert Report Deployment button. 2. In the SQL Server Report Server URL field, type in the URL to access reporting services (if you change this later, you must click the Refresh button). 3. The Power Xpert Reporting Database Server should have the name (or IP address) of the server. If not, either type it in or select it from the drop-down list. Remember, server names are preferable to IP addresses as they tend to be more stable. 4. Select the security model for the report account: a. If you've created an account for the reports in reporting services, select Credentials stored securely in SQL Server Report Server, then type in the user name and password. This is the preferred method. b. If you're using a Windows account for the reports, select Windows Credentials of user at time report is accessed. As the name implies, these are the current credentials for the user when the report is accessed. 16 Version December

25 Report Deployment IMPORTANT Scheduled reports will not work with this option. Also, you can't test Windows credentials from the Deployment Utility, so ensure that they are entered correctly. 5. If you're using the Credentials stored securely in SQL Server Report Server option, you can click the Test Connection button to verify that the account and server settings are correct. You should see an alert box stating that the test succeeded. If not, double-check the server name and account. 6. Click the Update button to store these settings. The status for Data Source Deployment should turn to a green check. 7. Under Report Deployment, click the Deploy Reports button. The Report Deployment status should change to a green check. Figure 2.8. Report Deployment Settings Version December

26 Redeploying/Upgrading Reports Redeploying/UpgradingReports If, for some reason, your deployed reports have been removed from Reporting Services, you can easily redeploy them. Redeploying reports will overwrite all currently deployed reports. To redeploy reports, click the Deploy Reports button. Note After an upgrade you may see a message on this screen instructing you to deploy new versions of reports. ReportServer Settings To deliver scheduled reports via , you must first specify both the SMTP server for your mail system and a valid sender address. After you've set the required mail configuration information, click the Update button to update these settings in PXR. To configure the mail server settings: 1. Click the Report Server Settings button. 2. Type a valid address in the system in the Sender Address field. 3. Type the server address or IP address for sending mail into the SMTP Server field. The SMTP server address is not verified and is assumed to be correct. 4. Click the Update button to store the new settings. The icon will change to a green check. 18 Version December

27 Power Xpert Reporting Web Site Figure 2.9. SMTP Server Settings PowerXpertReportingWebSite After installation, you must specify the database connection information to allow the PXR web server to connect to the reporting database. To configure the web server: 1. Click the Power Xpert Reporting Web Site button. 2. If you have changed the location of the PXR web site, type the new address into the Power Xpert Reporting Web Site URL and then click Refresh. 3. In the Server Name field, type the server or server\instance name. If the same machine also hosts the PXR reporting database, you can use localhost as the server name. 4. Select the Authentication option: a. If you choose Windows Authentication (the preferred method), you do not need an additional password or user name. b. If you choose SQL Server Authentication, you must also enter values for the User Name and Password. You must create and maintain this account in SQL Server. 5. Click the Test button to verify the settings. An alert box should appear stating that the test was successful. If the test fails, double check your settings Version December

28 Power Xpert Reporting Web Site and ensure that the specified account has administrative privileges on the server machine and in SQL Server. 6. Click the Update button to store the new settings. The status icon should change to a green check Figure PXR Web Server Settings If your organizational network uses a proxy to access the Internet and you will be using the Dashboard feature to connect to Microsoft Bing maps, you must specify the proxy address and, if required, port number. The URL must have a fully formed URL, including the protocol identifier. Refer to your information technology group for the proxy URL. Click Update to save the changes. 20 Version December

29 Chapter 3. Credentials PXR users must be able to authenticate to view reports. All components installed on a single server Components on separate servers If PXS, PXR, SQL Server, Reporting Services, and IIS are all installed on as single server within a Windows domain, you can use Windows authentication. This is easy to configure, just take the default values throughout setup and deployment. If you have two or more servers in your PXR system, then you can either use Windows authentication (perhaps the easiest approach) or a mix of Windows and SQL Server authentication. Should you choose to use the mixed approach, you can enable this through the SQL Server Management Studio under server Properties (right-click on the database instance). This setting is found on the Security page. Note Users or groups must be defined in the Microsoft SQL Server Reporting Services Report Manager: Substitute the appropriate machine name for localhost if required. ProvidingReportPrivilegestoUserAccounts When PXR is installed and deployed, two SQL Server database roles are created in the PXR database: Users must be mapped to one of these roles. Keep the following in mind when setting up user accounts. When SQL Server is installed, you are prompted if you wish your account to be given read/write access to databases. If you pick that option, then your account will also have read/write access to the PXR database. However, other accounts will not. For example, if you wish users in the Windows Administrators group on the SQL server computer to have read/write access to the PXR database, you must explicitly add that role to the Administrators group via SQL Server. If not all PXR users have administrative privilege, the easiest way to grant access to the PXR database is to set up two separate Windows user groups for the PXR users and assign the appropriate PXR database roles, within SQL Server, to these user groups. This has a significant advantage for your users in that they will be automatically authenticated, via their Windows credentials, to the PXR database (and therefore can access reports). User accounts must be mapped to one or both of these database roles to access reports. The following sections describe how to map either Windows accounts and SQL Server logins to these database roles. UserAccessinaWindowsAuthenticationScheme By default, users that are in the Windows Administrators group on the computer where SQL Server is installed will have read/write access to the PXR

30 User Access in a Windows Authentication Scheme database. Your site may be configured so that Domain Administrators have administrative privileges on all machines. If the PXR users are all within these user groups, they will have access. However, if not all PXR users have administrative privilege, the easiest way to grant access to the PXR database is to set up Windows user groups for the PXR users and assign the PXR database roles to these user groups. This has a significant advantage for your users in that they will be automatically authenticated, via their Windows credentials, to the PXR database (and therefore can access reports). If you are using a mixed Windows and SQL Server authentication scheme, which is recommended when you have a multi-server environment, you can create a single SQL Server account and have your users use this to access reports. This is less convenient to users; however, it does have the advantage of being able to easily create a non-expiring password (which may be forbidden by your IT policy for Windows accounts). Also, you don't have the luxury of users groups to work with and therefore must map each individual user account to the appropriate database roles. To assign access in SQL Server 2005: 1. Create a Windows user group that includes the PXR users. If not all PXR administrative users are also members of the Windows Administrative group, create a second Windows user group for these users 2. Launch SQL Server Management Studio from the Microsoft SQL Server 2005 program group in the Start menu. 3. Create a new login (right-click Login and select New > Login). 4. Click the General page, then select Windows Authentication and type domain\group as the Login name, where: domain group is the Windows domain for the group that you created. is the name of the group that you created. 5. Click the User Mapping page, then select PxsReporting under Users mapped to this login. Under Database membership for PxsReporting, select Power Xpert Reporting Read. 6. Click OK. Note If this group should have administrative access to PXR, also select Power Xpert Reporting Write. To assign access in SQL Server 2008: 1. Create a Windows user group that includes the PXR users. If not all PXR administrative users are also members of the Windows Administrative group, create a second Windows user group for these users 2. Launch SQL Server Management Studio from the Microsoft SQL Server 2008 program group in the Start menu. 3. Select the Server type, Server name, and your Authentication method (Windows or SQL Server). Type the user name and password. When you've finished, click Connect. 22 Version December

31 User Access in a SQL Server Authentication Scheme 4. Under the Object Explorer, expand the Security entry. 5. Create a new login (right-click Logins and select New Login). 6. Type the Login name, then select Windows Authentication. 7. Click User Mapping, then select PxsReporting under Users mapped to this login. Under Database membership for PxsReporting, select Power Xpert Reporting Read. 8. Click OK. Note If this group should have administrative access to PXR, also select Power Xpert Reporting Write. UserAccessinaSQLServerAuthenticationScheme SQL Server Authentication is a mode of security in SQL Server where the user IDs and related passwords used to connect to the SQL Server database are managed by SQL Server itself, not Windows. In a multi-server environment, you will likely want to use this approach to create an administrative account that can be used by functions within PXR itself, such as scheduling the automatic generation of reports. For users, the primary advantage of using SQL Server authentication is that you can easily provide a single user ID and password that both everyone can use and that never changes. This is often difficult to do with Windows accounts as organizational IT policies usually require periodic password changes. ConfiguringSQLServertoUseMixedWindows/SQLServerAuthentication To configure SQL Server for mixed authentication in SQL Server 2005 or 2008: 1. Launch SQL Server Management Studio from the Microsoft SQL Server 2005 program group in the Start menu. 2. Right-click the database instance and select Properties. 3. Click Security. 4. Select SQL Server and Windows Authentication mode. 5. Click OK. SettingupSQLServerAccounts Creating Logins in SQL Server Management Studio Launch SQL Server Management Studio from the Microsoft SQL Server 2005 program group in the Start menu. 2. Create a new login (right-click Login and select New > Login). 3. On the General page, select SQL Server Authentication and type user name as the Login name, where: user name is the login name for the account. 4. Type the password into the Password and Confirm Password tabs. Version December

32 User Access in a SQL Server Authentication Scheme 5. Clear the SQL Server Authentication check box. 6. Click the User Mapping page, then select PxsReporting under Users mapped to this login. Under Database membership for: PxsReporting, select Power Xpert Reporting Read. 7. Click OK. Note If this group should have administrative access to PXR, also select Power Xpert Reporting Write. Creating Logins in SQL Server Management Studio Launch SQL Server Management Studio from the Microsoft SQL Server 2008 program group in the Start menu. 2. Select the Server type, Server name, and your Authentication method (Windows or SQL Server). Type the user name and password. When you've finished, click Connect. 3. Under the Object Explorer, expand the Security entry. 4. Create a new login (right-click Logins and select New Login). 5. On the Login-New dialog box, type the Login name. 6. Select SQL Server Authentication and type Type the password into the Password and Confirm Password fields. 7. Choose the password policies you wish to be in effect. 8. For the Default database, select PxsReporting. 9. Click User Mapping, then select PxsReporting under Users mapped to this login. Under Database role membership for: PxsReporting, select Power Xpert Reporting Read. 10. Click OK. Note If this group should have administrative access to PXR, also select Power Xpert Reporting Write. 24 Version December

33 Chapter 4. CustomizingtheReport Menu By default, the PXR Report Viewer provides a link to each of the reports shipped with PXR. However, you can edit the ReportConfig.xml configuration file to either remove specific reports from the list or add custom reports. The file normally resides in the C:\Program Files (x86)\eaton Power Xpert Reporting\WebSite\App_Data folder. You can edit this file with any text editor. It's a good practice to make a backup of the ReportConfig.xml before editing it. RemovingReportsFromtheList The Visible attribute for the Report element controls whether a particular reports is displayed (or not). To remove reports from the Report Viewer list: 1. Open the ReportConfig.xml in your favorite editor. 2. Locate the Report element corresponding to the report that you wish to remove from the list. The names of the reports are listed in the Name attribute. For example, the following is the opening tag for the Report element for the Branch Circuit Monitor report. Report Folder="/Power Xpert Software Reports/Capacity/" Name="Branch Circuit Monitor" HasDateRange="true" HasReportingHierarchy="true" DisplayName="Capacity - Branch Circuit Monitor" Visible="true"> 3. Locate the Visible attribute, and change the value from true to false. 4. Save the file and exit. AddingCustomReportstotheList Note For information detailing how to construct a custom report, contact Eaton customer support. The position of reports in the Report Viewer list is determined by the order of the Report elements in the ReportConfig.xml file. Adding a report to the Report Viewer list is as easy as simply picking a position between existing Report elements and adding a new Report element for your custom report. The following explains the various attributes for the Report element: <Report Folder="/Test" Name="Test Report" HasDateRange="true" HasReportingHierarchy="true" DisplayName="Acme Custom Report" Visible="true"> </Report>

34 Adding Custom Reports to the List Where: Folder HasDateRange defines the folder within SQL Server Reporting Services in which the custom report resides. It's a good practice to keep custom reports in a separate folder from the default reports shipped with PXR. giving this attribute a value of true allows the Report Viewer interface to get the date parameters and pass them to the report. If this attribute is set to true, then the custom report must have the following parameters: NamedDateRange string StartDate datetime EndDate datetime HasReportingHierarchy giving this attribute a value of true requires that the custom report must have the following parameter: ReportingHierarchyId string ShowParameterPrompts giving this attribute a value of true causes the Report Viewer to show the SQL Server Reporting Services parameters interface for users to enter the extra parameters. Users can then click View Report from the SQL Server Reporting Services interface. 26 Version December

35 Chapter 5. SettingupTrustDelegation forpxsandpxr Background A user can encounter security problems when attempting to access PXR via PXS. The difficulty arises because a user's credentials (through the web client) must first be passed to the PXS server and then to the PXR server. However, Windows doesn't allow the credentials to be passed for a second hop unless both the PXS and PXR machines are configured for trusted delegation. Trusted delegation is set through the machine properties in Active Directory. This following details how to set up trusted delegation. Prerequisite This procedure assumes that a Service Principle Name (SPN) was configured for Microsoft SQL Server under the computer object on the machine in which SQL server resides. You can read more about setting SPNs at technet.microsoft.com/nl-nl/library/cc773257(ws.10).aspx. An SPN is necessary for mutual authentication between clients and the service. Also, this assumes that the clients as well as the PXS and PXR servers are in the same domain. SettingUpTrustedDelegation To set up the domain controller: Note It can take several minutes for Active Directory changes to propagate throughout the domain. 1. On the domain controller machine, launch Active Directory. You can launch Active Directory from a Windows command prompt via dsa.mcs. 2. Select the computer object for the computer hosting the PXS web site (IIS). 3. Select the Delegation tab. 4. Select Trust this computer for delegation to specified services only and under that select Use Kerberos only.

36 Setting Up Trusted Delegation Figure 5.1. Setting the Delegation Properties 5. Click Add. 6. In the Add Services dialog box, click the Users or Computers button. 7. Under Enter the object names to select, type the name of the PXR database server. Figure 5.2. Specifying the PXR Database Server 8. Click OK. 9. In the Available services list, choose these two Service Types: MSSQLSVc and http. You can use Ctrl+click to multiselect. 28 Version December

37 Accessing PXR Via HTTPS Figure 5.3. Selecting Service Types 10. Click OK to close the Add Services dialog box. 11. Click Apply and then OK to close the Properties dialog box. Note All web clients that are currently logged in to PXS should log off and then log in again. When they next access PXS, Reports should display properly. AccessingPXRViaHTTPS It is possible to use HTTPS to provide an added measure of security for PXR. These guidelines are provided to assist you with that; however, to be successful you should have an Information Technologies background and an excellent working knowledge of Active Directory and network security. To make HTTPS work: Ensure that all computers, including the system hosting the instance of SQL Server as well as all PXR servers, are on the same domain. Configure PXS to use an SSL certificate. See the Power Xpert Software Administrator's Guide for information. Change the Reporting Notification URL in the PXS configuration to use the HTTPS equivalent. See the Power Xpert Software Administrator's Guide for information. Import the SSL certificate on the system running the instance of SQL Server used by PXR. Run both the SQL Server and SQL Server Agent services through the same user that imported the certificate. Version December

38 30

39 Chapter 6. Localization PXR supports localized date and currency formats in both reports and within the Administration Utility. To change these formats in the Administration Utility, you must change it for the client machine (that is, the machine on which the Administration Utility is run). You can change the format through the Windows Control Panel. For example, in Windows 2008, Server R2 you would select Clock, Language, and Region and then the Change the date, time, or number format. This should launch the Region and Language dialog box with the Format tab selected. From there, you can choose your language preference in the Format list. Note You may need to reboot the client machine after changing the format before you'll see any change. You'll see the date and currency formats you've selected throughout Administration Utility. For example, the Attribute Properties dialog box, date-and-time fields in date range selection controls, etc. However, this won't affect reports displayed in your browser. To change the date and currency format in reports, you'll need to change the Language Preference choice in Internet Explorer. To do that, choose Internet Options from Tools menu, the click the Languages button.

40 32