EVault Software Portal 7.8 Installation and Configuration Guide

Transcription

1 EVault Sftware Prtal 7.8 Installatin and Cnfiguratin Guide

2 Revisin: This manual has been updated fr Versin 7.8. Sftware Versin: 7.80 (June 2015) 2015 EVault Inc. EVault, A Seagate Cmpany, makes n representatins r warranties with respect t the cntents heref and specifically disclaims any implied warranties f merchantability r fitness fr any particular purpse. Furthermre, EVault reserves the right t revise this publicatin and t make changes frm time t time in the cntent heref withut bligatin f EVault t ntify any persn f such revisin f changes. All cmpanies, names and data used in examples herein are fictitius unless therwise nted. N part f this dcument may be reprduced, transmitted, transcribed, stred in a retrieval System r translated int any language including cmputer language, in any frm r by any means electrnic, mechanic, magnetic, ptical, chemical r therwise withut prir written permissin f: EVault, A Seagate Cmpany c/ Crpratin Trust Center 1209 Orange Street Wilmingtn, New Castle Delaware EVault, EVault Sftware, EVault SaaS, and EVault DeltaPr, are registered trademarks f EVault Inc. All ther prducts r cmpany names mentined in this dcument are trademarks r registered trademarks f their respective wners. Acknwledgements: Tw encryptin methds, DES and TripleDES, include cryptgraphic sftware written by Eric Yung. The Windws versins f these algrithms als include sftware written by Tim Hudsn. Bruce Schneier designed Blwfish encryptin. Part f the sftware embedded in this prduct is gsoap sftware. Prtins created by gsoap are Cpyright Rbert 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 Sftware Agent, EVault Sftware CentralCntrl, and EVault Sftware Directr applicatins have the encryptin ptin f AES (Advanced Encryptin Standard). Advanced Encryptin Standard algrithm (named Rijndael, prnunced Rain Dll ) was develped by cryptgraphers Dr. Jan Daemen and Dr. Vincent Rijmen. This algrithm was chsen by the Natinal Institute f Standards and Technlgy (NIST) f the U.S. Department f Cmmerce t be the new Federal Infrmatin Prcessing Standard (FIPS). The EVault Sftware Agents and EVault Sftware Directr applicatins als have the added security feature f an ver the wire encryptin methd.

3 Cntents 1 Intrductin t Prtal System Overview Frnt-end system (web accessible) Back end cmpnents (nt externally accessible) EVault Reprts cmpnents (ptinal) Prtal Distributed System (recmmended) Prtal Single System Prerequisites Sftware prerequisites Default prts SQL Server requirements Install Prtal Install Prtal n a distributed system Install back-end system cmpnents Install frnt-end system cmpnents Install the Prxy and Redirectr Install Prtal n a single system Integrate Prtal with EVault Reprts Assciate custmer shrt names using Prtal Assciate custmer shrt names using Web CentralCntrl Cnfigure Prtal Encrypt the view state Cnfigure a web farm Hide the legacy interface check bx Change the frm text in reprt s Enable and set up reprts in Prtal Cnfigure single sign-n (SSO) Cnfigure Prtal t use a federated identity server Install IdP Signing Certificate n the machine where Prtal is installed Username in the SAML tken User rle in the SAML tken Page 3

4 5.6.5 User site in the SAML tken SAML tken/expected claims Trubleshting single sign-n Mdify Prtal Cnvert Prtal frm a single system t a tw-server distributed system Upgrade Prtal Dmain names and Agent registratins after an upgrade Prepare fr a Prtal upgrade Upgrade Prtal cmpnents Update the Web CentralCntrl URL fr EVault Reprts Make the upgraded Prtal available t users Rll back databases after an upgrade System validatin Validate the Prtal installatin Lg in t Prtal fr the first time Lg in t the legacy interface Create a site Create an Admin user Add a cmputer Add a backup jb View the Reprts tab Validate the Legacy Web CentralCntrl installatin Lg in t Web CentralCntrl fr the first time Create a cmpany Create an Admin user Register Agents Create a backup jb Prpagate an agent s settings Access EVault Reprts Trubleshting and Maintenance Redirecting Prts Securing Web CentralCntrl sites SQL database installatin failure Agent desn t register t Redirectr Unauthrized prxy errrs Page 4

5 9.6 Agents g ffline spradically Cannt lad type when lading Prtal lgin page NT AUTHORITY\SYSTEM lgin fails when navigating t Prtal Legacy Web CentralCntrl UI nt accessible frm Prtal lgin page Users cannt lg in using Internet Explrer errr when attempting t pen the Prtal website IIS default page appears instead f Prtal sign-in page Database transactin lg files require mnitring Prtal Disaster Recvery Back up Prtal data and settings Recver a Prtal instance Rebuild Prtal and Web CentralCntrl cmpnent infrmatin Page 5

6 1 Intrductin t Prtal EVault Prtal prvides a centralized pint f cntrl fr remtely managing backups and restres f servers n large cmputer netwrks. Prtal is the latest Web interface frm EVault, and adds functinality beynd what the legacy Web CentralCntrl interface prvides. The Prtal web applicatin makes backup management and reprting easier and mre intuitive thrugh a simple web interface. It is als a scial cllabratin tl that enables users t access status feeds and cmmunicatins with the user cmmunity. Prtal is built n Web CentralCntrl applicatin cmpnents, which allws users t utilize the Prtal interface withut having t re-cnfigure their existing Agents. Using a supprted Web brwser, users can lg in t Prtal r the legacy Web CentralCntrl interface frm the same lgin page. This guide describes hw t install Prtal. Infrmatin n creating backups and restres is nt part f this guide but can be fund in the Prtal nline help. Prtal is scalable, and can accmmdate a variety f different-sized rganizatins. A simple system can run n a single cmputer and efficiently handle apprximately 500 cmputers. A distributed farm system can handle much larger rganizatins with tens f thusands f cmputers. 1.1 System Overview Prtal includes the frnt-end and back-end cmpnents described in the fllwing tables. These cmpnents can be installed as a distributed system (recmmended) r n a single server Frnt-end system (web accessible) Cmpnent Prtal UI Web CentralCntrl UI (ptinal) AMP Redirectr Service Lad Balancer Descriptin Brwser-based interface that allws fr cntrl and remtely managing backups and restres f servers n large cmputer netwrks. Prtal UI als allws fr reprts generatin as well as access t status feeds and cllabrative capability between users in the same cmpany. Legacy brwser-based interface that allws fr cntrl and remtely managing backups and restres f servers n large cmputer netwrks. Accepts Agent registratins and balances the number f authrized Agents between available prxies in the Prtal envirnment. A Lad Balancer (nt prvided with Prtal) can be installed t balance the lad acrss multiple Prtal frnt-end systems. Page 6

7 Cmpnent AMP Prxy Prtal Service Cnnectr Hst Prtect Service Task Scheduler Descriptin Acts as the access pint fr numerus Agents t cnnect t the Prtal envirnment. It passes messages between the Agent and the backend services as well as messages frm the UI t the Agent allwing fr cnfiguratin f the Agent as well as status uplads frm the Agent. Multiple AMP prxy servers can be used t increase the number f Agents the verall envirnment can supprt. A maximum f 1000 Agents per AMP Prxy is recmmended. A mechanism that prvides internal cmmunicatin between the Prtal UI and the backend services/database. A secnd mechanism that prvides internal cmmunicatin between the Prtal UI and the backend services/database. Executes scheduled reprts as well as ther back end tasks that are executed n a schedule Back end cmpnents (nt externally accessible) Cmpnent Descriptin SQL Databases WebCC database Cntains Agent cntent infrmatin. UserManagement database Cntains User Management infrmatin. SiteManagement database Cntains site-specific cntent infrmatin. EVaultWeb database Cntains user cntent infrmatin. Task Service Ntificatin Service Registratin Service Prpagatin Service Status Flags scheduled backups that are missed. This cmpnent is installed with the SQL databases. Allws Agents t ntify the UI f Agent cnfiguratins, jbs statuses, and ther infrmatin. Allws Agents t register with Prtal. Used t prpagate Agent jb cnfiguratins t ther Agents. Only required fr the ptinal legacy Web CentralCntrl UI. Reprts n the running state f sme f the back-end services. Page 7

8 1.1.3 EVault Reprts cmpnents (ptinal) EVault Reprts is a separate prduct that can be integrated with Prtal and the legacy Web CentralCntrl UI. If yu want t integrate EVault Reprts with Prtal r the legacy Web CentralCntrl UI, yu can install the fllwing cmpnents using the EVault Reprts installatin kit. Cmpnent Tken Manager Lader Reprt Manager EVault Reprts database Descriptin Creates and distributes authenticatin tkens which are used t prvide authenticatin and scping arund the custmers included in reprts that are generated fr Prtal. Receives vault metadata fr reprts generatin. Used t cnfigure reprt grups and subscriptins fr EVault Reprts. This cmpnent is ptinal when integrating EVault Reprts with the Prtal UI, and is required fr integrating EVault Reprts with the legacy Web CentralCntrl UI. Creates a variety f user strage, data, and usage reprts Imprtant: EVault Reprts cmpnents shuld nt be installed int the Prtal website. Page 8

9 1.2 Prtal Distributed System (recmmended) The distributed web farm system can be scaled ut t handle a large number f Agents and Users, as shwn in Figure 1. Nte: The Lad Balancer is ptinal, and is nt prvided by EVault. Figure 1 Prtal Distributed System Page 9

10 1.3 Prtal Single System The single system, shwn in Figure 2, is nt recmmended, but can be used fr envirnments with fewer than 500 Agents. Figure 2 Prtal Single System Page 10

11 2 Prerequisites As described in System Overview, Prtal cmpnents can be installed as a distributed system (recmmended) r n a single server. All cmpnents must be installed n a supprted 64-bit perating system. Fr a list f supprted platfrms, see the Prtal release ntes. Nte: If yu are upgrading t Prtal frm Web CentralCntrl n a 32-bit perating system, yu must first upgrade Web CentralCntrl cmpnents n the 32-bit platfrm and back up the Web CentralCntrl databases. Yu can then install Web CentralCntrl n a 64-bit platfrm, and restre the databases t the 64-bit system. Fr mre infrmatin, see the Web CentralCntrl Migratin Guide. On each system where Prtal cmpnents will be installed, d the fllwing: Turn ff IPV6. Use IPV4 addresses when prviding settings fr IP addresses. Make sure all servers are set t the same timezne and have the same time. Install required sftware prerequisites. See Sftware prerequisites. If Prtal cmpnents are installed as a distributed system, pen the required prts. Fr mre infrmatin, see Default prts. 2.1 Sftware prerequisites The fllwing sftware must be installed befre yu can install Prtal n a single system: Micrsft Internet Infrmatin Services (IIS) 7.0 r later, including all rle services that are installed by default, plus the fllwing available rle services and features: Under Cmmn HTTP Features: Static Cntent HTTP Errrs HTTP Redirectin Under Applicatin Develpment:.NET Extensibility 3.5.NET Extensibility 4.5 ASP.NET 3.5 ASP.NET 4.5 ISAPI Extensins ISAPI Filters Nte: Make certain that ASP.NET and.net Extensibility are turned n in Windws features, particularly if IIS is installed befre ASP.NET. Page 11

