Delaying the Startup of a Service - System Administration - On-Premises - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

On-Premises System Administration
Platform
OnBase
Product
System Administration - On-Premises
Release
Foundation 22.1
License
Standard
Essential
Premier

In some instances, you may want to delay the startup of a service. In order to delay the startup of a service, the DMServiceLauncher.exe utility must be used to configure what services to delay. This utility is available from your first line of support.

To delay a service:

  1. Copy DMServiceLauncher.exe to the server where the service resides.
  2. Double-click on DMServiceLauncher.exe. The DM Service Launcher dialog box is displayed.
  3. Click Add. The Service Properties dialog box is displayed.
  4. Select the Service that should be delayed.
  5. Select the Data Source that the selected OnBase service logs onto.
  6. Click Save and Close.
  7. Repeat steps 3-6 for each service that you want to delay.
  8. Enter the number of seconds that the start of the service(s) should be delayed in the Startup Delay field.
  9. Click Save.
  10. Click Install. Clicking Install will install DM Service Launcher as service in Windows.
  11. In Windows, select Start | Control Panel.
  12. Double-click Administrative Tools.
  13. Double-click Services.
  14. Select the DM Service Launcher service, right-click and select Properties.
  15. Select Automatic as the Startup type.
  16. Click OK.

To use this with a particular OnBase service, ensure there are no dependencies configured for the OnBase service and make sure it is set to Manual startup. Add the service to the DM Launcher configuration following the above instructions. When the server starts, the launcher should wait for the time delay, connect to the database, and start the OnBase service.

When the DM Service Launcher service starts, it first waits for the specified time delay. It will then go through each service and try to connect to the Data Source. If the connection succeeds, the service will be started, and the program goes on to the next configured service. If it fails, it will sleep for 5 seconds and try the connection again. It should do this for up to 30 seconds per service, after which point it gives up and goes on to the next service. When all services have either started or timed out, the DM Service Launcher service will stop and exit.