EVault Software. Web CentralControl 7.2. Administrator Guide

Transcription

1 EVault Software Web CentralControl 7.2 Administrator Guide

2 Revision: This manual has been updated for Version 7.2. Software Version: 7.2 (August 2013) 2013 EVault Inc. EVault, A Seagate Company, makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, EVault reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of EVault to notify any person of such revision of changes. All companies, names and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval System or translated into any language including computer language, in any form or by any means electronic, mechanic, magnetic, optical, chemical or otherwise without prior written permission of: EVault, A Seagate Company c/o Corporation Trust Center 1209 Orange Street Wilmington, New Castle Delaware EVault, EVault Software, EVault SaaS, and EVault DeltaPro, are registered trademarks of EVault Inc. All other products or company names mentioned in this document are trademarks or registered trademarks of their respective owners. Acknowledgements: Two encryption methods, DES and TripleDES, include cryptographic software written by Eric Young. The Windows versions of these algorithms also include software written by Tim Hudson. Bruce Schneier designed Blowfish encryption. Part of the software embedded in this product is gsoap software. Portions created by gsoap are Copyright Robert A. van Engelen, Genivia Inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The EVault Software Agent, EVault Software CentralControl, and EVault Software Director applications have the encryption option of AES (Advanced Encryption Standard). Advanced Encryption Standard algorithm (named Rijndael, pronounced Rain Doll ) was developed by cryptographers Dr. Joan Daemen and Dr. Vincent Rijmen. This algorithm was chosen by the National Institute of Standards and Technology (NIST) of the U.S. Department of Commerce to be the new Federal Information Processing Standard (FIPS). The EVault Software Agents and EVault Software Director applications also have the added security feature of an over the wire encryption method.

3 Contents 1 Administration Overview Welcome to Web CentralControl Administration Web CentralControl Features and Requirements Browser Limitations Terms Used in This Guide Installation Migrating to a 64-Bit Server Installation Overview Prerequisites Recommended Setup SQL Server Requirements Web CentralControl Recovery Encrypting View State for Web CentralControl Securing Your Websites Limit Language Choices Agent Update Indicator URLs for the Agent Assistant Default Installation Directories Agent Custom Commands Backup Log timeouts in the.config files Installation log Web CentralControl Typical Installation Installation Steps - Typical Web CentralControl Custom Installation Overview Contents Page 3

4 2.4.2 Installation Steps - Custom Installing Web CentralControl for an Intranet/Internet mix AMP Redirectors Configuring Web CentralControl for a Web Farm Configure Logging Level Modify, Repair, Remove/Uninstall Modify Repair Remove/Uninstall Web CentralControl Upgrade Rolling Back an Upgrade Status Application Usage Installation Web CentralControl Administration Overview ADMINISTRATION Company Logging In for the First Time: Super user Search for Company or User Name Account Management Create New Company Edit Company Remove a Company Account Administrator Create New User Edit User Remove User Vault Profile Contents Page 4

5 3.3.9 Support User Login Message Management Add Message Edit Message Remove Message Your Messages Preferences User Lockout Reset Quick Links Settings for EVault Reports Usage Metrics Agent Installation Kit Management Agent Installation Kit Add or Update Agent Installation Kit Removal Upgrading the vsphere Agent Appendix: Condensed List of Installation Steps Contents Page 5

6 1 Administration Overview 1.1 Welcome to Web CentralControl Administration The Web CentralControl program provides a centralized point of control for remotely managing backups and restores of servers on large computer networks. With Web CentralControl, you can configure, monitor and manage all of your remote backup and restore activities. Your backups are encrypted and transmitted via your network, or the Internet, to a remote and secure vault (i.e., EVault Software Director). Through Microsoft Internet Explorer or Mozilla Firefox on a network, you can use Web CentralControl to access registered Agents for backup and recovery. You cannot directly upgrade a Web CentralControl installation from a 32-bit server to a 64-bit server, but migration is possible. For information about this, see the Web CentralControl Migration Guide. This manual describes the installation of the Web CentralControl application, as well as administration functions to use initially (and others to use routinely). Backups and restores are not part of this administration. Web CentralControl provides online help for backups and restores, and all backup/restore users can access it. Administration functions have separate online help. These functions are also described in Web CentralControl Administration in this guide. Web CentralControl installation is not documented in the online help. It is only documented in this guide. Overview Page 6

