Creating Multiple Portals - External Access Client - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - external

External Access Client

External Access Client
Foundation 23.1

For each installation of the External Access Client, multiple portals can be configured in different virtual directories.


One External Access Client license is required for each portal.

To create additional portals, the following steps are required:

  1. Create a new folder to house the directory for each new instance of the External Access Client.
  2. Copy the contents of the External Access Client directory, then paste them into the new folder.
  3. Modify the web.config file for the new External Access Client to point to the correct virtual root. The following example has been modified:
                            <add key="dmsVirtualRoot" value="http://DOC-019794/ExternalAccessClientHR" />

    The value should reflect the machine and virtual directory that contains the new External Access Client.

  4. Remove the following from the web.config file of the new portal:
    <add key="ExternalAccessNum" value="[portal ID]" />

    The value of the value attribute contains a portal ID number that tells the External Access Client what portal to launch. When the element is not present, you are prompted to complete portal setup for a new portal upon accessing the External Access Client.

  5. Create a new application pool for each additional portal. For more information, see the Web Server documentation.
  6. Go to the new instance of the External Access Client. The Portal Setup page is displayed.
  7. Enter a name for the portal in the External Client Name field.
  8. Select a Layout Type. This selection determines the portal's subscription level, which affects which StatusView portlets available in this portal and determines which Monthly Active-User Fee is charged.

    See Licensing for more information about Monthly Active-User Fees.

    The following options are available for selection:

    • Read Only- Grants access to Custom Query, Folder, Envelopes, External Links, and HTML portlets.

    • Contribute- Grants access to all Read Only portlets as well as DKT, E-Forms, and File Upload portlets.

    • Full Access- Grants access to all Read Only portlets and all Contribute portlets as well as Workflow, Workflow Dashboard, Workflow Process Statistics, Workflow Queue Activity, Workflow Queue Filter, WorkView Filter, and WorkView Summary portlets.

    • Internal User- Grants access only to internal OnBase users. The portal can be configured for use by existing OnBase users or by external users. When configured for Internal User, existing OnBase users are able to log in to the External Access Client. When configured for Read Only, Contribute, or Full Access, users who do not already exist in OnBase are able to create new accounts and log in to the External Access Client.

      When the portal is configured for Internal User, the Create Account page is not available from the portal. When an OnBase user logs in to the portal, a concurrent license is consumed.

      When this option is selected, only the External Client Name, Layout Type, and Admin User Group fields are required.

  9. From the Admin User Group drop-down list, choose the user group that will have administrative rights in the portal.
  10. From the Super User Group drop-down list, choose the user group in which users will be placed if they are granted Super User privileges.

    This information can be changed by an administrative user after portal setup is complete.

  11. Enter a valid e-mail address in the Administrator Email Address field. Create a password in the Password field and retype it in the Verify Password field to ensure the passwords match.
    This creates an administrative user. The administrative user belongs to the user group specified in the Admin User Group field. The administrative user can then log in and configure the External Access Client.
  12. Click Run Setup. A Message dialog box appears.
  13. Click OK to confirm the portal has been created.

    If you open the web.config file, you will see that the ExternalAccessNum ID is present with a new value. This value is assigned to the newly created portal.


    User accounts do not carry over to the newly created portal. Users can only belong to one portal.

Any configuration that takes place in the new portal is unique to that portal, and it does not affect any existing portals.