Pre-Installation Steps

Prior to beginning the installation process, please ensure that the following list of requirements is implemented to ensure a smooth installation:

If this is an upgrade of an existing Framework installation, be sure to take a full backup of your SQL Server database before performing the upgrade.

The SQL Server transaction has been removed from the v14 upgrade due to the size of the upgrade. Because the upgrade now does not use a transaction, it is important that a backup of the database is taken just before the upgrade. If an error occurs during the upgrade, changes cannot be rolled back and the database will be left in an unstable, unrecoverable state, so the database backup must be restored.

Ensure the server processing the installation has access to https://services.akcelerant.com. This URL is used to communicate with the Akcelerant installation web services during the installation to validate the license key as well as log the details of the installation.
Obtain the following credentials from IT:
- Database backup location
- Connection string
- Web server name
- Domain, Username and Password
- Installation key
- SQL User and Password needed to connect to the server
- SharePath
- Reporting Services Server (if applicable)
- Reporting Services Folder (if applicable)
These credentials will be needed in order to complete a successful installation.

Obtain the installation key(s).
The installation key is unique to every organization. Each instance of the Framework being installed requires its own key. During the installation, a prompt requests the installation key. Once installed, the installation key is available on the Collaboration Portal, along with other details and options regarding the installation.

For new installations, please contact your Akcelerant Customer Care Representative to receive your institution’s installation key.

If the installation key is not entered, an institution is unable to proceed with the installation.

Validate the version of the Akcelerant Framework.
The Akcelerant Framework version must be at minimum of 10.31.15.
Validate the Windows Operating System is supported.
The following operating systems are supported for database, web, application and public (DMZ) servers used for the Akcelerant Framework:
- Windows Server 2003 (Standard and Enterprise)
- Windows Server 2008 (Standard and Enterprise)
- Windows Server 2008 R2 (Standard and Enterprise)

Validate the SQL Server and Report Server version is supported.
An existing SQL instance on the network may be used or a new SQL instance dedicated to the Akcelerant Framework may be setup. The following SQL Server & SSRS (SQL Server Reporting Services) versions are supported (32 or 64 bit, Enterprise or Standard):

SQL Server Versions:

SQL Server 2005¹: http://msdn.microsoft.com/en-us/library/ms143219(v=sql.90).aspx
SQL Server 2008²: http://msdn.microsoft.com/en-us/library/ms143219(v=SQL.100).aspx
SQL Server 2008R2³: http://msdn.microsoft.com/en-us/library/ms143219(v=sql.105).aspx

Report Server Versions:

SSRS 2005¹: http://msdn.microsoft.com/en-us/library/ms143736(v=sql.90).aspx
SSRS 2008²: http://msdn.microsoft.com/en-us/library/ms143736(v=sql.100).aspx
SSRS 2008 R2³: http://msdn.microsoft.com/en-us/library/ms143736(v=sql.105).aspx

¹ Reporting Services 2005 is not supported as all Loan Origination reports are built on the 2008 engine for greatest functionality. However, SQL 2005 can integrate with Reporting Services 2008.

² SQL Server 2008 SP1 or higher is required in order to use Microsoft Report Builder 2.0 integration.

³ SQL Server 2008 R2 is required in order to use Microsoft Report Builder 3.0 integration.

“Express” editions of SQL Server are not supported.

Ensure the installation user is assigned “serveradmin” role privileges on the SQL server.
This is required for the database to be created.
Validate all pre-requisite software is installed and configured on web, application and DMZ servers.

