The following procedure describes how to install the Healthcare Form Manager using the installer and setup wizard. To install the Healthcare Form Manager using a command line, see Controlling the Installer from the Command Line.
If you are upgrading a Healthcare Form Manager deployment that was installed manually, be sure to uninstall the old components before running the installer. If the previous deployment was installed using the installer, you do not need to uninstall the old components.
To install the Healthcare Form Manager using the installer:
- Open the folder containing the installer.
- Double-click setup.exe. The Hyland Healthcare Form Manager Setup Wizard is displayed.
Click Next. The Destination Folder page is displayed.
- Enter the directory where the Healthcare Form Manager application should be installed. To browse to the directory, click Change.
Click Next. The Data Source page is displayed.
Enter the name of a valid connection string in the field. This value should match the name of a connection string configured in the web.config file for the Application Server.
For information about configuring data source connection strings, see the Application Server module reference guide.
Click Next. The Healthcare Form Manager Settings page is displayed.
- Select the Web site where the Healthcare Form Manager should be installed.
Enter a name for the Healthcare Form Manager application in the Application Name field.
It is considered a best practice to omit parentheses from the Application Name.
Under Communication Method, specify how the Healthcare Form Manager and the OnBase Application Server will communicate.
.NET remoting allows the Healthcare Form Manager to use binary over HTTP to communicate with the Application Server. Remoting provides better performance than SOAP and is enabled by default.
The Healthcare Form Manager may be unable to use remoting if a firewall needs to inspect the information passed between the Application Server and the Healthcare Form Manager, such as when the two servers are hosted on different machines. In these situations, use SOAP.
SOAP allows the Healthcare Form Manager to use XML SOAP over HTTP to communicate with the Application Server. This option is useful for load balancing or situations where a firewall needs to inspect the information passed between the Healthcare Form Manager and the Application Server.
If a load balancer is balancing traffic from the Healthcare Form Manager to the Application Server, then the Healthcare Form Manager must be configured to use SOAP.Tip:
In most situations, select Remoting if the Healthcare Form Manager and the OnBase Application Server are hosted on the same machine. If the Healthcare Form Manager and the Application Server are hosted on different machines, select SOAP.
Select any other IIS settings you want to enable.
Use identity impersonation to run the IIS worker process
Identity impersonation allows the Healthcare Form Manager process to run under a specified account. If this option is deselected, then the Healthcare Form Manager process runs under the Network Service account.
Select to run the Healthcare Form Manager using an HTTPS connection. If this option is selected, you must ensure the server is correctly configured for HTTPS connections.
If this option is deselected, then an HTTP connection is used. When you click Next, you are prompted to acknowledge that you understand the risks associated with disabling this security layer before you can proceed with the installation.
Use NT/LDAP Authentication
NT/LDAP authentication allows users of the Healthcare Form Manager to be logged on using their Active Directory or LDAP authentication credentials, provided OnBase is configured for that authentication scheme.
Click Next. You are prompted to provide the URLs for the Healthcare Form Manager and the Application Server.
In the Healthcare Form Manager base URL field, enter the virtual root for the Healthcare Form Manager.
The installer only supports installation to a virtual directory. You cannot use the installer to install to a Web site root.
If you selected Enable TLS earlier in the installation, the Healthcare Form Manager base URL must begin with https://. The name of the virtual directory must match the Application Name configured on the previous screen.
In the Application Server URL field, enter the full URL to the Service page on the OnBase Application Server you are installing. The file extension of the service page depends on the Communication Method you selected on the previous screen.
If you selected Remoting, the service page is Service.rem.
If you selected SOAP, the service page is Service.asmx.Tip:
Use localhost in the URL of the Application Server if it is installed on the same machine as the Healthcare Form Manager. For example, https://localhost/AppServer64/Service.rem.
Click Next. If you enabled identity impersonation, you are prompted for impersonation account credentials.
If prompted, enter the impersonation account credentials.
In the User Name field, enter the domain and user name to use to run the IIS worker process for the Healthcare Form Manager. This must be entered in the domain\username format.
In the Password field, enter the password for the user account provided.
In the Confirm Password field, re-enter the password for the user account provided. This field is used to ensure that the password is typed correctly.
The impersonation account is granted modify rights to specific files and folders in the directory where the Healthcare Form Manager is installed. The installer does not add modify rights for any other groups. If impersonation is not used, users may experience permissions errors when the Healthcare Form Manager attempts to modify certain files.
- Click Next. The installer is now ready to install the Healthcare Form Manager.
- Click Install.
- When the installation is complete, click Finish.
- Modify Web.config settings as needed. See Configuring Web.config Settings.