Using Pick as a Start Activity
使用Pick來做起始活動
Introduction
介紹
This sample demonstrates how to use a BPEL pick activity to start a process when the message exchange involves different incoming messages or multiple partner links.
這個例子演示當消息交換包含不同的輸入(incoming)消息或多個partner link的時候,如何使用一個BPEL的pick活動來開始一個流程。
In this example, two different types of messages are received over two different partner links. The process consists of the following:
在本例中，兩個不同的partner link接收到兩個不同數據的消息。流程包含：
- A pick activity with the "createInstance" attribute set to yes
- 一個“createInstance”屬性爲yes的pick活動。
- OnMessage handlers for each of the message types being processed
- 處理的每一個消息類型都有OnMessage handler
- The two types of messages that the process handles are a custom order message and a UBL order message. UBL is the Universal Business Language, a "generic XML interchange format for business documents that can be extended to meet the requirements of particular industries." UBL is published by the same organization that publishes the BPEL specification, OASIS.
- 流程控制的兩個類型的消息是一個自定義定單消息和一個UBL定義消息。UBL是指Universal Bussness Language，一個“可擴展符合具體行業的產生業務文件的XML交換格式。”UBL和BPEL一樣，都是由OASIS所發佈的。
- The first onMessage handler has an assign activity to create an acknowledgement response message corresponding to the received message. The response message includes data from the received message.
- 第一個OnMessage handler有一個assign活動建立一個與接收消息相對應的確認響應消息。這響應消息含有所接收消息的數據。
- Both onMessage handlers have a reply activity to send the response message back via the same partner link through which the received message arrived.
- 兩個onMessage handler都有一個reply活動，通過與所接收消息相同的partner link回傳迴應消息。
The following diagram represents the process. The onMessage handler on the left contains a sequence primary activity that contains the assign and reply activities. Note that onMessage handlers may directly contain only one activity. The onMessage handler on the right contains an implicit flow primary activity that contains the assign and reply activities. The flow activity is hidden (to save space) because ActiveBPEL Designer has added it automatically.
下面的圖表現了這個流程。在左邊的OnMessage handler包括一個Sequence的根活動，上面含有assign和reply活動。注意這個onMessage handler可以直接包含單一活動。右邊的onMessage handler包含一個implicit流程根活運，上面含assign和reply活動。流程活動是隱藏的（節省空間），因爲ActiveBPEL Designer會自動加上它。
Deploying the Process
分佈Process
Running the Process
運行Process
The OASIS-provided sample ublOrderMessage.xml does not comply with their schema. Therefore, you must disable validation before simulating the process in ActiveBPEL Designer or running it in the ActiveBPEL Server. This is done by un-checking the "Validate Input/Output messages against schema" option:
OASIS提供的例子—ublOrderMessage.xml並沒有遵循他們的schema。因此，你必須在ActiveBPEL Designer模擬或在ActiveBPEL Server運行前關閉校驗。可以反選項“Validate Input/Output message against schema”選項達到這目的:
- For ActiveBPEL Designer, visit "Window > Preferences > ActiveBPEL > Simulation".
- 在ActiveBPEL Designer，選擇 “Window> Proferences> ActiveBPEL> Simulation
- For the ActiveBPEL Server, visit the administration console's "Configuration" page.
- 在ActiveBPEL Server，訪問管理平臺(Administration console)中的“Configuration”頁面。
See Running the Samples. There are two separate services, one for the order process message and one for the UBL order message. For the order process message, use the service name orderProcessPLTService and the sample data file orderMessage.xml. For the UBL order message, use the service name ublOrderPLTService and the sample data file ublOrderMessage117.xml (not ublOrderMessage.xml)
參考Running the Samples。這裏有兩個獨立的服務，一個用於定單流程消息，另一個用於UBL定單消息。定單流程消息，使用名爲orderProcessPLTService和樣版數據orderMessage.xml。UBL定單消息，使用ublOrderPLTService和樣版數據文件ublOrderMessage117.xml(不是ublOrderMessage.xml)。
Copyright © 2004–2006 Active Endpoints, Inc. - All Rights Reserved