The following software must be installed prior to Akcelerant Framework installation:
- IIS Versions – the following versions of IIS are supported:
  - IIS 6.0 (typically installed by default on Windows 2003 Server)
    http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/750d3137-462c-491d-b6c7-5f370d7f26cd.mspx?mfr=true
  - IIS 7.0 and 7.5 (typically installed by default on Windows 2008 and Windows 2008 R2 Server)
    http://www.iis.net/learn/install/installing-iis-7/installing-iis-7-and-above-on-windows-server-2008-or-windows-server-2008-r2
    
    Enable IIS 7.0/7.5 Web Server Role Services (under Server Manager)
    http://technet.microsoft.com/en-us/library/cc753473.aspx
    1. ASP
    2. ASP.net
    3. Security, Basic Authentication
    4. Security, Windows Authentication
    5. IIS 6 Management Compatibility
    6. IIS 6 Metabase Compatibility
    7. IIS 6 WMI Compatibility
    8. IIS 6 Scripting Tools
    9. IIS 6 Management Console
    10. Static Content IIS Role
- Component Services
  Install component services if Windows 2008 or 2008 R2 is installed. http://technet.microsoft.com/en-us/library/cc772579.aspx
- SQL Client Tools
  Install SQL Client Tools matching the version of SQL running on the database (available on the SQL Server Installation disc).
- SQL Server 2005 Backward Compatibility Components
  - 32 bit (http://go.microsoft.com/fwlink/?LinkId=202308&clcid=0x409)
  - 64 bit (http://go.microsoft.com/fwlink/?LinkId=202310&clcid=0x409)
- .NET Framework 4.0 http://www.microsoft.com/en-us/download/details.aspx?id=17851
- Disable UAC
  Disable UAC (User Access Control) to ensure scheduled processes run properly.
  http://technet.microsoft.com/en-us/library/cc709691(v=ws.10).aspx#BKMK_S3

Create a shared directory
A directory must be created that is accessible to the web and application servers. The Framework stores various documents in this directory, and will grow over time. To accommodate this growth, the directory should not be created on a drive with limited space available. There are no naming requirements for this folder, but it must be accessible to all servers in the configuration. When prompted for the share folder path during installation, it is suggested that a UNC path be provided. For example: \\yourserver\sharename.

This folder is critical to include in a disaster recovery plan as its contents are irreplaceable if lost.

The following items are stored by the Framework in this directory:

Archived import and export files
Credit reports
Skip Trace reports
Documents uploaded through the Framework
Log files
Letter templates and history

Create an Akcelerant Framework service account
The Framework requires a service account to run many components of the installation. This account can either be a domain account or a local account. Use a local account if installing all components of the Akcelerant Framework on the same server. A domain account is required for multi-server configurations to ensure a single user is able to authenticate on each configured server. The service account (local or domain) should be customized with the following:

Properties:

User cannot change password
Password never expires
24 hour per day network access

Permissions:

Read/Write permissions to the Windows Temp directory (typically C:\Windows\Temp). The Framework uses COM Interoperability for some of its features. At runtime, the .NET Framework may create and execute files in the temp directory.
Read/Write permissions to the Akcelerant share folder. Since the share folder is used to store several types of critical files, it is advised that full access is granted.

Processes configured to run:

Anonymous requests in IIS (application pools)
COM+ application (dlls)
Scheduled tasks (daily processes)
Database access (if using a trusted connection)

Do not log into the web server with the Akcelerant service account when installing the Framework, as it results in the disruption of critical services when logging off the server. When running the installation, use another local admin account and follow the prompts to enter the Akcelerant service account.

Create an Akcelerant Customer Care domain account
After the installation has completed and throughout the term of your support agreement with Akcelerant, the assistance of Akcelerant Customer Care may be required to connect to servers and troubleshoot issues. At minimum, this account may require read-only access to the SQL Server, more specifically to the Akcelerant database.

The Akcelerant service account should not be used for these connections to your server as it can cause critical failures in the Akcelerant application when the user logs off under that account.

Institutions are able to grant access to an Akcelerant Customer Care Representative if they need to make changes to the database to correct issues. Click here for more information on the SQL database membership roles.

NOTE: The role of ddladmin provides the representative with the most flexibility and is the most common role granted. The role of db_datareader is the minimum role required for troubleshooting.