Skip to content

Service class management

Create service class

  1. From the File menu, pick New Service Class

  2. Give the service class a name; e.g. FileWatcher_ServiceClass

    Screenshot

  3. Associate it with a package

  4. Select the DS_FILEWATCHER template

  5. Press the Add button to create it

  6. In the Details tab, the description can be changed and the cluster mode set to DEFAULT, LEADER_CLUSTER, or ROUND_ROBIN. Save the new Service class.

    Screenshot

  7. The Alerts tab can be used to set the expected actions to take for Normal and Unexpected shutdowns, or Heartbeat timeouts.

    Screenshot

  8. The Reserved Params tab can be used to set various reserved parameters. Unlike instances, the host, port. and taskset are not configured here. They can be assigned automatically or overriden when the service is run.

    Screenshot

  9. The Service Params tab shows the same parameters as seen for an instance.

    Screenshot

  10. The History tab shows all the past and current running services for the class. The names may be the auto-generated ones or any name manually entered when running the Service class. There may be multiple instances running at one time.

    Screenshot

Uniqueness

Service class names must be unique with respect to instances and connection groups. A service class can't be created using the same name as an instance or connection group and vice versa.

Other considerations

Service classes are versioned, packaged, included in checkpoints, and are handled like any other entity type.

Non-admin users can interact with services and service classes by being given entitlements for the UxProcess, UxInterrogation and UxRuntime roles.

Control UI non-admin

Back to top