These configuration properties affect the way SafeRupi processes and responds to messages. They do not affect how OGF Usage records are parsed. For that information, see the parser configuration section. The following properties are available
ogf.rupi.table
Default Value = OGFURecord
Specifies the database table name records are to be stored in. The default value assumes table by the specified name exists in the database. An example schema for such a table can be found in the installation documentation.
ogf.rupi.record-constraints.file
No Default Value
Used to define record constraints (as described in the RUPI specification). The value of this configuration property should be a location to a file containing a rupi:RecordConstraints element. The element should be a valid rupi:RecordConstraints element as defined in the RUPI specification schema. The file should contain the element only as it will be copied in it's entirety and placed in the response message (i.e. do not include any <xml version=...>).
The path given can be absolute within to the underlying file system. It can also be relative to the current working directory that the service is running from, or on the Java classpath this service is running in.
ogf.rupi.max-bits
No Default Value
Used to define one of the transfer constraints (as described in the RUPI specification). The value of this configuration property should be a positive integer specifying approximately the maximum number of bits the size of a publish request message can be.
ogf.rupi.max-records
No Default Value
Used to define one of the transfer constraints (as described in the RUPI specification). The value of this configuration property should be a positive integer specifying approximately the maximum number of OGF Usage Records a publish request message can contain.
