Installing Integration for Duck Creek - Integration for Duck Creek - Foundation 24.1 - Foundation 24.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Integration for Duck Creek

Integration for Duck Creek
Foundation 24.1

The OnBase Integration API (OIA) that is the core of the Integration for Duck Creek is installed when the Application Server is installed.

For more information about general installation and configuration of the Application Server, see the Application Server module reference guide.

In order to enable the OIA, the Application Server's web.config file must be modified.

To enable the OIA:

  1. In the Application Server's web.config file, navigate to the OWIN-specific settings within the appsettings section.
  2. In the AppServerOrigin element, in the value attribute enter the base URL of the Application Server. In a load-balanced environment, this value is the load balancer.
  3. In the owin:AutomaticAppStartup element, ensure the value attribute is set to true in order to automatically enable the OIA endpoints upon Application Server initialization.
  4. Navigate to the OnBase Integration API-specific settings within the appsettings section.
  5. In the owin:oia:msgItemTypeId element, in the value attribute enter the EIS Message Item Type ID of the Message Item Type that is configured to capture Keyword Update requests for processing in Workflow.
  6. In the owin:oia:lifeCycleId element, in the value attribute enter the Workflow life cycle ID of the life cycle that is configured to process Message Items captured by the Keyword Update service.
  7. In the owin:oia:tmpFilePath element, in the value attribute enter the path to a directory that will contain temporary files generated by the Document Upload service.

    In load-balanced environments, the owin:oia:tmpFilePath setting must be configured to use a UNC path accessible by all Application Servers exposing OIA endpoints.

  8. In the owin:oia:tmpFileAgeInMs element, in the value attribute enter the time in milliseconds after which generated temporary files are able to be deleted by the internal cleanup service.
  9. In the owin:oia:cleanupIntervalInMs, in the value attribute enter the time in milliseconds that is the interval of time that the internal cleanup service will use to scan the temporary file directory.
  10. After making the necessary changes, save and close the web.config file.