-
To use other than default database for Message Archiving component, you need to add following line to your
etc/init.propertiesfile:message-archive/archive-repo-uri=jdbc:mysql://localhost/new_database_to_use?user=username&password=passwordwhere:
-
message-archiveis name under which you configured Message Archiving component -
jdbc:mysql://localhost/new_database_to_use?user=username&password=passwordis JDBC URI required to connect to database
To change database used by AMP component (default store for offline messages) you need to add following lines to
etc/init.propertiesfile:--amp-repo-uri=jdbc:mysql://localhost/new_database_to_use?user=username&password=passwordwhere:
jdbc:mysql://localhost/new_database_to_use?user=username&password=passwordis JDBC URI required to connect to database
-
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
1981
|
Issue Votes (0)
Watchers (0)
Hey guys I was just wondering if there was anything in the works to have the ability to specify a separate DB cluster for offline messages OR the ability to add read slaves for the current DB cluster.