Achieving survivability in business process execution language for Web services (BPEL) with exception-flows

Survivability is defined as the capability of a service to fulfill its mission in a timely manner, even in the presence of attacks, failures, or accidents. Because of the severe consequences of failure, organizations are focusing on service survivability as a key risk management strategy for busines...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Hauptverfasser: Fung, C.K., Hung, P.C.K., Folger, D.H.
Format: Tagungsbericht
Sprache:eng
Schlagworte:
Online-Zugang:Volltext bestellen
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 74
container_issue
container_start_page 68
container_title
container_volume
creator Fung, C.K.
Hung, P.C.K.
Folger, D.H.
description Survivability is defined as the capability of a service to fulfill its mission in a timely manner, even in the presence of attacks, failures, or accidents. Because of the severe consequences of failure, organizations are focusing on service survivability as a key risk management strategy for business processes. There are three key survivability properties: resistance, recognition, and recovery. Recovery, a hallmark of survivability, is the capability to maintain critical components and resource during attack, limit the extent of damage, and restore full services following attack. Exception handling is a way to deals with the recovery aspect of survivability. Business process execution language for Web services (BPEL) has been proposed for formal specification of business processes and interaction protocols. BPEL defines an interoperable integration model that facilitates expansion of automated process integration in both intra- and intercorporate environments. A business process description requires the specification of both the normal flow and the possible variations due to exceptional situations that can be anticipate and monitored. This paper bridges the analysis of business process survivability and its recovery aspect in terms of exception handling in the context of BPEL. The feasibility of the proposed model is demonstrated using an illustrative travel reservation example.
doi_str_mv 10.1109/EEE.2005.26
format Conference Proceeding
fullrecord <record><control><sourceid>ieee_6IE</sourceid><recordid>TN_cdi_ieee_primary_1402270</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>1402270</ieee_id><sourcerecordid>1402270</sourcerecordid><originalsourceid>FETCH-LOGICAL-i175t-e2c84f92afc6754480d9b0d05be5ac51b38334239a2a390646d25fe51a2d2feb3</originalsourceid><addsrcrecordid>eNotkL9PhDAcxZsYE83J5OjSUQewP4GO5wVPExIdNI6XtnzLVREIBc777-Wib_ksn_eGh9A1JQmlRN0XRZEwQmTC0jMUqSwnWaokY5lIL1AUwidZwpXIGL9EX2u79zD7tsZhGmY_a-MbPx6xb7GZgm8hBNwPnT0RfsBOo-9a3Oi2nnQN2HUD_gCDAyzlRcK3D69FeYcPftwvvoX-5Meu6Q7hCp073QSI_rlC74_F2-YpLl-2z5t1GXuayTEGZnPhFNPOppkUIieVMqQi0oDUVlLDc84F40ozzRVJRVox6UBSzSrmwPAVuvnb9QCw6wf_rYfjjgqyfED4LwtvVw0</addsrcrecordid><sourcetype>Publisher</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>Achieving survivability in business process execution language for Web services (BPEL) with exception-flows</title><source>IEEE Electronic Library (IEL) Conference Proceedings</source><creator>Fung, C.K. ; Hung, P.C.K. ; Folger, D.H.</creator><creatorcontrib>Fung, C.K. ; Hung, P.C.K. ; Folger, D.H.</creatorcontrib><description>Survivability is defined as the capability of a service to fulfill its mission in a timely manner, even in the presence of attacks, failures, or accidents. Because of the severe consequences of failure, organizations are focusing on service survivability as a key risk management strategy for business processes. There are three key survivability properties: resistance, recognition, and recovery. Recovery, a hallmark of survivability, is the capability to maintain critical components and resource during attack, limit the extent of damage, and restore full services following attack. Exception handling is a way to deals with the recovery aspect of survivability. Business process execution language for Web services (BPEL) has been proposed for formal specification of business processes and interaction protocols. BPEL defines an interoperable integration model that facilitates expansion of automated process integration in both intra- and intercorporate environments. A business process description requires the specification of both the normal flow and the possible variations due to exceptional situations that can be anticipate and monitored. This paper bridges the analysis of business process survivability and its recovery aspect in terms of exception handling in the context of BPEL. The feasibility of the proposed model is demonstrated using an illustrative travel reservation example.</description><identifier>ISBN: 9780769522746</identifier><identifier>ISBN: 0769522742</identifier><identifier>DOI: 10.1109/EEE.2005.26</identifier><language>eng</language><publisher>IEEE</publisher><subject>Accidents ; Attack tree ; BPEL ; Exceptional Handling ; Formal specifications ; Imaging phantoms ; Independent component analysis ; Information technology ; Monitoring ; Protocols ; Risk management ; Service oriented architecture ; Survivability ; Web services</subject><ispartof>2005 IEEE International Conference on e-Technology, e-Commerce and e-Service, 2005, p.68-74</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/1402270$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>309,310,776,780,785,786,2052,4036,4037,27902,54895</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/1402270$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Fung, C.K.</creatorcontrib><creatorcontrib>Hung, P.C.K.</creatorcontrib><creatorcontrib>Folger, D.H.</creatorcontrib><title>Achieving survivability in business process execution language for Web services (BPEL) with exception-flows</title><title>2005 IEEE International Conference on e-Technology, e-Commerce and e-Service</title><addtitle>EEE</addtitle><description>Survivability is defined as the capability of a service to fulfill its mission in a timely manner, even in the presence of attacks, failures, or accidents. Because of the severe consequences of failure, organizations are focusing on service survivability as a key risk management strategy for business processes. There are three key survivability properties: resistance, recognition, and recovery. Recovery, a hallmark of survivability, is the capability to maintain critical components and resource during attack, limit the extent of damage, and restore full services following attack. Exception handling is a way to deals with the recovery aspect of survivability. Business process execution language for Web services (BPEL) has been proposed for formal specification of business processes and interaction protocols. BPEL defines an interoperable integration model that facilitates expansion of automated process integration in both intra- and intercorporate environments. A business process description requires the specification of both the normal flow and the possible variations due to exceptional situations that can be anticipate and monitored. This paper bridges the analysis of business process survivability and its recovery aspect in terms of exception handling in the context of BPEL. The feasibility of the proposed model is demonstrated using an illustrative travel reservation example.</description><subject>Accidents</subject><subject>Attack tree</subject><subject>BPEL</subject><subject>Exceptional Handling</subject><subject>Formal specifications</subject><subject>Imaging phantoms</subject><subject>Independent component analysis</subject><subject>Information technology</subject><subject>Monitoring</subject><subject>Protocols</subject><subject>Risk management</subject><subject>Service oriented architecture</subject><subject>Survivability</subject><subject>Web services</subject><isbn>9780769522746</isbn><isbn>0769522742</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>2005</creationdate><recordtype>conference_proceeding</recordtype><sourceid>6IE</sourceid><sourceid>RIE</sourceid><recordid>eNotkL9PhDAcxZsYE83J5OjSUQewP4GO5wVPExIdNI6XtnzLVREIBc777-Wib_ksn_eGh9A1JQmlRN0XRZEwQmTC0jMUqSwnWaokY5lIL1AUwidZwpXIGL9EX2u79zD7tsZhGmY_a-MbPx6xb7GZgm8hBNwPnT0RfsBOo-9a3Oi2nnQN2HUD_gCDAyzlRcK3D69FeYcPftwvvoX-5Meu6Q7hCp073QSI_rlC74_F2-YpLl-2z5t1GXuayTEGZnPhFNPOppkUIieVMqQi0oDUVlLDc84F40ozzRVJRVox6UBSzSrmwPAVuvnb9QCw6wf_rYfjjgqyfED4LwtvVw0</recordid><startdate>2005</startdate><enddate>2005</enddate><creator>Fung, C.K.</creator><creator>Hung, P.C.K.</creator><creator>Folger, D.H.</creator><general>IEEE</general><scope>6IE</scope><scope>6IL</scope><scope>CBEJK</scope><scope>RIE</scope><scope>RIL</scope></search><sort><creationdate>2005</creationdate><title>Achieving survivability in business process execution language for Web services (BPEL) with exception-flows</title><author>Fung, C.K. ; Hung, P.C.K. ; Folger, D.H.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-i175t-e2c84f92afc6754480d9b0d05be5ac51b38334239a2a390646d25fe51a2d2feb3</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>2005</creationdate><topic>Accidents</topic><topic>Attack tree</topic><topic>BPEL</topic><topic>Exceptional Handling</topic><topic>Formal specifications</topic><topic>Imaging phantoms</topic><topic>Independent component analysis</topic><topic>Information technology</topic><topic>Monitoring</topic><topic>Protocols</topic><topic>Risk management</topic><topic>Service oriented architecture</topic><topic>Survivability</topic><topic>Web services</topic><toplevel>online_resources</toplevel><creatorcontrib>Fung, C.K.</creatorcontrib><creatorcontrib>Hung, P.C.K.</creatorcontrib><creatorcontrib>Folger, D.H.</creatorcontrib><collection>IEEE Electronic Library (IEL) Conference Proceedings</collection><collection>IEEE Proceedings Order Plan All Online (POP All Online) 1998-present by volume</collection><collection>IEEE Xplore All Conference Proceedings</collection><collection>IEEE Electronic Library (IEL)</collection><collection>IEEE Proceedings Order Plans (POP All) 1998-Present</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Fung, C.K.</au><au>Hung, P.C.K.</au><au>Folger, D.H.</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>Achieving survivability in business process execution language for Web services (BPEL) with exception-flows</atitle><btitle>2005 IEEE International Conference on e-Technology, e-Commerce and e-Service</btitle><stitle>EEE</stitle><date>2005</date><risdate>2005</risdate><spage>68</spage><epage>74</epage><pages>68-74</pages><isbn>9780769522746</isbn><isbn>0769522742</isbn><abstract>Survivability is defined as the capability of a service to fulfill its mission in a timely manner, even in the presence of attacks, failures, or accidents. Because of the severe consequences of failure, organizations are focusing on service survivability as a key risk management strategy for business processes. There are three key survivability properties: resistance, recognition, and recovery. Recovery, a hallmark of survivability, is the capability to maintain critical components and resource during attack, limit the extent of damage, and restore full services following attack. Exception handling is a way to deals with the recovery aspect of survivability. Business process execution language for Web services (BPEL) has been proposed for formal specification of business processes and interaction protocols. BPEL defines an interoperable integration model that facilitates expansion of automated process integration in both intra- and intercorporate environments. A business process description requires the specification of both the normal flow and the possible variations due to exceptional situations that can be anticipate and monitored. This paper bridges the analysis of business process survivability and its recovery aspect in terms of exception handling in the context of BPEL. The feasibility of the proposed model is demonstrated using an illustrative travel reservation example.</abstract><pub>IEEE</pub><doi>10.1109/EEE.2005.26</doi><tpages>7</tpages></addata></record>
fulltext fulltext_linktorsrc
identifier ISBN: 9780769522746
ispartof 2005 IEEE International Conference on e-Technology, e-Commerce and e-Service, 2005, p.68-74
issn
language eng
recordid cdi_ieee_primary_1402270
source IEEE Electronic Library (IEL) Conference Proceedings
subjects Accidents
Attack tree
BPEL
Exceptional Handling
Formal specifications
Imaging phantoms
Independent component analysis
Information technology
Monitoring
Protocols
Risk management
Service oriented architecture
Survivability
Web services
title Achieving survivability in business process execution language for Web services (BPEL) with exception-flows
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-01T18%3A50%3A58IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-ieee_6IE&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=Achieving%20survivability%20in%20business%20process%20execution%20language%20for%20Web%20services%20(BPEL)%20with%20exception-flows&rft.btitle=2005%20IEEE%20International%20Conference%20on%20e-Technology,%20e-Commerce%20and%20e-Service&rft.au=Fung,%20C.K.&rft.date=2005&rft.spage=68&rft.epage=74&rft.pages=68-74&rft.isbn=9780769522746&rft.isbn_list=0769522742&rft_id=info:doi/10.1109/EEE.2005.26&rft_dat=%3Cieee_6IE%3E1402270%3C/ieee_6IE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=1402270&rfr_iscdi=true