7 1.2 Web CentralControl Features and Requirements Note: It is easier than ever to give your users access to EVault Reports. To learn how to take advantage of this, see EVault Reports integration information in Web CentralControl Typical Installation, Web CentralControl Custom Installation, and Settings for EVault Reports. Features of Web CentralControl: - Communication between Web CentralControl and the Agents is encrypted (SSL/TLS). - Installation can range from simple (typical) setups on one machine to custom setups on multiple machines. - Six levels of roles and permissions, from Super user (site administrator) to view status only. - Users can propagate a job from one Agent to another. This allows configuration of multiple Agents, without the need to modify each Agent individually. - The Administrator can post informational messages on user dashboards. - The application can support up to 50 concurrent user connections per server. If you need more, you must use a web farm for multiple servers. The Web CentralControl application requires: - Microsoft Windows Server 2012, 2008, or NET Framework version 3.5 SP1, plus ASP.NET - Internet Information Services (IIS) version 7.0 or later (already active), except for Windows Server 2003 installations, which require IIS For new installations, SQL Server/Server Express 2012 or 2008 R2 (mixed mode authentication). See SQL Server Requirements for details. - Agent software version 5.6 or later Note: Web CentralControl itself does not require a license. Agents and Plug-Ins receive their licenses through the vault. Browser requirements: - Internet Explorer 8 or later, or a recent version of Firefox Note: Compatibility View in Internet Explorer is not supported. - Cookies and JavaScript must be enabled; pop-up blockers must be disabled Overview Page 7

8 - Minimum recommended screen resolution is 1024 x Browser Limitations You can use the Web CentralControl user interface through Microsoft Internet Explorer and Mozilla Firefox. Because Web CentralControl is a secure web application, some browser functions are not permitted, or they do not operate as they do on typical internet sites. Besides the conditions mentioned previously (regarding cookies, JavaScript, and pop-up blockers), you should also adhere to the following conditions. Failure to do so can cause unpredictable results. You cannot have more than one Web CentralControl window open in the same login session. That is, you should not use Ctrl+N (New Window) or Ctrl+T (New Tab) to open a browser window from within another browser window. You may, however, start a separate new browser. Do not use the Back or Forward buttons in your browser. This will cause unpredictable behavior. The Web CentralControl program may appear to work properly, but it may not produce correct results. In Firefox, to avoid scrollbars on Administration pop-up windows, suppress the location bar: 1. Type about:config into the location bar. 2. Press Enter to display the list of preferences. 3. Highlight the following setting, and set its value to false. dom.disable_window_open_feature.location Go to the Web CentralControl login screen to continue. Internet Explorer has a security feature where a pop-up or modal dialog window may have an address or status bar showing. This tends to reduce the size of usable data in the window. You can turn this feature off through these steps: 1. Open a browser window. 2. Open the Tools menu, and click Internet Options. 3. Go to the Security tab, and click Custom level. 4. Under Miscellaneous, find the Allow websites to open windows without address or status bars option, and set it to Enable. Overview Page 8

9 1.3 Terms Used in This Guide AMP Proxy: AMP is an Agent Management Protocol. This protocol is used to communicate between Web CentralControl and the BUAgent, through a proxy server. There can be multiple AMP Proxy servers, each of which can support up to 1,000 registered Agents. AMP Redirector: The AMP Redirector service sits between Web CentralControl and multiple proxy servers. Its function is to balance the load to the proxy servers. An AMP Redirector service is always required to be running. BUAgent: A Backup Agent (BUAgent) is an Agent for Web CentralControl. Web CentralControl can only control BUAgents. BAMS/BANS protocol: BAMS (Backup Agent Management SOAP) is the interface that Web CentralControl uses to communicate with the BUAgent. BANS (Backup Agent Notification SOAP) is the interface the BUAgent uses to upload data and register with Web CentralControl. ( SOAP means Simple Object Access Protocol.) Registration Service: This Web service allows the Agent to register with Web CentralControl through the AMP proxy. Propagation: Users can propagate a job from one Agent to another. This helps speed up the configuration of multiple Agents in the same company. The user can configure multiple Agents from one base job without having to modify each Agent independently. Users can also update particular settings after the initial job propagation. A Propagation Service runs any job propagation requests submitted by users. Messaging: The Super user can create system-wide messages that users will see in the Your Messages sections of their Backup and Recovery dashboards. The messages can be languagespecific, and filtered for companies and Agent types. Overview Page 9

10 2 Installation This chapter describes Web CentralControl installation. Web CentralControl can be a simple (Typical) installation with all the components on the same machine. Or it can be a Custom installation, with the components installed separately. A Custom installation, using all of the default selections, offers the same functionality as a Typical installation. The same kit automatically installs the Web CentralControl components for Typical installation and Custom installation: Notification Service: Allows the Agent to upload information to Web CentralControl through the AMP Proxy Registration Service: Allows the Agent to register with Web CentralControl through the AMP Proxy SQL Server Database Setup: Used by all the Web services, Windows Services, AMP Proxy and AMP Redirector AMP Proxy: Allows the Agents to connect to (and then be managed by) Web CentralControl and the BackupConsole Propagation Service: Runs job propagation requests submitted by users User Interface: Provides login capabilities, user management and the ability to manage remote Agents. It also contains the BackupConsole and Login applications. AMP Redirector Service: Allows Agents to connect to the AMP Redirector to register and be redirected to the AMP Proxy, which allows them to be managed by Web CentralControl. Optional component: Status: Program that provides a page that checks the status of the Web CentralControl components, including Notification/Registration service, Proxy availability and Database availability. See 2.7 Status Application for details. Note: You should perform regular backups of the Web CentralControl databases (using the SQL Server Agent Plug-In or database dumps). 2.1 Migrating to a 64-Bit Server You cannot directly upgrade a Web CentralControl installation from a 32-bit server to a 64-bit server, but migration is possible. To migrate to the 64-bit version of Web CentralControl, you must upgrade to the 32-bit version of Web CentralControl 7.2x first. To see instructions for migration, refer to the Web CentralControl Migration Guide. Installation Page 10

