Service Instance

A Service Instance is a Grooper Service that has been installed on a Server or Workstation.

Remarks

Service instances must be installed from Grooper Configuration, using the Service Manager control on the Services Tab. After initial installation, service instances may be started, stopped, or configured using the Service Instance Viewer control in Grooper Design Studio. The Service Instance Viewer can be accessed from the property panel of any Machine object in Grooper Design Studio. To manage all services for an entire Grooper repository, use the Service Instance Viewer found on the Machines Folder (immediately below the Infrastructure Folder).

List of Service Instance Types

Name Description
Activity Processing The Activity Processing service executes Unattended Activities, which perform the work associated with a step in a Batch Process.
ApplicationXtender CMIS Server Exposes an OpenText ApplicationXtender repository over CMIS.
FileBound CMIS Server Exposes a FileBound repository over CMIS.
Grooper CMIS Server Provides web-based connectivity to a Grooper repository over the CMIS protocol.
Grooper Licensing Distributes runtime licenses to Grooper applications.
Import Watcher Import Watcher is a Grooper service which periodically polls an external storage platform, importing new documents as they become available.
System Maintenance Service Provides Grooper system maintenance services.

Properties

The following 6 properties are defined.

Property Name Description
Service Settings
Repository Type: Repository Connection

The repository to which this service instance is bound. Service instances are bound permanently to a Grooper repository. To change to repository, delete the service instance and reinstall it using the desired repository.

Service Name Type: String

The name for the service.

Service Display Name Type: String

The display name for the service.

Thread Priority Type: ThreadPriority, Default: Normal

The priority level with which threads will be created. Can be one of the following values:

  • Lowest - The can be scheduled after threads with any other priority.
  • BelowNormal - The can be scheduled after threads with Normal priority and before those with Lowest priority.
  • Normal - The can be scheduled after threads with AboveNormal priority and before those with BelowNormal priority. Threads have Normal priority by default.
  • AboveNormal - The can be scheduled after threads with Highest priority and before those with Normal priority.
  • Highest - The can be scheduled before threads with any other priority.
If the service is running on a workstation, a priority lower than normal will help prevent the service from impacting the user interface responsiveness.

User Name Type: String

The user account under which the service should run. The account specified must:

  • Have the Logon as Service permission on the machine on which the service is to run.
  • Have access to the Grooper database, if Windows security is being used for SQL connections.
  • Have access to the Grooper file store location.
Password Type: String

The password for the user account under which the service should run.