Aptify strongly recommends that you install and test the installation on a test environment first using a copy of your production server before running it directly on the production server. |
If a rule is set, right-click on the rule and select Delete from the drop-down menu. Otherwise, go to step 5.
Repeat step d for any additional rules in the record.
Click Save and Close.
Download the Aptify 6.3 Service Pack Installer ZIP file to a folder on the database server and unzip its contents. This Zip file has installer for Aptify Database installer, Aptify Web Installer and Aptify eBusiness6 installer. The database installer is the folder with name 'APTIFY_630_Database'.
When using low-end hardware, Aptify recommends running the installation program locally on the database server; do not run it over the network. |
The Windows API requires that fully qualified file names are less than 260 characters. Aptify recommends that the Aptify 6.3 Service Pack Installer ZIP file is unzipped in a folder close to the drive's root folder (for example C:\Downloads) in order to limit the possibility of exceeding the character limitation for fully qualified file names imposed by the operating system. |
Enter login information for your database server. Specify an account with system administrator privileges to both the Aptify database and SQL Server. The user should also be tied to a Developer license to ensure that the setup can perform such tasks as entity creation when needed.
Selecting the System Administrator option when creating a user in the Aptify database sets the user to a dbowner in SQL Server. It does not add the user to the sysadmin role. You will need to manually add the user to the sysadmin role through SQL Server. If in doubt, check the user's permissions in the Security > Logins area of SQL Management Studio before proceeding with the installation. |
Review the Installation welcome screen and click Next to continue.
Only if you are planning to reinstall the SQL Server Reporting System (SSRS) in your environment, enter the location where the SSRS reports are stored in the SSRS Reports Path field. If it is already installed with 6.3 installation, please do not reconfigure this again. Please follow the notes below if you want to freshly install SSRS with 6.3 installation.
The location should be entered in the following format:
You can leave this field blank if an SQL Reporting Server is not already configured or if you are not planning on using SSRS in your environment. The location can be configured at a later time. |
SSRS setup is by default installed with 6.1 upgrade installation. If a Client on 6.2 wants to upgrade to 6.3 and configure SSRS , then reset the attribute "InstallSSRS" to True in Setup.Exe.Config file, before starting the 6.3 installation. By default this attribute is set to False and will not reinstall SSRS since it is already installed and configured with 6.2 installation. Set the attribute as following in Setup.Exe.Config if SSRS need to be installed new during 6.3 installations <add key="InstallSSRS" value="True" /> |
If you have organization-specific configurations, you can check any or all of the options on the Validation step to help identify invalid repository and database objects, and foreign key constraint errors.
Aptify recommends that you check all validation options to ensure Aptify 6.3 installs successfully. |
When using the Generic Import wizard with the Aptify 6.3 Desktop interface to import a Microsoft Access 2013 or 2016 file, the import may fail if running the 64-bit version of Microsoft Office 2013 or 2016. The error that is generated is: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. The import fails because the user's computer has the 64-bit version of Access 2013 or 2016 installed, while the Aptify shell requires the 32-bit version. The current workaround for this issue is to install the 32-bit version of the Access Database Engine Redistributable on the user's computer. The installation file, AccessDatabaseEngine.exe, can be found in the Access Database Update sub-folder.
If you are planning on viewing reports using SQL Server Reporting Services (SSRS), you will need to install the 32-bit version of the Microsoft SQL Server System CLR Types and Report Viewer.
Save and close the Entities record.
Regenerate the base view for any related entities that join the entity for which you just enabled row set security.