11 2.2 Installation Overview This section describes the installation process that applies to both Typical and Custom installations. The sections following this overview describe Typical and Custom installations in detail Prerequisites 1. For new installations, Microsoft SQL Server/Server Express 2012 or 2008 R2 (mixed mode authentication) needs to be installed and running. See SQL Server Requirements for details. Note that SQL Server is not part of the Web CentralControl installation. 2. Internet Information Services (IIS) 7.0 or later is required. This is not part of the Web CentralControl installation. 3..NET Framework version 3.5 SP1 is required, as well as ASP.NET. Web CentralControl registers these, but does not install them. Note: If you install products such as Web CentralControl and EVault Reports on the same machine, they should use different virtual directory names for the same application. For example, when Login is the default virtual directory name, Web CentralControl can use Login and EVault Reports can use ERLogin. If you don t use different names, one will overwrite the other. This does not apply if they are on different machines Recommended Setup The user interface (i.e., the BackupConsole and User Management applications), AMP Proxy, and AMP Redirector should reside on systems in a perimeter network, or they should be made available over the Internet. They are the connection points to the system. The Notification Service, Registration Service, Propagation Service, and Database should reside on one or more internal systems that are not accessible from the Internet. These services do need to be internally accessible by the user interface, AMP Proxy, and AMP Redirector systems Recovery Options for Web CentralControl Service Properties Windows Services (such as AMP Proxy, AMP Redirector, AMP Propagation, and BUAgent) typically use a default option to Take No Action for recovery. This means that if one of these services halts, it must be restarted manually. But the Web CentralControl installation process changes the default responses for these services to restart after a 10-minute wait. The Administrator may want to change these recommended timeouts. Installation Page 11

12 In Windows, under Administrative Tools > Services (Local), select one of the EVault services. Under the Recovery tab, you will see menus for response if this service fails such as Restart service after <10> minutes. You can change the recommended times if you wish. Figure 1. - Recovery Options for Services SQL Server Requirements For new Web CentralControl installations, Microsoft SQL Server/Server Express 2012 or 2008 R2 must be installed and running, with the following requirements: SQL Server Option Instance feature Authentication Collation Instance name Requirement Database Engine Services Mixed Mode (SQL Server and Windows authentication) Any case-insensitive collation Any instance name; no restrictions SQL Server should be installed on a system that is not externally visible, configured with default settings, and ready for use. When SQL Server and Web CentralControl services are installed on different servers, TCP/IP must be enabled for the database instance. SQL credentials must also be specified for connecting to the database from remote servers. Installation Page 12

13 Web CentralControl can use the same SQL Server instance as EVault Reports. However, for scalability and environments with many Agents and vaults, it is preferable to use separate SQL Server instances for Web CentralControl and EVault Reports Web CentralControl Recovery If your Web CentralControl installation is damaged or deleted, you might be able to recover. There are three databases associated with the Web CentralControl program. These contain all of the data that has been entered since the initial installation. - WebCC - UserManagement - SiteManagement It is assumed that you have made backups of the databases with the SQL Server Agent Plug-In, or created database dump files with SQL Server Express. You can then restore the databases after you reinstall the Web CentralControl application. Note: An open-file solution should not be used for backups here. You must reinstall the software to the same locations as before, restore the databases, and then restart all of the services. When you reinstall the Web CentralControl application, you will need to create new (empty) databases. Then you can restore the databases with the backup from the SQL Server Agent Plug- In Web CentralControl Backup / Restore Here are recommendations for backing up Web CentralControl: At a minimum, the three Web CentralControl databases (UserManagement, SiteManagement and WebCC) must be backed up. To restore, you need to first reinstall the software at the same locations and IPs as before, restore the databases, and then restart all of the services. Complete DR Backups For a complete DR backup, the following must be backed up. Note that this will require multiple jobs to accomplish. The three databases: UserManagement, SiteManagement and WebCC System State, including Windows System Files Installation Page 13

