਀㰀氀椀渀欀 栀爀攀昀㴀∀搀愀琀愀⼀猀礀洀戀漀氀攀㄀⸀樀瀀最∀ 爀攀氀㴀∀猀栀漀爀琀挀甀琀 椀挀漀渀∀ 琀礀瀀攀㴀∀搀愀琀愀⼀椀挀漀∀㸀 ਀㰀洀攀琀愀 栀琀琀瀀ⴀ攀焀甀椀瘀㴀∀䌀漀渀琀攀渀琀ⴀ吀礀瀀攀∀ 挀漀渀琀攀渀琀㴀∀琀攀砀琀⼀栀琀洀氀㬀 挀栀愀爀猀攀琀㴀椀猀漀ⴀ㠀㠀㔀㤀ⴀ㄀∀ ⼀㸀 ਀ LBACT Tool਀㰀⼀栀攀愀搀㸀 ਀㰀戀漀搀礀㸀 ਀ ਀ऀ㰀琀搀 眀椀搀琀栀㴀∀㄀㔀─∀ 爀漀眀猀瀀愀渀㴀∀㐀∀ 㸀☀渀戀猀瀀㬀㰀⼀琀搀㸀 ਀ऀ㰀琀搀 眀椀搀琀栀㴀∀㄀㔀─∀ 爀漀眀猀瀀愀渀㴀∀㐀∀ 㸀☀渀戀猀瀀㬀㰀⼀琀搀㸀 ਀ ਀ऀ㰀℀ⴀⴀऀ㰀琀搀 挀漀氀猀瀀愀渀㴀∀㈀∀ 挀氀愀猀猀㴀∀洀攀渀甀∀㸀 ਀ऀऀऀ   ਀ऀⴀⴀ㸀 ਀ ਀ऀ㰀琀搀 眀椀搀琀栀㴀∀㄀㠀─∀ 挀氀愀猀猀㴀∀戀漀砀∀㸀 

BPEL Clustering Architecture

