How to Untarget the JMS Reporting Provider When Server Not Running

If the server is not running in the Oracle Service Bus domain, you can use the WebLogic Scripting Tool (WLST) to remove the JMS Reporting Provider from the Oracle Service Bus domain. For more information about WLST, see

Oracle Fusion Middleware Oracle WebLogic Scripting Tool.

To untarget a reporting provider, complete the following steps:

If you have not already set up your environment to use WLST, see "Main Steps for Using WLST" in

"Using the WebLogic Scripting Tool" in Oracle Fusion Middleware Oracle WebLogic Scripting Tool.

Invoke WLST Offline.

C:>java com.bea.plateng.domain.script.jython.WLST_offline

To read the domain that was created using the Configuration Wizard execute:

wls:/offline>readDomain("C:/oracle/user_projects/domains/base_domain")

To untarget the reporting provider data source execute:

wls:/offline/base_domain>unassign("JdbcSystemResource", "wlsbjmsrpDataSource", "Target", "AdminServer")

To the reporting provider application execute:

wls:/offline/base_domain>unassign("AppDeployment", "JMS Reporting Provider", "Target", "AdminServer")

To update the domain execute:

wls:/offline/base_domain>updateDomain()

To close the domain execute:

wls:/offline/base_domain>closeDomain()

Exit from the WLST command prompt execute:

wls:/offline>exit()

After the Oracle Service Bus JMS reporting provider is untargeted, the Reporting module in the Oracle Service Bus Console indicates that the reporting provider is not deployed.

Note:
In a cluster, the JMS Reporting Provider is targeted to Cluster. Therefore in a cluster, to view and purge messages, you must configure at least one managed server to run with the Administration server. If no managed servers are running, the Oracle Service
Bus Console displays a message that the reporting provider is unavailable.