Skip to main content

Configuring agtgdmno for use with generic Domino databases

You must configure the following items in the configuration file:

  • List operations

  • UserAttributes operation

  • LotusScript agent operations

Configuring list operations

List operations are programmed into agtgdmno; they are not handled by a LotusScript agent. The form of the KVGroup for list operations for a generic Domino database is:

"list" "" = {

 "user" "" = {
   "database"          = "<Domino server>!!<target database>.nsf"
      "view"              = "<Target database view>"
      "sort-column"       = "<Field which the view is sorted on>"
      "search-field"      = "<Name of the field to search on>"
      "longid-field"      = "<Long ID field>"
      "shortid-field"     = "<Short ID field>"
      #The full name field does not need to be specified if
      #first-name-field and last-name-field are specified
      "fullname-field"    = "<Full name field>"
      #The first-name-field, middle-name-field, and last-name-field
      #do no need to be specified if the fullname-field is
      #specified.
      "first-name-field"  = "<First name field>"
      "middle-name-field" = "<Middle name field>"
      "last-name-field"   = "<Last name field>"
      "type-field"        = "<Type field>"
      "type-value"        = "<Type value>"
   }

   "group" "" = {
      "database"          = "<Domino server>!!<target database>.nsf"
      "view"              = "<Target database view>"
      "sort-column"       = "<Field which the view is sorted on>"
      "search-field"      = "<Name of the field to search on>"
      "groupid-field"     = "<Group ID field>"
      "member-field"      = "<Group members field>"
      "description-field" = "<Group description field>"
   }

   "attribute" "" = {
      "attribute"         = "groups"
      "attribute"         = "<attribute name 2>"
       .
       .
      "attribute"         = "<attribute name N>"
   }
 }

By default a generic Domino target has no defined attributes, so for each attribute listed in the attribute KVGroup, you need to add a matching attribute to the target. See the Bravura Security Fabric configuration documentation to learn how to do this.

Configuring UserAttributes operation

The UserAttributes operation is programmed into agtgdmno . It is not handled by a LotusScript agent. The form of the KVGroup for the UserAttributes operation for a generic Domino database is:

"userattributes" "" = {

    "user" "" = {
      "database"          = "<Domino server>!!<target database>.nsf"
      "view"              = "<Target database view>"
      "sort-column"       = "<Field which the view is sorted on>"
      "search-field"      = "<Name of the field to search on>"
      "longid-field"      = "<Long ID field>"
      "shortid-field"     = "<Short ID field>"
      #The full name field does not need to be specified if
      #first-name-field and last-name-field are specified
      "fullname-field"    = "<Full name field>"
      #The first-name-field, middle-name-field, and last-name-field
      #do no need to be specified if the fullname-field is
      #specified.
      "first-name-field"  = "<First name field>"
      "middle-name-field" = "<Middle name field>"
      "last-name-field"   = "<Last name field>"
      "type-field"        = "<Type field>"
      "type-value"        = "<Type value>"
   }
   

   "group" "" = {
      "database"          = "<Domino server>!!<target database>.nsf"
      "view"              = "<Target database view>"
      "sort-column"       = "<Field which the view is sorted on>"
      "search-field"      = "<Name of the field to search on>"
      "groupid-field"     = "<Group ID field>"
      "member-field"      = "<Group members field>"
      "description-field" = "<Group description field>"
   }
   

   "attribute" "" = {
      "attribute"         = "groups"
      "attribute"         = "<attribute name 2>"
      ....
      "attribute"         = "<attribute name N>"
   }
}

By default a generic Domino target has no defined attributes, so for each attribute listed in the attribute KVGroup, you need to add a matching attribute to the target. See the Bravura Security Fabric configuration documentation to learn how to do this.

Configuring LotusScript agent operations

You must add a KVGroup for each LotusScript agent operation that has been defined using the following form. The KVGroup must be named using the correct agent operation. See Configuring agtgdmno .

"<Agent Operation>" "" = {
   "agent-name"           = "<LotusScript agent name>"
   "agent-database"       = "<Domino server>!!<agent database>.nsf"
   "agent-form"           = "<Agent database form>"
   "agent-statistics"     = "<yes/no option for outputting
                              the log information from LotusScript agent>"
}