The content tags (these are not attributes to a tag) specify what is retained in a store. These are
Name | Description | Tag |
transactions | Transactions that are pending. These are generally short-lived and should not be persisted for extended periods. | <transactions/> |
client | Registered clients that the service knows about. These should be persisted | <clients/> |
clientApprovals | Approvals for clients. These should be persisted. | <clientApprovals/> |
There is one optional attribute associated with any content tag and this is "tablename". In cases where the underlying store is an SQL store, you may use this to specify the table name, overriding the default. This attribute is ignored by other stores.
This puts the client approvals in a file store
<config> <service address="localhost"> <fileStore path="/var/www/store"> <clientApprovals/> </fileStore> </service> </config>
Specifying the table name:
<service name="postgres-config" disableDefaultStores="true"> <postgresql username="bob" password="mairzydoats" schema="math" database="oa4mp"> <transactions tablename="transaction2"/> <clients tablename="gateways"/> <clientApprovals/> </postgresql> <!-- other stuff --> </service>
In this example, the default stores are disabled, so if there is some issue with the database configuration, memory stores won't be used, but starting the server will fail. Two of the tables have been created by the administrator with names different than in the default setup.