Shows OmniGroupServer status information for all repositories, or a specified repository.


This action uses port 4000 to request details about the group server which is located on a machine with the IP address


Parameter Description Required
EncryptResponse Encrypt the output.  
FileName The file to write output to.  
ForceTemplateRefresh Forces the server to load the template from disk.  
Output Writes output to a file.  
Redirected Allows the query to be performed against the repository.  
Repository Restricts the repository details to one repository.  
Stats Displays statistics about the datastore.  
Template The template to use for the action output.  
TemplateParamCSVs A list of variables to use for the specified template.  


An example GetStatus response:

      <ProductName>Omni Group Server</ProductName>
         <ProductName>LDAP Group Server</ProductName>
         <ProductName>Text Group Server</ProductName>

The response can show the following information for each repository:

Response Field Description
Name The name of the repository, as configured in the OmniGroupServer configuration file.
Sections A list of configuration file sections that configure the task (as specified by GroupServerSections).
Library The name of the library being used.
DataStore The path to the datastore file that contains the user and group information.
UserCount The number of users stored in the repository.
GroupCount The number of groups stored in the repository.

The total number of membership relationships between users and groups or between pairs of groups.


Nested group memberships are counted. For example, if Group1 is a member of Group2 which is a member of Group3, then there are three relationships including Group1 being a member of Group3.

However, if User1 is a member of Group2 which is a member of Group3, the count does not include User1 being a member of Group3.

QueueSize The number of updates that have not yet been committed to the datastore. The number of updates might not match the number of users, groups, or memberships, because multiple operations may be required for a single user or group update.