Install SQL Server
In order to run an Attix5 AccountServer using a separate SQL Server you need to first install Microsoft SQL Express or Professional (2005 for Attix5 Pro V6 or 2012 for Attix5 Pro V7 and above).
Note:��During the installation process, it is advised to use mixed mode authentication.
Configure SQL Server for network connectivity
On the SQL Server machine, use SQL Server Configuration Manager to enable TCP/IP protocol. Ensure that the interface you will connect to is �?oActive�?� and �?oEnabled�?�. You should also set the TCP port for either IPAll or the individual interfaces. The standard SQL port is 1433.
After any changes, the SQL service needs to be restarted. You should ensure that this is running before attempting the SQL installation on the AccountServer machine.��You can also choose to set the Server Browser service to running.
It is recommended that you install Microsoft SQL Management Studio and make sure you can connect to the local SQL Server.
Important note:��The AccountServer and ReportServer databases, �?oStoragePlatform�?� and �?oStoragePlatformReports�?� are not automatically created when installing to separate SQL server. You will need to manually create these in SQL Server Management Studio. It is advised to use the default names �?oStoragePlatform�?� and �?oStoragePlatformReports�?�. The databases will not be populated with tables when they are created, but are populated when the AccountServer service first runs.
Configure database credentials
There are several options available for connecting to the database, and the selection of these alters how settings should be configured during the Storage Platform installation.
Note:��The simplest method of authentication is SQL authentication, as this avoids any external authentication dependencies, and is the recommended authentication method. If Windows authentication is used, the Windows credentials of the SQL server machine will be checked against the client. This includes Active Directory authentication. For any Windows user to enabled for SQL login, their username need to be listed in the SQL server �?oLogins�?� section within "Security", and set with appropriate database rights (see "Configure and assign database rights" below).
For example, to connect to the SQL server �?oVULCAN�?� from the AccountServer machine �?oROMULUS�?�, with Windows authentication selected, �?oVULCAN\Administrator�?� or simply �?oAdministrator�?� can be used to log in. When using Windows authentication, there is usually no prompt for credentials; the credentials of the current login session will be used. Logging in to the AccountServer machine (ROMULUS) as Administrator with the password �?oPassword123�?� when the SQL Server (VULCAN) also has an Administrator password of �?oPassword123�?� enables you to connect successfully from the AccountServer using SQL Management Studio. If the Administrator password is different on the SQL Server, or if you logged in as a different user, the credentials will not match, and you will not be able to connect to SQL Management Studio using Windows authentication. If the user does not exist on the SQL Server, or is not added as a Login in SQL, the user will also be unable to connect. As an alternative, it is possible to create a separate SQL-only set of credentials for connecting to the SQL Server. Ensure that the Login is �?oEnabled�?� and permission to login is �?oGrant�?�, or the user will not be able to login or connect to the database.
In "General", it is advised to disable �?oEnforce password expiration�?� or you could be disconnected automatically from the database after your password ages out, and have to reconfigure your connection strings at a later date.
Configure and assign database rights
Regardless of authentication method, the connecting user will need the following rights: in "Server Roles", the user needs at least �?odbcreator�?�, but can also be set with �?osysadmin�?�.
In "User Mapping", for the StoragePlatform and StoragePlatformReports databases, ensure that �?odb_owner�?� and �?opublic�?� are both checked. This assigns the roles to the users for each database.��
Install SQL Management Studio (optional)
It is recommended that SQL Management Studio be installed on the AccountServer. This will allow you to test connectivity to the SQL Server before beginning the AS installation. In order to install SQL Management Studio you will need to install .NET 3.5 and MSXML 6. The Attix5 Storage Platform also requires .NET 4, so this should also be installed. Use the SQL Management Studio to connect to the SQL Server. To do this, enter the host and instance name details for the SQL Server in the Server Name field, e.g. �?oServer1\SQLEXPRESS�?�. The host can either be a Windows machine name, a DNS name or an IP address.
Note:��If using Windows or DNS name, these will need to be resolved in order to connect to the SQL Server. For example, if using a DNS name, make sure that the AccountServer machine is configured correctly with DNS details, and that these resolve as expected.
Enter the credentials that the AccountServer will use to connect. These can either be Windows credentials, or SQL credentials, depending on how you have configured SQL.
Click the��Connect��button to test connectivity to the SQL Server. If you are unable to connect, you are advised to troubleshoot your connection details before installing the AccountServer.
Note:��For a full SQL installation, SQL Management Studio can be downloaded separately. Also note that SQL Management Studio 2005 will not connect to an SQL 2008 instance.��
Install the AccountServer
Follow the instructions below:
- Run the Attix5 Storage Platform installation. Click the��Next��button to begin the configuration wizard and select��Advanced Configuration��when prompted.��
- Select��AccountServer��and enter your installation key on the next screen.��
- Select��Specify the connection strings manually (advanced users only)��and click the��Next��button.��
- On the �?oConnection Strings�?� screen, click the connection button for the AccountServer Database.��
- Enter the credentials you earlier configured for connecting to the SQL Server:��
- Click the��Connection��tab and enter the host details and instance name of the database you are connecting to.��
- Select the log on method, and enter the username and password if using SQL authentication. Also, select��Allow saving password��if using SQL.��
- Select the name of your AccountServer database if it is not �?oStoragePlatform�?�.��
- Click the��Test Connection��button to test connectivity to the SQL Server.
Note:��If you are using Windows authentication, the credentials you are currently logged in with be used to test the connection, so it is best to log in and install with the credentials that the service will run as. The AccountServer service will need to be configured with these credentials after the installation completes, so might fail to start as the installation completes.��
- Click the��Provider��tab and ensure that SQL Server is selected.��
- Click the��Advanced��tab and set the SQL Server connection timeout. The default is 30 seconds.��
- If required, use the All tab to edit any variables.��
- Click the��OK��button.��
- Click the connection button for the Reports Database and configure the database the same way you configured the AccountServer Database. The Reports Database's default name is "StoragePlatformReports".
- When the databases have been configured, click the��Next��button.��
- Enter the Master password for the AccountServer and click the��Next��button.
- Select the Service Port bindings for the AccountServer and click the��Next��button.
- Check that the details are correct and click the��Apply��button.
The AccountServer will now be configured.
Note:��If you are using Windows authentication and the service fails to start, the service logon will need changing after closing the configuration wizard.
- Click the��Close��button.
Verify AccountServer installation
To verify that the AccountServer has installed correctly and connected to the SQL Server, open the most recent AccountServer log file. You should see details of the database being created.����
You should also check the database using SQL Management Studio.
Note:��The StoragePlatform and StoragePlatformReports databases are now populated with tables.
Your AccountServer using a separate SQL Server is now ready for use. Further configuration details for the AccountServer can be found in the Storage Platform manual.
Note on upgrading from V5.1:
The upgrade from V5.1 to V6 should be run from the old NameServer so that account information can be detected. Account details will be exported from V5.1 to a script in the��AS_Service\Data-Import\��folder. When the AS service is started, after the tables have been created, the script will be executed to populate the tables.��
Old Article ID: 81
Previous Views: 5165
Posted: 06 Jan, 2012 by -- .
Updated: 05 Mar, 2015 by Du Plessis S.