14 The installation directories of these components: AMP Proxy (default location C:\Program Files\EVault Software\WebCC Services\AMP Proxy Service) AMP Redirector (default location C:\Program Files\EVault Software\WebCC Services\AMP Redirector Service) Propagation Service (default location C:\Program Files\EVault Software\WebCC Services\PropagationService) Task Service (default location C:\Program Files\EVault Software\WebCC Services\Task Service) BackupConsole (default location C:\inetpub\wwwroot\BackupConsole) Login (default location C:\inetpub\wwwroot\login) Notification (default location C:\inetpub\wwwroot\notification) Registration (default location C:\inetpub\wwwroot\registration) Status (default location C:\inetpub\wwwroot\WebCCStatus) (if installed) Language Files (default location C:\Program Files\EVault Software\WebCC Services\LanguageFiles) To restore all of this, you must restore from all of the jobs that created the backups. The backup with System State and the files needs to be restored first, then the databases, and then all of the services need to be restored and restarted. If a web farm was also being used, the machine.cfg file needs to be readjusted after the restore to enable the farm again. Note: All of the Agents connected to the Proxy will go offline during a restore process and will need to be restarted. You can prevent the need to restart the Agents by making the AMP Proxy service unavailable while you restore the server Encrypting View State for Web CentralControl ASP.NET view state is the technique used by an ASP.NET web page to preserve changes to the state of a Web Form across postbacks. That is, the view state represents the state of the page when it was last processed on the server. View state makes the use of the Web Forms model possible. By default, with.net the view state is verified but not encrypted. If Web CentralControl (using only one UI application) will run in a service environment, the view state should be encrypted. Installation Page 14

15 There are some manual steps that must be taken to encrypt the view state. If Web CentralControl is not running on a web farm, to turn on encryption for Web CentralControl, the user must modify the web.config file in this directory: C:\Windows\Microsoft.NET\Framework\<version>\Config There is a line in the web.config file that resembles this: <machinekey validationkey="autogenerate,isolateapps" decryptionkey="autogenerate,isolateapps" validation="hmacsha256"/> To turn on encryption, only the validation= setting needs to change. Change it to 3DES. The resulting line should look similar to this: <machinekey validationkey="autogenerate,isolateapps" decryptionkey="autogenerate,isolateapps" validation="3des"/> If you make this change, all.net web applications that run under.net will have their view states encrypted. Note: If the Web CentralControl UI application is running on a web farm, there are different steps that are required to set up view state encryption on the web farm. See Configuring Web CentralControl for a Web Farm Securing Your Websites If you choose to secure your websites after you have installed Web CentralControl, the following steps must be completed. 1. Assign your Certificate to the website where the UserManagement (Login) and BackupConsole web applications reside. 2. In IIS Manager, ensure that the SSL (Secure Sockets Layer) protocol is required for the Login and BackupConsole virtual directories. 3. Update the following fields in the web.config file in the BackupConsole web application's installation location to use https instead of http at the start of the URL: StartupPage LoginSite Help.Base.Url Note: Do not modify the remainder of the line. Installation Page 15

16 4. Update the following fields in the web.config file in the UserManagement (Login) web application's installation location to have https instead of http at the start of the URL: FlorenceSite LoginSite Help.Base.Url Note: Do not modify the remainder of the line. 5. Restart IIS. You will need to connect to to use your application now. You should also install a default redirection page at the location to redirect to the page. This helps to prevent problems with users referencing the non-secure website. Note: Attempts to log in with the http prefix rather than https will result in permission errors Limit Language Choices During the installation you are asked for your choice of languages, in addition to the default English. You can choose from French, German, Spanish, and Portuguese. If you do not install an additional language now, you can do it later by rerunning the installation with Modify. You can also remove a language this way. The dialog for language selection only appears during a fresh Install, Upgrade or Modify process. Repair and Uninstall scenarios do not show the dialog. Notes about languages If Web CentralControl is used with multiple languages, messages (in Your Messages ) need to be created for each language, in that language. If a message is not provided for a particular language, users who log in using that language will not see the message. If Web CentralControl is used with multiple languages, quick links need to be created with text for each language, in that language. If a quick link does not have text for a particular language, users who log in using that language will not see the links. See also Your Messages and 3.6 Quick Links. Installation Page 16

17 2.2.8 Agent Update Indicator Web CentralControl can place an icon next to an Agent version if it is not at the most recent version. To accomplish this, the Super user has an Agent Install Kit Management screen that allows them to define which Agents can be upgraded, the versions, and where the upgrades come from. See 3.8 Agent Installation Kit Management for more information. If an Agent that is registered to Web CentralControl has a version earlier than the one indicated in the file, that Agent will get an icon next to their Agent version number in the Agent grid. If the user pauses the mouse pointer over that icon, they will get a message indicating that there is a newer version of the Agent available for that system. Figure 2. - A newer Agent version is available If the Super user has added an Agent type to be upgraded, a URL is provided for the location of the Agent installation kit. The user will be able to click on the Agent Update indicator icon. This will download the new installation kit, and the user can run it to upgrade the Agent. Users cannot clear the update indicator icon. It will remain until they upgrade the Agent. Installation Page 17

