This content has been marked as final. Show 4 replies
Hi Veronica,1 person found this helpful
I don't think there's such a thing for OSB... All you can do is to go to operational settings configurations and enable monitoring and message tracing, it will spit out lots of information but not graphically organised like EM does for BPEL processes...
https://blogs.oracle.com/soacommunity/entry/soa_management_with_enterprise_manager1 person found this helpful
SOA Management Pack EE
in the this pack you do have some functionality for the oracle service bus, but i doubt you will see a flow like in bpel.
osb doesn't store his state of processes like bpel does in his dehydration store, so i don't think you will be able to retrieve the executed flow of older process instances
Eric, you say I'll not be able to view older instances. Will I be able to see current OSB instances then in SOA Management Pack EE? This document is not clear on that.
OSB is stateless in nature whereas BPEL dehydrates the runtime information in DB. This is why you can see instance trace or audit trail in BPEL however OSB does support auditing but you have to write your own framework on top of it to achieve your requirement.1 person found this helpful
From OSB doc -
G.2 Creating an Audit Trail for a Message Flow
Auditing the entire message flow pipeline during processing is time consuming. However, you can use the reporting action to perform selective auditing of the message flow pipeline during run time. You insert the reporting action at required points in the message flow pipeline and extract the required information. The extracted information may be then stored in a database or sent to the reporting stream to write the auditing report.http://docs.oracle.com/cd/E23943_01/admin.1111/e15867/app_auditing.htm#CHDCDBJJ
To understand the functionality of Reporting in OSB, you may refer -