12 Under Security: Windws Authenticatin Under.NET Framewrk Features: HTTP Activatin On Windws 2012, HTTP Activatin must be installed under bth.net Framewrk 3.5 Features and.net Framewrk 4.5 Features. On Windws 2008, HTTP Activatin must be installed under.net Features..NET Framewrk 4.5.NET Framewrk 3.5 Micrsft SQL Server r SQL Server Express 2012 r 2008 R2 (mixed mde authenticatin), installed and running. Fr detailed infrmatin, see SQL Server requirements. If yu are installing Prtal cmpnents as a distributed system (recmmended), the fllwing table shws prerequisites that are required n each system. System Prtal and ptinal legacy Web CentralCntrl UI (frnt-end) Prerequisite Internet Infrmatin Services (IIS) 7.0 r later, including all rle services that are installed by default, plus the fllwing available rle services: Under Cmmn HTTP Features: Static Cntent HTTP Errrs HTTP Redirectin Under Applicatin Develpment:.NET Extensibility 3.5.NET Extensibility 4.5 ASP.NET 3.5 ASP.NET 4.5 ISAPI Extensins ISAPI Filters Under Security: Windws Authenticatin Under.NET Framewrk Features: HTTP Activatin.NET Framewrk 4.5.NET Framewrk 3.5 AMP prxy and Redirectr.NET Framewrk 3.5 Page 12

13 System Databases Prerequisite Micrsft SQL Server 2012 r 2008 R2 (mixed mde authenticatin) must be installed and running. Fr detailed infrmatin, see SQL Server Requirements..NET Framewrk 3.5 Web services, including Ntificatin, Registratin, and Prpagatin, and Status (backend) Internet Infrmatin Services (IIS) 7.0 r later, including all rle services that are installed by default, plus the fllwing available rle services: Under Cmmn HTTP Features: Static Cntent Under Applicatin Develpment:.NET Extensibility 3.5.NET Extensibility 4.5 ASP.NET 3.5 ASP.NET 4.5 ISAPI Extensins ISAPI Filters.NET Framewrk Default prts The fllwing table shws default prts that must be pen t enable cmmunicatin between Prtal cmpnents installed as a distributed system (recmmended). System Prt Cmmunicatin Prtal and ptinal legacy Web CentralCntrl UI (frnt-end) Outbund: 6502 Outbund: Outbund: 1433 Outbund: 80 Outbund: 1433 T AMP Prxy T Web service (prpagatin) (back-end) T Database T EVault Reprts tken manager (if used) T EVault Reprts database (if used) AMP prxy Outbund: 80 T Web services (back-end) Outbund: 1433 Inbund: 6502 Inbund: 8087 T Database Frm User interface Frm Web service (prpagatin) (back-end) Frm Agents (cmputers) Redirectr Outbund:80 T Web services Page 13

14 System Prt Cmmunicatin Outbund: 1433 Inbund: 8086 T Database Frm Agents Databases Frm User interface Inbund: 1433 Frm AMP prxy Frm Redirectr Web services, including Ntificatin, Registratin, and Prpagatin (back-end) Status page (if used) Agents (cmputers) Outbund: 6502 Inbund: Inbund: 80 Outbund: 80 Outbund: 1433 Outbund: 8087 Outbund: 8086 Frm Status page (if used) T AMP prxy Frm User interface Frm AMP prxy Frm Redirectr Frm Status page (if used) T Web services T Database T AMP prxy T Redirectr Page 14

15 2.3 SQL Server requirements Fr new Prtal installatins, a supprted Micrsft SQL Server versin must be installed and running, with the fllwing requirements: SQL Server Optin Instance feature Authenticatin Cllatin Instance name Requirement Database Engine Services Mixed Mde (SQL Server and Windws authenticatin) Any case-insensitive cllatin Any instance name; n restrictins SQL Server shuld be installed n a system that is nt externally visible, cnfigured with default settings, and ready fr use. When SQL Server and Prtal services are installed n different servers, TCP/IP must be enabled fr the database instance. SQL credentials must als be specified fr cnnecting t the database frm remte servers. During installatin, yu must specify a user fr cnnecting t SQL Server. This user must have permissin t access the master, mdel, Msdb and tempdb databases. (DBOwner) When Windws authenticatin is used fr cnnecting t SQL Server during installatin, the sysadmin server rle must be enabled fr the NT AUTHORITY/SYSTEM lgin. Prtal can use the same SQL Server instance as EVault Reprts. Hwever, fr scalability and envirnments with many Agents and vaults, it is preferable t use separate SQL Server instances fr Prtal and EVault Reprts. Page 15

16 3 Install Prtal EVault recmmends installing Prtal as a distributed system, with cmpnents n multiple systems. See Install Prtal n a distributed system. Yu can als install all Prtal cmpnents n ne machine. The single system is nt recmmended, but can be used fr envirnments with fewer than 500 Agents. See Install Prtal n a single system. Nte: Beginning with Versin 7.61, Prtal is installed using a single installatin kit. 3.1 Install Prtal n a distributed system T install Prtal n a distributed system, d the fllwing: Install back-end system cmpnents. Back-end system cmpnents include the databases, Ntificatin service, Registratin service, and Prpagatin service. Install frnt-end system cmpnents. Frnt-end system cmpnents include the Prtal UI and ptinal legacy Web CentralCntrl UI. Install prxy systems. Install the AMP Prxy n each prxy system, and install the Redirectr n ne f the prxy systems Install back-end system cmpnents When installing Prtal n a distributed system, yu must first install the back-end system cmpnents: Databases Ntificatin service Registratin service Prpagatin service The website where the Ntificatin and Registratin services are installed must nly be accessible frm within the lcal netwrk (specifically, frm the systems where the Prxy and the Redirectr are installed). It must nt be available ver the internet. The Agents d nt need t cnnect t these services directly. T install back-end system cmpnents: 1. On the system where yu want t install back-end Prtal cmpnents, run the Prtal installatin kit. 2. On the Welcme page, click Next. 3. On the View Ntes page, click Next. Page 16

17 4. On the License Agreement page, read the license agreement. Select I accept the terms f the license agreement, and then click Next. 5. On the SQL Server Setup page, chse the SQL Server instance where the databases will be installed. Specify the authenticatin methd, and then click Next. Yu can ptinally click Test Cnnectin t validate yur cnnectin with the database server. Nte: The SQL Server instance must have been installed with mixed mde authenticatin. The database can be installed using Windws authenticatin. The SQL Server instance must nt cntain existing EVaultWeb, WebCC, UserManagement, r SiteManagement databases. 6. On the Select Features page, select the fllwing cmpnents, and then click Next: SQL Databases Nte: The Task Service is installed with the SQL databases. Ntificatin Service Registratin Service Prpagatin Service 7. On the Ntificatin and Registratin Cnfiguratin page, enter the IP address that the Prxy and Redirectr will use t access the Ntificatin and Registratin services, and then click Next. Page 17

18 8. On the Ntificatin Service Lcatins and Virtual Directry page, specify the fllwing Ntificatin service infrmatin, and then click Next: Installatin lcatin Lg file lcatin. Fr security reasns, the lg files shuld nt be under the same path where the Ntificatin service is installed. Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, recrd it. Yu will need t enter it when installing the prxy. 9. On the Registratin Service Lcatins and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, recrd it. Yu will need t enter it when installing the prxy. 10. On the Services/Supprt Files page, specify the lcatin fr installing services and supprt files, and then click Next. 11. In the cnfirmatin dialg bx, click Yes. After the cmpnents are installed, a Cmpnent Status page appears. This page indicates which cmpnents have been installed and which cmpnents need t be installed befre the system will be peratinal. The page als indicates if ne f the cmpnents is nt at the same versins as the ther cmpnents and will need t be upgraded. Cmpnents which are currently installed, but are nt up t the current versin, may shw as missing. Page 18

19 T save a cpy f the Cmpnent Status infrmatin, enter a lcatin fr saving the file, and then click Save. 12. Click Next. 13. On the Prtal Installatin Successful page, click Finish Install frnt-end system cmpnents After installing back-end system cmpnents n ne server in a distributed system, yu can install frnt-end system cmpnents n anther server. Frnt-end cmpnents include the Prtal UI and the ptinal legacy Web CentralCntrl UI. The fllwing cmpnents are als installed when yu install the Prtal UI: Prtal Service Cnnectr, Hst Prtect Service, and Task Scheduler. If yu install the legacy Web CentralCntrl UI, users can access the Web CentralCntrl UI frm the Prtal sign in page by selecting the Sign in t legacy Web CentralCntrl interface check bx. If yu want t hide this check bx, see Hide the legacy interface check bx. T install frnt-end system cmpnents: 1. On the system where yu want t install frnt-end Prtal cmpnents, run the Prtal installatin kit. 2. On the Welcme page, click Next. Page 19

20 3. On the View Ntes page, click Next. 4. On the License Agreement page, read the license agreement. Select I accept the terms f the license agreement, and then click Next. 5. On the SQL Server Setup page, specify the SQL Server instance where the databases are installed. Specify the authenticatin methd, and then click Next. Yu can ptinally click Test t validate yur cnnectin with the database server. 6. On the Select Features page, select Prtal UI. If yu als want t install the legacy Web CentralCntrl interface, select Web CentralCntrl UI. Click Next. 7. On the Language Selectin page, select languages fr displaying Prtal text, and then click Next. In additin t the default English, yu can select French, German, Spanish, and Prtuguese. The selected languages will als be available in the legacy Web CentralCntrl UI, if it is installed. If yu d nt install a language nw, yu can add it later by rerunning the installatin in Mdify mde. Yu can als remve a language this way. 8. On the Dmain Name page, specify the Prtal dmain name and prt, and then click Next. On this page, yu can prvide the dmain name fr Prtal, as well as the prtcl t use (http/https). This is the address which yur end users will use t cnnect t Prtal. Nte: Beginning in versin 7.61, Prtal and the legacy Web CentralCntrl UI are accessed using the same dmain name. Fr example, if Prtal is accessed using Web CentralCntrl culd be accessed using Page 20