18 2.2.9 URLs for the Agent Assistant During the Agent installation, if you chose to install the Agent Assistant, you were prompted for the URL of the Web CentralControl application, and the URL of the Web CentralControl Help. The installation process does not check the validity of the URL addresses. So if you cannot start Web CentralControl, or run the Help (or if you need to change the addresses), run the Agent installation kit in Modify mode. Alternatively, you can change the settings through line commands. For example, you can use this command to install an Agent with the Agent Assistant, and then register the Agent with Web CentralControl: setup.exe /s /v" FEATUREMAESTRO=on REGISTERWITHWEBCC=True AMPNWADDRESS= com AMPPASSWORD=LetMeIn3 BCKLOGINURL= BCKHELPURL= /qn" In this example, setup.exe represents the name of the installation package. For more information about these line commands, see the online help for Backup and Recovery Default Installation Directories By default the installer places the files for fresh installations in a directory called: C:\Program Files\EVault Software\WebCC Services where C: may be another drive. You may still change the path, if required. All the EVault Software applications are then located in a single directory, but have their own subdirectory to run in. Requirements (such as locking down for admin users only) won't affect the other applications. The kit will not remove the top-level directory unless it is empty at the end of an uninstallation Agent Custom Commands A folder called "ScheduleScripts" in the Agent installation folder is used to allow Web CentralControl to use the custom commands that you create. If this folder does not exist, you should create it. The script file itself is a.bat file that must reside in this ScheduleScripts folder. See Custom Commands in the Web CentralControl help for more information. Installation Page 18

19 Backup Log timeouts in the.config files If you show "Errors Only" or "Errors and Warnings Only" for large files (see Log File Viewer), Web CentralControl might time out and issue errors. A Unix Agent can take a long time to parse the log file when filtering it, so you may want to increase the length of the timeout period. As a workaround, change the.config files. For log-viewer page timeouts, add the following lines to the BackupConsole application's web.config file: <location path="pages/job/logviewer.aspx"> <system.web> <httpruntime executiontimeout="1000"/> </system.web> </location> Add the lines to the Configuration section of the web.config file, directly after the </appsettings> line. In this example, the value is in seconds. For the Proxy/Agent keep alive timeouts, in the AMP Proxy Service application directory, in the AmpService.exe.config file, there is a line that reads: <add key="proxy.keepalive.interval" value="60000" /> This value is in milliseconds and (for example) may be increased to For SOAP call timeouts, in the AMP Proxy Service application directory, in the AMPService.exe.config file, there is a line that reads: <add key="proxy.soap.timeout" value="100000" /> This value is in milliseconds and (for example) may be increased to Note: Increasing the keep alive interval to 5 or 10 minutes means that Web CentralControl will not receive information that an Agent is offline until 5 or 10 minutes after the Agent has gone offline. This means that the Agent will still show as online in the UI, even though it is offline. If you attempt to access this Agent that appears to be online, you will get errors because the Agent will not respond. Installation Page 19

20 Installation log Web CentralControl creates an installation log during a new Installation, Repair, Upgrade or Uninstall. This log file can be used for troubleshooting and installation support. The log file is overwritten each time the installation runs. Typically, the only place to write to a file during the installation is the temporary directory from where the installation is running. The behavior of the log file is as follows: While the installation is running, the log file will be in the installation s Temp folder. At the end of the installation, the log file will be copied to one of two locations: - If the AMP Proxy, AMP Redirector, Propagation Service or Support Files are selected for installation, the log file will be copied into the common parent directory (default is C:\Program Files\EVault Software\WebCC Services). - If the above are not selected for installation, but User Interface, Notification, or Registration services are selected for installation, the log file will be copied into the common parent log location (default is C:\Logs). - If none of the above is selected or the log file cannot be copied to one of those directories, the installation log remains in the Temp directory. In the Installation log, you will see what the installation has used. This can include: Start date and time Mode selected Database instance Name of installation part (starting) Name of installation part (finishing) Other steps, such as changing, replacing, cleaning up, and backing up Process completed Note: If an uninstallation succeeds, the Installation log is removed. But if the uninstallation fails, or is cancelled, the Installation log will remain in its original location in the temporary folder. Installation Page 20

21 2.3 Web CentralControl Typical Installation A typical installation is the fastest and easiest installation. All the required components are installed on one server. Before the installation starts, you should have:.net installed IIS installed SQL Server/Server Express 2012 or 2008 R2 (mixed mode authentication) installed. See SQL Server Requirements for details Installation Steps - Typical This section describes the steps involved in the installation. 1 Run the installation kit, WebCentralControl-7-2x-xxxx.exe (where xxxx is the build version). The installation kit may have been renamed. 2 Welcome Dialog: States what product is being installed. 3 View Notes: Information about Support and Release Notes appears. 4 Software License Agreement: Ensures the user accepts the terms of the software license agreement (SLA) before installing the software. 5 Install Type: Choose a Typical Installation. This will install all the necessary components on the same machine. (Custom installation is covered later in this manual.) Installation Page 21

