Skip to main content
System StatusContact Support
VersionOne Community

Installing Analytics (On-Premise)

Editions

This feature is available in Ultimate edition only.

editions-u.png

The content in this article applies to On-premise VersionOne instances only. If you are an On-Demand (V1 Hosted) customer, see On-Demand (V1 Hosted) System Maintenance.

Installing or managing an instance of Analytics involves creating or updating the Analytics meta-data database schema and the Analytics web application. 

Prerequisites

To perform the steps below, you need to run the setup program as Administrator. On newer versions of Windows, this involves more than just logging in as Administrator, or a user with Administrative privileges. The best way to ensure that you run setup with the appropriate privileges is to right-click on the Setup executable and select "Run As Administrator".

Steps

Step 1. What action do you want to take?

If an existing instance of Analytics is detected on the machine, you are presented with a panel that requires you to choose an action before proceeding. The default action is to upgrade the existing instance. You may also remove an instance or install a new instance.

Step 2. Select from these installed instances:

When upgrading or removing an instance you must specify an instance for the action. This panel is only presented if more than one instance is installed on the machine. Once you choose an instance, the next button is enabled.

Step 1. What do you want to name this web application?

When installing a new instance you must agree to the terms of the license agreement before proceeding. There is a link on this panel to access the appropriate license agreement.

Each application on a website is required to have a unique name.  This name becomes part of the URL used to access the specific application.  When installing a new instance, the default application name is "Analytics", and we recommend using this name unless it's already taken.  If you need to change the name, there are specific rules for naming websites.   A brief explanation of these rules can be found on Wikipedia or on the W3C website.

Naming_web_application.png

 

Step 3. What URL will be used to access this web application?

This is the URL used to access Analytics from a browser.  The default URL is http://localhost/[Instance Name].  At a minimum you need to replace "localhost" with the proper machine name for accessing this website.  You may also need to replace http with https if the site will be secure.

Step 4. Integration with Lifecycle

Each instance of Analytics is paired with a single instance of Lifecycle.  This panel allows you to specify the instance you intend to pair with the  Analytics instance being installed.

image001.png

Step 5. Lifecycle URL

This URL is used when creating links back to Lifecycle.  Therefore, it needs to be the URL used by the browser, to connect to the desired instance.  This URL needs to be in the form "http[s]://[machine name]/[VersionOne instance name].  For example, http://v1webserver/VersionOne.   We recommend that you not use "localhost" as the machine name even if Analytics and Lifecycle are installed on the same machine. Doing so will prevent remote users from accessing Analytics. 

Step 6. Integration Code

The integration code is used to ensure that Analytics is communicating with a known instance of Lifecycle.  This code can be any sequence of letters, numbers, and characters.  The value provided here must also be provided to the Lifecycle instance when Analytics is enabled.  We recommend that you refrain from using simple words.  

Step 7. Analytics Metadata Database server

The Analytics application has a small database for persisting the Custom Reporting meta data and your custom report definitions.  This database was created during the  Data Mart Setup process.  The Analytics setup program needs to know this information in order to configure the Analytics application and to create the default metadata.  

On this panel you select the database server hosting  the Analytics metadata database and provide credential that Setup will use to connect to that server.  It's important to note that the credentials provided here are only used by Setup; these are not the credentials used by the Analytics application.

  • How do I resolve the "Cannot Connect to Database" error message? This error indicates that Setup cannot connect to the database server you specified. A common cause for this error is specifying only the machine name and omitting the SQL Server instance name. To include the instance name, use the format "[machine_name]\[instance_name]" - for example, if you're installing on a local server in which both IIS & SQL are running, and the instance name is SQLEXPRESS (the name that express uses when installing), you would use "(local)\SQLEXPRESS". If the server is a remote server, you'd use the actual machine name.

Analytics_Metadata_database_server.png

Step 8. Analytics Metadata Database

As mentioned above, the Analytics metadata database was created by the Data Mart Setup process.  The default name for this database is "[VersionOne Database Name]-analytics"; for example VersionOne-analytics. 

