Service Location and Deployment Configuration - Unity Client - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Premier - Essential

Unity Client

Platform
OnBase
Product
Unity Client
Release
Foundation 23.1
License
Standard
Premier
Essential

After clicking Next, the Service Location dialog is displayed.

  1. Click Add.
  2. Enter in the Display Name field the name of the service location.
  3. Enter in the Service Path field the full URL to the OnBase application or Web server service (for example, https://machinename/AppServer/Service.asmx or https://machinename/AppNet/Service.asmx).
    Note:

    URLs that use the HTTPS binding must be correctly configured on the server for secure connections.

  4. In the Data Source field, enter the data source name for the appropriate data source.
  5. Select Use NT / LDAP Authentication if your system uses Active Directory or LDAP Authentication.
    Note:

    In order to use Active Directory or LDAP authentication, the database against which Unity Client runs must also be configured for Active Directory or LDAP authentication. The installer configures Unity Client to match the authentication scheme of the database.

  6. Select Use ADFS if your system uses AD FS (Active Directory Federation Services) authentication.
    Note:

    Use ADFS is not the same Active Directory authentication scheme as Use NT/LDAP Authentication. The Use ADFS option is not available for all modules. If this option is not displayed, the module you are installing either does not support AD FS or must be manually configured for AD FS authentication. You cannot enable both Use ADFS and Use NT/LDAP Authentication. For more information about configuring OnBase to use AD FS, see the Legacy Authentication Methods module reference guide.

    Selecting Use ADFS causes the remainder of the deployment to be run in Advanced Mode, even if Advanced Mode was not selected initially, because the configuration file for the module must be updated before signing and finalizing the deployment.

    Note:

    Depending on the module being updated or added, you may be required to complete information in additional dialogs specific to the module. See the main installation steps above for information on any additional dialogs or steps that must be completed before signing the deployment.

    For information on how to use the obunity.exe.config file to configure Unity Client for ADFS, see the Authentication module reference guide.

  7. Click Next. The Additional Settings dialog is displayed.
  8. On the General tab, in the Default Mail Client drop-down select box, select the default mail client that users will use to send external mail from within the Unity Client.
  9. Select the Enable HTTPS Web Requests if you are installing Application Enabler and you want to expose an HTTPS endpoint to allow third-party applications to perform Application Enabler context events.

    Type the port number for the HTTPS endpoint in the Port field. The default value is 15425.

    Tip:

    For more information on HTTPS Automation requirements, see HTTPS Automation Requirements.

    Note:

    If HTTPS Automation is selected during installation, the location of the HTTPS certificate must be specified in the obunity.exe.config file before signing the deployment.

  10. Select the Enable Persistent Logon check box if users should be able to use persistent logon. When selected, the Remember me on this computer check box is displayed in the log on dialog box. When this check box is selected, the Unity Client stores the user's credentials and uses them to automatically log on to OnBase during future sessions. Credentials are stored until the user manually logs off. This feature is only available with OnBase authentication.
  11. Select the Enable Email Link As check box if the Send To | Mail Recipient (as Link) option should be available to users:

    Select Upop URI if Unity Pop hyperlink URI files will be sent via Send To | Mail Recipient (as Link). Select Upop Shortcut File if Unity Pop shortcut files will be attached via Send To | Mail Recipient (as Link). Select DocPop URL if DocPop hyperlink URLs will be sent via Send To | Mail Recipient (as Link).

    Note:

    The Create Integration Hyperlink privilege is required to send Upop URI links.

    Note:

    If checksums are enabled for DocPop, the generated DocPop URL will also contain a checksum, but the link will only be created for a list of documents with a size that is less than or equal to the DocumentQueryLimit Application Setting in the Application Server's web.config file settings.

  12. Click Next. The Default Configuration File dialog is displayed.
  13. You can select a default configuration file. If you don't want to specify a file, select None.

    If you want to specify a configuration file and include it with the deployment, select the Include Configuration File with Deployment option. Specify the path to the configuration file in the Configuration Path field.

    If you want to specify a configuration file but not include it in the deployment, select the External Path to Configuration File option. Specify the path to the configuration file in the External Path field. The path specified must be accessible to users.

  14. Click Next. The Application Enabler Options dialog is displayed.
  15. On the General tab, select Enable HTTP Automation to expose an HTTP endpoint to allow third party applications to perform Application Enabler context events.
    Type the port number for the HTTP endpoint in the Port field. The default value is 15412.
  16. Click the Pop Configuration tab.
  17. The Pop Configuration tab allows you to configure URLs for DeficiencyPop, Patient Window, and FolderPop.

    Specify the appropriate URL in the field for each feature as needed.

    • For DeficiencyPop, enter the URL for the Medical Records Login.aspx page. If DeficiencyPop should share sessions with Application Enabler and not require a login every time a related context is triggered, select the Enable session sharing check box. In order for this to function properly, users must log into Application Enabler using a service location which is pointing to a Medical Records Management server. For checksum validation to occur, EnablePopChecksum must be set to true in the Medical Records Management server's web.config file. For more information on the EnablePopChecksum setting, see the Medical Pop Integrations documentation. If Include external deficiencies is selected, the external attribute is set to true. For more information on these settings, see the Application Enabler module reference guide.

    • For Patient Window, enter the URL for Patient Window Login.aspx page. If Patient Window should share sessions with Application Enabler and not require a login every time a related context is triggered, select the Enable session sharing check box. For checksum validation to occur, EnableChecksum must be set to true in the Patient Window's web.config file. For more information on the EnableChecksum setting, see the Medical Pop Integrations documentation. If View patient banner is selected for Patient Window, the showBanner attribute is set to true. For more information on this setting, see the Application Enabler module reference guide.

    • For FolderPop, enter the URL to the FolderPop.aspx page. Select the Open FolderPop Results in Separate Windows option if you want FolderPop links to be opened in separate windows. Select the Send the session ID to web server option if you want the AE - FolderPop context to reuse the active session that Application Enabler has instead of consuming a new session. If the option is not selected, users will have to log into each FolderPop instance that is launched after logging into Application Enabler.

      Note:

      The Application Enabler - Retrieve Documents and Application Enabler - Retrieve Folders contexts still require users to log in through a standard Application Server and cannot use a Medical Records Management server.

  18. Click Next. The Deployment Signing dialog box is displayed.
    Note:

    Do not sign the deployment until you have made any required changes to the obunity.exe.config file. See Before Signing the Deployment.