22 Figure 3. - Typical Installation 6 Web Site selection. If you have more than one web site in your IIS, you can select it here. Note: If you have only one web site on this system, this dialog will not appear, and the single web site will be selected by default. Figure 4. - Web Site selection - Typical Installation Installation Page 22

23 7 Domain Name: Configure the Web application s domain name. Figure 5. - Domain Name - Typical Installation The computer name or IP that you enter here must match the name or IP in the path that you use in the Web Browser to log in. Installation Page 23

24 8 SQL Server Setup - Select SQL Server Figure 6. - SQL Server Setup You can optionally click Test to validate your connection with the database server. Note that SQL Server authentication requires the Login ID and password that the DBA used to create the database instance (which must be empty, or populated from a previous installation). Installation Page 24

25 9 Select the languages to install You are asked for your choice of languages, in addition to the default English. You can choose from French, German, Spanish, and Portuguese. If you do not install a language now, you can do it later by rerunning the installation with Modify. You can also remove a language this way. The dialog for language selection only appears during a fresh Install, Upgrade or Modify process. Repair and Uninstall do not present the dialog. 10 Services/Support files installation path Figure 7. - Services/Support files install path Installation Page 25

26 11 AMP Proxy IP address configuration Figure 8. - AMP Proxy IP addresses Enter the domain name and the external IP address (for Agents) and internal IP address (for Web CentralControl) for the AMP Proxy. Installation Page 26

27 12 Integrate with EVault Reports If you integrate Web CentralControl with EVault Reports, users can see the Reporting tab in Web CentralControl. Note: Although this integration is optional, it is easier than ever to give your users access to EVault Reports. Web CentralControl authentication (login) information can now be used to allow EVault Reports access. Figure 9. - EVault Reports integration To fully integrate Web CentralControl with EVault Reports, you must also associate Customer short name values (from the vault) and Report Group Name values (from EVault Reports Manager) with Web CentralControl companies. For more information, see Settings for EVault Reports. Installation Page 27

28 If you selected Integrate Web CentralControl and EVault Reports on the previous screen, you are asked here for the EVault Report URLs. For integration to work, EVault Reports must already be installed, and you must provide correct URLs for the EVault Reports installation. The Report Viewer URL is used for end users who have access to reports. When these users click the Reporting tab in Web CentralControl, they are redirected to the EVault Reports URL where they can run reports for their company. The Subscription (Report Manager) URL is used for super users. When these users click the Report Administration tab in Web CentralControl, they are redirected to the EVault Reports Manager site where they can configure subscriptions and report groups. The Token Manager Service URL is only required if you have selected the Web CentralControl Authentication login method for integrating Web CentralControl with EVault Reports. Figure Integrate Web CentralControl and EVault Reports Installation Page 28

29 If EVault Reports is not installed, or you provide incorrect EVault Reports URLs, end users will see messages such as the following: Figure Cannot find integrated sites 13 - Begin the installation: Figure Begin the typical installation The installation runs automatically from here. Installation Page 29

