From DeveloperWorks, The WebSphere Contrarian: Are you sure you want to reorg that messaging engine database?

The standard practice for database administration is to periodically check on the database and table organization to insure optimal performance -- but do these standard practices apply to a database used for JMS persistent message storage with IBM WebSphere Application Server? (IBM WebSphere Developer Technical Journal)

An interesting article about your messaging engines databases and how they are structured.

Related Posts

• The top 15 WebSphere MQ best practices
• WebSphere Application Server and The Spring Framework
• Using DataPower SOA Appliances to query WebSphere Service Registry and Repository
• Developerworks SOA Best Practices and Top 10 SOA and Web services tutorials and articles
• Using Spring and Hibernate with WebSphere Application Server

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.