਀ऀऀऀ㰀甀氀㸀
  • Overview
    • ਀ऀऀऀ㰀氀椀㸀㰀椀㸀㰀愀 栀爀攀昀㴀∀椀洀瀀氀⸀栀琀洀氀∀⼀㸀䤀洀瀀氀攀洀攀渀琀愀琀椀漀渀㰀⼀愀㸀㰀⼀椀㸀㰀⼀氀椀㸀 ਀ऀऀ㰀栀㌀㸀䰀䈀䄀䌀吀 吀漀漀氀㰀⼀栀㌀㸀 ਀ऀऀऀ

    Contact

    ਀ऀ䄀昀攀昀 䨀洀愀氀 䴀愀氀攀樀 㰀戀爀⼀㸀 ReDCAD - DGIMA - ENIS
    ਀ऀ刀漀甀琀攀 搀攀 氀愀 匀漀甀欀爀愀 欀洀 ㌀⸀㔀㰀戀爀⼀㸀 B.P. 1173, 3038, Sfax - Tunisia
    ਀    㰀戀㸀䔀洀愀椀氀㨀㰀⼀戀㸀 afef.jmal@redcad.org਀ऀऀऀ ਀ऀऀ㰀栀㌀㸀䌀漀渀琀爀椀戀甀琀漀爀猀㰀⼀栀㌀㸀 ਀㰀愀 栀爀攀昀㴀∀栀琀琀瀀㨀⼀⼀眀眀眀⸀爀攀搀挀愀搀⸀漀爀最⼀洀攀洀戀攀爀猀⼀愀昀攀昀⸀樀洀愀氀∀ 琀愀爀最攀琀㴀∀开戀氀愀渀欀∀㸀㰀昀漀渀琀 挀漀氀漀爀㴀∀戀氀愀挀欀∀㸀䴀匀挀⸀ 䄀昀攀昀 䨀洀愀氀 䴀愀氀攀樀㰀⼀昀漀渀琀㸀㰀⼀愀㸀㰀戀爀㸀 ਀  㰀愀 栀爀攀昀㴀∀栀琀琀瀀㨀⼀⼀眀眀眀⸀爀攀搀挀愀搀⸀漀爀最⼀洀攀洀戀攀爀猀⼀稀攀椀渀攀戀⸀戀攀渀洀愀欀栀氀漀甀昀∀ 琀愀爀最攀琀㴀∀开戀氀愀渀欀∀㸀㰀昀漀渀琀 挀漀氀漀爀㴀∀戀氀愀挀欀∀㸀䤀渀最⸀ 娀攀椀渀攀戀 䈀攀渀 䴀愀欀栀氀漀甀昀㰀⼀昀漀渀琀㸀㰀⼀愀㸀㰀戀爀㸀 ਀   㰀愀 栀爀攀昀㴀∀栀琀琀瀀㨀⼀⼀眀眀眀⸀爀攀搀挀愀搀⸀漀爀最⼀洀攀洀戀攀爀猀⼀洀欀爀椀挀栀攀渀⼀∀ 琀愀爀最攀琀㴀∀开戀氀愀渀欀∀㸀㰀昀漀渀琀 挀漀氀漀爀㴀∀戀氀愀挀欀∀㸀䐀爀⸀ 䴀漀攀稀 䬀爀椀挀栀攀渀㰀⼀昀漀渀琀㸀㰀⼀愀㸀 㰀戀爀㸀 ਀ऀ㰀愀 栀爀攀昀㴀∀栀琀琀瀀㨀⼀⼀眀眀眀⸀爀攀搀挀愀搀⸀漀爀最⼀洀攀洀戀攀爀猀⼀樀洀愀椀攀氀∀ 琀愀爀最攀琀㴀∀开戀氀愀渀欀∀㸀㰀昀漀渀琀 挀漀氀漀爀㴀∀戀氀愀挀欀∀㸀倀爀漀昀⸀ 䴀漀栀愀洀攀搀 䨀洀愀椀攀氀㰀⼀昀漀渀琀㸀㰀⼀愀㸀 ऀऀऀ ऀ ਀ऀ㰀琀搀㸀 ਀㰀戀爀㸀 ਀㰀栀㌀㸀㰀挀攀渀琀攀爀㸀㰀昀漀渀琀 挀漀氀漀爀㴀∀搀愀爀欀 漀爀愀渀最攀∀㸀㰀椀㸀䌀愀猀攀 匀琀甀搀礀㰀⼀椀㸀㰀⼀昀漀渀琀㸀㰀⼀挀攀渀琀攀爀㸀㰀⼀栀㌀㸀㰀⼀愀㸀 ਀㰀瀀 愀氀椀最渀㴀∀樀甀猀琀椀昀礀∀㸀 In this section, we describe a related case study to a travel agency as a composite service TravelAgency. Then, we detail the implementation of this service in BPEL. Finally, we illustrate the use of our conformance testing tool to test an architecture balancing load between servers deploying our considered composite service. ਀㰀⼀瀀㸀 ਀㰀漀氀 琀礀瀀攀㴀∀㄀∀㸀
  • Description of the composite service TravelAgency:
    • ਀吀漀 椀氀氀甀猀琀爀愀琀攀 漀甀爀 猀漀氀甀琀椀漀渀Ⰰ 眀攀 挀漀渀猀椀搀攀爀攀搀 愀 挀愀猀攀 猀琀甀搀礀 漀昀 愀 琀爀愀瘀攀氀 愀最攀渀挀礀 愀猀 搀攀猀挀爀椀戀攀搀 椀渀 琀栀攀 渀攀砀琀 昀椀最甀爀攀⸀ ਀㰀挀攀渀琀攀爀㸀㰀椀洀最 猀爀挀㴀∀搀愀琀愀⼀昀椀最㜀⸀樀瀀最∀⼀㸀㰀⼀挀攀渀琀攀爀㸀
    Composite Service TravelAgency
    ਀

    ਀䤀渀 琀栀攀 挀漀渀琀攀砀琀 漀昀 琀栀椀猀 挀愀猀攀 猀琀甀搀礀Ⰰ 眀攀 挀漀渀猀椀搀攀爀 琀眀漀 瀀爀漀挀攀猀猀攀猀 琀栀愀琀 椀渀挀氀甀搀攀 愀挀琀椀瘀椀琀椀攀猀 爀攀瀀爀攀猀攀渀琀椀渀最 瀀爀漀昀攀猀猀椀漀渀愀氀 琀愀猀欀猀 漀爀 椀渀琀攀爀愀挀琀椀漀渀猀 戀攀琀眀攀攀渀 圀攀戀 猀攀爀瘀椀挀攀猀 愀渀搀 挀氀椀攀渀琀猀㨀 琀栀攀猀攀 愀爀攀 琀栀攀 琀爀愀瘀攀氀 猀攀愀爀挀栀 瀀爀漀挀攀猀猀 愀渀搀 琀栀攀 琀爀愀瘀攀氀 戀漀漀欀椀渀最 瀀爀漀挀攀猀猀⸀ 吀栀攀猀攀 琀眀漀 瀀爀漀挀攀猀猀攀猀 甀猀攀 琀栀攀 猀攀爀瘀椀挀攀猀 漀昀 愀椀爀氀椀渀攀猀 愀渀搀 栀漀琀攀氀猀 琀漀 昀椀渀搀 愀瘀愀椀氀愀戀氀攀 漀昀昀攀爀猀⸀ 吀栀攀 琀爀愀瘀攀氀 猀攀愀爀挀栀 瀀爀漀挀攀猀猀 椀渀挀氀甀搀攀猀 琀眀漀 圀攀戀 匀攀爀瘀椀挀攀猀㨀 琀栀攀 栀漀琀攀氀猀 猀攀愀爀挀栀 猀攀爀瘀椀挀攀 䠀漀琀攀氀匀攀愀爀挀栀 愀渀搀 琀栀攀 昀氀椀最栀琀猀 猀攀愀爀挀栀 猀攀爀瘀椀挀攀 䘀氀椀最栀琀匀攀愀爀挀栀⸀ 䈀漀琀栀 猀攀爀瘀椀挀攀 栀漀琀攀氀猀 戀漀漀欀椀渀最 䠀漀琀攀氀䈀漀漀欀 愀渀搀 昀氀椀最栀琀猀 戀漀漀欀椀渀最 䘀氀椀最栀琀䈀漀漀欀 挀栀愀爀愀挀琀攀爀椀稀攀 琀栀攀 琀爀愀瘀攀氀 戀漀漀欀椀渀最 瀀爀漀挀攀猀猀⸀ Five partners participate then in the whole process: customers, hotels search service, flights search service, hotels booking service and flights booking service.
    ਀圀栀攀渀 愀 挀氀椀攀渀琀 猀攀渀搀猀 愀 琀爀椀瀀 爀攀焀甀攀猀琀 昀漀爀 琀栀攀 琀爀愀瘀攀氀 愀最攀渀挀礀Ⰰ 琀栀攀 琀爀愀瘀攀氀 猀攀愀爀挀栀 瀀爀漀挀攀猀猀 椀渀琀攀爀愀挀琀猀 眀椀琀栀 椀渀昀漀爀洀愀琀椀漀渀 猀礀猀琀攀洀猀 漀昀 愀椀爀氀椀渀攀 挀漀洀瀀愀渀椀攀猀 ⠀爀攀猀瀀⸀ 栀漀琀攀氀 挀栀愀椀渀猀⤀ 昀漀爀 昀氀椀最栀琀猀 ⠀爀攀猀瀀⸀ 栀漀琀攀氀 爀漀漀洀猀⤀ 琀栀愀琀 洀愀琀挀栀 挀氀椀攀渀琀 渀攀攀搀猀⸀ 吀栀攀渀Ⰰ 琀栀攀 琀爀愀瘀攀氀 愀最攀渀挀礀 猀攀渀搀猀 琀栀攀 爀攀猀瀀漀渀猀攀 愀猀 愀 猀攀琀 漀昀 漀昀昀攀爀猀 琀栀愀琀 挀漀洀戀椀渀攀 挀漀渀挀攀爀渀攀搀 昀氀椀最栀琀猀 愀渀搀 愀瘀愀椀氀愀戀氀攀 栀漀琀攀氀猀⸀ 匀漀 琀栀攀 挀氀椀攀渀琀 挀漀甀氀搀 挀栀漀漀猀攀 愀渀 漀昀昀攀爀⸀ 吀栀椀猀 猀琀攀瀀 猀琀愀爀琀猀 琀栀攀 琀爀愀瘀攀氀 戀漀漀欀椀渀最 瀀爀漀挀攀猀猀Ⰰ 眀栀椀挀栀 椀渀琀攀爀愀挀琀猀 眀椀琀栀 琀栀攀 猀攀爀瘀椀挀攀猀 漀昀 愀椀爀氀椀渀攀 挀漀洀瀀愀渀椀攀猀 愀渀搀 栀漀琀攀氀猀 琀漀 挀栀攀挀欀 愀瘀愀椀氀愀戀椀氀椀琀礀⸀ 䄀挀挀漀爀搀椀渀最 琀漀 琀栀攀 愀瘀愀椀氀愀戀椀氀椀琀礀 爀攀猀甀氀琀猀Ⰰ 琀栀椀猀 瀀爀漀挀攀猀猀 愀猀欀猀 琀栀攀 挀氀椀攀渀琀 琀漀 挀漀渀昀椀爀洀 琀栀攀 戀漀漀欀椀渀最 愀渀搀 琀漀 瀀爀漀瘀椀搀攀 瀀愀礀洀攀渀琀 搀攀琀愀椀氀猀⸀ 䤀渀 琀栀攀 氀愀猀琀 猀琀愀最攀Ⰰ 琀栀椀猀 瀀爀漀挀攀猀猀 洀愀欀攀猀 琀栀攀 戀漀漀欀椀渀最 愀渀搀 猀攀渀搀猀 愀 挀漀渀昀椀爀洀愀琀椀漀渀 戀礀 攀ⴀ洀愀椀氀 琀漀 琀栀攀 挀氀椀攀渀琀⸀ We suppose that the travel agency is equipped with a set of servers orchestrated by a load balancer to handle many client requests and ensure so high availability.਀

  • Implementation and deployment of the composite service TravelAgency:
    • ਀吀漀 椀洀瀀氀攀洀攀渀琀 愀渀搀 搀攀瀀氀漀礀 琀栀攀 䈀倀䔀䰀 挀漀洀瀀漀猀椀琀攀 猀攀爀瘀椀挀攀 吀爀愀瘀攀氀䄀最攀渀挀礀Ⰰ 眀攀 甀猀攀搀 琀栀攀 伀爀愀挀氀攀 䨀䐀攀瘀攀氀漀瀀攀爀 琀漀漀氀⸀ ਀㰀漀氀 琀礀瀀攀㴀∀愀∀㸀
  • Oracle JDeveloper Studio Edition:
    • ਀㰀瀀 愀氀椀最渀㴀∀樀甀猀琀椀昀礀∀㸀 Oracle JDeveloper is a free development environment. It is used to implement applications and Web services using Java, XML and SQL. To graphically design a BPEL process, Oracle JDeveloper provides a palette that illustrates various activities of a BPEL process. This development environment offers the possibility of verifying the syntax of an implemented BPEL process, also to deploy it, in a BPEL server, via a configurable connection to this server.਀㰀戀爀㸀 The implementation in BPEL of the composite service TravelAgency is described by a sequential flow of activities.਀吀栀椀猀 椀洀瀀氀攀洀攀渀琀愀琀椀漀渀 椀猀 爀攀愀氀椀稀攀搀 眀椀琀栀 伀爀愀挀氀攀 䨀䐀攀瘀攀氀漀瀀攀爀 琀漀漀氀⸀ ਀㰀氀椀㸀 㰀戀㸀䐀攀瀀氀漀礀洀攀渀琀 漀昀 琀栀攀 挀漀洀瀀漀猀椀琀攀 猀攀爀瘀椀挀攀 吀爀愀瘀攀氀䄀最攀渀挀礀㨀㰀⼀戀㸀㰀⼀氀椀㸀

    ਀伀爀愀挀氀攀 䨀䐀攀瘀攀氀漀瀀攀爀 攀渀愀戀氀攀猀 琀栀攀 搀攀瀀氀漀礀洀攀渀琀 漀昀 愀 䈀倀䔀䰀 瀀爀漀挀攀猀猀 椀渀 琀栀攀 伀爀愀挀氀攀 䈀倀䔀䰀 匀攀爀瘀攀爀⸀ 吀漀 挀栀攀挀欀 椀昀 琀栀攀 䈀倀䔀䰀 瀀爀漀挀攀猀猀 眀愀猀 眀攀氀氀 搀攀瀀氀漀礀攀搀Ⰰ 眀攀 洀甀猀琀 挀漀渀猀甀氀琀 琀栀攀 挀漀渀猀漀氀攀 伀爀愀挀氀攀 䈀倀䔀䰀 䌀漀渀琀爀漀氀 漀昀 愀 䈀倀䔀䰀 猀攀爀瘀攀爀 椀渀 琀栀攀 䈀倀䔀䰀 挀氀甀猀琀攀爀⸀ The next figure shows the interface of the console Oracle BPEL Control. Observe that the composite service and its service partners (FlightSearch) (HotelSearch) (FlightBook) and (Hotelbook) are deployed.਀

    ਀㰀挀攀渀琀攀爀㸀㰀攀洀㸀嘀攀爀椀昀椀挀愀琀椀漀渀 漀昀 琀栀攀 搀攀瀀氀漀礀攀洀攀渀琀 漀昀 琀栀攀 挀漀洀瀀漀猀椀琀攀 猀攀爀瘀椀挀攀 吀爀愀瘀攀氀䄀最攀渀挀礀㰀⼀攀洀㸀㰀⼀挀攀渀琀攀爀㸀   ਀㰀瀀 愀氀椀最渀㴀∀樀甀猀琀椀昀礀∀㸀 Oracle BPEL Control also shows that the instance of ID 1120041, of a BPEL process, was executed on the BPEL server installed on the machine host3 because vmh3 represents the identifier of this BPEL server.਀
       Top of Page
    ਀
  • Test scenarios:
    • ਀㰀瀀 愀氀椀最渀㴀∀樀甀猀琀椀昀礀∀㸀 For conformance testing of the proposed load balancing architecture, we defined several possible scenarios.਀㰀戀爀㸀 In this section, we present three proposed scenarios. The first two scenarios are used to test if the correct BPEL server was invoked. The third scenario is used to test the invocation time of a BPEL server compared to tmax (timeout).਀㰀戀爀㸀㰀戀爀㸀 ਀㰀戀㸀ⴀऀ㰀甀㸀匀挀攀渀愀爀椀漀 ㄀㨀㰀⼀甀㸀㰀⼀戀㸀㰀戀爀㸀

    ਀䤀渀 琀栀椀猀 猀挀攀渀愀爀椀漀Ⰰ 眀攀 愀猀猀甀洀攀 琀栀愀琀㨀㰀戀爀㸀 • the load balancer is configured to use the round-robin algorithm,
    ਀∀ठ琀栀攀 渀甀洀戀攀爀 漀昀 猀攀爀瘀攀爀猀 椀猀 琀眀漀Ⰰ㰀戀爀㸀 • 30 BPEL instances are invoked each one second, which corresponds to 1000 milliseconds for the BPEL invocation frequency,
    ਀∀ठ琀洀愀砀 瘀愀氀甀攀 椀猀 攀焀甀愀氀 琀漀 ㄀　　 洀椀氀氀椀猀攀挀漀渀搀猀⸀㰀戀爀㸀 We aim to check the respect of the adopted algorithm principle under the previous load conditions.
    ਀㰀戀㸀ⴀऀ匀挀攀渀愀爀椀漀 ㄀ 爀攀猀甀氀琀㨀㰀⼀戀㸀㰀戀爀㸀 The next figure shows the generated test progress over time, according to the first scenario.਀

    ਀㰀挀攀渀琀攀爀㸀㰀攀洀㸀吀攀猀琀 倀爀漀最爀攀猀猀 䄀挀挀漀爀搀椀渀最 琀漀 匀挀攀渀愀爀椀漀 ㄀㰀⼀攀洀㸀㰀⼀挀攀渀琀攀爀㸀  

    ਀吀栀攀 琀攀猀琀攀爀 戀攀最椀渀猀 眀椀琀栀 挀漀渀昀椀最甀爀椀渀最 愀渀搀 猀琀愀爀琀椀渀最 琀栀攀 䈀倀䔀䰀 挀氀甀猀琀攀爀 攀氀攀洀攀渀琀猀⸀ 吀栀攀 昀椀爀猀琀 椀渀瘀漀欀攀搀 䈀倀䔀䰀 猀攀爀瘀攀爀 戀礀 琀栀攀 氀漀愀搀 戀愀氀愀渀挀攀爀 椀猀 琀栀攀 猀攀爀瘀攀爀 爀甀渀渀椀渀最 漀渀 琀栀攀 洀愀挀栀椀渀攀 栀漀猀琀㈀⸀ 吀栀攀爀攀昀漀爀攀Ⰰ 琀栀攀 昀椀爀猀琀 琀爀愀渀猀椀琀椀漀渀 眀栀椀挀栀 猀漀甀爀挀攀 椀猀 氀漀愀搀 戀愀氀愀渀挀攀爀 栀愀猀 愀猀 搀攀猀琀椀渀愀琀椀漀渀 栀漀猀琀㈀⸀ 䤀琀猀 琀礀瀀攀 椀猀 吀椀洀攀搀䜀甀愀爀搀䄀猀猀椀最渀洀攀渀琀⸀ 䤀渀搀攀攀搀Ⰰ 琀栀椀猀 琀爀愀渀猀椀琀椀漀渀 椀猀 氀愀戀攀氀攀搀 戀礀㨀㰀戀爀㸀 • a temporal constraint on the network waiting time,
    ਀∀ठ愀 挀漀渀搀椀琀椀漀渀 琀漀 挀栀攀挀欀 琀栀攀 瀀爀椀渀挀椀瀀氀攀 漀昀 琀栀攀 氀漀愀搀 戀愀氀愀渀挀椀渀最 愀氀最漀爀椀琀栀洀 愀猀 愀 昀甀渀挀琀椀漀渀 眀栀椀挀栀 爀攀琀甀爀渀猀 愀 䈀漀漀氀攀愀渀Ⰰ㰀戀爀㸀 • another condition to estimate if the test instance number was reached,
    ਀∀ठ愀 瘀愀爀椀愀戀氀攀 眀栀椀挀栀 眀椀氀氀 戀攀 甀瀀搀愀琀攀搀Ⰰ 椀琀 挀漀爀爀攀猀瀀漀渀搀猀 琀漀 琀栀攀 猀攀焀甀攀渀挀攀 爀攀瀀爀攀猀攀渀琀椀渀最 椀渀瘀漀欀攀搀 䈀倀䔀䰀 猀攀爀瘀攀爀猀⸀㰀戀爀㸀 We notice that the obtained sequence at the end of test complies with the principle of the round-robin algorithm. In addition, the value of tmax was not exceeded during the test. In this case, the tester generates a "Verdict = Pass" indicating that the load balancer real functioning according to the first test scenario is conform to the specification of the round-robin algorithm.਀㰀挀攀渀琀攀爀㸀㰀愀 栀爀攀昀㴀∀⌀栀愀甀琀∀㸀㰀䤀䴀䜀 匀刀䌀㴀∀搀愀琀愀⼀䠀愀甀琀⸀樀瀀最∀ 愀氀椀最渀㴀∀挀攀渀琀攀爀∀㸀㰀⼀愀㸀☀渀戀猀瀀㬀☀渀戀猀瀀㬀☀渀戀猀瀀㬀㰀愀 栀爀攀昀㴀∀⌀栀愀甀琀∀㸀㰀昀漀渀琀 挀漀氀漀爀㴀∀⌀㤀䈀䐀䈀㄀㠀∀㸀㰀戀椀最㸀吀漀瀀 漀昀 倀愀最攀㰀⼀戀椀最㸀㰀⼀昀漀渀琀㸀㰀⼀愀㸀㰀⼀挀攀渀琀攀爀㸀 ਀㰀戀㸀ⴀऀ㰀甀㸀匀挀攀渀愀爀椀漀 ㈀㨀㰀⼀甀㸀㰀⼀戀㸀㰀戀爀㸀

    ਀圀攀 猀甀瀀瀀漀猀攀 琀栀愀琀 琀攀猀琀 椀渀瀀甀琀猀 愀爀攀 猀椀洀椀氀愀爀 琀漀 琀栀漀猀攀 漀昀 猀挀攀渀愀爀椀漀 ㄀Ⰰ 漀渀氀礀 琀栀攀 氀漀愀搀 戀愀氀愀渀挀椀渀最 愀氀最漀爀椀琀栀洀 搀椀昀昀攀爀猀⸀ 䤀渀 昀愀挀琀Ⰰ 眀攀 愀猀猀甀洀攀 琀栀愀琀 琀栀攀 氀漀愀搀 戀愀氀愀渀挀椀渀最 愀氀最漀爀椀琀栀洀 椀猀 眀攀椀最栀琀攀搀 爀漀甀渀搀ⴀ爀漀戀椀渀⸀ 圀攀 愀氀猀漀 琀愀爀最攀琀 琀漀 攀瘀愀氀甀愀琀攀 眀栀攀琀栀攀爀 椀琀猀 瀀爀椀渀挀椀瀀氀攀 椀猀 爀攀猀瀀攀挀琀攀搀 漀爀 渀漀琀⸀㰀戀爀㸀 - Scenario 2 result:
    ਀吀栀攀 琀攀猀琀 攀砀攀挀甀琀椀漀渀 瀀爀漀最爀攀猀猀 椀猀 搀椀猀瀀氀愀礀攀搀 椀渀 琀栀攀 昀漀氀氀漀眀椀渀最 昀椀最甀爀攀⸀ ਀㰀挀攀渀琀攀爀㸀㰀椀洀最 猀爀挀㴀∀搀愀琀愀⼀猀㈀⸀樀瀀最∀⼀㸀㰀⼀挀攀渀琀攀爀㸀

    Test Progress According to Scenario 2
    ਀㰀瀀 愀氀椀最渀㴀∀樀甀猀琀椀昀礀∀㸀 Indeed, the elements of the BPEL cluster are initially configured and launched by the tester according to provided inputs by the user. The weight value of the first BPEL server is equal to two, while the value of the second weight is equal to one. The BPEL server running on the machine host3 is the first invoked server by the load balancer. Therefore, the first transition which source is the load balancer has as destination host3. Its type is TimedGuardAssignment. Indeed, this transition:
    ਀∀ठ攀瘀愀氀甀愀琀攀猀 琀栀攀 瘀愀氀甀攀 漀昀 渀攀琀眀漀爀欀 眀愀椀琀椀渀最 琀椀洀攀 挀漀洀瀀愀爀攀搀 琀漀 琀洀愀砀Ⰰ㰀戀爀㸀 • checks the principle of the load balancing algorithm,
    ਀∀ठ樀甀搀最攀猀 椀昀 琀栀攀 渀甀洀戀攀爀 漀昀 琀攀猀琀 椀渀猀琀愀渀挀攀 眀愀猀 爀攀愀挀栀攀搀Ⰰ㰀戀爀㸀 • updates the sequence representing the invoked BPEL servers.
    ਀圀攀 渀漀琀椀挀攀 琀栀愀琀 琀栀攀 漀戀琀愀椀渀攀搀 猀攀焀甀攀渀挀攀 搀甀爀椀渀最 琀栀攀 琀攀猀琀 搀漀攀猀 渀漀琀 爀攀猀瀀攀挀琀 琀栀攀 瀀爀椀渀挀椀瀀氀攀 漀昀 琀栀攀 眀攀椀最栀琀攀搀 爀漀甀渀搀ⴀ爀漀戀椀渀 愀氀最漀爀椀琀栀洀⸀ 䤀渀 昀愀挀琀Ⰰ 琀栀攀 昀椀昀琀栀 䈀倀䔀䰀 椀渀猀琀愀渀挀攀 猀栀漀甀氀搀 戀攀 栀愀渀搀氀攀搀 戀礀 琀栀攀 䈀倀䔀䰀 猀攀爀瘀攀爀 爀甀渀渀椀渀最 漀渀 栀漀猀琀㌀ 洀愀挀栀椀渀攀 戀攀挀愀甀猀攀 琀栀椀猀 猀攀爀瘀攀爀 栀愀猀 愀猀 眀攀椀最栀琀 瘀愀氀甀攀 琀眀漀⸀ 䤀渀 琀栀椀猀 挀愀猀攀Ⰰ 琀栀攀 琀攀猀琀攀爀 最攀渀攀爀愀琀攀猀 愀 ∀嘀攀爀搀椀挀琀 㴀 䘀愀椀氀㨀 䄀氀最漀爀椀琀栀洀 渀漀琀 爀攀猀瀀攀挀琀攀搀∀ 椀渀搀椀挀愀琀椀渀最 琀栀愀琀 琀栀攀 瀀爀椀渀挀椀瀀氀攀 漀昀 琀栀攀 眀攀椀最栀琀攀搀 爀漀甀渀搀ⴀ爀漀戀椀渀 愀氀最漀爀椀琀栀洀 椀猀 渀漀琀 椀渀 愀挀挀漀爀搀愀渀挀攀 眀椀琀栀 琀栀攀 猀瀀攀挀椀昀椀挀愀琀椀漀渀⸀
       Top of Page
    ਀ - Scenario 3:
    ਀㰀瀀 愀氀椀最渀㴀∀樀甀猀琀椀昀礀∀㸀 We suppose that test inputs are similar to those of scenario 1, only the value of tmax is different. We presume that this value is equal to fifty milliseconds. We aim to observe if this period is exceeded.
    ਀㰀戀㸀ⴀऀ 匀挀攀渀愀爀椀漀 ㌀ 爀攀猀甀氀琀㨀㰀⼀戀㸀㰀戀爀㸀 The next figure shows the generated test report after the execution of the third scenario.਀
    ਀㰀挀攀渀琀攀爀㸀㰀攀洀㸀䜀攀渀攀爀愀琀攀搀 吀攀猀琀 刀攀瀀漀爀琀 䄀挀挀漀爀搀椀渀最 琀漀 匀挀攀渀愀爀椀漀㌀㰀⼀攀洀㸀㰀⼀挀攀渀琀攀爀㸀   ਀㰀瀀 愀氀椀最渀㴀∀樀甀猀琀椀昀礀∀㸀 For the first three BPEL instances, the value of tmax was not exceeded. In addition, the sequence constructed during the test complies with the principle of round-robin algorithm. We remark that the value of tmax is exceeded in the fourth BPEL instance. Indeed, the tester, for this instance, is waiting for a request sent by the load balancer to the BPEL server running on host2 machine. A timeout is observed because the value of waitingTime is greater than tmax. In this case, the tester generates a "Verdict = Fail: Reaching network timeout" because the value of network maximum waiting time, which value is equal to fifty milliseconds, was exceeded.਀㰀⼀氀椀㸀 ਀

    ਀

    ਀ ਀㰀挀攀渀琀攀爀㸀㰀愀 栀爀攀昀㴀∀⌀栀愀甀琀∀㸀㰀䤀䴀䜀 匀刀䌀㴀∀搀愀琀愀⼀䠀愀甀琀⸀樀瀀最∀ 愀氀椀最渀㴀∀挀攀渀琀攀爀∀㸀㰀⼀愀㸀☀渀戀猀瀀㬀☀渀戀猀瀀㬀☀渀戀猀瀀㬀㰀愀 栀爀攀昀㴀∀⌀栀愀甀琀∀㸀㰀昀漀渀琀 挀漀氀漀爀㴀∀⌀㤀䈀䐀䈀㄀㠀∀㸀㰀戀椀最㸀吀漀瀀 漀昀 倀愀最攀㰀⼀戀椀最㸀㰀⼀昀漀渀琀㸀㰀⼀愀㸀㰀⼀挀攀渀琀攀爀㸀 ਀ऀ㰀⼀琀搀㸀 ਀   ਀ऀ㰀琀搀 挀漀氀猀瀀愀渀㴀∀㈀∀ 挀氀愀猀猀㴀∀昀漀漀琀攀爀∀㸀 ਀ऀऀऀऀ㰀瀀 愀氀椀最渀㴀∀挀攀渀琀攀爀∀ 猀琀礀氀攀㴀∀琀攀砀琀ⴀ愀氀椀最渀㨀 挀攀渀琀攀爀㬀∀㸀㰀昀漀渀琀 挀漀氀漀爀㴀眀栀椀琀攀㸀㰀猀瀀愀渀 氀愀渀最㴀∀䔀一ⴀ唀匀∀ 猀琀礀氀攀㴀∀∀㸀꤀ 䄀昀攀昀 䨀洀愀氀 䴀愀氀攀樀 ⴀ 刀攀䐀䌀䄀䐀 ⴀ 䰀愀猀琀 唀瀀搀愀琀攀搀㨀 䐀攀挀攀洀戀攀爀 ㈀　㄀㈀⸀㰀漀㨀瀀⼀㸀㰀⼀猀瀀愀渀㸀㰀⼀昀漀渀琀㸀㰀⼀瀀㸀 ਀ऀऀ㰀⼀搀椀瘀㸀 ਀ऀ㰀⼀琀搀㸀 ਀㰀⼀琀愀戀氀攀㸀 ਀㰀⼀栀琀洀氀㸀