JDBC persistence configuration examples?
rcdunn Apr 16, 2006 8:07 PMI am trying to change the persistence store to PostgreSQL according to 5.2 in the JBossMessagingGettingStarted.pdf.
JBoss Messaging is shipped with several pm configuration files for the most commonly used
database servers such as Oracle, mySQL or MSSQL. These files are located in /docs/examples/config
It specifies:
To change the pm configuration, navigate to /server/$SERVER_CONF/deploy/jboss-messaging.sar/META-INF
and edit jboss-service.xml From the example folder, copy the mbean definition that is appropriate for your data-
base server e.g. mysql-jdbcpersistencemanager-service.xml Paste it in place of the existing one then restart the
server.
However, in the jboss-messaging-1.0.0.Beta1.zip I find no such collection of examples, other than MySQL. I assume this is an oversight. Is there anywhere I can download an example PostgreSQL? I will attempt to roll my own in the meantime, but would prefer one already tested by someone more familiar with JBoss Messaging.
I have everything apparently working according to the example test cases, but I found a few glitches (like the above), and the apparent omission (or mis-configuration by me) of the file note at the beginning of Chapter 5:
Note: In JBoss Messaging 1.0 most of those services are configurable via mbean definitions which are all located
in jboss-messaging.sar/META-INF/jboss-service.xml. In the next release, configurations will be broken down
into separate xml files.
The closest thing I see to it is:
$JBOSS_HOME/server/messaging/tmp/deploy/tmp26612jboss-messaging-scoped.sar
From the path, I assume this is a dynamically deployed/created instance and not one I would edit (and it does not have a file system entry that corresponds to jboss-messaging.sar/META-INF/jboss-service.xml anyway).
Any corrections, comments, pointers, URL's, etc. greatly appreciated.
I apologize if I should have separated this post into two, but it all falls into trying to change the JDBC persistence to PostgreSQL and I assume most or all is a mis-configuration problem on my end.