Installing the 32-Bit Application Server - Application Server - English - Foundation 22.1 - OnBase - external

Application Server

Platform
OnBase
Product
Application Server
Release
Foundation 22.1
License

This section describes installing the OnBase 32-bit Application Server using the graphical installer.

For complete details on running the installer from the command line, see Controlling the Installer from the Command Line.

If you are modifying or removing a previous installation, see Change, Repair, or Remove an Installation.

To install the 32-bit Application Server:

  1. Launch the Application Server installer by executing setup.exe. This executable is usually located in the ..\install\Application Server\ folder of your source installation files.
    Note:

    If the installer is being copied from the source location to be run from a different location, the entire Application Server folder and its contents must be copied to the new location.

    The welcome page is displayed. If you are modifying or removing a previous installation, the Program Maintenance dialog is displayed. See, Change, Repair, or Remove an Installation.

  2. Click Next. The Destination Folder page is displayed.
  3. To change the installation location of the Application Server, click Browse. The Change destination folder dialog box is displayed.
  4. Enter the path to the destination folder in the Folder name field or select it from the Look in drop-down list. If the destination folder is not changed, the 32-bit Application Server is installed to the following default location: C:\inetpub\wwwroot\AppServer\
    Note:

    The installer only supports installation to a virtual directory. You cannot use the installer to install to a Web site root. The OnBase Web and Application Servers cannot be installed to the same virtual directory. The name of the virtual directory must match the configured Application Name for the server.

  5. Click Next. The Additional Components Destination Folder page is displayed.

    To change the installation location of additional components being installed with the Application Server (such as the Web Application Management Console), enter a new folder location or click Change to navigate to the folder location.

    Note:

    It is highly recommended to install additional components in a separate directory from the Application Server.

  6. Click Next. The Application Server Settings page is displayed.
    • Select a Web Site to install the OnBase Application Server to from the drop-down list. The Web Site list is populated with the Web sites configured in IIS and available to the target machine.

    • Enter a name for the OnBase Application Server in the Application Name field. The default name for the Application Server is AppServer.

      Note:

      The OnBase Web and Application Servers cannot have the same Application Name. It is a best practice not to use parentheses in the Application Name.

    • Select Use identity impersonation to run the IIS worker process to use identity impersonation to run the installed OnBase Application server under the account specified. If this option is deselected then the server runs under the Network Service account.

      The impersonation account is granted modify rights to the directories and sub-directories of the Application server (in a default installation, AppServer is the Application Server directory). The installer does not add modify rights for any other groups.

      Note:

      Ensure that the account the installed server is running under is granted modify rights to the server directories. If modify rights are not extended, you may experience permissions errors in modules attempting to modify files on the server.

    • Select Enable TLS to run the Application Server with an HTTPS connection. If this option is selected, you must ensure that your server is correctly configured for HTTPS connections.

      If this option is deselected then an insecure network connection is used. You are prompted to acknowledge that you understand the risks associated with disabling this security layer before you can proceed with the installation.

    • Select Use NT/LDAP Authentication to enable Active Directory or LDAP Authentication for the Application Server.

  7. If you selected Use identity impersonation to run the IIS worker process for the Web or Application Server settings, the IIS Settings page is displayed.
    • In the User Name field, enter the domain and user name to use to run the IIS worker process for your server. This must be entered in the domain\username format.

    • In the Password field, enter the password that corresponds to the user name provided.

    • In the Confirm Password field, re-enter the password that corresponds to the user name provided. This is used to ensure that the password is typed correctly.

  8. Click Next. The Ready to install... page is displayed.
  9. Select Create Desktop shortcut(s) when applicable to create a shortcut to the Web Application Management Console on the Windows desktop.
  10. Click Install to begin the installation.

    Click Back to return to the previous page to change configuration options, or click Cancel to close the installer without installing the Application Server.

    When the installation is complete, the Completed the Hyland Application Server x86 Setup Wizard page is displayed.

  11. Depending on whether you want to configure data source connection strings at this point, do one of the following:
    • Click Finish to close the installer without configuring connection strings. You will still need to configure connection strings in the Application Server web.config file before the Application Server will function correctly.

    • Select the Launch Web Application Management Console option and click Finish. The connection strings dialog box from Web Application Management Console is displayed.

    The connection strings dialog box allows you to configure connection strings.

  12. To encrypt all connection strings configured in the application's .config file, ensure the Options | Encrypt Connection Strings menu option is selected. This option is automatically selected by default every time you open the connection strings dialog box, and the connection strings are encrypted when the .config file is saved.
    CAUTION:

    It is strongly recommended to encrypt the connection strings. If they are not encrypted, all data source connection information is visible in the .config file and could expose sensitive data, including any entered database user names and passwords.

  13. Click Add to start creating a new connection string. The fields on the right become available for interaction.
  14. If you are configuring Reporting Dashboards with a secondary connection string with a read-only database user account, select Options | Populate Read-Only User. This optional feature populates the User ID and Password fields with the credentials for the read-only user. See the Reporting Dashboards documentation for more information.
    If you are creating a connection string for any other purpose, skip this step.
  15. In the fields on the right, enter the following information about the data source:

    Option

    Description

    Data Source Name

    A unique name that you create to identify the connection string.

    Note:

    This identifying name may be different from the name of the actual database.

    Data Provider

    The data provider type used for the database. Select one of the following:

    • System.Data.SqlClient: Select this for a SQL Server database.

    • Oracle.ManagedDataAccess.Client: Select this for an Oracle database.

    Note:

    Only SQL Server and Oracle data providers can be used to connect to the OnBase database.

  16. Depending on your selection for Data Provider in the previous step, enter the following database connection information:
    • If System.Data.SqlClient is selected (for a SQL Server database):

      System.Data.SqlClient Option

      Description

      Data Source

      Enter the server\instance name of the SQL Server instance hosting the database.

      Database

      Enter the name of the SQL Server database.

    • If Oracle.ManagedDataAccess.Client is selected (for an Oracle database):

      Oracle.ManagedDataAccess.Client Option

      Description

      TNS Connection String

      Select this option to enter a full TNS connection string to connect to the Oracle database. Deselect the option to use the connection name instead.

      Note:

      Selecting this option enables the Host, Database, Protocol, and Port fields for interaction.

      Data Source

      Enter the TNS name or connect descriptor of the Oracle database.

      Note:

      This field is available only if the TNS Connection String option is deselected.

      Host

      Enter the host address of the Oracle database.

      Database

      Enter the name of the Oracle database.

      Protocol

      Select the protocol to use for connecting to the Oracle database. Options are:

      • TCP

      • TCPS

      Port

      Enter the port to use for connecting to the Oracle database.

  17. Enter the following security information:

    Option

    Description

    Integrated Security

    Select this option to use Windows Authentication to connect to the database.

    CAUTION:

    It is strongly recommended to use integrated security instead of a database account for authentication. To use integrated security, the Windows user connecting to the database must be the same user that is running the connecting server or service (such as the Application Server). This user must also be configured with the configgp role in the database.

    User ID

    The user name of the database user account accessing the database.

    Note:

    This user name is for a database user account, not a user account for OnBase.

    Password

    The password of the database user account accessing the database.

    Note:

    This password is for a database user account, not a user account for OnBase.

  18. Enter any additional options.

    Option

    Description

    Additional Options

    Any additional options for the connection string. For more information on available connection string options and syntax, see the documentation for your database provider (SQL Server or Oracle).

  19. Click Test Connection to test whether the entered information forms a valid connection string.
  20. Click Create to save the information in the fields and create the connection string. The name of the data source is added to the Data Sources list on the left, and the connection string is displayed in the Connection String section.
  21. Select File | Save to save the .config file.
  22. Select File | Close to exit the connection strings dialog box.
    Note:

    To ensure that the required system settings take effect, it is considered a best practice to restart the installing machine once the installer has finished.