Monday, August 1, 2011

JMS Reporting Provider is not deployed, or it is not active

Provider Not Available
JMS Reporting Provider is not deployed, or it is not active


If you get this message when you click on Operations/Message Reports

open WL console,
check if "JMS Reporting Provider" is deployed;

this application should use the
Module jmsResources ->
Queue wli.reporting.jmsprovider.queue ->
Server wlsbJMSServer

and the wlsbjmsrpDataSource - mapped to a DB

When you do a Report action, a message is queued to the JMS queue, and asynchronously dequeued to the DB.

PurgingMDB listens on the queue wli.reporting.purge.queue, which is part of the same module jmsResources .

DB scripts are in $ORACLE_HOME/Oracle_OSB1/dbscripts/oracle/reporting_runtime.sql, tables WLI_QS_REPORT_ATTRIBUTE and WLI_QS_REPORT_DATA

The JMS Reporting Provider is in $ORACLE_HOME/Oracle_OSB1/lib/common/jmsreportprovider.ear, so you can redeploy it from there.




See here for list of resources


Here the full doc on reporting

Here how to untarget the JMS Reporter

No comments: