Bocada 19.2 Installation Guide€¦ · • ASP.NET 3.5 and higher • The Data Collection Server...
Transcript of Bocada 19.2 Installation Guide€¦ · • ASP.NET 3.5 and higher • The Data Collection Server...
1 Bocada Installation Guide
Version 192 Installation Guide
2 Bocada Installation Guide
Copyright copy 2019 Bocada LLC All Rights Reserved Bocada and BackupReport are registered trademarks of Bocada LLC Vision Prism vpConnect and the Bocada logo are trademarks of Bocada LLC Other product names mentioned herein may be trademarks or registered trademarks of their respective companies Protected by US patents 6640217 6708188 6745210 7457833 7469269 7496614 8407227 The material in this manual is for information only and is subject to change without notice While efforts have been made to ensure accuracy Bocada LLC assumes no liability resulting from errors or omissions in this document or from the use of information contained herein Bocada LLC reserves the right to make changes in the product design and documentation without reservation and without notification to its users
3 Bocada Installation Guide
Contents Introduction 4
Pre-Installation Checklist 4
Minimum System Requirements 4
Hardware 5
Supported Browsers 5
Regional Settings 5
SQL Server 6
Data Collection Server 6
Application Server 7
Firewall Port Requirements 9
Pre-installation 10
Download Latest Version 10
Planning 11
Hardware and Software Requirements 12
Release Notes 12
License Key 13
Installation 13
Data Collection Service 14
Application Server 24
Configure HTTPS Certificate 32
Deploying the Certificate 32
Upgrade 33
Accessing the Application 34
Adding Bocada License 35
General Settings 36
Technical Support 37
Appendices 38
Appendix A Database Troubleshooting 38
Appendix B Windows Services and User Management 40
Appendix C Website Setup 41
Appendix D Windows Server Roles amp Features 43
4 Bocada Installation Guide
Introduction
This document describes the requirements and instructions for installing Bocada Please discuss Bocada configuration options with your Bocada Sales or Support Engineer should you need further clarity You will need at minimum one Windows Server which will host
bull Microsoft SQL Server
bull Bocada Data Collection Services
bull Bocada Web Application running on Microsoft IIS Web Server
Pre-Installation Checklist
Detailed requirements for installation are in other sections of this document Please use this checklist to verify that you are ready for the installation
HardwareVM with adequate Disk RAM and CPU (see below for details)
Windows with supported OS versions and settings (see below for details)
Microsoft SQL Server installed
Bocada server(s) added to the Windows Active Directory domain
Service login to install and run the Bocada Services including required SQL permissions
SQL Server User with required credentials
Microsoft IIS server role installed
Firewalls open between Bocada components as needed
Firewalls open between Bocada Data Collection Service(s) and backup servers See Plugin Configuration Guides for details
Supported web browser (see below for details)
Bocada Installation software
Bocada license key (please contact salesbocadacom regarding licensing)
Version Specific Note
Bocada 191 and beyond incorporates security upgrades which require an updated version of a component that must be installed manually
bull Microsoft SQL Native Client for communication with SQL Server 2012 or earlier
httpswwwmicrosoftcomen-usdownloaddetailsaspxid=50402
We are addressing this issue moving forward and upcoming releases of Bocada will handle this
automatically during installation
Minimum System Requirements
The following describe the minimum required to run the Bocada product Virtual servers are supported for the application and data collection servers
5 Bocada Installation Guide
Hardware For an initial deployment of Bocada the following are considered a minimum
bull 2 CoresCPU
bull 12 GB RAM
bull 250 GB Disk space Bocada recommends that the SQL Server be placed on a server separate from where the Bocada software is installed for any long-term production deployment
Supported Browsers The following browsers are supported for use with this version of the Bocada application
bull Chrome (up to 71x)
bull Firefox (up to 64x)
bull Internet Explorer (11x 10x)
When using Internet Explorer IE Enhanced Security must be turned off in order for all Bocada reports to run properly Internet Explorer versions prior to 100 are not supported and some features will be unavailable The most current version of Firefox and Chrome at the time of release are supported older versions of these browsers may work as well but are not officially supported
Regional Settings The regional setting for the Application Data Collection and SQL Servers must be set to English (United States) and the date format set to MMDDYYYY Please check any Windows group policies that may govern this setting
6 Bocada Installation Guide
SQL Server
Software
Microsoft SQL Server (Standard or Enterprise edition not Express or Developer) versions
bull Microsoft SQL Server 2016
bull Microsoft SQL Server 2014
bull Microsoft SQL Server 2012 ndash all SPs
bull Microsoft SQL Server 2008 R2 ndash SP1 SP2 SP3
bull Microsoft SQL Server 2008 SP2
SQL Server Notes
bull Do not create a database prior to installation The Installer will create the Bocada database during installation of the Data Collection server
bull The SQL Server user credentials used to perform the installation (or upgrade) of the Bocada database must be a member of the lsquodborsquo schema and have the db_creator role for permission to create that database
bull The user account used during installation must be assigned to the lsquodborsquo schema as the
Default Schema This can be verified through SQL Server Management Studio in the
Login Properties window for that user (in User Mapping)
Data Collection Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 35 Framework
bull NET 45 Framework
bull ASPNET 35 and higher
bull The Data Collection Server must be part of a Domain (not necessarily the same domain
as the backup servers) application users (and various other features) leverage Active
Directory Domain Services
7 Bocada Installation Guide
Application Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 45 Framework
bull Internet Information Services IIS (latest supported version)
bull Configured to use Windows Authentication
bull Configured to allow IIS 60 metabase compatibility
bull ASPNET 35 and higher
bull ASPNET 20 set to ldquoAllowedrdquo
bull The following Roles from Server Manager must be installed
bull Web Server Common HTTP features (ALL)
bull Web Server Application Development (ALL)
bull Web Server Security (Basic and Windows Authentication)
bull Management Tools IIS Management Console
bull Management Tools IIS 6 Management Compatibility (IIS 6 Metabase Compatibility
and IIS 6 Management Console)
bull The following Features from Server Manager must be installed
bull NET Framework 35 Features (NET Framework 35 (includes NET 20 and 30) and
HTTP Activation)
bull NET Framework 46 Features (NET Framework 46 ASPNET 46 WCF Services
(TCP Port Sharing))
bull Please see Appendix D Windows Server Roles amp Features for screenshots of the Roles
and Features for different versions of Windows Server
bull The Application Server must be part of a Domain and should be within the same
Domain as the Data Collection Server Application users (and various other features)
leverage Active Directory Domain Services
bull The Bocada Application Server must have SMTP connectivity to the mail server to send email
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
2 Bocada Installation Guide
Copyright copy 2019 Bocada LLC All Rights Reserved Bocada and BackupReport are registered trademarks of Bocada LLC Vision Prism vpConnect and the Bocada logo are trademarks of Bocada LLC Other product names mentioned herein may be trademarks or registered trademarks of their respective companies Protected by US patents 6640217 6708188 6745210 7457833 7469269 7496614 8407227 The material in this manual is for information only and is subject to change without notice While efforts have been made to ensure accuracy Bocada LLC assumes no liability resulting from errors or omissions in this document or from the use of information contained herein Bocada LLC reserves the right to make changes in the product design and documentation without reservation and without notification to its users
3 Bocada Installation Guide
Contents Introduction 4
Pre-Installation Checklist 4
Minimum System Requirements 4
Hardware 5
Supported Browsers 5
Regional Settings 5
SQL Server 6
Data Collection Server 6
Application Server 7
Firewall Port Requirements 9
Pre-installation 10
Download Latest Version 10
Planning 11
Hardware and Software Requirements 12
Release Notes 12
License Key 13
Installation 13
Data Collection Service 14
Application Server 24
Configure HTTPS Certificate 32
Deploying the Certificate 32
Upgrade 33
Accessing the Application 34
Adding Bocada License 35
General Settings 36
Technical Support 37
Appendices 38
Appendix A Database Troubleshooting 38
Appendix B Windows Services and User Management 40
Appendix C Website Setup 41
Appendix D Windows Server Roles amp Features 43
4 Bocada Installation Guide
Introduction
This document describes the requirements and instructions for installing Bocada Please discuss Bocada configuration options with your Bocada Sales or Support Engineer should you need further clarity You will need at minimum one Windows Server which will host
bull Microsoft SQL Server
bull Bocada Data Collection Services
bull Bocada Web Application running on Microsoft IIS Web Server
Pre-Installation Checklist
Detailed requirements for installation are in other sections of this document Please use this checklist to verify that you are ready for the installation
HardwareVM with adequate Disk RAM and CPU (see below for details)
Windows with supported OS versions and settings (see below for details)
Microsoft SQL Server installed
Bocada server(s) added to the Windows Active Directory domain
Service login to install and run the Bocada Services including required SQL permissions
SQL Server User with required credentials
Microsoft IIS server role installed
Firewalls open between Bocada components as needed
Firewalls open between Bocada Data Collection Service(s) and backup servers See Plugin Configuration Guides for details
Supported web browser (see below for details)
Bocada Installation software
Bocada license key (please contact salesbocadacom regarding licensing)
Version Specific Note
Bocada 191 and beyond incorporates security upgrades which require an updated version of a component that must be installed manually
bull Microsoft SQL Native Client for communication with SQL Server 2012 or earlier
httpswwwmicrosoftcomen-usdownloaddetailsaspxid=50402
We are addressing this issue moving forward and upcoming releases of Bocada will handle this
automatically during installation
Minimum System Requirements
The following describe the minimum required to run the Bocada product Virtual servers are supported for the application and data collection servers
5 Bocada Installation Guide
Hardware For an initial deployment of Bocada the following are considered a minimum
bull 2 CoresCPU
bull 12 GB RAM
bull 250 GB Disk space Bocada recommends that the SQL Server be placed on a server separate from where the Bocada software is installed for any long-term production deployment
Supported Browsers The following browsers are supported for use with this version of the Bocada application
bull Chrome (up to 71x)
bull Firefox (up to 64x)
bull Internet Explorer (11x 10x)
When using Internet Explorer IE Enhanced Security must be turned off in order for all Bocada reports to run properly Internet Explorer versions prior to 100 are not supported and some features will be unavailable The most current version of Firefox and Chrome at the time of release are supported older versions of these browsers may work as well but are not officially supported
Regional Settings The regional setting for the Application Data Collection and SQL Servers must be set to English (United States) and the date format set to MMDDYYYY Please check any Windows group policies that may govern this setting
6 Bocada Installation Guide
SQL Server
Software
Microsoft SQL Server (Standard or Enterprise edition not Express or Developer) versions
bull Microsoft SQL Server 2016
bull Microsoft SQL Server 2014
bull Microsoft SQL Server 2012 ndash all SPs
bull Microsoft SQL Server 2008 R2 ndash SP1 SP2 SP3
bull Microsoft SQL Server 2008 SP2
SQL Server Notes
bull Do not create a database prior to installation The Installer will create the Bocada database during installation of the Data Collection server
bull The SQL Server user credentials used to perform the installation (or upgrade) of the Bocada database must be a member of the lsquodborsquo schema and have the db_creator role for permission to create that database
bull The user account used during installation must be assigned to the lsquodborsquo schema as the
Default Schema This can be verified through SQL Server Management Studio in the
Login Properties window for that user (in User Mapping)
Data Collection Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 35 Framework
bull NET 45 Framework
bull ASPNET 35 and higher
bull The Data Collection Server must be part of a Domain (not necessarily the same domain
as the backup servers) application users (and various other features) leverage Active
Directory Domain Services
7 Bocada Installation Guide
Application Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 45 Framework
bull Internet Information Services IIS (latest supported version)
bull Configured to use Windows Authentication
bull Configured to allow IIS 60 metabase compatibility
bull ASPNET 35 and higher
bull ASPNET 20 set to ldquoAllowedrdquo
bull The following Roles from Server Manager must be installed
bull Web Server Common HTTP features (ALL)
bull Web Server Application Development (ALL)
bull Web Server Security (Basic and Windows Authentication)
bull Management Tools IIS Management Console
bull Management Tools IIS 6 Management Compatibility (IIS 6 Metabase Compatibility
and IIS 6 Management Console)
bull The following Features from Server Manager must be installed
bull NET Framework 35 Features (NET Framework 35 (includes NET 20 and 30) and
HTTP Activation)
bull NET Framework 46 Features (NET Framework 46 ASPNET 46 WCF Services
(TCP Port Sharing))
bull Please see Appendix D Windows Server Roles amp Features for screenshots of the Roles
and Features for different versions of Windows Server
bull The Application Server must be part of a Domain and should be within the same
Domain as the Data Collection Server Application users (and various other features)
leverage Active Directory Domain Services
bull The Bocada Application Server must have SMTP connectivity to the mail server to send email
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
3 Bocada Installation Guide
Contents Introduction 4
Pre-Installation Checklist 4
Minimum System Requirements 4
Hardware 5
Supported Browsers 5
Regional Settings 5
SQL Server 6
Data Collection Server 6
Application Server 7
Firewall Port Requirements 9
Pre-installation 10
Download Latest Version 10
Planning 11
Hardware and Software Requirements 12
Release Notes 12
License Key 13
Installation 13
Data Collection Service 14
Application Server 24
Configure HTTPS Certificate 32
Deploying the Certificate 32
Upgrade 33
Accessing the Application 34
Adding Bocada License 35
General Settings 36
Technical Support 37
Appendices 38
Appendix A Database Troubleshooting 38
Appendix B Windows Services and User Management 40
Appendix C Website Setup 41
Appendix D Windows Server Roles amp Features 43
4 Bocada Installation Guide
Introduction
This document describes the requirements and instructions for installing Bocada Please discuss Bocada configuration options with your Bocada Sales or Support Engineer should you need further clarity You will need at minimum one Windows Server which will host
bull Microsoft SQL Server
bull Bocada Data Collection Services
bull Bocada Web Application running on Microsoft IIS Web Server
Pre-Installation Checklist
Detailed requirements for installation are in other sections of this document Please use this checklist to verify that you are ready for the installation
HardwareVM with adequate Disk RAM and CPU (see below for details)
Windows with supported OS versions and settings (see below for details)
Microsoft SQL Server installed
Bocada server(s) added to the Windows Active Directory domain
Service login to install and run the Bocada Services including required SQL permissions
SQL Server User with required credentials
Microsoft IIS server role installed
Firewalls open between Bocada components as needed
Firewalls open between Bocada Data Collection Service(s) and backup servers See Plugin Configuration Guides for details
Supported web browser (see below for details)
Bocada Installation software
Bocada license key (please contact salesbocadacom regarding licensing)
Version Specific Note
Bocada 191 and beyond incorporates security upgrades which require an updated version of a component that must be installed manually
bull Microsoft SQL Native Client for communication with SQL Server 2012 or earlier
httpswwwmicrosoftcomen-usdownloaddetailsaspxid=50402
We are addressing this issue moving forward and upcoming releases of Bocada will handle this
automatically during installation
Minimum System Requirements
The following describe the minimum required to run the Bocada product Virtual servers are supported for the application and data collection servers
5 Bocada Installation Guide
Hardware For an initial deployment of Bocada the following are considered a minimum
bull 2 CoresCPU
bull 12 GB RAM
bull 250 GB Disk space Bocada recommends that the SQL Server be placed on a server separate from where the Bocada software is installed for any long-term production deployment
Supported Browsers The following browsers are supported for use with this version of the Bocada application
bull Chrome (up to 71x)
bull Firefox (up to 64x)
bull Internet Explorer (11x 10x)
When using Internet Explorer IE Enhanced Security must be turned off in order for all Bocada reports to run properly Internet Explorer versions prior to 100 are not supported and some features will be unavailable The most current version of Firefox and Chrome at the time of release are supported older versions of these browsers may work as well but are not officially supported
Regional Settings The regional setting for the Application Data Collection and SQL Servers must be set to English (United States) and the date format set to MMDDYYYY Please check any Windows group policies that may govern this setting
6 Bocada Installation Guide
SQL Server
Software
Microsoft SQL Server (Standard or Enterprise edition not Express or Developer) versions
bull Microsoft SQL Server 2016
bull Microsoft SQL Server 2014
bull Microsoft SQL Server 2012 ndash all SPs
bull Microsoft SQL Server 2008 R2 ndash SP1 SP2 SP3
bull Microsoft SQL Server 2008 SP2
SQL Server Notes
bull Do not create a database prior to installation The Installer will create the Bocada database during installation of the Data Collection server
bull The SQL Server user credentials used to perform the installation (or upgrade) of the Bocada database must be a member of the lsquodborsquo schema and have the db_creator role for permission to create that database
bull The user account used during installation must be assigned to the lsquodborsquo schema as the
Default Schema This can be verified through SQL Server Management Studio in the
Login Properties window for that user (in User Mapping)
Data Collection Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 35 Framework
bull NET 45 Framework
bull ASPNET 35 and higher
bull The Data Collection Server must be part of a Domain (not necessarily the same domain
as the backup servers) application users (and various other features) leverage Active
Directory Domain Services
7 Bocada Installation Guide
Application Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 45 Framework
bull Internet Information Services IIS (latest supported version)
bull Configured to use Windows Authentication
bull Configured to allow IIS 60 metabase compatibility
bull ASPNET 35 and higher
bull ASPNET 20 set to ldquoAllowedrdquo
bull The following Roles from Server Manager must be installed
bull Web Server Common HTTP features (ALL)
bull Web Server Application Development (ALL)
bull Web Server Security (Basic and Windows Authentication)
bull Management Tools IIS Management Console
bull Management Tools IIS 6 Management Compatibility (IIS 6 Metabase Compatibility
and IIS 6 Management Console)
bull The following Features from Server Manager must be installed
bull NET Framework 35 Features (NET Framework 35 (includes NET 20 and 30) and
HTTP Activation)
bull NET Framework 46 Features (NET Framework 46 ASPNET 46 WCF Services
(TCP Port Sharing))
bull Please see Appendix D Windows Server Roles amp Features for screenshots of the Roles
and Features for different versions of Windows Server
bull The Application Server must be part of a Domain and should be within the same
Domain as the Data Collection Server Application users (and various other features)
leverage Active Directory Domain Services
bull The Bocada Application Server must have SMTP connectivity to the mail server to send email
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
4 Bocada Installation Guide
Introduction
This document describes the requirements and instructions for installing Bocada Please discuss Bocada configuration options with your Bocada Sales or Support Engineer should you need further clarity You will need at minimum one Windows Server which will host
bull Microsoft SQL Server
bull Bocada Data Collection Services
bull Bocada Web Application running on Microsoft IIS Web Server
Pre-Installation Checklist
Detailed requirements for installation are in other sections of this document Please use this checklist to verify that you are ready for the installation
HardwareVM with adequate Disk RAM and CPU (see below for details)
Windows with supported OS versions and settings (see below for details)
Microsoft SQL Server installed
Bocada server(s) added to the Windows Active Directory domain
Service login to install and run the Bocada Services including required SQL permissions
SQL Server User with required credentials
Microsoft IIS server role installed
Firewalls open between Bocada components as needed
Firewalls open between Bocada Data Collection Service(s) and backup servers See Plugin Configuration Guides for details
Supported web browser (see below for details)
Bocada Installation software
Bocada license key (please contact salesbocadacom regarding licensing)
Version Specific Note
Bocada 191 and beyond incorporates security upgrades which require an updated version of a component that must be installed manually
bull Microsoft SQL Native Client for communication with SQL Server 2012 or earlier
httpswwwmicrosoftcomen-usdownloaddetailsaspxid=50402
We are addressing this issue moving forward and upcoming releases of Bocada will handle this
automatically during installation
Minimum System Requirements
The following describe the minimum required to run the Bocada product Virtual servers are supported for the application and data collection servers
5 Bocada Installation Guide
Hardware For an initial deployment of Bocada the following are considered a minimum
bull 2 CoresCPU
bull 12 GB RAM
bull 250 GB Disk space Bocada recommends that the SQL Server be placed on a server separate from where the Bocada software is installed for any long-term production deployment
Supported Browsers The following browsers are supported for use with this version of the Bocada application
bull Chrome (up to 71x)
bull Firefox (up to 64x)
bull Internet Explorer (11x 10x)
When using Internet Explorer IE Enhanced Security must be turned off in order for all Bocada reports to run properly Internet Explorer versions prior to 100 are not supported and some features will be unavailable The most current version of Firefox and Chrome at the time of release are supported older versions of these browsers may work as well but are not officially supported
Regional Settings The regional setting for the Application Data Collection and SQL Servers must be set to English (United States) and the date format set to MMDDYYYY Please check any Windows group policies that may govern this setting
6 Bocada Installation Guide
SQL Server
Software
Microsoft SQL Server (Standard or Enterprise edition not Express or Developer) versions
bull Microsoft SQL Server 2016
bull Microsoft SQL Server 2014
bull Microsoft SQL Server 2012 ndash all SPs
bull Microsoft SQL Server 2008 R2 ndash SP1 SP2 SP3
bull Microsoft SQL Server 2008 SP2
SQL Server Notes
bull Do not create a database prior to installation The Installer will create the Bocada database during installation of the Data Collection server
bull The SQL Server user credentials used to perform the installation (or upgrade) of the Bocada database must be a member of the lsquodborsquo schema and have the db_creator role for permission to create that database
bull The user account used during installation must be assigned to the lsquodborsquo schema as the
Default Schema This can be verified through SQL Server Management Studio in the
Login Properties window for that user (in User Mapping)
Data Collection Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 35 Framework
bull NET 45 Framework
bull ASPNET 35 and higher
bull The Data Collection Server must be part of a Domain (not necessarily the same domain
as the backup servers) application users (and various other features) leverage Active
Directory Domain Services
7 Bocada Installation Guide
Application Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 45 Framework
bull Internet Information Services IIS (latest supported version)
bull Configured to use Windows Authentication
bull Configured to allow IIS 60 metabase compatibility
bull ASPNET 35 and higher
bull ASPNET 20 set to ldquoAllowedrdquo
bull The following Roles from Server Manager must be installed
bull Web Server Common HTTP features (ALL)
bull Web Server Application Development (ALL)
bull Web Server Security (Basic and Windows Authentication)
bull Management Tools IIS Management Console
bull Management Tools IIS 6 Management Compatibility (IIS 6 Metabase Compatibility
and IIS 6 Management Console)
bull The following Features from Server Manager must be installed
bull NET Framework 35 Features (NET Framework 35 (includes NET 20 and 30) and
HTTP Activation)
bull NET Framework 46 Features (NET Framework 46 ASPNET 46 WCF Services
(TCP Port Sharing))
bull Please see Appendix D Windows Server Roles amp Features for screenshots of the Roles
and Features for different versions of Windows Server
bull The Application Server must be part of a Domain and should be within the same
Domain as the Data Collection Server Application users (and various other features)
leverage Active Directory Domain Services
bull The Bocada Application Server must have SMTP connectivity to the mail server to send email
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
5 Bocada Installation Guide
Hardware For an initial deployment of Bocada the following are considered a minimum
bull 2 CoresCPU
bull 12 GB RAM
bull 250 GB Disk space Bocada recommends that the SQL Server be placed on a server separate from where the Bocada software is installed for any long-term production deployment
Supported Browsers The following browsers are supported for use with this version of the Bocada application
bull Chrome (up to 71x)
bull Firefox (up to 64x)
bull Internet Explorer (11x 10x)
When using Internet Explorer IE Enhanced Security must be turned off in order for all Bocada reports to run properly Internet Explorer versions prior to 100 are not supported and some features will be unavailable The most current version of Firefox and Chrome at the time of release are supported older versions of these browsers may work as well but are not officially supported
Regional Settings The regional setting for the Application Data Collection and SQL Servers must be set to English (United States) and the date format set to MMDDYYYY Please check any Windows group policies that may govern this setting
6 Bocada Installation Guide
SQL Server
Software
Microsoft SQL Server (Standard or Enterprise edition not Express or Developer) versions
bull Microsoft SQL Server 2016
bull Microsoft SQL Server 2014
bull Microsoft SQL Server 2012 ndash all SPs
bull Microsoft SQL Server 2008 R2 ndash SP1 SP2 SP3
bull Microsoft SQL Server 2008 SP2
SQL Server Notes
bull Do not create a database prior to installation The Installer will create the Bocada database during installation of the Data Collection server
bull The SQL Server user credentials used to perform the installation (or upgrade) of the Bocada database must be a member of the lsquodborsquo schema and have the db_creator role for permission to create that database
bull The user account used during installation must be assigned to the lsquodborsquo schema as the
Default Schema This can be verified through SQL Server Management Studio in the
Login Properties window for that user (in User Mapping)
Data Collection Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 35 Framework
bull NET 45 Framework
bull ASPNET 35 and higher
bull The Data Collection Server must be part of a Domain (not necessarily the same domain
as the backup servers) application users (and various other features) leverage Active
Directory Domain Services
7 Bocada Installation Guide
Application Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 45 Framework
bull Internet Information Services IIS (latest supported version)
bull Configured to use Windows Authentication
bull Configured to allow IIS 60 metabase compatibility
bull ASPNET 35 and higher
bull ASPNET 20 set to ldquoAllowedrdquo
bull The following Roles from Server Manager must be installed
bull Web Server Common HTTP features (ALL)
bull Web Server Application Development (ALL)
bull Web Server Security (Basic and Windows Authentication)
bull Management Tools IIS Management Console
bull Management Tools IIS 6 Management Compatibility (IIS 6 Metabase Compatibility
and IIS 6 Management Console)
bull The following Features from Server Manager must be installed
bull NET Framework 35 Features (NET Framework 35 (includes NET 20 and 30) and
HTTP Activation)
bull NET Framework 46 Features (NET Framework 46 ASPNET 46 WCF Services
(TCP Port Sharing))
bull Please see Appendix D Windows Server Roles amp Features for screenshots of the Roles
and Features for different versions of Windows Server
bull The Application Server must be part of a Domain and should be within the same
Domain as the Data Collection Server Application users (and various other features)
leverage Active Directory Domain Services
bull The Bocada Application Server must have SMTP connectivity to the mail server to send email
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
6 Bocada Installation Guide
SQL Server
Software
Microsoft SQL Server (Standard or Enterprise edition not Express or Developer) versions
bull Microsoft SQL Server 2016
bull Microsoft SQL Server 2014
bull Microsoft SQL Server 2012 ndash all SPs
bull Microsoft SQL Server 2008 R2 ndash SP1 SP2 SP3
bull Microsoft SQL Server 2008 SP2
SQL Server Notes
bull Do not create a database prior to installation The Installer will create the Bocada database during installation of the Data Collection server
bull The SQL Server user credentials used to perform the installation (or upgrade) of the Bocada database must be a member of the lsquodborsquo schema and have the db_creator role for permission to create that database
bull The user account used during installation must be assigned to the lsquodborsquo schema as the
Default Schema This can be verified through SQL Server Management Studio in the
Login Properties window for that user (in User Mapping)
Data Collection Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 35 Framework
bull NET 45 Framework
bull ASPNET 35 and higher
bull The Data Collection Server must be part of a Domain (not necessarily the same domain
as the backup servers) application users (and various other features) leverage Active
Directory Domain Services
7 Bocada Installation Guide
Application Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 45 Framework
bull Internet Information Services IIS (latest supported version)
bull Configured to use Windows Authentication
bull Configured to allow IIS 60 metabase compatibility
bull ASPNET 35 and higher
bull ASPNET 20 set to ldquoAllowedrdquo
bull The following Roles from Server Manager must be installed
bull Web Server Common HTTP features (ALL)
bull Web Server Application Development (ALL)
bull Web Server Security (Basic and Windows Authentication)
bull Management Tools IIS Management Console
bull Management Tools IIS 6 Management Compatibility (IIS 6 Metabase Compatibility
and IIS 6 Management Console)
bull The following Features from Server Manager must be installed
bull NET Framework 35 Features (NET Framework 35 (includes NET 20 and 30) and
HTTP Activation)
bull NET Framework 46 Features (NET Framework 46 ASPNET 46 WCF Services
(TCP Port Sharing))
bull Please see Appendix D Windows Server Roles amp Features for screenshots of the Roles
and Features for different versions of Windows Server
bull The Application Server must be part of a Domain and should be within the same
Domain as the Data Collection Server Application users (and various other features)
leverage Active Directory Domain Services
bull The Bocada Application Server must have SMTP connectivity to the mail server to send email
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
7 Bocada Installation Guide
Application Server
Software
bull Microsoft Windows Server 2016
bull Microsoft Windows Server 2012 R2
bull Microsoft Windows Server 2008 R2
Additional requirements
bull NET 45 Framework
bull Internet Information Services IIS (latest supported version)
bull Configured to use Windows Authentication
bull Configured to allow IIS 60 metabase compatibility
bull ASPNET 35 and higher
bull ASPNET 20 set to ldquoAllowedrdquo
bull The following Roles from Server Manager must be installed
bull Web Server Common HTTP features (ALL)
bull Web Server Application Development (ALL)
bull Web Server Security (Basic and Windows Authentication)
bull Management Tools IIS Management Console
bull Management Tools IIS 6 Management Compatibility (IIS 6 Metabase Compatibility
and IIS 6 Management Console)
bull The following Features from Server Manager must be installed
bull NET Framework 35 Features (NET Framework 35 (includes NET 20 and 30) and
HTTP Activation)
bull NET Framework 46 Features (NET Framework 46 ASPNET 46 WCF Services
(TCP Port Sharing))
bull Please see Appendix D Windows Server Roles amp Features for screenshots of the Roles
and Features for different versions of Windows Server
bull The Application Server must be part of a Domain and should be within the same
Domain as the Data Collection Server Application users (and various other features)
leverage Active Directory Domain Services
bull The Bocada Application Server must have SMTP connectivity to the mail server to send email
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
8 Bocada Installation Guide
FIPS
FIPS is a security measure that prevents proper operation of the Bocada application Please
ensure that FIPS is disabled on the Data Collection and Application servers and Windows group
policy is configured accordingly If FIPS is enabled it will cause failure of the Application Server
installation when using SQL Authentication
Disable FIPS
1 Click Start gt Run gt type gpeditmsc and press Enter or click OK
2 In the Local Group Policy Editor under the Computer Configuration node navigate to
Windows Settings gt Security Settings gt Local Policies gt Security Options scroll down to
lsquoSystem cryptography Use FIPS-compliant algorithms for encryption hashing and
signingrsquo
3 If this setting is not already lsquoDisabledrsquo double-click to open the dialog panel select
lsquoDisabledrsquo and click OK
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
9 Bocada Installation Guide
Firewall Port Requirements
DCS and Application Server to Database
Each Bocada DCS and the Bocada Application Server communicates with the SQL Server database using TCPIP The default port used by SQL instances is 1433 but this port is configurable and may have been changed In addition UDP port 1434 might be required for the SQL Server Browser Service if named instances are used These ports should be opened in both directions
Service Protocol Default SQL Port Direction
SQL Server TCP 1433 Both
SQL Server browser UDP 1434 Both
Bocada Application WCF Service
When installing the Bocada Application and Data Collector on separate servers the Windows Communication Foundation (WCF) port 8003 must be open on the firewall of the Application Server The Data Collection Server must also allow outbound connections to the Application Server to connect to the WCF service
Service Protocol Default Port Direction
WCF Application Server and Report
Data TCP 8003
Incoming (on Application Server) Outgoing (on Data Collection
Server)
WCF Application Server and Metadata
Exchange HTTP 8002
Incoming (on Application Server) Outgoing (on Data Collection
Server)
Bocada Application IIS Web Server
The default web port in IIS is port 80 However when installing the Bocada Application Server it is possible to configure a different HTTP port for accessing the application See IIS Configuration below
Service Protocol Default Port
IIS HTTP 80
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
10 Bocada Installation Guide
Backup Server Communication
Additional ports that may be necessary to communicate to each Backup Server for data collection are listed in the respective Plug-in Configuration Guides for those backup products
Pre-installation Note Please see the convenient Pre-installation Checklist at the top of this document
Download Latest Version
Bocada can be downloaded via ftp with the username and password provided by your Bocada representative Current documentation is available in the Docs folder at that location
Note If your Bocada release zip file was downloaded using HTTP protocol instead of FTP then your browser may have added a ldquoZoneIndentifier$DATArdquo stream to the zip file This places a security block on the zip file and when the contents of the zip file are unzipped they will also have this stream applied to them To avoid this problem there are a couple of solutions
bull When the zip file is downloaded right click on the file and select Properties Click on the Unblock button to unblock the zip file Unzip the contents of the zip file to another folder and the contents will not be blocked
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
11 Bocada Installation Guide
Planning
The planning area of the Bocada Software Installation consists of
bull Hardware and Software Requirements
bull Release Notes
bull Installation Guide (this document)
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
12 Bocada Installation Guide
Hardware and Software Requirements
Run Hardware and Software Requirements to verify your system meets the minimum requirements Any prerequisites not met will be indicated with a red ldquoXrdquo and must be addressed prior to installation Requirements are detailed above in the Minimum System Requirements section
Release Notes
Please read the current version Release Notes to learn about new features enhancements and any known issues Click on the Release Notes link in the Setup Application to open the release notes
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
13 Bocada Installation Guide
License Key
The license key is provided by the Bocada Finance department The following information is required
bull SQL Server Fully Qualified Domain Name (FQDN)
bull SQL Instance name (default is no instance)
bull SQL Port (default is 1433)
bull Database Name (default is lsquoBocadarsquo)
Note The above information used to create the license key must match the environment exactly for data collection to function If the SQL Server FQDN Instance or DB names are changed contact Bocada
Installation Proceed with installation once the prerequisites have been met The Bocada installation consists of two separate components
1 Data Collection Service 2 Application Server
Every installation requires at least one installed Data Collection Service which must be installed prior to the Application Server The primary (master) Data Collection Service installation will create or upgrade the Bocada database required to run the application and any additional data collectors necessary for larger environments Installation needs to be performed by a Domain Account with administrative privileges (minimum of Local Admin on the Data Collection server) and it should be noted that the Domain Account running the installer will be the only User initially added to the Bocada application The installer will also install the Bocada Database (if one is not detected already) and so should have the db_creator role for the SQL server Privileges may be reduced to db_owner after installation is completed Note that the Default Schema for the user account performing the installation should be set to lsquodborsquo in SQL Server Important Note Prior to installing the Data Collection Service as part of an upgrade please confirm that you have backed up the database If there are multiple Data Collection Servers the first installation will become the Master Data Collection Server Note The Master Data Collection Server is retained in the Bocada database If the Master DCS is to be renamed or moved contact Bocada Support
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
14 Bocada Installation Guide
Data Collection Service
Installation Page
Click Install Data Collection Service on the main installation page
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
15 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
16 Bocada Installation Guide
Data Collection Installer
Verify Database Server Requirements
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
17 Bocada Installation Guide
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
Destination Folder Select Next to install to the default location or Change to a different destination
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
18 Bocada Installation Guide
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
19 Bocada Installation Guide
Service Login Notes
bull When installing the Master Data Collection Server and Application Server on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate
bull The Domain Account or SQL Authenticated user chosen must have access to the SQL server and
bull Must have sufficient SQL Server permission to create and update the Bocada database
bull Can have permissions lowered to db_owner (Database Owner) after the initial install
bull Should be set to use lsquodborsquo as the Default Schema in SQL Server (see below)
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Any secondary Data Collection Servers may be installed and run with Local System Account authentication even if the Master DCS is using a Domain Account
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
Confirm DBO Schema for Bocada SQL User
The SQL User (using Windows or SQL Authentication methods) Must have DBO as the default schema This can be confirmed through SQL Server Management Studio
1 Navigate to Security (instance level) --gt Logins 2 Open the Login Properties window for that user (Right click the user --gt select
Properties) 3 Select User Mapping 4 Verify that the Default Schema for that user is set to lsquodborsquo
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
20 Bocada Installation Guide
Database Server Enter the SQL Server fully-qualified domain name (FQDN) instance name (if any) and non-standard port (if any) and database name as specified in the Bocada license key If you select Windows Authentication the Bocada database will default to the domain account that is running the service Then select Next
Database Server Notes
bull If this Data Collection installation is not the primary (master) DCS Instance and Database must match that used for the master installation
bull If the environment variables for server instance (andor port) and database do not match that given for the license key data collection will not function and you will need to obtain a different license key through Bocada Support
The installation will attempt to connect to the Database If authentication fails the following error will be displayed
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
21 Bocada Installation Guide
At this point the Database or Login settings must be verified Please refer to Appendix A for troubleshooting information
Start Installation When upgrading to a newer version of Bocada the confirmation screen will be displayed
After confirming the intent to upgrade or for new installations click Install to begin installation
Installation Note
bull If the installer is unable to start the Bocada Data Collection Service then it will need to be started manually Please refer to Appendix B for troubleshooting assistance
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
22 Bocada Installation Guide
Installinghellip
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
Clicking Finish will return the main installer where you can continue to the Application installation or close the installer to install the Application on another server
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
23 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
24 Bocada Installation Guide
Application Server
Installation Page Click Install Application Server on the main installation page
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
25 Bocada Installation Guide
Requirements Page
Review the requirements for installation
When you have all necessary details for the SQL Server amp instance click Next
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
26 Bocada Installation Guide
Application Server Installer
License Agreement Carefully review and accept the terms of the license agreement then click Next If you have questions or concerns regarding the license agreement please cancel the installation and contact Bocada Support
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
27 Bocada Installation Guide
Destination Folder Enter a desired installation directory or leave as default then select Next to install
Select Yes to send anonymous product usage data (such as the License Count report) to Bocada or No to opt out of product data sharing
Service Login Enter the Windows User Domain Account credentials or select Local System Account then click Next
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
28 Bocada Installation Guide
Service Login Notes
bull When installing the Data Collection and Application on separate servers a Domain Account which can access both servers must be used for the services on the two servers to communicate This Domain account should have at least Local Admin permissions on both servers
bull The Domain Account chosen must have access to the Bocada database as noted above After installation permissions can be reduced to the db_owner role for this database
bull Using the Domain Account of the User running the installer is recommended If a different User is entered they must be added as an Administrator user from the Bocada Users view
bull Using a Domain account with a non-expiring password is recommended to prevent future authentication issues that would prevent data collection
bull Running the service Local System Account for authentication will require that the service connect to the SQL Server using SQL Server Authentication
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
29 Bocada Installation Guide
Database Server Enter the SQL Server FQDN Instance andor Port (if applicable) and Database Name as specified in the Bocada license key and select Next
Database Server Notes
bull The information entered must match what was used for the Data Collection installation
After clicking Next the installation will attempt to connect to the Database If unable the following error will be displayed Please refer to Appendix A for troubleshooting information
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
30 Bocada Installation Guide
IIS Configuration A web application will be installed as part of the Bocada Application Configure IIS and click Next to start installation
IIS Configuration Notes
bull If Default is selected the Application will be installed using the specified HTTP Port (eg port 8086) from the HTTP Port setting
bull If HTTPS is selected the Application will be installed using HTTPS using the specified HTTP Port from the HTTP Port setting
bull If Virtual Directory on Port 80 is selected the Application will be installed to HTTP Port 80 using the HTTP Virtual Directory specified
bull An HTTP Virtual directory can only be created if there is already a website on the HTTP Port 80
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
31 Bocada Installation Guide
Start Installation Click Install to begin installation of the application Server
Installation Complete Once the installation is successful you will be presented with an option to view the installation log Select Show the Windows Installer log to view the installation log if desired then click Finish
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
32 Bocada Installation Guide
Configure HTTPS Certificate If HTTPS was select during the Application install the following steps will provide a guide for deploying your SSL certificate Note that the certificate is not something Bocada can provide since the server name is required with the certificate
Deploying the Certificate After acquiring a certificate it will need to be applied to the binding in IIS Manager 1) Open the IIS Manager 2) Select the Bocada Web Site 3) Select ldquoBindingsrdquo from the right-hand side of the Manager 4) Select your Site Binding and click ldquoEdithelliprdquo
5) In the Edit Site Binding window select your certificate from the SSL Certificate drop down and then click OK
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
33 Bocada Installation Guide
Upgrade
Upgrading Bocada requires first uninstalling the previous Bocada application then installing the newest version Please visit the Bocada 192 Upgrade Guide for instructions and notes on the upgrade process
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
34 Bocada Installation Guide
Accessing the Application After completing installation there are two ways to access the application
1 Using a supported browser local to the Application Server
bull httplocalhost[port][VirtualDirectory]
or
bull http[AppServerFQDN][port][VirtualDirectory]
2 Using a supported browser from a server other than the Application Server
bull http[AppServerFQDN][port][VirtualDirectory]
or
bull http[AppServerShortName][port][VirtualDirectory] (in-network only)
User Access Note bull During the application installation the Windows User that was logged in during the
installation is automatically added as an Administrator to the product This is the only account with access to Bocada until other Users are added Additional Users can be added by this Administrator from the Bocada Administration module under Users For more information about User management please refer to the Bocada Administration guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
35 Bocada Installation Guide
Adding Bocada License Upon initial login the Edit General Settings wizard will be displayed with a text field for a product key Paste the product key into the field and click Add then Finish
Congratulations Bocada is now licensed and ready to use
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
36 Bocada Installation Guide
General Settings Upon setup most users will immediately want to edit their Global Report Settings From the Administration module (at lower left) select Settings to view your Global Settings Next select the Edit icon from the right Action panel to open the Edit General Settings wizard (as above) Select the second tab Global Report Settings to make global changes appropriate to your own environment
bull Most users will want to set the Default Time Zone to match the time zone of their backup servers (if backup servers are in multiple time zones these can be configured individually)
bull Since most backup jobs are done at night and can take an indeterminate length of time to startfinish most users will want to set their Backup Day to begin at Noon
bull See the Bocada Admin Guide for common next steps available at ftpftp2bocadacomDocs
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
37 Bocada Installation Guide
Technical Support For technical support or if you would like a copy of our standard support agreement please contact us E-mail supportbocadacom
Phone 425-818-4480
Toll-free 866-BOCADA-1
(866-262-2321)
Both new and existing customers who have purchased annual support and maintenance have full access to Bocada Support
bull Online knowledge base and problem ticketing system bull E-mail and toll-free telephone assistance Monday through Friday 6 am to 6 pm
Pacific US Time (except holidays) bull Product documentation and documentation updates bull Program error fixes hotfixes and service packs bull Product upgrades for the Bocada application
To access the support portal click on ldquoCustomer Support Portalrdquo from the following URL httpswwwbocadacomproduct-support
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
38 Bocada Installation Guide
Appendices
Appendix A Database Troubleshooting
Possible Errors during installation Error seen ldquoERROR Must install Bocada with the DBO schema but schema is currently helliprdquo
Reason The domain account that is used has insufficient permissions to perform the installation Troubleshooting The SQL Server user credentials used to perform the installation needs to be a member of the lsquodborsquo schema and have the db_creator role in order to create the Bocada database
Possible Errors during operation
Issue Possible Reason Troubleshooting Step(s)
Cannot connect to SQL database
SQL server is incorrect or server short name is used
bull Confirm SQL Server name is correct and FQDN is used
Instance or Port specified is incorrect
bull Confirm Instance and Port (leave blank for default)
DomainSQL User specified does not have access to SQL Server
bull Confirm access using SQL Server Management Studio
SQL Server services are not running
bull Confirm that SQL Server Services are running
Remote connection failure
SQL Server is not allowing Remote Connection
bull Configure SQL Server to Allow Remote Connections
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
39 Bocada Installation Guide
Installation or Upgrade fails
SQL Server version is unsupported
bull Specify different SQL Server with supported version
bull Upgrade SQL Server to supported version
Return to Data Collection Service Installation
Return to Application Server Installation
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
40 Bocada Installation Guide
Appendix B Windows Services and User Management Services management (including manually starting services) and User management processes are described in the following two Microsoft TechNet references Windows Services Management httpstechnetmicrosoftcomen-uslibrarycc77240828v=ws1129aspxf=255ampMSPPError=-2147217396 Windows User Management httpstechnetmicrosoftcomen-uslibrarydd391974(v=ws10)aspx The following settings for the Bocada services must be met for the application to function properly Bocada Data Collection Service
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Bocada Service (Application Server)
bull Startup Type is Automatic bull The account assigned to start the service (Log On) has sufficient privileges to start services bull Local System account is not used when Data Collection and Application are on separate
servers
Note Management of the Bocada Data Collection and Application services requires Administrative privileges on the server(s) where the applications are installed If launching the application results in an error one possible solution is to explicitly raise the permissions of the user running the Bocada Service on the Bocada installation directory to Admin Return to Data Collection Service Installation
Return to Application Server Installation
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
41 Bocada Installation Guide
Appendix C Website Setup During Application Server installation the following web site options are available for set up
Example IIS Configuration
Reason Web Site Address
HTTP Port = 80 Directory = NULL
Using default HTTP Port HTTP Port is not in use
httpappserverdomaincom
HTTP Port = 80 Directory = ldquobocadardquo
Using default HTTP Port HTTP Port is in use
httpappserverdomaincombocada
HTTP Port = 8080 Directory = NULL
Using non-default HTTP Port HTTP Port is not in use
httpappserverdomaincom8080
HTTP Port = 8080 Directory = ldquobocadardquo
Using non-Default HTTP Port HTTP Port is in use
httpappserverdomaincom8080bocada
For illustration purposes appserverdomaincom is the Bocada Application Server Possible Errors during installation HTTP Virtual Directory not specified selected HTTP Port (80) already in use
HTTP Virtual Directory is specified for a port which is not already in use
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
42 Bocada Installation Guide
Possible Errors while attempting to access the application Occasionally after successful installation of the application server the application may fail to load The following are possible errors with solutions
Error Message
Reason Solution
HTTP Error 40417 ndash Not Found
The requested content appears to be script and will not be served by the static file handler
Windows Server 2008 amp 2012 1 Issue the following command
CWindowsMicrosoftNETFrameworkv4030319aspnet_regiisexe -i
2 Restart IIS Windows Server 2016 1 Open Server Manager and navigate to Features gt
Add Features 2 Add the Windows Feature ldquoWeb Server (IIS) gt Web
Server gt Application Development gt ASPNET 46rdquo
Server Error in Bocada Application Runtime Error Description An exception occurred while processing your request
C++ runtime libraries are missing on the Application server
Download and install the missing component from the link below httpwwwmicrosoftcomen-usdownloaddetailsaspxid=5555
Headings amp Menus appear but Reports display no data
Browser is running in Protected Mode and the Bocada Application site is not a Trusted site
Navigate to Tools gt Internet Options gt Security uncheck the checkbox next to Enable Protected Mode and add the site to Trusted Sites If you then clear the cache (Tools gt Internet Options gt General gt Browsing History gt Delete) and refresh the browser session (CTRL-F5) reports should appear as normal
The Bocada Database was not correctly updated (some necessary components have been installed to the incorrect schema)
Verify that the Default Schema for the user account performing the installation is set to lsquodborsquo in SQL Server and reinstall the Data Collection Server to repair the Bocada database
Return to IIS Configuration
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
43 Bocada Installation Guide
Appendix D Windows Server Roles amp Features While the same Roles and Features are required of any Windows Server installation these appear slightly differently depending upon your version of Windows Server Below are some examples of Windows Server installation requirements from various server versions
Windows Server 2008R2
Roles
Features
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
44 Bocada Installation Guide
Windows Server 2012R2
Roles
Features
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
45 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
46 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
47 Bocada Installation Guide
Windows Server 2016
Roles
Features
48 Bocada Installation Guide
48 Bocada Installation Guide