Page tree
Skip to end of metadata
Go to start of metadata

Note

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. 


  1. Backup your database before starting the installation process.
  2. Log into the Aptify database server with an account that has administrative privileges.
  3. If you have not already done so, back up your Aptify database server.
  4. To ensure a successful upgrade, you should remove Row Set Security from the Persons and Companies entities before beginning the install. You can reinstate the Row Set Security settings once the install is successful. Follow these steps for the Persons and Companies entities:
    1. Open the record for the entity in the Entities service.
    2. Click the Row Set Security tab and determine whether a rule is set for this entity.
    3. Record the rule information for use later in re-enabling this functionality.
    4. If a rule is set, right-click on the rule and select Delete from the drop-down menu. Otherwise, go to step 5.

    5. Repeat step d for any additional rules in the record.

    6. Click Save and Close.

  5. Close the Aptify desktop application on the database server, if currently running.
  6. Download the Aptify 6.2 Service Pack Installer ZIP file to a folder on the database server and unzip its contents. The database installer is the folder with name 'APTIFY_62_Database'.

    Note

    When using low-end hardware, Aptify recommends running the installation program locally on the database server; do not run it over the network.

    Note Concerning Character Limitations

    The Windows API requires that fully qualified file names are less than 260 characters. Aptify recommends that the Aptify 6.2 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.

  7. Browse to the location of the installation files, right-click the Setup application file under the folder and select the Run As Administrator option to launch the Aptify 6.2 installation program.

  8. 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.

    Note

    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.


  9. Review the Installation welcome screen and click Next to continue.

  10. Review the displayed setup information concerning your database server's configuration and click Next to continue. The installer identifies the set of Aptify applications detected on the database server. Options include Platform (for the Aptify Framework), Core Business Applications (for Aptify's standard CRM business applications), add-on applications, and if applicable, the optional e-Business/Surveys applications.

  11. The Service Pack Installer automatically identifies the current version of Aptify and components installed on the database server and selects the box(es) for the update(s) not currently installed.
  12. 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.1 installation, please do not reconfigure this again. Please follow the notes below if you want to freshly install SSRS with 6.2 installation.

    The location should be entered in the following format:

    https://<ServerName>/<SSRSServerName>?/<ReportsFolderName> 

    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.1 wants to upgrade to 6.2 and configure SSRS , then reset the attribute "InstallSSRS" to True in Setup.Exe.Config file, before starting the 6.2 installation. By default this attribute is set to False and will not reinstall SSRS since it is already installed and configured with 6.1 installation.

    Set the attribute as following in Setup.Exe.Config if SSRS need to be installed new during 6.2 installations

    <add key="InstallSSRS" value="True" />

  13. Click Next to continue.
  14. 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.2 installs successfully.


  15.  Click Next to continue.
  16. The Install Service Pack screen identifies what you will be installing. Review the items to be installed. 
  17. Click Finish to begin the installation.
  18. Click OK when prompted that 6.2 has been successfully installed to close the installer.
  19. Launch the Aptify desktop application to confirm that the update has been successfully installed. During the load process, the splash screen image should change and show the version increment from Version 6.1 to Version 6.2.
  20. For each client computer that connects to the Aptify Desktop client (including Application Servers and the e-Business server), you need to install the following software, if not already installed. You can find these files in the APTIFY_6_Desktop_Update.ZIP package, under the Data\OtherSetups folder. This zip can be found in your folder on the Aptify FTP site:
    • When using the Generic Import wizard with the Aptify 6.2 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.

    • Microsoft .NET 4.5 Framework, this was part of the 5.5.3 Desktop update, so it may already be installed.
    • 32-bit version of the Crystal Reports 13 viewer, this was part of the 5.5.3 Desktop update, so it may already be installed.

  21. If you disabled Row Set Security for the Persons and/or Companies entities in step 4, re-enable the rule(s).
    1. Open the record for the entity in the Entities service.
    2. Click the Row Set Security tab.
    3. Open a new Row Set Security sub‐type record.
      • Either click the New Record... button in the menu bar, or right‐click in the gray area and select New from the pop‐up menu to open a new record.

    4. Enter the rule you recording back in step 4 in the Base View Where Clause field.
    5. Enter a description for the rule.
    6. Click OK to save the rule.
    7. Enter additional rules for the same entity, if necessary. Aptify uses an AND operator to separate multiple Base View Where Clauses within a generated base view.
      • Alternatively, you can click OK and New in Step h to save the current and open a new Row Set Security record in one step.

    8. Save and close the Entities record.

    9. Regenerate the base view for any related entities that join the entity for which you just enabled row set security.

  22. If your organization uses the View Scheduling feature to schedule the execution of one or more views by an application server, review the instructions in Removing Duplicate Windows Tasks for Scheduled Views to prevent duplicate Windows Tasks from executing.
  23. If you have Aptify e-Business, one or more application servers, or Mobile Point of Sale installed, run the Object Repository Synchronizer utility to update the relevant bin folders so they have the latest Aptify objects. The Object Repository Synchronizer is included in the service pack's Utilities folder. Where applicable, be sure to only download objects from the relevant Sync Repository Objects record. See Important Post-Installation Considerations for more details.
  24. Once Aptify 6.2 is installed, to activate the Suggested Tabs features, an administrator must modify the Update Relevant Tabs Model scheduled task record to create a corresponding Windows task on the Application Server, Perform the following steps:
    1. In the Scheduled Tasks service of the Process Pipeline Administration application, find and open the Update Relevant Tabs Module scheduled task record.
    2. In the Job Account Name and Password fields of the Schedule tab, enter the username and password for the user account that is used to run scheduled tasks on the Application Server.
    3. Select the Is Enabled option.
    4. Save and close the record.
  25. Once Aptify 6.2 is installed, you can install the 6.2 version of the Aptify Web interface. See Implementing the Aptify Web Interface for more details.
    • If you have the initial release of the Aptify Web interface and you wish to install the 6.2 version, you will need to install a new Aptify site. See Implementing the Aptify Web Interface for more details.
  26. If you are using Melissa Data for address verification and using the COM Object version (rather than the web service version), you may need to change the rank of the Address Verification Systems record for the COM Object version (typically ID 1) so it is a higher rank than the web version (typically ID 3).