21 It is highly recmmended that https be used. Fr a seamless user experience, a signed certificate shuld be applied t the website where this applicatin is installed. This will need t be dne after the installatin is cmplete. When cnfiguring the system fr external access, the dmain name that is prvided here shuld be the name which is registered n the internet fr Prtal. If the system is being set up befre external access is cnfigured, the applicatin will nly wrk after yu successfully set up the dmain name that has been prvided here. If the dmain name changes after installatin, the installed cmpnents will need t be manually updated. 9. On the Prtal Select Installatin and Lg Paths page, specify the Prtal installatin lcatin and Lgs lcatin, and then click Next. 10. On the Prtal Service Cnnectr Lcatin and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. 11. On the Hst Prtect Lcatin and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. 12. On the Task Scheduler Select Installatin Path page, specify the Task Scheduler installatin lcatin and lg file lcatin, and then click Next. 13. If yu are installing the legacy Web CentralCntrl UI, cmplete the fllwing steps (i t iv): i) On the Lgin Lcatins and Virtual Directry page, specify the fllwing infrmatin, and then click Next. Installatin lcatin Lg file lcatin. Fr security reasns, the lg file lcatin shuld nt be under the lcatin where the Lgin website is installed. Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, recrd it. Yu will need t enter it when installing the prxy. This cmpnent prvides the lgin prtal t Web CentralCntrl. This virtual directry will be part f the URL the users will see when they use yur applicatin. The breakdwn f the URL t cnnect t this applicatin is as fllws: Page 21

22 http(s)://<dmainname>/<virtualdirectry>/lgin.aspx Nte that the default here, Lgin, is deliberately different frm the default ERLgin directry name that EVault Reprts uses. If yu install bth prducts n ne server, and any Virtual Directry Names are the same, ne will verwrite the ther. Yu will nt have this prblem if they are n different machines. ii) On the Backup Cnsle Lcatins and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, make a nte f it as it will need t be prvided during the installatin f the prxies. iii) On the Prpagatin Service Lcatin page, enter the netwrk address and prt fr the Prpagatin service, installed n the back-end system. iv) On the Integrate Legacy Web CentralCntrl with EVault Reprts page, yu can ptinally chse t integrate the legacy Web CentralCntrl UI with EVault Reprts. If yu integrate Web CentralCntrl with EVault Reprts, users can see the Reprting tab in the legacy Web CentralCntrl UI. Page 22

23 Nte: Althugh this integratin is ptinal, it is easy t give yur users access t EVault Reprts. Web CentralCntrl authenticatin (lgin) infrmatin can nw be used t allw EVault Reprts access withut requiring additinal lgin credentials fr EVault Reprts. The recmmended integratin is using the Web CentralCntrl Authenticatin. Fr this t wrk, the EVault Reprts must have been installed using Lgin/Tken Manager authenticatin. As well, yu must als assciate Custmer shrt name values (frm the vault) and Reprt Grup Name values (frm EVault Reprts Manager) with Web CentralCntrl cmpanies. Fr mre infrmatin, see Integrate with EVault Reprts. If yu integrate Web CentralCntrl and EVault Reprts, yu are asked fr EVault Reprts URLs. Fr the integratin t wrk, EVault Reprts must already be installed, and yu must prvide crrect URLs fr the EVault Reprts installatin. The Reprt Viewer URL is used fr end users wh have access t reprts. When these users click the Reprting tab in Web CentralCntrl, they are redirected t the EVault Reprts URL where they can run reprts fr their cmpany. The Subscriptin (Reprt Manager) URL is used fr super users. When these users click the Reprt Administratin tab in Web CentralCntrl, they are redirected t the EVault Reprts Manager site, where they can cnfigure subscriptins and reprt grups. The Tken Manager Service URL is nly required if yu have selected the Web CentralCntrl Authenticatin lgin methd fr integrating Web CentralCntrl with EVault Reprts. If EVault Reprts is nt installed, r yu prvide incrrect EVault Reprts URLs, end users will see messages such as the fllwing: Page 23

24 Nte: EVault Reprts is a separate installatin. See the EVault Reprts User Guide fr detailed infrmatin. Imprtant: EVault Reprts cmpnents shuld nt be installed int the Prtal website. 14. In the cnfirmatin dialg bx, click Yes. After the cmpnents are installed, a Cmpnent Status page appears. This page indicates which cmpnents have been installed, and which cmpnents need t be installed befre the system will be peratinal. The page als indicates if ne f the cmpnents is nt at the same versins as the ther cmpnents and will still need t be upgraded. Cmpnents which are currently installed, but are nt up t the current versin, may shw as missing. T save a cpy f the Cmpnent Status infrmatin, enter a lcatin fr saving the file, and then click Save. 15. Click Next. 16. On the Prtal Installatin Successful page, click Finish. A dialg bx asks if yu want t pen a brwser t the Prtal lgin page. Page 24

25 3.1.3 Install the Prxy and Redirectr When installing Prtal n a distributed system, the final system t be installed is the Prxy/Redirectr system. Only a single Redirectr service needs t be installed, but multiple prxy systems can be setup fr the same Prtal envirnment. Each prxy supprts up t 1000 Agent cnnectins. The Redirectr and any Prxies installed need t be accessible by all Agents cnnecting t yur envirnment. Fr envirnments which will supprt bth lcal netwrk (LAN) internet cnnected Agents, all Agents need t have access t the same dmain names/ip addresses fr the Prxy. T install the Prxy and Redirectr: 1. On the server where yu want t install the Prxy, run the Prtal installatin kit. 2. On the Welcme page, click Next. 3. On the View Ntes page, click Next. 4. On the Sftware License Agreement page, read the license agreement. Select I accept the terms f the license agreement, and then click Next. 5. On the SQL Server Setup page, specify the SQL Server instance where the databases are installed, and prvide SQL credentials fr the remte database. Click Next. Yu can ptinally click Test t validate yur cnnectin with the database server. 6. On the Select Features page, select AMP Prxy. If yu als want t install the Redirectr, select AMP Redirectr Service. Click Next. Page 25

26 7. On the AMP Service Cnfiguratin page, enter the web address f the Ntificatin service, and then click Next. The recmmendatin is t use the internal IP address f the system where the Ntificatin service is installed in the URL. This will avid any issues with the name reslving t an IPV6 IP address instead f an IPV4 address. The Prxy is unable t cnnect t the Ntificatin service when using an IPV6 address. 8. On the Cnfigure AMP Prxy page, specify the AMP Prxy dmain name and IP address, and then click Next. The dmain name prvided here shuld be the name that is accessible and reslvable by all Agents. Fr cnfiguratins where the Agents will be lcated utside yur netwrk, this address wuld be the external dmain name registered fr yur envirnment. Fr cnfiguratins where the Agents are nly lcated within yur lcal netwrk (LAN), the name can be the system name fr the system where the Prxy is installed. The address that is prvided fr the Prtal is the internal IP address fr the system where the prxy installed. 9. On the AMP Redirectr Service Cnfiguratin page, enter the Registratin Service web address, and then click Next. The same recmmendatins given fr the Ntificatin service als apply t the registratin service. 10. On the Services/Supprt Files page, enter the lcatin fr installing services and supprt files, and then click Next. 11. In the cnfirmatin dialg bx, click Yes. Page 26

27 After the cmpnents are installed, a Cmpnent Status page appears. This page indicates which cmpnents have been installed and which cmpnents need t be installed befre the system will be peratinal. The page als indicates if ne f the cmpnents is nt at the same versins as the ther cmpnents and will still need t be upgraded. Cmpnents which are currently installed, but are nt up t the current versin, may shw as missing. T save a cpy f the Cmpnent Status infrmatin, enter a lcatin fr saving the file, and then click Save. 12. Click Next. 13. On the Prtal Installatin Successful page, click Finish. At this pint it is recmmended that yu validate the installatin. See System validatin fr the steps t d this. If all that is successful then the installatin is functinal and ready t g. If there are any prblems, see Trubleshting and Maintenance fr pssible slutins. 3.2 Install Prtal n a single system Yu can install all Prtal cmpnents n a single server. Hwever, this cnfiguratin is nly suitable fr small deplyments (fewer than 500 Agents). T install Prtal n a single system: 1. Run the Prtal installatin kit. Page 27

28 2. On the Welcme page, click Next. 3. On the View Ntes page, click Next. 4. On the License Agreement page, read the license agreement. Select I accept the terms f the license agreement, and then click Next. 5. On the SQL Server Setup page, chse the SQL Server instance where the databases will be installed. Specify the authenticatin methd, and then click Next. Yu can ptinally click Test Cnnectin t validate yur cnnectin with the database server. Nte: The SQL Server instance must have been installed with mixed mde authenticatin. The database can be installed using Windws authenticatin. The database cannt cntain existing EVaultWeb, WebCC, UserManagement, r SiteManagement databases. 6. On the Select Features page, select the fllwing items, and then click Next. SQL Databases Nte: The Task Service is installed with the SQL databases. Prtal UI Ntificatin Service AMP Prxy AMP Redirectr Service Registratin Service Prpagatin Service (ptinal legacy) Web CentralCntrl UI Page 28

29 7. On the Language Selectin page, select languages fr displaying Prtal text, and then click Next. In additin t the default English, yu can select French, German, Spanish, and Prtuguese. The selected languages will als be available in the legacy Web CentralCntrl UI, if it is installed. If yu d nt install a language, yu can add it later by rerunning the installatin in Mdify mde. Yu can als remve a language this way. 8. On the Dmain Name page, specify the Prtal dmain name and prt, and then click Next. On this page, yu can prvide the dmain name fr Prtal, as well as the prtcl t use (http/https). This is the address which yur end users will use t cnnect t Prtal. Nte: Beginning in versin 7.61, Prtal and the legacy Web CentralCntrl UI are accessed using the same dmain name. Fr example, if Prtal is accessed using Web CentralCntrl culd be accessed using It is highly recmmended that https be used. Fr a seamless user experience, a signed certificate shuld be applied t the website where this applicatin is installed. This will need t be dne after the installatin is cmplete. When cnfiguring the system fr external access, the dmain name that is prvided here shuld be the name which is registered n the internet fr Prtal. If the system is being set up befre external access is cnfigured, the applicatin will nly wrk after yu successfully set up the dmain name that has been prvided here. If the dmain name changes after installatin, the installed cmpnents will need t be manually updated. Page 29