On this panel you select the Analytics metadata database that will be used with this instance of Analytics.  If you do not see the database name listed in the dropdown box, you have most likely selected the wrong database server.  

Analytics_metadata_database.png

Step 9. Analytics Database Credentials

How you answer this question determines which credentials are used by the Analytics web application when connecting to the Analytics metadata database.  Your options are:

Analytics_metadata_database_credentials.png

Option Description
Let setup create a user With this option Setup will create a new user on the database server and assign that user to the Analytics metadata database.  The username and password are randomly generated.   Additionally, when the instance is upgraded, new credentials are created.
My DBA Provided Credentials In some environments, access to databases is controlled.  If your DBA provided you credentials, choose this option and enter the credentials you were given.

Step 10. Data Mart Database server

The Data Mart database is used to generate all reports in Analytics.  This database was created by the Data Mart setup program and is paired with the instance of Analytics being installed.  Analytics Setup will read the database server and database name information from the Analytics database.  

On this panel you provide credential that Setup will use to connect to the Data Mart dataabse server.  It's important to note that the credentials provided here are only used by Setup; these are not the credentials used by the Analytics application.

  • How do I resolve the "Cannot Connect to Database" error message? This error indicates that Setup cannot connect to the database server you specified. A common cause for this error is specifying only the machine name and omitting the SQL Server instance name. To include the instance name, use the format "[machine_name]\[instance_name]" - for example, if you're installing on a local server in which both IIS & SQL are running, and the instance name is SQLEXPRESS (the name that express uses when installing), you would use "(local)\SQLEXPRESS". If the server is a remote server, you'd use the actual machine name.

Data_mart_database_server.png

Step 11. Data Mart Database

The Data Mart database information is read from the Analytics metadata database.  This panel is here to inform you of the database being used for this instance of Analtytics.

data_mart_database.png

Step 12. Data Mart  Database Credentials

How you answer this question determines which credentials are used by the Analytics web application when connecting to the Data Mart database.  Your options are:

data_mart_database_credentials.png

Option Description
Let setup create a user With this option Setup will create a new user on the database server and assign that user to the Data Mart database.  The username and password are randomly generated.   Additionally, when the instance is upgraded, new credentials are created.
My DBA Provided Credentials In some environments, access to databases is controlled.  If your DBA provided you credentials, choose this option and enter the credentials you were given.

Step 13. SMTP Parameters

Reports in Analytics can be emailed to people within, or outside, of your organization.  This panel allows you to enable the email feature and provide details for connecting to your SMTP server.

SMTP_Parameters.png

Step 14. Should the Analytics database be preserved or deleted?

When removing an instance of the Analytics, you need to decide if you want the metadata database destroyed.  If you choose delete, the database is removed and cannot be recovered, unless you have a backup.

Step 15. Setup is ready to perform the following actions

This panel allows you to review the changes that setup is about to make.  Click Next to apply the changes.

Setup_is_ready_to_perform_the_following_actions.png

Step 16. Please wait while Setup installs ....

This panel allows you to view the progress of the changes being made.

Please_wait_while_Setup_installs_Analytics.png

Step 17. Success

When setup is successful you receive a small window indicating this fact.  Click OK to close setup.

You are now ready to enable Analytics in your Lifecycle instance.  To do this:

  1. Log into Lifecycle as a user with an Admin Privileges role of "System Administrator" (admin for example).  
  2. Click Admin in the main menu, and then click on the Analytics tab.  
  3. Click the Enabled check box, and then enter the URL used to access Analytics
  4. Enter the integration code, and then click Save.
  5. (Optional) Click Test Connection to make sure the set up is working properly.

Setup_is_Successful.png

Error Messages

When setup fails, you are presented with a window that indicates the failure and provides an option to open the log file.  In most cases the error message clearly indicate what failed (i.e. Insufficient rights to create database), however there are situations when Windows returns a cryptic error code.  In these situations, please email Support and include the setup log file.

  • Was this article helpful?