You can find it here. A community around BPEL hosted by the OASIS, sponsored by BEA and IBM.
On the site you will find a knowledge WIKI, Forums, News, Events, Products, Job Offers and Blogs.Documentation and white papers are there to be found too. I discovered the site accidentally because they put my Blog on their blogroll. I applied for an account and got the RSS feed on my feed burner (integrated in my Flock browser). For the moment I haven't found much on the website in terms of blogs but it is clearly a recent site and it needs time to mature and grow. I will make some advertisement for the site in my network and try to get some poeple working with BPEL to post on the site.
Marwane El Kharbili.
Showing posts with label BPEL. Show all posts
Showing posts with label BPEL. Show all posts
May 13, 2008
Apr 24, 2008
Is my Blog about BPEL?
Well, I might suprise you by saying among other things of course, but BPEL is certainly a topic of interest to me. yes! This question is motivated by the fact that I discovered that my blog was listed on BPEL.XML as a blog dealing with BPEL. I was surprised and pleased at the same time. You can see the whole list of blogs here, if you are interested.
It is not because BPEL like BPM, web 2.0, Enterprise 2.0, SOA and other acronyms And this for many reasons has become a piece of jewelry that every blog can afford and has to wear in order to attract some readers. BPEL is a de facto standard for business process execution languages. This itself is a reason enough. All technical BPM vendors I know of support BPEL. In ARIS too BPEL is supported (Modeling and transformations from business process modeling notations like EPC and BPMN for example) in ARIS (e.g. SOA Architect). Designing Business Process Models with the background idea that these are destined to be transformed into BPEL is fundamentally different from utterly designing BP models on the business level. A whole set of additional constraints become necessary, on what the modeler is allowed to model.
Additionally, the ultimate goal of process transformations, is to achieve the ability of propagating all the models information and data you define for business processes to the execution level, where processes really take place. This would show the strength and power of such transformations. Simply because they form a transport channel of the business requirements and logic from the business level to the execution level, where the modeled and incepted added value is really realized. Every bit of information (your business system's entropy, if you will) you lose on the way to the execution system is a loss for the business.
These are the reasons why I think that although separation between BP modeling and BP execution is necessary for the sake of business, being really careful about what happens with BPEL and paying attention at how it could influence BPM is crucial.
Marwane El Kharbili.
It is not because BPEL like BPM, web 2.0, Enterprise 2.0, SOA and other acronyms And this for many reasons has become a piece of jewelry that every blog can afford and has to wear in order to attract some readers. BPEL is a de facto standard for business process execution languages. This itself is a reason enough. All technical BPM vendors I know of support BPEL. In ARIS too BPEL is supported (Modeling and transformations from business process modeling notations like EPC and BPMN for example) in ARIS (e.g. SOA Architect). Designing Business Process Models with the background idea that these are destined to be transformed into BPEL is fundamentally different from utterly designing BP models on the business level. A whole set of additional constraints become necessary, on what the modeler is allowed to model.
Additionally, the ultimate goal of process transformations, is to achieve the ability of propagating all the models information and data you define for business processes to the execution level, where processes really take place. This would show the strength and power of such transformations. Simply because they form a transport channel of the business requirements and logic from the business level to the execution level, where the modeled and incepted added value is really realized. Every bit of information (your business system's entropy, if you will) you lose on the way to the execution system is a loss for the business.
These are the reasons why I think that although separation between BP modeling and BP execution is necessary for the sake of business, being really careful about what happens with BPEL and paying attention at how it could influence BPM is crucial.
Marwane El Kharbili.
Mar 18, 2008
BPEL4PEOPLE and people
In his post, Fred Cummins criticizes the fact that BPEL4PEOPLE doesn't fulfill expectations of business users. Fred says that BPEL (see here for version 2.0 from OASIS) is not a language for business people but for programmers. Well, I personally don't know of any programmer who writes BPEL code himself. BPEL is a language for machines, for executions engines. BPEL is destined to be generated not written. On the other hand, BPEL4PEOPLE should allow including and defining human interaction. I don't personally know if that means that the BPEL4PEOPLE execution engine allows defining tasks that are realized by humans (Humanoid services so to say, if considering the general notion of a service) or if it means that it allows BPEL to be defined by people. I do however think the first explanation is the right one.
Nevertheless, in the second part of the post, Fred Cummins talks about possible repercussions of BPDM. The use of BPMN 1.1 (see here) and BPDM together would allow definition of choreography and orchestration for services, both of which are critical concepts in SOA.
I would conclude that there is a wave of opinions directly linking BPM to SOA, so Joe McKendrick, in "BPM and SOA Need Each Other." I must say that I do not think that SOA should be directly linked to BPM. This would simply restrict any flexibility BPM implementation has and its independence from technology, which provides the stability business people like and need so much. The whole story is all about ROI. If you don't want to take a bet on SOA, then why should you? In the end, it is your processes that create value, not your soa architecture. This however, does not exclude that we work on technologies allowing us using the current standards to build a bridge between business process management and an SOA implementation, just because both worlds go so well along with another.
Marwane El Kharbili.
Nevertheless, in the second part of the post, Fred Cummins talks about possible repercussions of BPDM. The use of BPMN 1.1 (see here) and BPDM together would allow definition of choreography and orchestration for services, both of which are critical concepts in SOA.
I would conclude that there is a wave of opinions directly linking BPM to SOA, so Joe McKendrick, in "BPM and SOA Need Each Other." I must say that I do not think that SOA should be directly linked to BPM. This would simply restrict any flexibility BPM implementation has and its independence from technology, which provides the stability business people like and need so much. The whole story is all about ROI. If you don't want to take a bet on SOA, then why should you? In the end, it is your processes that create value, not your soa architecture. This however, does not exclude that we work on technologies allowing us using the current standards to build a bridge between business process management and an SOA implementation, just because both worlds go so well along with another.
Marwane El Kharbili.
Subscribe to:
Posts (Atom)