30 9. On the Prtal Select Installatin and Lg Paths page, specify the Prtal installatin lcatin and Lgs lcatin, and then click Next. 10. On the Prtal Service Cnnectr Lcatin and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. 11. On the Hst Prtect Lcatins and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. 12. On the Task Scheduler Select Installatin Path page, specify the Task Scheduler installatin lcatin and lg file lcatin, and then click Next. 13. If yu are installing the legacy Web CentralCntrl UI, cmplete the fllwing steps (i t iii): i) On the Lgin Lcatins and Virtual Directry page, specify the fllwing infrmatin, and then click Next. Installatin lcatin Lg file lcatin. Fr security reasns, the lg file lcatin shuld nt be under the lcatin where the Lgin website is installed. Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, recrd it. Yu will need t enter it when installing the prxy. This cmpnent prvides the lgin prtal t Web CentralCntrl. This virtual directry will be part f the URL the users will see when they use yur applicatin. The breakdwn f the URL t cnnect t this applicatin is as fllws: http(s)://<dmainname>/<virtualdirectry>/lgin.aspx Nte that the default here, Lgin, is deliberately different frm the default ERLgin directry name that EVault Reprts uses. If yu install bth prducts n ne server, and any Virtual Directry Names are the same, ne will verwrite the ther. Yu will nt have this prblem if they are n different machines. ii) On the Backup Cnsle Lcatins and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Page 30

31 Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, make a nte f it as it will need t be prvided during the installatin f the prxies. iii) On the Integrate Legacy Web CentralCntrl with EVault Reprts page, yu can ptinally chse t integrate the legacy Web CentralCntrl UI with EVault Reprts. If yu integrate Web CentralCntrl with EVault Reprts, users can see the Reprting tab in the legacy Web CentralCntrl UI. Nte: Althugh this integratin is ptinal, it is easy t give yur users access t EVault Reprts. Web CentralCntrl authenticatin (lgin) infrmatin can nw be used t allw EVault Reprts access withut requiring additinal lgin credentials fr EVault Reprts. The recmmended integratin is using the Web CentralCntrl Authenticatin. Fr this t wrk, the EVault Reprts must have been installed using Lgin/Tken Manager authenticatin. As well, yu must als assciate Custmer shrt name values (frm the Page 31

32 vault) and Reprt Grup Name values (frm EVault Reprts Manager) with Web CentralCntrl cmpanies. Fr mre infrmatin, see Integrate with EVault Reprts. If yu integrate Web CentralCntrl and EVault Reprts, yu are asked fr EVault Reprts URLs. Fr the integratin t wrk, EVault Reprts must already be installed, and yu must prvide crrect URLs fr the EVault Reprts installatin. The Reprt Viewer URL is used fr end users wh have access t reprts. When these users click the Reprting tab in Web CentralCntrl, they are redirected t the EVault Reprts URL where they can run reprts fr their cmpany. The Subscriptin (Reprt Manager) URL is used fr super users. When these users click the Reprt Administratin tab in Web CentralCntrl, they are redirected t the EVault Reprts Manager site, where they can cnfigure subscriptins and reprt grups. The Tken Manager Service URL is nly required if yu have selected the Web CentralCntrl Authenticatin lgin methd fr integrating Web CentralCntrl with EVault Reprts. If EVault Reprts is nt installed, r yu prvide incrrect EVault Reprts URLs, end users will see messages such as the fllwing: Nte: EVault Reprts is a separate installatin. See the EVault Reprts User Guide fr detailed infrmatin. Imprtant: EVault Reprts cmpnents shuld nt be installed int the Prtal website. 14. On the Ntificatin Service Lcatins and Virtual Directry page, specify the fllwing Ntificatin service infrmatin, and then click Next: Installatin lcatin Lg file lcatin. Fr security reasns, the lg files shuld nt be under the same path where the Ntificatin service is installed. Page 32

33 Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, recrd it. Yu will need t enter it when installing the prxy. 15. On the Registratin Service Lcatins and Virtual Directry page, specify the fllwing infrmatin, and then click Next: Installatin lcatin Lg file lcatin Virtual Directry Name. Change this name if it will cnflict with anther already installed website/service. If yu change the virtual directry name, recrd it. Yu will need t enter it when installing the prxy. 16. On the AMP Prxy IP Cnfiguratin page, specify the AMP Prxy dmain name and IP address, and then click Next. The dmain name prvided here shuld be the name that is accessible and reslvable by all Agents. Fr cnfiguratins where the Agents will be lcated utside yur netwrk, this address wuld be the external dmain name registered fr yur envirnment. Fr cnfiguratins where the Agents are nly lcated within yur lcal netwrk (LAN), the name can be the system name fr the system where the Prxy is installed. The address that is prvided fr the Prtal is the internal IP address fr the system where the prxy installed. 17. On the Services/Supprt Files page, enter the lcatin fr installing services and supprt files, and then click Next. 18. In the cnfirmatin dialg bx, click Yes. After the cmpnents are installed, a Cmpnent Status page appears. This page indicates which cmpnents have been installed and which cmpnents need t be installed befre the system will be peratinal. The page als indicates if ne f the cmpnents is nt at the same versins as the ther cmpnents and will still need t be upgraded. Cmpnents which are currently installed, but are nt up t the current versin, may shw as missing. Page 33

34 T save a cpy f the Cmpnent Status infrmatin, enter a lcatin fr saving the file, and then click Save. 19. Click Next. 20. On the Prtal Installatin Successful page, click Finish. A dialg bx asks if yu want t pen a brwser t the Prtal lgin page. At this pint it is recmmended that yu validate the installatin. See System validatin fr the steps t d this. If all that is successful then the installatin is functinal and ready t g. If there are any prblems, see Trubleshting and Maintenance fr pssible slutins. Page 34

35 4 Integrate Prtal with EVault Reprts Prtal can be integrated with EVault Reprts. T allw yur users t access EVault Reprts, yu need t assciate Custmer shrt name values (frm the vault) and Reprt Grup Name values (frm EVault Reprts Manager) with Prtal sites and Web CentralCntrl cmpanies. If these values are nt prperly cnfigured, users cannt access reprts thrugh Prtal r the legacy Web CentralCntrl UI, even if EVault Reprts has been integrated. Yu can assciate custmer shrt names with reprt grup names using Prtal r the legacy Web CentralCntrl UI. Yu must enable and set up reprts in Prtal befre the Reprts tab will appear. Nte: If EVault Reprts is integrated with Web CentralCntrl versin 7.60 r earlier, and yu upgrade t Prtal and Web CentralCntrl versin 7.61 r later, yu must update the Web CentralCntrl URL in the ReprtViewer and ReprtManager web.cnfig files fr EVault Reprts. Fr mre infrmatin, see Update the Web CentralCntrl URL fr EVault Reprts. 4.1 Assciate custmer shrt names using Prtal T assciate custmer shrt names using Prtal: 1. Lg in t Prtal as a super user. 2. On the navigatin bar, click Sites. 3. In the grid, pen the site by clicking its rw. 4. Click the Shrt Names tab. 5. In the Shrt Name t add bx, type the shrt name (frm the vault) t assciate with the site. 6. Click Add. 7. Click Save. Page 35

36 4.2 Assciate custmer shrt names using Web CentralCntrl T assciate custmer shrt names using Web CentralCntrl: 1. In Web CentralCntrl, g t Accunt Management and select a cmpany. 2. Click Edit. The Edit Cmpany screen pens. 3. Click Reprt Settings. The Reprt settings screen pens. 4. In the Cmpany shrt name field, enter the value f a Custmer shrt name (frm the vault). This assciates the cmpany with specific reprts. 5. Click Add. The value that yu have entered appears in the Cmpany shrt name list. Use the Add and Remve buttns t cntinue updating the list. 6. Enter a value fr the Reprt grup name field. This value must exactly match a Reprt Grup Name in EVault Reprts. The Reprt grup name can be <DEFAULT> (which allws users t access all reprts), but this is nly apprpriate if <DEFAULT> remains as a Reprt Grup Name in EVault Reprts. Click Save t return t the Edit Cmpany screen. 7. Click Save again. Nw the users in the cmpany can access the reprts that are assciated with their Cmpany shrt name and Reprt grup name settings. Fr details abut Custmer shrt name values frm the vault, and Reprt Grup Name settings in EVault Reprts, refer t the Directr Operatins Guide and the EVault Reprts User Guide. Page 36

37 5 Cnfigure Prtal 5.1 Encrypt the view state ASP.NET view state is the technique used by an ASP.NET web page t preserve changes t the state f a Web Frm acrss pstbacks. The view state represents the state f the page when it was last prcessed n the server. View state makes the use f the Web Frms mdel pssible. By default with.net, the view state is verified but nt encrypted. Yu must take sme manual steps t encrypt the view state. Yu must encrypt the view state fr bth the Lgin site and the BackupCnsle site. Nte: If Prtal is running n a web farm, different steps are required t set up view state encryptin n the web farm. See Cnfigure a web farm. T encrypt the view state: 1. Find the web.cnfig file fr the Lgin site and fr the BackupCnsle site. By default, the Lgin site web.cnfig file is in C:\inetpub\wwwrt\Lgin. By default, the BackupCnsle site web.cnfig file is in C:\inetpub\wwwrt\BackupCnsle. 2. In each web.cnfig file, lcate the fllwing line: <pages enableviewstatemac= true validaterequest= false > 3. In each web.cnfig file, add the fllwing in the pages element: viewstateencryptinmde= Always The resulting pages element will be: <pages viewstateencryptinmde= Always enableviewstatemac= true validaterequest= false > 4. Save each web.cnfig file. 5.2 Cnfigure a web farm A web farm uses multiple web servers t distribute yur UI prcessing lad acrss several servers. If yu need mre prcessing pwer, yu can simply add anther server withut needing t change yur Prtal cnfiguratin r installatin. The web farm uses a virtual IP address (t which yur UI applicatin pints) that is then reslved int physical addresses fr the servers. The Agents must be registered t the IP f the cmputer hsting the AMP Redirectr service. Page 37

