Skip to main content
System StatusContact Support
VersionOne Community

Installing VersionOne Lifecycle

Step-by-step instructions for installing VersionOne Lifecycle Core on a Web server.

Installation Checklist

  1. Verify that the server meets the minimum System Requirements
    Refer to System Requirements for the complete list for both server and client machines.

  2. Install VersionOne Core
    Refer to VersionOne Core Installation for instructions.

  3. (Optional) Install VersionOne Data Mart and Analytics
    See Datamart Installation and Analytics Installation, and then run the Datamart Loader.

  4. Verify the installation

Steps

VersionOne is already installed on this machine. What action do you want to take?

If setup detects an existing instance of VersionOne, you will be asked to "Upgrade" (default), "Uninstall", or "Install a New Instance" an option before proceeding. Click Next.

setup_1_001.png

Agreement Confirmation

For new installations, select the check box to accept the terms of the licensing agreement (click on the link to read it), and then click Next.

setup_3.png

What do you want to name this web application?

For new instances, the default application name is "VersionOne". We recommend that you use this name (unless it's already taken) because this name it becomes part of the URL used to access the application.

If you need to change the name, refer to Wikipedia or W3C for web site naming rules and conventions.

setup_4.png

What authentication mode would you like to use?

VersionOne web supports several modes for user authentication. Here, you can select the mode that works for your organization.

  • VersionOne Authentication
    Users to supply credentials on a login form before accessing the VersionOne application. This mode is also referred to as Forms based authentication
  • Windows Integrated Authentication
    IIS to authenticate the user and provide the VersionOne application with their domain username after they are authenticated.

Regardless of the choice you make, users (members) cannot access the system until proper credentials are provided.

While this decision is an important one, you can change this setting later by running setup and choosing to upgrade the instance.

What if we want to use SSO or an internal form of Authentication?

The VersionOne application can be used in a SSO environment. In these environments, you need to select VersionOne Authentication on this panel. Once the install is complete, there are some additional configuration steps required for authentication to work. These steps vary depending on the type of authentication. You'll need to contact your account manager, or VersionOne support, for the details specific to your SSO provider.

setup_6.png

Please enter information required to access SQL Server.

In order to create, update, or remove the VersionOne run-time database, the setup application needs to access your database server.

On this panel, you must specify which database server will host the VersionOne database and how the setup application will connect to that server. The credentials provided must have sufficient privileges to perform the actions required. For instance, if the setup application will create the run-time database and necessary credentials, then the user provided on this panel must have authority to create databases and credentials.

It's important to note that the credentials provided here are not the credentials used by the VersionOne application.

setup_7.png

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

What database should the new instance use?

How you answer this question determines which database is used by the VersionOne application for persistence storage (the run-time database name). By default Setup expects the database name to match the web application name. Following this convention is recommended because it avoids confusion when trying to determine which database is used by the VersionOne instance. The default instance name is "VersionOne", therefore the default database name is "VersionOne".

  • Create a new database
    This is the default option if Setup cannot find a database name that matches the web application name. When you choose this option, Setup will create a new database with the name provided and configure the VersionOne web application to use this database.

  • Attach to an existing database
    This is the default option if Setup finds a database whose name matches the web application name. When you choose this option, Setup will configure the VersionOne web application to use the specified database

If you are restoring an VersionOne instance from a backup, you need to restore the database before running setup and choose "Attach to an existing database" specifying the restored database.

I cannot choose the "Create a new database" option. The "Create a new database" option is not available if the credentials used to connect to the database server do not have sufficient privileges to create a database. To resolve this issue, go back one panel and connect to SQL Server with credentials that have the appropriate privileges .

Specify the database user

This step determines which credentials are used when the VersionOne web application connects to the run-time database. Your options are:

  • Let setup create a user
    With this option Setup will create a new user on the database server and assign that user to the VersionOne 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. These credentials are kept in a user.config file located in the VersionOne applications web directory.

If you choose the "My DBA Provided Credentials" option, Setup will not manage your user credentials on upgrade. If you need to change the credentials at a later date you will need to edit the user.config file to perform the update.

What database rights are required if my DBA creates our database?

When installing VersionOne with an existing database, the Windows/SQL account used for setup needs fewer SQLServer rights, as it does not need to create a new database. To allow setup to create VersionOne database schema, modify database configuration settings (see below), and populate it with application data, the account used (either the individual running setup or a SQL login specified during setup) must be a user on the VersionOne database, and a member of the db_owner database role.

Note that any upgrades to VersionOne also require that the account used during setup be db_owner on the VersionOne database.

VersionOne Database Configuration

The VersionOne application requires its database be configured as follows:

ALTER DATABASE [{database}] SET
ARITHABORT ON,
CONCAT_NULL_YIELDS_NULL ON,
QUOTED_IDENTIFIER ON,
ANSI_NULLS ON,
ANSI_PADDING ON,
ANSI_WARNINGS ON,
NUMERIC_ROUNDABORT OFF

If not already set to these values, they will be updated when setup executes

setup_8.png

Setup is read 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_4_001.png

Please wait while Setup installs ...

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

setup_11.png

Setup Completed Successfully

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

setup_-_completed_successfully.png

  • Was this article helpful?