I am using the Business Rules service on Bluemix, and it does not seem to use the Decision Warehouse. Is there another way to trace the rule firing?
相关问题
- Bluemix Analytics for Apache Spark log file inform
- Not able to push my local app to bluemix
- How to extract current date in watson conversation
- Can I use IBM Watson services without Bluemix?
- Debug nodejs app in CF
相关文章
- Is there an npm module to modify a pdf file in nod
- Kubernetes Persistent Volume Claim mounted with wr
- Drools vs JBPM ? differences, pros and cons
- how to order SoftLayer_Virtual_ReservedCapacityGro
- Can I call the Bluemix message hub service from Py
- GYP ERR! build error. stack Error: 'make'
- Unable to run bms-samples-cordova-hellopush - bms_
- Spark Hive reporting pyspark.sql.utils.AnalysisExc
As you noticed, the Decision Warehouse is not a feature within the Business Rules service. Also, rule traces are disabled.
You can add trace filter tags to the payload request. Use the REST form (
&trace=true
) to view the trace filter tags:(You can get the values for instanceID, domain, ruleApp, ruleset and the corresponding versions from the “URL” in the Ruleset Details page.)
If you work with XML, choose the XML option, in which case the generated payload will contain filter tags such as:
If you work with JSON, choose the JSON option instead. The generated payload will contain filter entries, for example:
Add these tags/entries with the appropriate filter enabled in the execution request. The payload response will contain the requested traces.
Another way is to enable the Decision trace information when getting the WSDL or WADL. See the documentation at “Decision trace information” in the IBM ODM documentation at "IBM Operational Decision Manager 8.7.0>Operational Decision Manager 8.7> Decision Server Rules>Rule Execution Server console online help>Viewing and managing transparent decision services>Viewing or downloading an HTDS description file", Step 6 and collect the execution information on the client side.