Wondering how you can create a new Unity Scheduler Service Instance? This blog and the video below will show you how.

How to Create a New Unity Scheduler Service Instance

How to Create a New Unity Scheduler Service Instance

1. First, navigate to the new task group that you want to use to run your workflow timers within Unity management console. You’ll need to create a new Unity scheduler service instance associated with this task group. You can do this via the command line, but we tend to prefer to write it out with a notepad first.
2. To start, you need to enter the path of your scheduler service executable. This is typically found in the C drive program files 86 Hyland services Unity scheduler. Copy out that path.
3. Next, enter in the executable name. For our example, it was Hyland.core.scheduler.NTService.exe.
4. Important: Make sure your path is within double quotes. Next, we’ll enter the command, which is flash create.
5. From here, to create the new instance, there are four required parameters:
   1. For our video example in the demo above, -SN is going to be the service name for our new service. So, we entered Hyland Unity scheduler-workflow timer.
   2. Next, we needed to enter “OBU” which is the OnBase service account that will be set up for this service. In our example environment, our service account in OnBase was called OB service.
   3. Next, it’s time to add the OBP parameter, which is the password for the specified OnBase service account.
   4. The last of the four required parameters is OBD which is going to be the name of your onbase ado.net connection string.
6. Now, the next parameter is OBG. While this isn’t required, if you don’t provide a value for OBG, the service that you create will run the tasks for the unassigned task group. In this case in our example demo, we wanted it to run for our workflow timers task group, so we went in and indicated that name.
7. Now, beyond this, there are five optional parameters:
   1. DN will be the display name that shows up in the Windows services list, so we changed our service name a little bit to “Hyland unity scheduler workflow timers.” If you don’t specify a value for display name, then it’s just going to use the service name in that first parameter that we provided.
   2. Next is desc for description. This is going to be the description that shows up in your Windows services list. For our example, we entered “Hyland unity scheduler instance to run workflow timers task group.”
8. We won’t dive too deeply into the next three parameters, but they are:
   1. -U, which is if you’d like to run your Windows service under a domain account. Make sure you include both the domain and the account that you’d like to use.
   2. Next is P, which is the password for the account you indicated in the u parameter.
   3. Lastly, we have T for startup type. This can either be A for automatic, D for disabled, or M for manual. If you don’t include this parameter, it’ll default to manual, and if you don’t include a username for the U parameter, it’ll default to the local system.
9. Now that we have our command ready, we launched the command prompt as an admin. We copied our command over and pressed “enter” as it ran, and it showed us the different steps it was doing. Next, you’ll get confirmation that the command has finished. To verify this, open up your services to see if the service is there. When we did this in the demo, we found that it was, in fact, there, so we successfully created a new unity scheduler instance.

Want to Expand your OnBase Knowledge?

Bookmark our Question Corner playlist on YouTube. Every other week, we add a new OnBase demo led by experts from the Naviant Customer Success Team. Each demo is 3-10 minutes long and answers questions frequently asked by OnBase users like you.

View Playlist

Want More Content Like This?

Subscribe to the Naviant Blog. Each Thursday, we’ll send you a recap of our latest info-packed blog so you can be among the first to access the latest trends and expert tips on workflow, intelligent automation, the cloud, and more.