Index Changes
Page Difference

Difference between version and version     

Back to IEP Systemic Qualities, or IEP Systemic Qualities Info


At line 7 changed 4 lines.
* INFO and higher logs needs to be associated with unique number and printed to bundle file
* NDC - Component needs to set service assembly name, process name, MEx id or process instance id or both, so that logging messages can be searched and filtered.
* At INFO level the information should be minimal. During normal operation of the system (as messages get processed successfully) there should be no log output at info level.
* Loggers needs to be listed in jbi.xml. Configured values needs to be retained GF/component bounce backs. Only list important ones with meaningful description.
** INFO and higher logs needs to be associated with unique number and printed to bundle file
** NDC - Component needs to set service assembly name, process name, MEx id or process instance id or both, so that logging messages can be searched and filtered.
** At INFO level the information should be minimal. During normal operation of the system (as messages get processed successfully) there should be no log output at info level.
** Loggers needs to be listed in jbi.xml. Configured values needs to be retained GF/component bounce backs. Only list important ones with meaningful description.
At line 13 changed 3 lines.
* When it is not able to process the inbound requests (transformation error, Db not available (there could be more scenarios) it should set error on ME.
* It also needs to set ME properties - com.sun.jbi.crl.faultcode, com.sun.jbi.crl.faultstring, com.sun.jbi.crl.faultactor & com.sun.jbi.crl.faultdetail).
* faultcode takes two values "Client" and "Server". If the error is because the data is invalid (and it will never succeed if the same message gets re-sent) it should be send back as a "client" error, otherwise a "server" error. Example for "server" error is Db not available and request is associated with XA. When error code is "server", redelivery logic would kick-in if the consumer is configured for redelivery. "Db not available" needs to be handled handled gracefully by waiting for Db to recover if the request is not associated with XA.
** When it is not able to process the inbound requests (transformation error, Db not available (there could be more scenarios) it should set error on ME.
** It also needs to set ME properties - com.sun.jbi.crl.faultcode, com.sun.jbi.crl.faultstring, com.sun.jbi.crl.faultactor & com.sun.jbi.crl.faultdetail).
** faultcode takes two values "Client" and "Server". If the error is because the data is invalid (and it will never succeed if the same message gets re-sent) it should be send back as a "client" error, otherwise a "server" error. Example for "server" error is Db not available and request is associated with XA. When error code is "server", redelivery logic would kick-in if the consumer is configured for redelivery. "Db not available" needs to be handled handled gracefully by waiting for Db to recover if the request is not associated with XA.
At line 17 changed 4 lines.
* Component configuration - Component should support configuration both at install time and run time. Display of configuration screen should be consistent. Details can be found at http://wiki.open-esb.java.net/Login.jsp?redirect=SystemicQualities.ConsolidatedConfiguration
* Alerts - Alerts needs to be sent from IEP-SE during its life cycle and execution.
* Administration - IEP implements mechanism to query process, operators and configuration information. This is specific to IEP-SE. It is equivalent to BPEL-SE providing a mechanism to query BP instances, variables etc.
* Statistics MBean - Andi and Gopalan confirmed it is not required, frame work provides functionality.[Need to measure the time taken in the component - operations]
** Component configuration - Component should support configuration both at install time and run time. Display of configuration screen should be consistent. Details can be found at http://wiki.open-esb.java.net/Login.jsp?redirect=SystemicQualities.ConsolidatedConfiguration
** Alerts - Alerts needs to be sent from IEP-SE during its life cycle and execution.
** Administration - IEP implements mechanism to query process, operators and configuration information. This is specific to IEP-SE. It is equivalent to BPEL-SE providing a mechanism to query BP instances, variables etc.
** Statistics MBean - Andi and Gopalan confirmed it is not required, frame work provides functionality.[Need to measure the time taken in the component - operations]
At line 22 changed 3 lines.
* Throttling - so that user can choose to configure # of message to be delivered.
* Redelivery - When the total number of redelivery attempts for a given message have been exhausted, the redelivery loop is terminated with Redirect (sending a message to error EP), Suspend, Delete or Return error (propagating error). IEP consuming EP can be only configured with Redirect and Delete for the following reasons. suspend - what we are suspending? no clear definition. Returning error - no constructs in the IEP process handle the errors. Not clear on the value add even if we define constructs.
** Throttling - so that user can choose to configure # of message to be delivered.
** Redelivery - When the total number of redelivery attempts for a given message have been exhausted, the redelivery loop is terminated with Redirect (sending a message to error EP), Suspend, Delete or Return error (propagating error). IEP consuming EP can be only configured with Redirect and Delete for the following reasons. suspend - what we are suspending? no clear definition. Returning error - no constructs in the IEP process handle the errors. Not clear on the value add even if we define constructs.
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-16) was last changed on 23-Jul-08 19:37 PM, -0700 by Gopalan Suresh Raj