This topic describes how to install the Aptify site on a web server so users with valid user accounts in Aptify can access the system using a supported web browser.
To do this, perform the following steps:
The Aptify web interface should be installed and tested on a non-production environment first before applying to a production web server, just as if you were installing an Aptify Service Pack. Be sure to back up the server where you will install the production Aptify web server, to provide a fall-back option, in case a problem occurs during the Aptify website installation. |
When installing the Aptify browser-based interface, the setup program overwrites any existing site if you specify the same name and location. Before starting the install, copy/backup the old site to a different location and delete the existing site or select a different website location for the new site. Once the install is complete, you can review and migrate any configurations to the new site. |
Confirm that the database server has the same version of Aptify as the version you are installing on the web server (i.e., the database server has Aptify 6.0, and you are installing the Aptify 6.0 on the web server). This is a pre-requisite before you can install the Aptify site.
If you have recently upgraded to 5.5.6 from an earlier version of Aptify that did not support the Web interface (such as 5.5.1 or earlier), check your SQL Server instance to confirm that the Full-Text Search components are installed. This is an optional selection when installing Microsoft SQL Server, but the Aptify Web interface requires that your server support full-text indexes. |
For web servers that will be available over the public Internet, you should install and test the Aptify site within the firewall first before moving the web server outside your organization's firewall.
For web servers that will be available on the public Internet, you must secure the site using HTTP over a Secure Socket Layer (SSL) to create an HTTPS site. The default installation of the Aptify site requires SSL. The site will not load successfully unless the site is configured to use SSL. See Securing the Aptify Web Site Using SSL for additional information. |
Create a new domain account or identify an existing domain with a valid end user license account to use on the Aptify web server.
The Aptify web interface does not currently support the authentication of users from multiple domains from a single website. If your environment supports users in multiple domains, contact Aptify Technical Support for assistance. |
The account must be a trusted user with a valid end user license (elevated permissions are not required) to the Aptify database server with the appropriate privileges to conduct the Aptify activity. The SOA user should also be in the Users group.
During the setup process, the SOA user is added to the AptifySOAAppPoolGroup. This group is only intended for the SOA user and ensure user tokens are secure.
Per packaging requirements for this version, the Application Pool Identity used by the Aptify website is set to LocalSystem and the identity used by the AptifyServiceAPI (SOA layer) site is set to run as the user specified in the setup program. |
Log into the web server using an account with administrative privileges.
Aptify recommends that you log into the web server with a Windows domain user with administrative privileges. There are certain updates related to the authentication model with the Aptify browser-based interface that requires a domain user with access to the database server. If you do choose to install as a local administrative, these updates must be done manually. See Choosing an Authentication Method for more details. |
It is highly recommended that the user account used for the SOA layer is not used to log into the Aptify web server. If the SOA layer user account is used to log into the web server and then logs out, you may need to reset Microsoft IIS to restore features such as reporting. |
When prompted, enter login information for the database server, specifying an installation account with system administrator privileges to both the Aptify database and SQL Server. The installation 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 (through the Aptify User Administration wizard) 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 in SQL Server through SQL Management Studio. If in doubt, check the user's permissions in the Security > Logins area of SQL Management Studio before proceeding with the installation. |
The default installation path is c:\inetpub\wwwroot and the Aptify sub-folder is created automatically.
For example, if you want to use the location c:\inetpub\wwwroot\myorg to install the website files, the path to the Aptify sub-folder would be c:\inetpub\wwwroot\myorg\aptify.
The default installation path of the Aptify SOA layer is c:\inetpub\wwwroot\ and the web folder is AptifyServicesAPI. The path and location can be modified manually once the Aptify website is installed. |
This field can be left blank, and the setup program uses the server host name and domain name to create URLs.
Some additional configuration needs to be done to support the site name entered. Microsoft IIS must be updated with the new site name, and the host file at c:\windows\system 32\Drivers\etc\host must to be updated to include the web server’s IP address and the site name. |
The default location is C:\Program Files\Aptify 6.0.
Select the Culture that your users will be using from the drop-down list.
Selecting the appropriate culture will ensure localization of date/time format is reflected in the web interface.
Note: Only one culture per instance of the Aptify web interface is supported at this time.
See Using Localization Administration for more information on Cultures and Localization.
If your environment contains over 10,000 products (or if you expect that it will exceed this amount), you may want to increase the value of the maxProductCount attribute. See Defining the Products Attribute for Aptify Web for more information.
If your environment contains customer-made Search Configuration records and they are used in service applications other than the HTML5 Web service application, you need to update these records to point to the correct Service Application.The Search Configuration entity has a required field for service application. This field associates a Search Configuration with a particular instance of Aptify Services. By default, the installer program assigns all Search Configurations to the HTML5 Web service application.
If your environment contains customer-made Service Application records should review the security-related entities under the Web Services application. The RestrictViews field on the Service Application entity is enabled by default and will stop your application from executing any views not enabled under Service Application Views, and the entities for those views must have read access under Service Application entities.
If your environment contains customer-created Service Data Objects (SDOs) records, you should validate that they are assigned to the correct database objects and to the correct Service Application records. The installer program attempts to match existing SDOs to existing database objects. Any SDO assigned to this database object needs to be updated to point to the correct database object. The installer program cannot assign customer-created SDOs to Service Applications, as it cannot determine which Service Applications should be allowed. Any customer-created SDOs will not be assigned a Service Application, and therefore will not execute after the upgrade. Each SDO must identify the Service Applications that are allowed to execute it.
Aptify has updated the version (from version 6 to version 9) of the Newtonsoft JSON DLL used to support changes to the Aptify form template metadata generator. This update changes the strong name of the DLL, so any assemblies, websites, and executables that reference the Newtonsoft.Json.dll, even indirectly, may issue errors about not being able to find version 6 of the DLL. Aptify recommends that the projects directly referencing Newtonsoft.Json.dll be recompiled against version 9, or websites and assemblies must employ a binding redirect to point to version 9 in their web.config or app.config files, respectively:
<dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-9.0.0.0" newVersion="9.0.0.0" /> </dependentAssembly> |