30 14 - Installation complete Figure Typical installation complete You should see the "InstallShield Wizard Complete" screen. This screen provides information about which URL to use, as well as logging in for the first time as super. You will also see a message: Do you wish to open the start page in your browser now? when you click Finish. Figure Open the start page now You can start it now or later, by pointing your browser to the address of the server, and logging in (for example, See also Logging In for the First Time: Super User. Installation Page 30

31 2.4 Web CentralControl Custom Installation A custom installation is similar to a typical installation, but it allows you to install the components separately (on different machines) if you want to. You can customize the location and name for User Interface, Login, BackupConsole, Notification Service, Registration Service, and Services/Support. Before starting the installation, you should have:.net installed IIS installed SQL Server/Server Express 2012 or 2008 R2 (mixed mode authentication) installed. See SQL Server Requirements for details Overview The same kit installs the Web CentralControl components for the Typical Installation and the Custom Installation. These are automatically included in a Typical installation: Optional: Notification Service Registration Service SQL Server Database Setup AMP Proxy Propagation Service User Interface AMP Redirector Service Status component For details about these components, see Installation in this chapter. Briefly, the steps for the installation are: 1. Run the installation kit WebCentralControl-7-2x-xxxx.exe (where xxxx is the build version). Note that the installation kit may have been renamed. 2. The Welcome screen is shown. 3. Information about support and release notes appears. 4. The SLA (Software License Agreement) is shown. You must accept this to be able to continue. Installation Page 31

32 5. Choose a Custom installation. 6. Select the features to install. 7. Choose the web application s website. (This only applies if there is more than one website installed on the system.) 8. Enter the web application s Domain name when prompted. 9. Select an SQL server. (SQL Server authentication credentials need to be used.) 10. Choose the Login installation path and log locations. 11. Enter a Login Virtual Directory name. 12. Select the languages to install. The default is English, but you can also choose from French, German, Spanish, and Portuguese. 13. Choose the BackupConsole installation path. 14. Enter a BackupConsole Virtual Directory Name. 15. Enter a Propagation IP address. 16. Choose the Notification installation path. 17. Enter a Notification Virtual Directory Name. 18. Choose the Registration installation path. 19. Enter a Registration Virtual Directory Name. 20. Choose the Services/Support files installation path. 21. Configure AMP Proxy IP addresses. Enter the external IP address that the Agents will use to connect to the AMP Proxy, and the internal IP address that the User Interface will use to connect to the AMP Proxy. 22. Integrate Web CentralControl and EVault Reports (optional). 23. Configure the Status path if you are prompted. 24. Begin the installation. 25. Installation completes. These steps are described in more detail after this section. (Note: Some of the options may not appear, depending on your other selections.) Installation Page 32

33 2.4.2 Installation Steps - Custom This section describes the steps involved in the installation. 1 Run the installation kit, WebCentralControl-7-2x-xxxx.exe. This may have been renamed. 2 Welcome screen: States what product is being installed. 3 View Notes: Information about support and release notes appears. 4 Software License Agreement: Ensures that the user accepts the terms of the Software License Agreement (SLA) before installing the software. 5 Install Type: Choose Custom Installation. This allows you to install the necessary components separately. (See also Installation Steps - Typical.) Figure Web CentralControl Custom Installation Installation Page 33

34 6 Select Features Figure Select features to install All components that you choose must be installed and running for the Web CentralControl application to function properly. If you do not install one or more components now, you can continue the installation, but you will be prompted for the location of where that component has been or will be installed. (Components can be installed on different systems, but their locations need to be provided during the configuration of the applications that rely on them.) All components must be installed in the configured locations before the application will function. For improved performance, it is recommended that the User Interface component be installed on a separate system from the Database, AMP Proxy and Propagation Service. For example, the User Interface, Notification Service, and Registration could be on a different system (under IIS) than the other components, which do not run under IIS. You may have more than one IIS server. The virtual directory name relates to the installation path of each component within the same IIS server. If you have more than one IIS server, the configuration prompts require the full web address of the remote IIS server for the local components that communicate with them. Installation Page 34

35 7. Web Site selection If you have more than one web site in your IIS, you can select it here. Note: If you have only one web site on this system, this dialog will not appear, and the single web site will be selected by default. Figure Web Site selection Custom installation If you select a web site that runs on a non-default port (http/https), the port number for that web site must be provided with the Domain name for this server at the Domain name prompt. Installation Page 35

36 8. Domain Name: Configure the Web application s domain name. Figure Domain Name Custom installation The computer name or IP that you enter here must match the name or IP of the path that you use for the browser to log in. Figure Failed to verify the provided Web Address This error message is typical if you have not set up your local IIS server with your selected domain name. In this case, the application will only work when you have successfully configured your IIS server with the domain name that has been provided here. If the Domain name changes after installation, the installed components will need to be manually updated. Installation Page 36

37 9 - SQL Server Setup - Select SQL Server Figure SQL Server Setup You can optionally click Test to validate your connection with the database server. Note that SQL Server authentication requires the Login ID and password that the DBA used to create the database instance (which must be empty, or populated from a previous installation). If the SQL Server setup option was selected for installation, this instance must not already have databases called WebCC, UserManagement, or SiteManagement. If the SQL Server setup option was not selected for installation, the SQL instance that is selected here should be the location where the SQL Server setup option was previously installed (or where it will be installed). Make sure that SQL Server has been installed using mixed mode authentication. Installation Page 37

38 10 Login: Select Installation Path and Log File location Figure Select Installation Path and Log File location Installation Page 38

39 11 Login: Virtual Directory Name Figure Enter Virtual Directory Name The installation path is where the application will be installed. The Log path is where this application will put its internal log files. Note: Do not locate the log files under the application path. If you do, they will not available to users over the internet. This component provides the login portal to Web CentralControl. This virtual directory will be part of the URL the users will see when they use your application. The breakdown of the URL to connect to this application is as follows: http(s)://<domainname>/<virtualdirectory>/login.aspx. Note that the default here, Login, is deliberately different from the default ERLogin directory name that EVault Reports uses. If you install both products on one server, and any Virtual Directory Names are the same, one will overwrite the other. You will not have this problem if they are on different machines. Installation Page 39

40 12 Select languages to install You are asked for your choice of languages, in addition to the default English. You can choose from French, German, Spanish, and Portuguese. If you do not install a language now, you can do it later by rerunning the installation in Modify mode. You can also remove a language this way. The dialog for language selection only appears during a fresh Install, Upgrade or Modify process. Repair and Uninstall do not show the dialog. 13 Backup Console: Select Installation Path Figure Backup Console Installation Path Installation Page 40

41 14 Backup Console: Virtual Directory Name Figure Backup Console Virtual Directory Name Installation Page 41

42 15 - BackupConsole Propagation IP address Figure BackupConsole Propagation IP address By default, the Propagation Service will be installed using the loopback IP address ( ). If your system does not allow the loopback, you can supply an alternate IP address for the local Propagation Service here. Installation Page 42

43 16 Notification Installation Path Figure Notification Installation Path Installation Page 43

44 17 Notification Virtual Directory Figure Notification Virtual Directory Installation Page 44

45 18 Registration Installation Path Figure Registration Installation Path Installation Page 45

46 19 Registration Virtual Directory Name Figure Registration Virtual Directory name Installation Page 46

47 20 Services/Support files install path Figure Services/Support files install path Installation Page 47

48 21 - AMP Proxy IP address configuration Figure AMP Proxy IP addresses Enter the domain name and the external IP address (for Agents) and internal IP address (for Web CentralControl) for the AMP Proxy. Installation Page 48

49 Integrating with EVault Reports 22 Integrate with EVault Reports If you integrate Web CentralControl with EVault Reports, users can see the Reporting tab in Web CentralControl. Note: Although this integration is optional, it is easier than ever to give your users access to EVault Reports. Web CentralControl authentication (login) information can now be used to allow EVault Reports access. Figure EVault Reports integration To fully integrate Web CentralControl with EVault Reports, you must also associate Customer short name values (from the vault) and Report Group Name values (from EVault Reports Manager) with Web CentralControl companies. For more information, see Settings for EVault Reports. Installation Page 49

50 If you selected Integrate Web CentralControl and EVault Reports on the previous screen, you are asked here for EVault Reports URLs. For integration to work, EVault Reports must already be installed, and you must provide correct URLs for the EVault Reports installation. The Report Viewer URL is used for end users who have access to reports. When these users click the Reporting tab in Web CentralControl, they are redirected to the EVault Reports URL where they can run reports for their company. The Subscription (Report Manager) URL is used for super users. When these users click the Report Administration tab in Web CentralControl, they are redirected to the EVault Reports Manager site, where they can configure subscriptions and report groups. The Token Manager Service URL is only required if you have selected the Web CentralControl Authentication login method for integrating Web CentralControl with EVault Reports. Figure Configuring EVault Reports integration Installation Page 50

51 If EVault Reports is not installed, or you provide incorrect EVault Reports URLs, end users will see messages such as the following: Figure Cannot find integrated sites Note: EVault Reports is a separate installation. See the EVault Reports User Guide for detailed information. After you successfully configure EVault Reports integration, you will see a Reporting tab in Web CentralControl. When you click the Reporting tab, you are taken to EVault Reports, which is a separate application. Figure Reporting tab in Web CentralControl Installation Page 51

52 23 Optional: Select the path for the Status component, if you have chosen to install it. See Status Application for details about this component. Figure Configuring Status (optional) Installation Page 52

53 24 - Begin the installation process Figure Begin the installation process The installation runs automatically from here Installation complete Figure Custom installation complete You should see the "InstallShield Wizard Complete" screen. This screen provides information about which URL to use, as well as logging in for the first time as super. Installation Page 53

54 You can start Web CentralControl after a complete installation by pointing your browser to the address of the server, and then logging in. For example: (See Logging In for the First Time: Super User.) Note: If you change the virtual directory of the Login component to something else, your URL will need to reflect this. The URL you should use is: http or https (depending whether you are using certificates or not) <http/https>://<domainname>/<virtualdirectory for Login component>/login.aspx Installing Web CentralControl for an Intranet/Internet mix You may want to install Web CentralControl to use on both your Intranet and Internet, which might have different domain names. If the domain names are the same, there is no conflict. If the domain names are different, the installation must be different. You will need to install two instances of the User Interface component (one on each domain). The other components (AMP Proxy, Notification, Registration, SQL Server setup, and Propagation) must only be installed in one location. Both instances of the UI must point to the same installation of the other components. During the User Interface installation (if it was installed without the other components), you will be prompted for the location of the Database, Propagation Service and AMP Proxy Service. If you provide the locations to the single installation of those components, both User Interface installations will allow your users to manage the same Agents from either the Internet or Intranet AMP Redirectors The AMP Redirector is a Web CentralControl service that sits between the Agent and proxy servers. It handles registration and initial connections of the Agents. The AMP Redirector must be set up for each Web CentralControl installation. Its function is to balance the load to the proxy servers. When an Agent attempts to connect to Web CentralControl (and its database) through a proxy server, the Redirector will direct it to the next one available with the lowest number of connections. During an upgrade from a previous Web CentralControl that did not use Redirector, the installer will add the Redirector if the AMP Proxy was previously installed. It will assume the port number of the AMP Proxy, and the proxy will be moved to port Installation Page 54