For more information click here. Also Samisa's podcast is available here
Wednesday, December 16, 2009
WSO2 Business Activity Monitor
WSO2 Business Activity Monitor, allows monitoring Service Mediation/Invocation data. The data is captured real time, and could be used for decision making activities. BAM is extensible and can be used to custom monitoring needs as well.
For more information click here. Also Samisa's podcast is available here
For more information click here. Also Samisa's podcast is available here
Saturday, December 05, 2009
SOAP v REST Explained
Nice way to explain "SOAP vs REST"
Source: http://blogs.zdnet.com/service-oriented/?p=3568&tag=trunk;content
Source: http://blogs.zdnet.com/service-oriented/?p=3568&tag=trunk;content
Thursday, November 12, 2009
Dr Kohana @ ABC lateline
More or less I have the same view on the issue. Dr. Kohana @ ABC - Lateline
Saturday, September 19, 2009
Wednesday, August 19, 2009
Drools 5.0 and business process modeling flexibility
The rules and workflows are considered to be two different paradigms for business process modeling[1]. Although there are some approaches[2, 3] that attempted combine the advantages of both rule driven and workflow driven business process modeling, the Drools 5.0 combined the advantage of both paradigms as a commercial product.
Earlier the drools modeling considered rules (conditions and actions) as first class citizens. The drools engine allows rules to be specified using the drools language or in xml to be interpreted by the rule processor. This is now provided as the Drools Expert. The java program that integrates the rules engine can pass java objects as facts in to the engine to be evaluated against a rule, or a group of rules. But now with the Drools Flow[4], the processes (better say workflows) are too considered as first class citizens (entities). Also earlier there is no notion of events. The events, such as exceptions, alerts should be handled by the (Java) program. Upon an event the program fires rules. But now with the Drools Fusion [5]the events too are considered first class entities that can be modeled along with processes and the rules. (Here I use the same terminology in the drools documentation. However it should be noted that their use of processes are very similar to the meaning of workflow in other literature. Also when they refer rules it seems they refer to a combination of event and actions). Apart from the above Drools-Govnor allow the users (especially the non-technical lot) to manage the rules using a web interface.
I see following main advantages of this development in drools with Drools Flow and Drools Fusion.
Now it is possible to implement the business logic without being restricted to rule-centric or process-centric modeling approach. Therefore from the design point of view the users can practice the best applicable approach to design different parts of the business logic. Because a flexible process modeling approach will be ended up somewhere in between these two paradigms.
Form the implementation point of view, now the developers have a common API to work with. Earlier the business processes have to be implemented using a different API while rules are specified using Drools (Now Drools Expert). That brought many limitations. For example it wasn’t possible to take decisions in a business process based on an outcome of a rule evaluation. There has to have an intermediary layer to bridge the gap. But now the rules can be used to take decisions on business processes and even assigning the actors to human tasks.
Also, the ability to model complex events using Drools Fusion is a great advancement compared to the earlier versions. In earlier the event handling is done by the java program and which eventually fires a set of rules. However now it is possible to do temporal reasoning of different events (e.g. E1 before E2), use sliding windows both time (e.g. items of last 10 minutes) and length based (e.g. last 10 items) etc.
Moreover the processes, events and rules (Condition, Actions) are all now part of one knowledge base. Thus it is easy to manage the state, share context of a particular process instance. Consequently the process instances can deviate from the pre-defined execution path, for example to handle an exception.
link
1.R. Lu and S. Sadiq, “A Survey of Comparative Business Process Modeling Approaches,” Business Information Systems, 2007, pp. 82-94.
2.A. Charfi and M. Mezini, “Hybrid web service composition: business processes meet business rules,” Proc. Proceedings of the 2nd international conference on Service oriented computing, ACM, 2004.
3.T. Graml, R. Bracht and M. Spies, “Patterns of business rules to enable agile business processes,” Enterprise Distributed Object Computing Conference, vol. 2, no. 4, 2008, pp. 385-402; DOI http://dx.doi.org/10.1080/17517570802245441.
4. “Drools Flow,” http://jboss.org/drools/drools-flow.html.
5. “Drools Fusion,” http://jboss.org/drools/drools-fusion.html.
Earlier the drools modeling considered rules (conditions and actions) as first class citizens. The drools engine allows rules to be specified using the drools language or in xml to be interpreted by the rule processor. This is now provided as the Drools Expert. The java program that integrates the rules engine can pass java objects as facts in to the engine to be evaluated against a rule, or a group of rules. But now with the Drools Flow[4], the processes (better say workflows) are too considered as first class citizens (entities). Also earlier there is no notion of events. The events, such as exceptions, alerts should be handled by the (Java) program. Upon an event the program fires rules. But now with the Drools Fusion [5]the events too are considered first class entities that can be modeled along with processes and the rules. (Here I use the same terminology in the drools documentation. However it should be noted that their use of processes are very similar to the meaning of workflow in other literature. Also when they refer rules it seems they refer to a combination of event and actions). Apart from the above Drools-Govnor allow the users (especially the non-technical lot) to manage the rules using a web interface.
I see following main advantages of this development in drools with Drools Flow and Drools Fusion.
Now it is possible to implement the business logic without being restricted to rule-centric or process-centric modeling approach. Therefore from the design point of view the users can practice the best applicable approach to design different parts of the business logic. Because a flexible process modeling approach will be ended up somewhere in between these two paradigms.
Form the implementation point of view, now the developers have a common API to work with. Earlier the business processes have to be implemented using a different API while rules are specified using Drools (Now Drools Expert). That brought many limitations. For example it wasn’t possible to take decisions in a business process based on an outcome of a rule evaluation. There has to have an intermediary layer to bridge the gap. But now the rules can be used to take decisions on business processes and even assigning the actors to human tasks.
Also, the ability to model complex events using Drools Fusion is a great advancement compared to the earlier versions. In earlier the event handling is done by the java program and which eventually fires a set of rules. However now it is possible to do temporal reasoning of different events (e.g. E1 before E2), use sliding windows both time (e.g. items of last 10 minutes) and length based (e.g. last 10 items) etc.
Moreover the processes, events and rules (Condition, Actions) are all now part of one knowledge base. Thus it is easy to manage the state, share context of a particular process instance. Consequently the process instances can deviate from the pre-defined execution path, for example to handle an exception.
link
1.R. Lu and S. Sadiq, “A Survey of Comparative Business Process Modeling Approaches,” Business Information Systems, 2007, pp. 82-94.
2.A. Charfi and M. Mezini, “Hybrid web service composition: business processes meet business rules,” Proc. Proceedings of the 2nd international conference on Service oriented computing, ACM, 2004.
3.T. Graml, R. Bracht and M. Spies, “Patterns of business rules to enable agile business processes,” Enterprise Distributed Object Computing Conference, vol. 2, no. 4, 2008, pp. 385-402; DOI http://dx.doi.org/10.1080/17517570802245441.
4. “Drools Flow,” http://jboss.org/drools/drools-flow.html.
5. “Drools Fusion,” http://jboss.org/drools/drools-fusion.html.
Wednesday, August 05, 2009
Tuesday, June 09, 2009
Sri Lanka - a birds eye view over paradise island
Nice video about SL. :-)
10 minute birds eye view over paradise island
10 minute birds eye view over paradise island
Monday, June 08, 2009
Autonomic computing vs Artificial intelligence
This article "Looking to nature for smarter software systems" explains the use of autonomic computing in a very simple way highlighting how it is different from Artificial Intelligence.
Tuesday, May 19, 2009
Tears and smiles..
This is a day that Sri Lanka re-writes her history in a new chapter. The myths that were surrounded with the separatism and terrorism are gone with the wind. Who said they are invincible...?
During my whole life what I saw was WAR.
Bombs were frequent and people used to ask "how many are dead?" Just a routine question. If there is a politician involved then there is something special in the news. Otherwise its just another blast.
Irrespective of day or night ambulances were rushing along the Galle Road from Ratmalana military base. That was a sign of renewed fighting. People flocked in front of TVs again to hear the score. Deaths of humans who used to breath like you and me are just numbers. Sometimes villagers have to cremate a sealed off body of a fallen soldier. My friends/relatives had to cut their leaves short as they were called for the duty. Families had to keep their uncertain eyes open until they come back during the next vacation that no one can predict.
We had to think twice before we schedule our work in Colombo. People were suspicious if you carry a bag or suite case. No chance of keeping it on a rack or under a seat. Buses were randomly stopped at check points. We had to walk through lines with our identity cards ready and wait for the inspection. Men, Women, Elderly and Children alike.
Large amount of money spent on WAR. Military vehicles scrolled along half made dusty roads while the children studying in open class rooms, waving their hands to soldiers.
Without any prior notice roads were closed in the city for VIPs passing by. You have to wait for hours in a bus packed with exhausted commuters. Sweating, cursing, hungry and angry.
This was the life of our generation. If you feel uncomfortable hearing my story, being a Sinhalese, lived in a Suburb of Colombo, you should never hear what a Tamil friend in my age have to say.
Those who preach us to negotiate with the world's most ruthless terrorist organization, never gone through the trauma we gone through for three decades. Those who are trying to satisfy Tamil diaspora just because of few votes, may they lose every election before they rot in hell. Those who put ridiculous conditions, just to give us a "loan", please keep it to yourself. After all we have to pay it back one day.
My heart goes for those families who are now displaced and are living in camps. Remind me the Tsunami in 2004. May they find their way back soon and start rebuilding their life. The worst is over. Its time to move on. No more bullets but ballets. May the politicians at least keep their personal agendas for 5 more years for themselves and work for the betterment of average Sri Lankans. Especially for the sake of those live in North and East.
Finally I would like to pay my gratitude to our armed forces who fought bravely to give a country that is free of terrorism. You are the best people who knows how awful the war is. Not the NGO "gembos" who preach us about the repercussions of war to get their pockets filled with easy $$$s. And HE the president, defense secy and all those who gave their fullest support to reach the target under the pressure from ignorant West. I salute you Sirs. A job well done. But be safe.
I wish the next generations would never ever go through such an experience. May the tears dry and bring a spreading smile along with peace and prosperity for my people.
During my whole life what I saw was WAR.
Bombs were frequent and people used to ask "how many are dead?" Just a routine question. If there is a politician involved then there is something special in the news. Otherwise its just another blast.
Irrespective of day or night ambulances were rushing along the Galle Road from Ratmalana military base. That was a sign of renewed fighting. People flocked in front of TVs again to hear the score. Deaths of humans who used to breath like you and me are just numbers. Sometimes villagers have to cremate a sealed off body of a fallen soldier. My friends/relatives had to cut their leaves short as they were called for the duty. Families had to keep their uncertain eyes open until they come back during the next vacation that no one can predict.
We had to think twice before we schedule our work in Colombo. People were suspicious if you carry a bag or suite case. No chance of keeping it on a rack or under a seat. Buses were randomly stopped at check points. We had to walk through lines with our identity cards ready and wait for the inspection. Men, Women, Elderly and Children alike.
Large amount of money spent on WAR. Military vehicles scrolled along half made dusty roads while the children studying in open class rooms, waving their hands to soldiers.
Without any prior notice roads were closed in the city for VIPs passing by. You have to wait for hours in a bus packed with exhausted commuters. Sweating, cursing, hungry and angry.
This was the life of our generation. If you feel uncomfortable hearing my story, being a Sinhalese, lived in a Suburb of Colombo, you should never hear what a Tamil friend in my age have to say.
Those who preach us to negotiate with the world's most ruthless terrorist organization, never gone through the trauma we gone through for three decades. Those who are trying to satisfy Tamil diaspora just because of few votes, may they lose every election before they rot in hell. Those who put ridiculous conditions, just to give us a "loan", please keep it to yourself. After all we have to pay it back one day.
My heart goes for those families who are now displaced and are living in camps. Remind me the Tsunami in 2004. May they find their way back soon and start rebuilding their life. The worst is over. Its time to move on. No more bullets but ballets. May the politicians at least keep their personal agendas for 5 more years for themselves and work for the betterment of average Sri Lankans. Especially for the sake of those live in North and East.
Finally I would like to pay my gratitude to our armed forces who fought bravely to give a country that is free of terrorism. You are the best people who knows how awful the war is. Not the NGO "gembos" who preach us about the repercussions of war to get their pockets filled with easy $$$s. And HE the president, defense secy and all those who gave their fullest support to reach the target under the pressure from ignorant West. I salute you Sirs. A job well done. But be safe.
I wish the next generations would never ever go through such an experience. May the tears dry and bring a spreading smile along with peace and prosperity for my people.
Friday, April 17, 2009
Cloud computing presentations
Ayanthi has published the presentation done by Dr. Sanjiva Weerawarana at the SOA symposium on cloud computing.
I'd like to add this presentation done by Dr. Rajkumar Buyya from the Grids Lab to it. This was presented today at the university and it brought a very interesting discussion.
The presentation discusses the evolution of Cloud Computing and how is it different from other paradigms such as Cluster and Grid. Further it discusses about certain case studies that used the Gridbus middleware.
And some interesting definitions for "Cloud Computing can be found here. [Beware 21 of them]
I'd like to add this presentation done by Dr. Rajkumar Buyya from the Grids Lab to it. This was presented today at the university and it brought a very interesting discussion.
The presentation discusses the evolution of Cloud Computing and how is it different from other paradigms such as Cluster and Grid. Further it discusses about certain case studies that used the Gridbus middleware.
And some interesting definitions for "Cloud Computing can be found here. [Beware 21 of them]
Wednesday, April 15, 2009
Workflow management systems. A liability or an asset?
Today more workflow systems appear to assist the business process management. The usual procedure is to draw a business process as a workflow diagram using a notation such as BPMN which will be converted to a code or more preferably to a process execution language script such as WS-BPEL (aka BPEL4WS).
This works fine until there is a requirement for a change in the process flow. The change can be a permanent one or it can be an ad-hoc one that caters for an exceptional situation. In the first case the process definition is changed which is known as an evolutionary change/adaptation. Where all the future instances of the process definition adhere to the new one. In the case of ad-hoc change only a particular process instance is changed which is known as momentary change thus would not affect the future instantiations.
One solution for this is to include all the possibilities into the process definition. For example BPEL switch statement. But some run time changes cannot be predicted during the design time. And even it could, the plethora of possibilities can make the design a very messy and complicated one.
Thus a running business implementation may have a business process but the frequent ad-hoc change might make it a liability than an asset. Making the stakeholders to by-pass the workflow definition rather than adhering to it. Thus it is required to find more flexible ways to design business processes that facilitate the frequent adaptation or change.
This will be my first post on this and will be followed by a series of discussion that will discuss the possible strategies to face the above challenge.
This works fine until there is a requirement for a change in the process flow. The change can be a permanent one or it can be an ad-hoc one that caters for an exceptional situation. In the first case the process definition is changed which is known as an evolutionary change/adaptation. Where all the future instances of the process definition adhere to the new one. In the case of ad-hoc change only a particular process instance is changed which is known as momentary change thus would not affect the future instantiations.
One solution for this is to include all the possibilities into the process definition. For example BPEL switch statement. But some run time changes cannot be predicted during the design time. And even it could, the plethora of possibilities can make the design a very messy and complicated one.
Thus a running business implementation may have a business process but the frequent ad-hoc change might make it a liability than an asset. Making the stakeholders to by-pass the workflow definition rather than adhering to it. Thus it is required to find more flexible ways to design business processes that facilitate the frequent adaptation or change.
This will be my first post on this and will be followed by a series of discussion that will discuss the possible strategies to face the above challenge.
Tuesday, March 10, 2009
Wednesday, March 04, 2009
Tuesday, February 17, 2009
Process Aware Information Systems
During my summer vacation, I started reading the Book "Process Aware Information Systems". The book caught my eye as I was passing a shelf in the library. After reading the preface I decided to have a better look.
The first section gives an overview of PAIS(Process Aware Information Systems) which includes a nice classification of PAIS and the rationale behind it, adding a little bit of history along with techniques and tools too.
Then the book discusses concepts of Workflow Management and modelling, person to person interactions, business to business integration etc.
The section two of the book is more like a reference. That includes UML modelling, petri nets, and event driven process chains. But hard to read continuously though.
The last section discusses more practical methodologies and standards such as XPDL and BPEL. For those who are interested in web services business processes like my self, this is again a good reference. But before reading this section its better to have look at those specifications first and may be started with "Introduction to XYZ..." kind of an article.
The first section gives an overview of PAIS(Process Aware Information Systems) which includes a nice classification of PAIS and the rationale behind it, adding a little bit of history along with techniques and tools too.
Then the book discusses concepts of Workflow Management and modelling, person to person interactions, business to business integration etc.
The section two of the book is more like a reference. That includes UML modelling, petri nets, and event driven process chains. But hard to read continuously though.
The last section discusses more practical methodologies and standards such as XPDL and BPEL. For those who are interested in web services business processes like my self, this is again a good reference. But before reading this section its better to have look at those specifications first and may be started with "Introduction to XYZ..." kind of an article.
Monday, February 09, 2009
Sunday, February 08, 2009
Friday, February 06, 2009
DNA Computing.. the future wetware
Subscribe to:
Posts (Atom)
