When we log in to bpel console and go to manager bpel domain logging tab,we get different parmeters which can be set to get the details about the error message of bpel process.We can get accurate log information about the process by tweaking the right loggers properties.
Various loggers are
default.collaxa.cube-It a general logger for BPEL.
default.collaxa.cube.activation-If you are using adapters in your process you need to set this property ,this is because the adapters are configured through activation agent.
default.collaxa.cube.compiler-This gives us the information about the compile time issues of the bpel process when we deploy a process.
default.collaxa.cube.engine-This provides log for the BPEL engine.
default.collaxa.cube.engine.bpel-It gives logs for all the bpel activity that are used in a bpel process.
default.collaxa.cube.engine.data-It logs information about the persistent /dehydration store.
We often find toplink error in our log files.toplink is nothing but oracle implementation of JPA concept.In JPA we use annotation however we use mapping in toplink but the underlying concept is same for both.It has to do more with persistent layer.
default.collaxa.cube.engine.delivery-It log information about all invocation,call backs,resolution of cor relation set.
default.collaxa.cube.engine.dispatch-IT logs information about all asynchronous message processing
default.collaxa.cube.services-If your process contains workflow services and decision components it can be logged by this parameter.
default.collaxa.cube.ws-Every call from the BPEL process goes through the it and it will show you what we are doing with the soap message that you post and everything until the message leaves the engine.
default.collaxa.cube.xml_It logs information about everything related to XML,Xpath,XSLT
YOu need to set these properties accordingly in order to get the correct information about your bpel process and where exactly it is getting failed.
No comments:
Post a Comment