DOI QR코드

DOI QR Code

Design and Implementation of Rule-based BPEL System for BPEL Rule Modeling

BPEL 규칙 모델링을 위한 규칙 기반 BPEL 시스템 설계와 구현

  • Kwak, Donggyu (School of Computer Science and Engineering, Soongsil University) ;
  • Choi, Jaeyoung (School of Computer Science and Engineering, Soongsil University)
  • Received : 2013.08.20
  • Accepted : 2013.09.05
  • Published : 2013.09.30

Abstract

BPEL is a standard executable language for specifying actions within business processes with Web services. BPEL workflow requires rule engine to describe application process in BPEL, as the requirements increase. It is needed to develop new BPEL's engine or modify BPEL's engine in order to add the functionality of rules to BPEL engines, but this method is not easy to implement and it requires very high cost. In this paper, we present an R4BPEL document, which uses the original BPEL grammar and includes a rule document. With this method, it is possible to build rule-based BPEL environment easily by adding web services with rules and R4BPEL document analyzer to the general-purpose Web services. In this paper, we campared a BPEL's document in proposed system with a BPEL's document in the existing system. And we demonstrated the simplicity of the rule-based system.

BPEL은 작업의 순서를 기술하는 워크플로우의 표준으로서, 웹 서비스를 기반으로 하는 분산 컴퓨팅 환경의 많은 응용 분야에 적용되고 있다. BPEL의 요구사항이 복잡해지면서 규칙기반의 엔진이 요구되고 있다. 본 논문은 BPEL 문법을 그대로 이용하면서 규칙을 추가하기 위해 규칙을 기술할 수 있는 R4BPEL 문서를 제안하고 규칙 웹 서비스를 이용하여 BPEL에 규칙을 사용할 수 있도록 제안한다. BPEL 엔진에 규칙 기능을 추가하기 위해서는 BPEL 엔진을 새롭게 개발하거나 수정해야 하는데, 이 방법은 많은 비용이 많이 필요하다. 제안하는 방법은 기존의 범용 BPEL 시스템에 규칙 웹 서비스와 R4BPEL 문서 분석기를 추가하여 손쉽게 규칙 기반의 BPEL 환경을 구성할 수 있다. 본 논문에서는 제안하는 시스템에서의 BPEL 문서와 기존 방식의 BPEL 문서를 비교하여 제안하는 시스템의 규칙 기반 BPEL 문서가 단순함을 보인다.

Keywords

References

  1. O. Zimmermann, V. Doubrovski, J. Grundler, K. Hogg, "Service-oriented architecture and business process choreography in an order management scenario: rationale, concepts, lessons learned", Proceeding OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications, pp.301-312, 2005.
  2. BPEL, http://www-128.ibm.com/developerworks/library/specification/ws-bpel/.
  3. OASIS, http://www.oasis-open.org.
  4. JBoss Rules, http://labs.jboss.com/jbossrules/docs.
  5. F. Rosenberg and S. Dustdar, "Business Rules Integration in BPEL - A Service-Oriented Approach", In Proceddings of the 7th International IEEE Conference on E-Commerce Technology (CEC 2005), 2005.
  6. AspectJ, http://www.eclipse.org/aspectj/
  7. Donggyu Kwak, Jaeyoung Choi, Chae-woo Yoo, "Rule based BPEL System using Aspect-Oriented Programming", Journal of Korean Institute of Information Scientists and Engineers, Vol.39, No.2, pp.153-161, Feb. 2012.
  8. B2J, http://www.eclipse.org/stp/b2j/
  9. Gregor Kiczales, John Lamping, Anurag Mendhekar, Chris Maeda, Cristina Videira Lopes, Jean-Marc Loingtier and John Irwin, "Aspect-Oriented Programming", ECOOP, pp.220-242, 1997.
  10. Drools, http://www.jboss.org/drools/.
  11. Honghua Cao, Shi Ying, Dehui Du, "Towards Model-based Verification of BPEL with Model Checking", Computer and Information Technology 2006, pp.190-194, 2006.