38 The Administratr is respnsible fr installing and cnfiguring the web farm. This includes setting the IP addresses, masks and gateways, and Netwrk Lad Balancing. These functins are nt cvered here. The installatin is dne in tw parts. One server (which is nt part f the farm) has all the cmpnents except the UI applicatin installed. The servers in the farm are then each installed with their wn cpies f the UI applicatin n each server. There can be multiple AMP Prxy servers, each f which can supprt up t 1000 registered Agents. Each AMP Prxy shuld be installed n its wn system (nt the UI system). All cmpnents n a web farm must be the same versin. If yu are upgrading, yu must upgrade all cmpnents n all servers t the same versin. Nte: The UI Web applicatin can supprt up t 50 cncurrent user cnnectins per server. If yu need mre, yu must use a web farm fr multiple servers. Nte: The Lad Balancer must be cnfigured t use sticky sessins. T cnfigure a web farm: 1. Install the Ntificatin Service, Registratin Service, SQL Server, and Prpagatin Service, all n ne machine (nt a part f the farm). This server des nt expse anything t the internet s des nt need t be accessible by the Agents. 2. Install the Prxy and Redirectr n a server which is externally accessible. Run the installatin n each machine. Select Custm Installatin, and chse the AMP Prxy and Redirectr features t install. Agents will need t cnnect t this server ver prts 8086 and If yu have mre than 1000 Agents cnnecting t this envirnment, yu will need t set up additinal prxies. Each prxy shuld be n its wn system. 3. Install the UI cmpnent n each f the farm servers. Run the installatin n each machine. Select Custm Installatin, and chse nly the User Interface feature t install. 4. Encrypt the View State fr the legacy Web CentralCntrl web sites next. All cmputers in the web farm with the WebCentralCntrl UI applicatin installed must have the same view state encryptin settings. T encrypt the view state, mdify the web.cnfig f the Lgin and BackupCnsle web applicatins n each UI installatin n the web farm: C:\inetpub\wwwrt\BackupCnsle and C:\inetpub\wwwrt\Lgin In the web.cnfig file, lcate the <system.web> sectin which is under the <cnfiguratin> sectin. There will be a line like the fllwing : <pages enableviewstatemac= true validaterequest= false > add the fllwing in the pages element: viewstateencryptinmde= Always Page 38

39 The resulting pages element will be: <pages viewstateencryptinmde= Always enableviewstatemac= true validaterequest= false > T ensure that all Web CentralCntrl sites can decrypt the view state, the machine key needs t be the same n all websites invlved in the farm. T d this, n ne system in the farm, pen the IIS Manager. Select the Lgin website and under the Features View, duble click n Machine key (in the ASP.NET sectin). On the page that pens, uncheck the Autmatically generate at runtime and Generate a unique key fr each applicatin ptins fr bth the validatin key and decryptin key sectins. Fr the Encryptin Methd, select SHA1. Fr the decryptin methd, select AES. Then click Generate Keys and Apply. Open the Web.cnfig file fr this applicatin and lcate the line in the file that starts with <machine key Cpy this line and paste it int the web.cnfig file fr the Lgin and BackupCnsle web applicatins n all servers in the web farm (including the BackupCnsle n the system where yu just mdified the Lgin website s web.cnfig file). The line shuld be put after the line </pages> in the web cnfig file. This will ensure it is in the crrect sectin f the file (<cnfiguratin> <system.web>) If yu view the Machine Key settings thrugh the IIS manager fr any f thse websites after saving the web.cnfig file, yu shuld see that all f the sites n all f the systems have the exact same settings with the exact same keys. Page 39

40 5. When using Prtal in a web farm cnfiguratin, all f the Prtal UIs invlved require the same machine key element in their cnfig files. Typically, the Prtal uses sticky sessins, s the nly change required t the Prtal cnfig files is the additin f the machinekey element. T d this, n ne system in the farm, pen the IIS Manager. Select Prtal Website and under the Features View, duble click n Machine key (in the ASP.NET sectin). On the page that pens, uncheck the Autmatically generate at runtime and Generate a unique key fr each applicatin ptins fr bth the validatin key and decryptin key Page 40

41 sectins. Fr the Encryptin Methd, select SHA1. Fr the decryptin methd, select AES. Then click Generate Keys and Apply. Open the Web.cnfig file fr this applicatin and lcate the line in the file that starts with <machine key Cpy this line and paste it int the web.cnfig file fr the Prtal Website n all servers in the web farm. The line shuld be put after the line </pages> in the web cnfig file. This will ensure it is in the crrect sectin f the file (<cnfiguratin> <system.web>) If yu view the Machine Key settings thrugh the IIS manager fr any f thse web sites after saving the web.cnfig file, yu shuld see that all f the sites n all f the systems have the exact same settings with the exact same keys. Page 41

42 5.3 Hide the legacy interface check bx If yu d nt want users t access the legacy Web CentralCntrl interface, yu can remve the Sign int the legacy Web CentralCntrl interface check bx frm the Prtal Sign In page. T hide the legacy interface check bx: 1. Open the web.cnfig file fr the Prtal. 2. Find the ExternalURi entry in the web.cnfig file. 3. Remve the value frm the entry. The resulting line shuld be: <add key= ExternalUri value= /> 5.4 Change the frm text in reprt s By default, reprt s include the fllwing sentence: Yu have received a reprt frm prtal.evault.cm. Yu can replace prtal.evault.cm in this sentence with any text value. T change the frm text in reprt s: 1. Open the web.cnfig file fr the Prtal. 2. Find the ReprtTemplateFrmURL entry in the web.cnfig file: <add key= ReprtTemplateFrmURL value= prtal.evault.cm /> 3. Replace prtal.evault.cm in this line with replacement text that yu want t appear in the Enable and set up reprts in Prtal T enable and set up reprts in Prtal: 1. Lg in t Prtal as a super user. 2. On the navigatin bar, click Glbal Settings. 3. Click the Reprt Settings tab. 4. On the Reprt Settings tab, select Enable Reprts tab. Page 42

43 5. In the Cnnectivity sectin, enter reprts database infrmatin and SQL Server credentials. 6. In the Tken Manager Cnfiguratin sectin, enter the URL fr the Tken Manager service. 7. In the Ntificatins sectin, enter an address fr sending a ntificatin if a custmer shrtname is missing. Custmer shrt name values (frm the vault) must be assciated with Reprt Grup Name values (frm EVault Reprts Manager). 8. Click Save. Page 43

44 5.6 Cnfigure single sign-n (SSO) By default, users are created in Prtal and authenticated thrugh a web frm. Hwever, users can be managed and authenticated using an external federated identity server (e.g., Active Directry Federatin Services). A Prtal instance can use nly ne authenticatin methd at a time: either Prtal web frm r federated identity server. Nte: If a Prtal instance is cnfigured t use Active Directry authenticatin, this cnfiguratin is intended t be permanent. If an instance must be changed frm federated identity server t Prtal web frm authenticatin, user recrds must be recreated in Prtal. When a federated identity server is used, a user is directed t the external server fr authenticatin. Once authenticated, the user is directed back t Prtal with a SAML tken. The tken includes infrmatin frm the identity server fr autmatically creating a user in Prtal. This autmatically-created user specifies the user s type and rights in Prtal. It cannt be used t sign in t Prtal. Infrmatin fr an autmatically-created user in Prtal is nt necessarily up-t-date with infrmatin in the federated identity server. Fr example, if a user is deleted frm Active Directry, the crrespnding user is nt autmatically deleted frm Prtal. The fllwing requirements must be met fr Prtal single sign-n: The federated identity server must supprt WS-Federatin (e.g., Active Directry Federatin Services). Prtal must be cnfigured t use the federated identity server. See Cnfigure Prtal t use a federated identity server. The SAML tken must cntain all f the infrmatin required t autmatically create r update the crrespnding user in Prtal. See Username in the SAML tken, User rle in the SAML tken, User site in the SAML tken, and SAML tken/expected claims Cnfigure Prtal t use a federated identity server T cnfigure Prtal t use a federated identity server, make the fllwing changes in the Prtal web.cnfig file: Disable frms authenticatin Enable federated authenticatin, which will handle incming SAML tkens Cnfigure identity prvider settings IMPORTANT: Other cnfiguratin changes may be required, depending n the identity server that yu use. T cnfigure Prtal t use a federated identity server: 1. Lcate the Prtal Web.cnfig file. By default, this file is saved in c:\inetpub\prtal Website. 2. Open the Prtal Web.cnfig file in a text editr. Page 44

45 3. Disable frms authenticatin by ding the fllwing: a) Lcate the fllwing lines: <authenticatin mde="frms"> <frms lginurl="~/accunt/lgon" timeut="30" /> </authenticatin> b) Replace the lines shwn abve with the fllwing lines: <authenticatin mde="nne" /> <authrizatin> <deny users="?" /> </authrizatin> 4. Enable federated authenticatin by ding the fllwing: a) Lcate the <add name="httprespnseheadersanitizer" > line. b) Directly after the <add name="httprespnseheadersanitizer" > line, add the fllwing lines: <remve name="frmsauthenticatin" /> <add name="wsfederatinauthenticatinmdule" type="evault.web.ui.wsfederatinauthenticatin, EVault.Web.UI" precnditin="managedhandler" /> 5. Cnfigure identity prvider settings by ding the fllwing: a) Lcate the </cnfiguratin> line. b) Directly befre </cnfiguratin> line, add the fllwing sectin: <system.identitymdel> <identitycnfiguratin> <claimsauthenticatinmanager type="evault.web.ui.claimstransfrmer, EVault.Web.UI"/> <audienceuris> <add value="yuraudienceuri" /> </audienceuris> <certificatevalidatin certificatevalidatinmde="chaintrust" /> <issuernameregistry type="system.identitymdel.tkens.validatingissuernameregistry, System.IdentityMdel.Tkens.ValidatingIssuerNameRegistry"> <authrity name="yurissuersiteid"> <keys> <add thumbprint="yurissuersigningcertificatethumbprint" /> </keys> <validissuers> <add name="yurissuersiteid" /> </validissuers> </authrity> </issuernameregistry> </identitycnfiguratin> </system.identitymdel> <system.identitymdel.services> Page 45

46 <federatincnfiguratin> <ckiehandler requiressl="true" /> <wsfederatin passiveredirectenabled="true" issuer="yurissuerurlpassiveredirectinuri" realm="yuraudienceuri" requirehttps="true" /> </federatincnfiguratin> </system.identitymdel.services> c) Replace the highlighted variables with the apprpriate values fr yur envirnment: yuraudienceuri is the Prtal installatin URI. yurissuerurlpassiveredirectinuri is the navigable URL f yur identity prvider. This value can be fund in the federatin metadata in the fllwing element: SingleSignOutNtificatinEndpint/EndpintReference/Address yurissuersiteid is the cnfigured URI f the issuer sent within SAML tken (smetimes referred t as Site ID ). This value can be fund in the federatin metadata in the entityid attribute f the EntityDescriptr element. yurissuersigningcertificatethumbprint is the IdP signing certificate thumbprint. It must be entered in uppercase with n dashes (e.g., 886B8DC3498FF93A8D0B844DC2F E7EE51 ). The IdP signing certificate must be installed n any machine where the Hst Prtect Service is installed. See Install IdP Signing Certificate n the machine where Prtal is installed. 6. If yu are using a self-signed certificate fr testing, disable certificate revcatin checking by ding the fllwing: a) Lcate the <certificatevalidatin line added in Step 5: <certificatevalidatin certificatevalidatinmde="chaintrust" /> b) Replace the line shwn abve with the fllwing line: <certificatevalidatin certificatevalidatinmde="chaintrust" revcatinmde="ncheck" /> 7. Save the Prtal Web.cnfig file Install IdP Signing Certificate n the machine where Prtal is installed Fr Prtal single sign-n, the Identity Prvider signing certificate must be installed n the machine where Prtal is installed. If Prtal is installed as a distributed system, the certificate must be installed n each machine where the Hst Prtect Service is installed. Page 46

