Service Location and Deployment Configuration - Agenda - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Agenda

Platform
OnBase
Product
Agenda
Release
Foundation 22.1
License
Standard
Essential
Premier

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 Agenda runs must also be configured for Active Directory or LDAP authentication. The installer configures Agenda 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.