Note | ||
---|---|---|
| ||
If your source and destination server are both running Aptify 5.5.5 and higher, the Aptify Configuration Migration (CM) Tool is already installed and can be launched directly from the Aptify desktop interface, you do not need to install CM Tool. However, if either is running a lower version of Aptify, you will need to install the CM Tool on the server. |
Info | ||
---|---|---|
| ||
This is first official release of the Aptify Configuration Migration (CM) Tool. If you have any questions or problems using the tool please contact Aptify Technical Support. Your feedback is appreciated! |
This topic describes how to install the Aptify Configuration Migration Utility (CM) Tool on a server (source or destination) so users with trusted accounts in Aptify can access the system using a supported web browser.To do this, perform the following steps:
Note |
---|
Note |
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 web site installation. |
Note | ||
---|---|---|
| ||
If you have an existing Aptify site, see important information related in Updating an Existing Aptify Web Site. |
...
Info |
---|
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. |
...
The account must be a trusted user with a valid license on the Aptify database server with the appropriate privileges to conduct Aptify activity.
...
Note | ||
---|---|---|
| ||
Per packaging requirements for this version, the Application Pool Identity used by the Aptify web site 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.
When installing Aptify 5.5.2, 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 in Aptify 5.5.2 for more details.
...
- See Updating an Existing Aptify Web Site for more details.
...
- Aptify 5.0 Desktop client
- Microsoft .NET Framework 4.5
- ASP .NET MVC 4
...
- The client application provides the active Aptify Object Repository service used during the installation process.
...
that the Aptify CM Tool must be installed on both the source and destination servers. The order in which you install the tool does not matter. |
Perform the following tasks before installing the Aptify CM Tool on a source or destination server:
- Verify the Aptify Desktop client is installed with an active Aptify Object Repository
- Verify that the user installing the tool has sufficient rights to the Aptify database and SQL Server.
- Verify the user installing the tool has system administrator privileges to both the Aptify database and SQL Server.
- Verify that the CM Tool setup files are NOT set to read-only
- Verify that the Aptify installation directory where the CM Tool is to be installed is NOT read-only
Perform the following steps to install the CM Tool.
Note | ||
---|---|---|
| ||
Aptify recommends that you have a current database backup available before installing this tool. In addition, Aptify recommends installing and testing the CM Tool in a test environment first. |
- Download the Aptify CM Tool installation ZIP file to a folder to the server you want to install the tool (source or destination) and unzip its contents.
- Browse to the location of the installation files and run Setup.exe to launch the installation program.Review the set of requirements to install. If your environment does not meet one or more of the specified requirements, click Cancel to abort the installation. Otherwise, click Next to continue.See Server Requirements for the Aptify Web Interface for more information on the Aptify site requirements.
- Click Next to continue.
- , double-click the Setup application file.
- You can also right-click the Setup application file and select the Run as Administrator option. On certain Windows servers, the Run as Administrator option bypasses the server's User Access Control (UAC) for the duration of the installation.
- You can also right-click the Setup application file and select the Run as Administrator option. On certain Windows servers, the Run as Administrator option bypasses the server's User Access Control (UAC) for the duration of the installation.
When prompted, enter login information for the database server, specifying an installation account with system administrator privileges (such as sa).
Aptify 5.5.1 Login
Aptify 5.5.2 Login
- Click OK to continue.
- When installing Aptify 5.5.1, review the installation details and select one of the following options:
- To install only the Aptify site, ensure that the Web Site option is selected and the Install Server Component option is cleared. This option is only applicable if you have previously installed the Aptify Server Components on the Aptify database server.
- To install the Aptify web site and the Aptify server component, keep both options selected.
- To install only the Aptify server components, ensure that the Web Site option is cleared and the Install Server Component option is selected.
- This option installs the necessary entities and metadata on your database server.
- While you can run the installer multiple times to create multiple Aptify sites that communicate with the same database server, you should only install the necessary entities and metadata on your database server once.
- Select the Website under which the Aptify site will be hosted.
- Default Website is selected by default, however you can host the Aptify website under another site. The site must be manually created through the IIS Manager prior to running the Aptify web site setup.
- Default Website is selected by default, however you can host the Aptify website under another site. The site must be manually created through the IIS Manager prior to running the Aptify web site setup.
- Enter the Application Pool name to be used for the Aptify web site.
- The default application pool name is Aptify_HTML5
- Per packaging requirements for this version, the Application Pool Identity used by the Aptify web site is set to LocalSystem.
- Enter the Application Pool name to be used for the Aptify SOA site.
- The default application pool name is Aptify_SOAWeb
- The default application pool name is Aptify_SOAWeb
- Specify the trusted user account that you want to use for the Aptify web site in the SOA Pool User Name field.
- Enter the password for this user in the Password field.
- Specify the location where the Aptify web site files should be installed on the web server in the Website Location field.
The default installation path is c:\inetpub\wwwroot and the Aptify folder is created automatically.
For example, if you want to use the location aptify1 rather than aptify, in the default location, you will need to create a folder called aptify1 under c:\inetpub\wwwroot.- Click OK to continue.
- Review the set of requirements to install. If your environment does not meet one or more of the specified requirements, click Cancel to abort the installation. Otherwise, click Next to continue.
- In the Aptify Directory field, enter the directory path where your Aptify Desktop client is installed.
- Aptify is typically installed under C:\Program Files\Aptify 5.0.
- or C:\Program Files\Aptify 5.5.
- Aptify is typically installed under C:\Program Files\Aptify 5.0.
- In the Shortcut Name field, enter a location on the SQL Server to which your user account has read/write access in the UNC Path to a Shared Folder field. (This is the Windows domain account you have used to log into the web server.)
- You must enter the location's path in the UNC (Universal Naming -Convention) format. The location should be a shared drive or folder on the SQL server.
During installation, the installer copies certain assemblies to the server location you specified. Therefore, the account currently logged into the web server must have read/write access to that location on the database server.
Aptify 5.5.1 Web Services Installation Aptify 5.5.2 Web Services Installation
- Click Next to continue and review your installation options.
- Click Finish to begin the installation process.name for the tool's shortcut. This name is used to create a Windows Desktop shortcut for this application.
- The name should be unique, if the name already exists, the setup program will not be able to create the Windows Desktop shortcut.
- The name should be unique, if the name already exists, the setup program will not be able to create the Windows Desktop shortcut.
- Click Next.
- Click Finish to start the installation.
- Installation will take several minutes to complete.
- Installation will take several minutes to complete.
- Click OK when prompted that Aptify has been successfully installed to close the installer.
- If a problem occurs during the installation, the Aptify Installer will notify you that an error occurred.
- If the
- install is not successful
- Restart the IIS service.
- Although technically not required, restarting the IIS service will ensure that all existing sessions connected to the web server are terminated before the website is used.
- You can restart the IIS service from either the Internet Information Service (IIS) Manager or from the Windows Services dialog.
- When you are installing Aptify 5.52, if you want to support both trusted (Windows users) and untrusted (SQL server) users, you will need to make updates to the web config file to support this. See Configuring Alternate Authentication Methods in Aptify 5.5.2 for more details.
- Connect to the Aptify web site to confirm that it loads properly using a supported web browser.
- By default, this step assumes that you have a user account (trusted or untrusted) with a valid license in Aptify.
- If connecting to Aptify directly from a web server that is not in a nested (hierarchical) domain, enter the following address: https://localhost/Aptify
- If you accepted the default virtual directory name, enter http://localhost/aptify
- If connecting to Aptify directly from a web server that is in a nested (hierarchical) domain, you must address it with the fully qualified domain, such as: http://server.teir2.teir1.com/aptify
- If connecting from another computer on the network, then enter http://[server name]/aptify in the browser window, contact Aptify Technical Support for assistance.
- Repeat the above steps for the other server (source or destination).
Note | ||
---|---|---|
| ||
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 web site is installed. |
privileges to both the Aptify database and SQL Server.
Note |
---|
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. |