47 5.6.3 Username in the SAML tken The username will be retrieved frm the fllwing attribute in the SAML tken: AttributeName="username" AttributeNamespace=" The suggested frmats fr username are: User Principal Name (UPN) - e.g., user@dmain.cm User Lgn Name - e.g., user Windws Accunt Name - e.g., dmain\user Due t Agent limitatins, it is best t keep t avid spaces and apstrphes in user names. Fr this reasn, the UPN frmat is recmmended. T ensure cmpatibility with the single sign-n implementatin in Prtal versins 7.70 and 7.62, if the username attribute is nt present, the username shuld be retrieved frm the fllwing attribute: EVaultPrtalUserName This attribute can be present in any namespace. If this attribute is nt present, use the default name attribute: AttributeName="name" AttributeNamespace=" ms" User rle in the SAML tken A user s rle in Prtal can be determined based n grup membership r anther Active Directry schema attribute. A custmer can use their existing grup structure, and map their existing (r new) rles t a specific prtal claim, using ADFS claim transfrmatin. The benefit f this apprach is that when using prper federatin with many external issuers (cmpnents that actually authenticate users), and a single federatin prvider (cmpnent that generates final SAML tken fr Prtal), the transfrmatin can be dne in ne place (federatin prvider) rather than requiring the same schema fr every issuer. Here is a wrking example f a claim as passed in the SAML tken t Prtal: <saml:attribute AttributeName="Rle" AttributeNamespace=" <saml:attributevalue>superuser</saml:attributevalue> <saml:attributevalue>supprt</saml:attributevalue> </saml:attribute> In this case, tw rles are passed t Prtal. If multiple rles are passed, Prtal will pick the mstprivileged rle User site in the SAML tken The current single sign-n implementatin is nt intended fr Prtal instances with many sites. Hwever, because there culd be mre than ne site in a Prtal instance, the SAML tken fr a Page 47

48 user must include a site identifier. When a user signs in t Prtal, the identifier will be matched with the existing site name in Prtal t retrieve its ID. Nte: Site names must be pre-ppulated in Prtal. <saml:attribute AttributeName="SiteName" AttributeNamespace=" <saml:attributevalue>data Factry Cmpany</saml:AttributeValue> </saml:attribute> The alternate way t prvide this infrmatin wuld be t prvide the SiteId attribute. This wuld crrespnd t CmpanyID in Web CentralCntrl, as shwn belw: <saml:attribute AttributeName="SiteId" AttributeNamespace=" <saml:attributevalue>22efa16b-32d c70- EFCDAAF38F02</saml:AttributeValue></saml:Attribute> If present, this attribute will take precedence and verride any value passed in a SiteName claim. It safer t use the SiteId attribute than the SiteName attribute, as thse IDs are unique and less likely t change SAML tken/expected claims This sectin lists the claims that Prtal will expect in the SAML tken. Username This is the user name. It culd be in address frmat (UPN), but it can als be lgn name (username) r windws accunt name (dmain\username) AttributeName="username" AttributeNamespace=" Here is sample claim transfrmatin rule fr UPN name: c:[type == " name", Issuer == "AD AUTHORITY"] => issue(stre = "Active Directry", types = (" query = ";userprincipalname;{0}", param = c.value); User Id This is the unique, nn-changing identifier f the user. AttributeName="userid" AttributeNamespace=" If the same value is passed in as username, it will be impssible t change the user name withut lsing the user identity. (Anew user wuld be created in Prtal). It is suggested t use LDAP bjectguid prperty fr this claim. Here is the example f that rule: Page 48

49 c:[type == " name", Issuer == "AD AUTHORITY"] => issue(stre = "Active Directry", types = (" query = ";bjectguid;{0}", param = c.value); First name This is the user first name: AttributeName="firstname" AttributeNamespace=" Last name This is the user last name: AttributeName="lastname" AttributeNamespace=" Name This is the username. This is standard claim, and is smetimes passed by the federatin prvider withut the ability t be verwritten by the username in frmat. Fr this reasn, this claim will be used nly if the username claim abve is nt prvided. This claim is ptinal and is prcessed fr backwards cmpatibility nly. If prvided, this shuld crrespnd t the AD UPN name ( frmat). AttributeName="name" AttributeNamespace=" claims" Rle This claim can cntain multiple values frm the fllwing list: SuperUser SupprtUser Admin, User ExecuteOnly ReadOnly AttributeName="rle" AttributeNamespace=" This claim can be ppulated by list f claim transfrmatin rules that will set up given rles based n AD grup membership, fr example: Page 49

50 c:[type == " Value == "S ", Issuer == "AD AUTHORITY"] => issue(type = " Value = "SuperUser", Issuer = c.issuer, OriginalIssuer = c.originalissuer, ValueType = c.valuetype); Site name This claim cntains the user s site name: AttributeName="sitename" AttributeNamespace=" When there is nly ne site, this value can be hardcded in the claim transfrmatin rule t the active site. Fr example: => issue(type = " Value = "Big Data Cmpany"); Site Id This ptinal claim cntains the site GUID (Web CentralCntrl Cmpany Id) fr the user site. If present, this will take precedence ver site name, allwing mre secure user t site assciatin. AttributeName="siteid" AttributeNamespace=" Here is example f usage: => issue(type = " Value = "B0ADAD3F-D66A A0-2C0BB14A4942"); User aut-prvisining This claim specifies whether user aut-prvisining shuld happen r nt. The pssible values wuld be true and false. If the claim is nt present, aut-prvisining will be disabled. This is prvided fr backwards-functinality. Fr new custmers, this claim shuld always be passed as True: AttributeName="userautprvisining" AttributeNamespace=" Here is a sample claim transfrmatin rule: => issue(type = " Value = "true"); Page 50

51 5.6.7 Trubleshting single sign-n Issue 1: After lgging ff Prtal, the ADFS sign-ut page appears. Hwever, if the Prtal URL is entered again withut restarting the brwser, the user is autmatically lgged in again. Why des this happen? Answer: Even thugh all authenticatin ckies are cleared prperly, this happens because the brwser caches authenticatin credentials t ADFS until the brwser is restarted. This can be verified by investigating sent headers with Firebug - ntice the Authrizatin NTLM header being sent. Yu can als manually clear authenticatin credentials in Firefx by pressing Ctrl+Shift+Del and chsing Active Lgins. This will frce ADFS t reauthenticate. In nrmal perating scenaris, we recmmend that users shuld clse the brwser after lgging ff ADFS t ensure that credentials are nt cached. Issue 2: When trying t sign in t Prtal, an errr page appears. The lgs state that the prblem ccurs because f a username that already exists. Answer: This culd ccur if a user with the same name was already created fr use with frms authenticatin (Prtal web frm authenticatin), r if a user with the same name was set up fr federated authenticatin (external user) but with a different external user id. If the riginal user is n lnger needed, it can be deleted by the super user. The new user will then be able t lgin successfully. Alternatively, the new user s username can be changed t avid duplicatin. Page 51

52 6 Mdify Prtal Yu can change which Prtal cmpnents are installed n a server by running the Prtal installatin kit. This can be useful if Prtal was installed n a single system, and yu want t change it t a distributed system. See Cnvert Prtal frm a single system t a distributed system. Yu can als change the languages that are installed and specify whether the installatin shuld be integrated with EVault Reprts The installers autmatically shut dwn services n the machine where yu are mdifying cmpnents. Hwever, if Prtal is installed n a distributed system, shut dwn services n ther machines befre mdifying yur installatin. T mdify Prtal: 1. On the machine where yu want t mdify cmpnents, run the Prtal installatin kit. 2. On the Welcme page, click Mdify, and then click Next. 3. On the SQL Server Setup page, chse the SQL Server instance where the databases will be installed. Specify the authenticatin methd, and then click Next. Yu can ptinally click Test t validate yur cnnectin with the database server. The Select Features page appears. Cmpnents that are currently installed n the server are selected n this page. 4. Select the check bx fr each cmpnent that yu want t add r keep. Clear the check bx fr each cmpnent that yu want t uninstall. 5. Click Next. 6. On the remaining installatin wizard pages, prvide the required infrmatin. Wizard pages that appear depend n the cmpnents selected n the Select Features page. Fr infrmatin abut specific pages, see Install Prtal n a single system. 7. In the cnfirmatin dialg bx, click OK. After the cmpnents are installed, a Cmpnent Status page appears. This page indicates which cmpnents have been installed and which cmpnents need t be installed befre the system will be peratinal. The page als indicates if ne f the cmpnents is nt at the same versins as the ther cmpnents and will still need t be upgraded. Cmpnents which are currently installed, but are nt up t the current versin, may shw as missing. 8. Click Next. 9. Click Finish. Page 52

53 6.1 Cnvert Prtal frm a single system t a tw-server distributed system T cnvert Prtal frm a single system t a distributed system, yu can mve frnt-end cmpnents t a new server. Mving back-end Prtal cmpnents t a new server is nt recmmended, as this prcess wuld require database migratin and is mre cmplex than mving frnt-end cmpnents. In the tw-server distributed system created using this prcedure, the Prtal UI is installed n the same system as the Redirectr and Prxy. Althugh this cnfiguratin differs frm the large-scale distributed system shwn in Prtal Distributed System (recmmended), it can supprt mre Agents than when all Prtal cmpnents are installed n a single system (recmmended fr fewer than 500 Agents). A tw-server distributed system can als serve as an interim step in mving t the recmmended distributed system. Yu can later add a lad balancer and multiple Prtal UI machines, r multiple prxies. See Cnfigure a web farm. T cnvert Prtal frm a single system t a tw-server distributed system: 1. Prepare a new server fr installing Prtal frnt-end cmpnents. Fr system requirements, see Prerequisites and the Prtal release ntes. 2. On the riginal server where Prtal cmpnents are currently installed, run the Prtal installatin kit t uninstall the fllwing frnt-end cmpnents: AMP Redirectr Service AMP Prxy Prtal UI Web CentralCntrl UI (if installed) Fr mre infrmatin, see Mdify Prtal. 3. After the uninstallatin is cmplete, pen the Internet Infrmatin Services (IIS) Manager n the server where yu uninstalled Prtal frnt-end cmpnents. 4. Right-click Prtal Services Website, and chse Edit Bindings. 5. In the Site Bindings dialg bx, click , and then click the Edit buttn. 6. In the Edit Site Binding dialg bx, delete frm the Hst name bx, and d ne f the fllwing: In the IP address list, select an IP address that the new frnt-end server (prepared in Step 1) can access. In the Hst name bx, enter either the system s name r its fully qualified dmain name (FQDN). Nte: The Prt value in the Edit Site Binding dialg bx remains as Click OK t clse the Edit Site Binding dialg bx. Page 53

54 8. Click Clse t clse the Site Bindings dialg bx. 9. Restart the Prtal Services Website. 10. On the new server fr frnt-end cmpnents (prepared in Step 1), run the Prtal installatin kit t install the fllwing frnt-end cmpnents: AMP Redirectr Service AMP Prxy Prtal UI Web CentralCntrl UI (ptinal) During the installatin, n the SQL Server Setup page, specify the SQL Server instance where the Prtal databases are installed n the riginal server. On the AMP Service Cnfiguratin page, enter the IP address r hstname specified in Step 6 as the Ntificatin service web address. On the AMP Redirectr Service Cnfiguratin page, enter the IP address r hstname specified in Step 6 as the Registratin service web address. Fr mre infrmatin, see Install frnt-end system cmpnents and Install the Prxy and Redirectr. Page 54

55 7 Upgrade Prtal Yu can upgrade existing Prtal cmpnents. Upgrade back-end system cmpnents and databases befre upgrading frnt-end system cmpnents. Yu cannt directly upgrade a Web CentralCntrl installatin frm a 32-bit server t a 64-bit server, but migratin is pssible. Yu must first upgrade Web CentralCntrl cmpnents n the 32-bit platfrm and back up the Web CentralCntrl databases. Yu can then install Web CentralCntrl n a 64-bit platfrm, and restre the databases t the 64-bit system. Fr mre infrmatin, see the Web CentralCntrl Migratin Guide. Befre yu start the upgrade prcess, make sure that each system has the crrect.net and ASP.NET versins installed. 7.1 Dmain names and Agent registratins after an upgrade Beginning in versin 7.61, the legacy Web CentralCntrl UI (if installed) is hsted under the same dmain as Prtal. Previusly, there were tw recmmended cnfiguratins fr running Prtal and Web CentralCntrl side-by-side n the same system: Run them bth under the same dmain, but using different prts (i.e., prts 80/81 r 443/444). In this case, after the upgrade, the legacy Web CentralCntrl UI will run n the same dmain and prt as Prtal, using prt 80 (r 443, if using https). Prtal will be accessible directly frm the URL f the dmain (i.e., http(s)://dmain.cm/), while the legacy Web CentralCntrl UI will be accessible using the dmain and the virtual directry cnfigured fr the lgin site (i.e., In case any f yur users bkmarked Prtal r Web CentralCntrl when it was cnfigured using the alternate prt, yu shuld set up a redirect s that they will be autmatically redirected t the crrect new URL. We als recmmend that yu prvide a ntificatin n their dashbard asking them t update their bkmarks. Run each website under a different dmain. In this case, Web CentralCntrl wuld have been cnfigured t run under a separate URL frm the Prtal (e.g., webcc.dmain.cm vs. prtal.dmain.cm). After the upgrade, bth sites run under the Prtal dmain (i.e., prtal.dmain.cm). This means that any custmers wh have bkmarked the webcc.dmain.cm URL will find that their bkmarks n lnger wrk. We recmmend that yu cntinue t have the riginal dmain registered, but redirect it t the Prtal dmain. Alng with the user interfaces, the Web CentralCntrl dmain was prbably used when registering Agents. Generally, in the past, we have recmmended that the same dmain name be used fr bth the user interface and fr Agent registratin, t simplify the end-user experience. This means that all existing Agents wuld be cnfigured t cnnect t the frmer Web CentralCntrl dmain address. If yu remve that dmain, when the Agents start up, they will be Page 55

56 unable t cnnect and will appear as permanently ffline. If yu want users t register their Agents using the Prtal dmain ging frward, yu must have bth the new dmain and the riginal dmain pinting t the same registratin service (prt 8086) s that bth the existing Agents and new registratins will be able t cnnect. The riginal dmain cannt be remved unless all existing Agents are re-registered t the UI using the new dmain. 7.2 Prepare fr a Prtal upgrade Befre upgrading Prtal, make sure that users cannt access the system, shut dwn services, and back up yur databases. T prepare fr a Prtal upgrade: 1. Redirect the Lgin page t a Site under maintenance page t ensure that n users lg in during the upgrade. 2. Restart the IIS server n the frnt-end system (i.e., the system with the UI cmpnent installed) t make sure that any already lgged in users will be lgged ut. 3. Shut dwn the AMP Prxy, Prpagatin Service, and Registratin Service. 4. Back up the EVaultWeb, WebCC, UserManagement, and SiteManagement databases. 5. Check that the Prtal and Web CentralCntrl UI is unavailable t the general public. 7.3 Upgrade Prtal cmpnents On each system where Prtal r Web CentralCntrl 7.5 cmpnents are installed, yu can upgrade the installed cmpnents. Beginning in versin 7.61, Prtal and the legacy Web CentralCntrl UI are hsted under the same website, using different directries. Fr infrmatin abut hw t redirect existing bkmarks, see Redirecting Prts. Nte: T upgrade frm Web CentralCntrl 7.50 n a 32-bit perating system, yu must first upgrade Web CentralCntrl cmpnents n the 32-bit platfrm and back up the Web CentralCntrl databases. Yu can then install Web CentralCntrl n a 64-bit platfrm, and restre the databases t the 64-bit system. Fr mre infrmatin, see the Web CentralCntrl Migratin Guide. T upgrade Prtal cmpnents: 1. On the machine where Prtal cmpnents are installed, run the Prtal installatin kit. 2. On the Welcme page, click Next. 3. On the SQL Server Setup page, chse the SQL Server instance where the databases are installed. Specify the authenticatin methd, and then click Next. Yu can ptinally click Test t validate yur cnnectin with the database server. Page 56

57 4. If cnfirmatin dialg bx shws cmpnents n the system that were installed using a Web CentralCntrl installatin kit, click Yes. 5. On the remaining installatin wizard pages, prvide the required infrmatin. Wizard pages that appear depend n the cmpnents that are being upgraded n the system. Fr infrmatin abut specific pages, see Install Prtal n a single system. 6. In the cnfirmatin dialg bx, click Yes. After the cmpnents are installed, a Cmpnent Status page appears. This page indicates which cmpnents have been installed and which cmpnents need t be installed befre the system will be peratinal. 7. Click Next. 8. On the Upgrade Cmplete page, click Finish. 7.4 Update the Web CentralCntrl URL fr EVault Reprts If EVault Reprts is integrated with Web CentralCntrl versin 7.60 r earlier, and yu upgrade t Prtal and Web CentralCntrl versin 7.61 r later, yu must update the Web CentralCntrl URL in tw EVault Reprts web.cnfig files. Beginning in versin 7.61, Web CentralCntrl is accessed using the same dmain name as the Prtal. Previusly, Web CentralCntrl was accessed using a separate URL. T update the Web CentralCntrl URL fr EVault Reprts: 1. Find the web.cnfig file in each f the fllwing directries: C:\inetpub \ReprtViewer C:\inetpub\ReprtManager 2. Open each web.cnfig file in a text editr. 3. In each f web.cnfig file, d the fllwing: Find the fllwing line: <add key= BackupRecveryURl value=" BackupCnsle/Pages/Main/Dashbard.aspx?ndeid=DASHBOARD" /> Change the line in the web.cnfig file t the fllwing: <add key= BackupRecveryURl value=" BackupCnsle/Pages/Main/Dashbard.aspx?ndeid=DASHBOARD" /> Where PrtalDmainName is the fully qualified dmain name (FQDN) f the Prtal. Page 57

58 Find the fllwing line: <add key= AdministratinURl value=" Lgin/Pages/Main/userManagement.aspx" /> Change the line in each web.cnfig file t the fllwing: <add key= AdministratinURl value=" Lgin/Pages/Main/userManagement.aspx" /> Where PrtalDmainName is the fully qualified dmain name (FQDN) f the Prtal. 4. Save the web.cnfig files. 7.5 Make the upgraded Prtal available t users T make the upgraded Prtal available t users: 1. After upgrading Prtal back-end and frnt-end cmpnents, verify that the Prtal installatin is functinal. See System validatin. 2. Remve the redirectin cmpleted in Prepare fr the Prtal upgrade, and pint t the lgin lcatin previusly used fr Prtal. Nte: Users can still access the legacy Web CentralCntrl frm the Prtal lgin page by selecting the Sign in t legacy Web CentralCntrl interface check bx. If yu want t hide this check bx, see Hide the legacy interface check bx. 7.6 Rll back databases after an upgrade During an upgrade, dump files are created. These can be used t manually rll back the databases in case the upgrade fails. The databases are backed up t the fllwing files: EVaultWeb.bak WebCC_database.bak UserManagement_database.bak SiteManagement_database.bak Each dump file name als includes the date and time when the file was created. Dump files are typically saved in the fllwing lcatin: C:\WebCCDBBackup\ Dump files remain after an upgrade. Yu shuld peridically clean up the files. The database files are nt remved whether the upgrade succeeds r fails. They are nt remved during uninstallatin. They are nt created r updated when a fresh Install, Repair, r Mdify is run. Page 58

59 8 System validatin After installing the Prtal, lg in t the Prtal and validate that it is wrking crrectly. If yu installed the Web CentralCntrl UI, validate that this legacy UI is wrking crrectly as well. If yu encunter issues, see Trubleshting and Maintenance fr pssible slutins. 8.1 Validate the Prtal installatin After installing Prtal, check that the system is wrking by perfrming the fllwing tasks: Lg in t Prtal fr the first time Lg in t the legacy interface Create a site Create an Admin user Add a cmputer Add a backup jb View the Reprts tab Lg in t Prtal fr the first time A default super user is added when yu install Prtal. Yu can lg in as this super user t start validating the installatin. T lg in t Prtal fr the first time: 1. In a supprted Web brwser, g t the Prtal URL. 2. Lg in using the default super user credentials: User Name = super Passwrd = 3Vlt1nc 3. In the Change Passwrd dialg bx, enter the super user s current passwrd and new passwrd, and then click Change Passwrd. Nte: The passwrd is case-sensitive. The Prtal screen appears. Page 59

60 8.1.2 Lg in t the legacy interface The Prtal sign in page includes an ptin fr lgging in t the legacy Web CentralCntrl interface. If yu installed the legacy Web CentralCntrl interface, yu can validate that the ptin n the Prtal sign in page is wrking. Nte: Yu can hide the legacy interface check bx frm the Prtal sign in page. See Hide the legacy interface check bx. T lg in t the legacy interface: 1. In a supprted Web brwser, g t the Prtal URL. 2. Type credentials in the User name and Passwrd bxes. 3. Select the Sign in t legacy Web CentralCntrl interface check bx. The Web CentralCntrl screen appears Create a site T create a site: 1. When lgged in as the super user, click Sites n the navigatin bar. 2. Click Create New Site. The Site Details tab pens. 3. In the Parent list, click This site has n parent. 4. In the Site Name bx, enter a name fr the new site. The site name must be unique. 5. (Optinal) Enter ther site infrmatin. 6. Click Save Site. The Site Details tab clses, and the new site appears in the grid Create an Admin user Super users cannt add cmputers r manage backups in Prtal. Yu must create an Admin user t ensure that yu can perfrm these tasks in the new Prtal installatin. T create an Admin user: 1. When lgged in as the super user, click User Manager n the navigatin bar. 2. Click Create New User. 3. On the User Inf tab, in the Address (Username) bx, type the user s address. The user will lg in t Prtal using this address. Page 60

61 4. In the First Name bx, type the user s given name. 5. In the Last Name bx, type the user s surname. 6. In the Rle list, click Admin. 7. In the Site list, click the site that yu created. See Create a site. 8. In the Passwrd and Cnfirm Passwrd fields, type the user s passwrd fr lgging in t Prtal. 9. Click Create Add a cmputer T add a Windws, Linux, r UNIX cmputer in Prtal yu must install r update Agent sftware n the cmputer. When asked t register the Agent with Web CentralCntrl, enter the hst name that was entered when installing the externally accessible AMP Redirectr Service. See Install prxy systems fr distributed systems, and Install Prtal n a single system. Fr mre infrmatin abut registering an Agent with Prtal, see the specific Agent guide. T add a VMware vsphere envirnment in Prtal, use the webcc register cmmand t enter the Web CentralCntrl hst name r IP address, and prt fr cmmunicating with Prtal. Fr mre infrmatin, see the vsphere Agent User Guide. When adding a cmputer fr Prtal, yu must enter the name f the Admin user yu created. See Create an Admin user. The added cmputer appears n the Cmputers page when this user, r anther Admin user fr the site, lgs in t Prtal Add a backup jb T add a backup jb: 1. In a supprted Web brwser, g t the Prtal URL. 2. Lg in as the Admin user yu created. See Create an Admin user. 3. On the navigatin bar, click Cmputers. 4. Find the cmputer that yu added (see Add a cmputer), and expand its view by clicking the cmputer rw. 5. If yu are adding the first backup jb fr a Windws cmputer, click Cnfigure Manually. 6. On the Vault Settings tab, click Add Vault. In the Vault Settings dialg bx, enter vault infrmatin and credentials fr cnnecting t the vault. Click Save. 7. Click the Jbs tab. 8. In the Select Jb Task list, click Create New Lcal System Jb. Page 61

62 9. In the Create New Jb dialg bx, specify the fllwing infrmatin: In the Name bx, type a name fr the backup jb. In the Descriptin bx, type a descriptin fr the backup jb. In the Destinatin list, select the vault where yu want t save the backup data. In the Lg File Optins list, select the level f detail fr jb lgging. If the Encryptin Settings list appears, select an encryptin methd fr string the backup data. If the backup data will be encrypted, enter an encryptin passwrd in the Passwrd and Cnfirm Passwrd bxes. Yu can als enter a passwrd hint in the Passwrd Hint bx. 10. In the Select Files and Flders fr Backup bx, select drives, flders, and files t include in the backup jb. 11. Click Create Jb. The jb is created, and the View/Add Schedule dialg bx appears. Click Cancel if yu d nt want t create a schedule View the Reprts tab T determine whether EVault Reprts is integrated with Prtal, lg in as an Admin user, and click the Reprts tab. Reprts nly appear n the tab if EVault Reprts is integrated with Prtal. See Integrate with EVault Reprts. 8.2 Validate the Legacy Web CentralCntrl installatin If yu installed the legacy Web CentralCntrl UI, check that the system is wrking by perfrming the fllwing tasks: Lg in t Web CentralCntrl fr the first time Create a cmpany Create an Admin user Register agents Create a backup jb Prpagate an agent s settings Access EVault Reprts Page 62

63 8.2.1 Lg in t Web CentralCntrl fr the first time A default super user is added when yu install Web CentralCntrl. Yu can lg in as this super user t start validating the installatin. T lg in t Web CentralCntrl fr the first time: 1. In a supprted web brwser, g t the Prtal URL: Select the Sign int the legacy Web CentralCntrl interface check bx. Nte: Yu can hide the legacy interface check bx frm the sign in page. See Hide the legacy interface check bx. 2. Lg in using the super user credentials yu set when verifying the Prtal lgin. 3. Verify that yu are redirected t the legacy Web CentralCntrl Administratin site. The Administratin screen appears. Initially nly ne cmpany is created. The cmpany is called ADMINISTRATION, and there are n users attached t it Create a cmpany T create a cmpany: 1. When lgged in as the super user, click Add in the Cmpanies pane. 2. In the New Cmpany dialg bx, enter a name fr the new cmpany. The cmpany name must be unique. 3. (Optinal) Enter ther site infrmatin. 4. Click Save. The cmpany appears in the cmpany list Create an Admin user Super users cannt add cmputers r manage backups in the legacy Web CentralCntrl UI. Yu must create an Admin user t ensure that yu can perfrm these tasks. T create an Admin user: 1. When lgged in as the super user, click the cmpany that yu created. See Create a cmpany. 2. In the Users pane, click Add. 3. In the New User dialg bx, in the User Name bx, type the user s address. Page 63

64 The user will lg in t Web CentralCntrl using this address. 4. In the Passwrd and Cnfirm Passwrd bxes, type the user s passwrd fr lgging in t Web CentralCntrl. 5. In the Rle list, click Accunt administratr. 6. Click Add beside Vault Prfile. In the Vault Prfile dialg bx, enter vault infrmatin and credentials fr cnnecting t the vault. Click Save. 7. Click Save. 8. Verify that yu can lgin using these new credentials: In a supprted web brwser, g t the Prtal URL: Select the Sign in t the legacy Web CentralCntrl interface check bx. Nte: The legacy interface check bx can be hidden frm the sign in page. See Hide the legacy interface check bx. Prvide the Username and the Passwrd yu just created. Verify that yu are able t lg in t the Prtal site. Lg ut and select the Sign in t the legacy Web CentralCntrl interface ptin. Verify that yu are able t lg in, and are redirected t the legacy Web CentralCntrl BackupCnsle site Register Agents T register a Windws, Linux, r UNIX cmputer in Web CentralCntrl yu must install r update Agent sftware n the cmputer. When asked t register the Agent with Web CentralCntrl, enter the hst name that was entered when installing the externally accessible AMP Redirectr Service. See Install prxy systems fr distributed systems, and Install Prtal n a single system. Fr mre infrmatin abut registering an Agent with Prtal, see the specific Agent guide. T register a VMware vsphere envirnment in Prtal, use the webcc register cmmand t enter the Web CentralCntrl hst name r IP address, and prt fr cmmunicating with Web CentralCntrl. Fr mre infrmatin, see the vsphere Agent User Guide. When registering a cmputer fr Web CentralCntrl, yu must enter the name f the Admin user yu created. See Create an Admin user. The uncnfigured agent appears when this user lgs in t Web CentralCntrl. Page 64

65 8.2.5 Create a backup jb T create a backup jb: 1. In a supprted Web brwser, g t the Web CentralCntrl URL: 2. Lg in as the Admin user yu created. See Create an Admin user. 3. D ne f the fllwing: In the left pane f the screen, click the Uncnfigured Agents view. Select an agent that yu registered (see Register agents). Click the link fr cnfiguring a new agent. The Cnfigure Agent page appears. In the Agent Descriptin bx, enter an agent descriptin. Click Next. In the left pane f the screen, click the All Agents view. Select an agent that yu registered (see Register agents). In the lwer pane f the screen, click the Add menu, and then click Jb. The New Jb page appears. 4. On the Jb Type Selectin page, enter a jb name, and select the backup surce type. Click Next. 5. On the Selectin page, select files and directries t back up. Click Next. 6. On the Optins page, enter encryptin settings. Click Next. 7. On the Schedule page, click Next. 8. On the Destinatin page, select a vault destinatin. Click Save Changes Prpagate an agent s settings Befre yu can test prpagatin in a legacy Web CentralCntrl UI, yu must register mre than ne agent t Web CentralCntrl. See Register agents. T prpagate an agent s settings: 1. In a supprted Web brwser, g t the Web CentralCntrl URL: 2. Lg in as the Admin user yu created. See Create an Admin user. 3. Select an agent that yu registered (see Register agents). 4. In the Edit menu, click Prpagate Agent Settings. 5. On the Prpagate Agent Settings page, chse Agent settings t prpagate t anther Agent. Click Next. 6. In the Agents List, click the Agent t which yu want t prpagate settings. Page 65

66 7. Click Add Selected Agent. 8. Click Prpagate Access EVault Reprts If EVault Reprts is installed and integrated with Web CentralCntrl, a Reprting Administratin tab appears beside the Administratin tab when yu are lgged in as a Super user. The Reprting Administratin feature places a tab beside the regular Administratin tab. Yu will nt see this if yu d nt have the Reprting Administratin feature installed. This feature allws the Super user t give Administratrs, r Administratrs and Users (r n ne) access t EVault Reprts. The "Reprting Administratin" tab takes yu t the EVault Reprts site. Page 66

67 9 Trubleshting and Maintenance This sectin describes issues that yu might encunter when installing and managing Prtal and the ptinal legacy Web CentralCntrl UI, and prvides suggestins fr reslving issues and maintaining Prtal. 9.1 Redirecting Prts Issue: Prtal r Web CentralCntrl was previusly re-cnfigured t use nn-default prts, and users have bkmarks which use thse nn-default prts. After upgrade t versin 7.61 r later, bth the Prtal and Web CentralCntrl websites use the default prts. Slutin: Create a website which listens n the riginal (nn-default) prt and redirects the user t the default prt Open IIS Manager Under Sites right click and Add Web Site Cnfigure the website as belw: The Physical Path shuld pint t a directry which has n ther websites in it. It is recmmended t create a new directry fr this site. The Hst Name shuld be the name that was previusly cnfigured fr the website yu wish t redirect (i.e., the site that was previusly Page 67