網(wǎng)路冷眼@BlogJava

1.5.4 Implementing a simple book order process （實(shí)現(xiàn)一個(gè)簡單的訂書流程）（下）

Now point your browser to http://localhost:8080/activiti-explorer and login with the user kermit and the same password. When you click on the link "Unassigned tasks" you should a screen with one user task with the name of "Complete order" like the screenshot shown in figure 1.12.

現(xiàn)在，請將瀏覽器指向http://localhost:8080/activiti-explorer并以用戶名和密碼均為kermit的方式登錄。當(dāng)點(diǎn)擊鏈接“未分配任務(wù)（Unassigned tasks）是，你應(yīng)該看見如圖1.12所示的“完成訂單（Complete order）”的屏幕顯示。

Figure 1.12 A screenshot of the Activiti Explorer showing the user task of the simple book order process.

圖 1.12 顯示訂書流程用戶任務(wù)的Activiti Explorer的截屏。

For sake of completeness you can claim the user task and see that it becomes available in the "My tasks" page. There you can complete the tasks, which triggers the process instance to complete to the end state. We can now also take a quick look at the Activiti Probe application to look for this process instance in the Activiti process database table. So go to http://localhost:8080/activiti-probe and login again with the user kermit. Then go to "Database" and the "ACT_HI_PROC_INST" database table as shown in figure 1.13.

為了完整起見，您可以領(lǐng)取用戶任務(wù)，觀察“我的任務(wù)（My Task）”頁面是否可用。一旦您完成任務(wù)，這將觸發(fā)流程實(shí)例完成時(shí)結(jié)束狀態(tài)。現(xiàn)在我們可以快速瀏覽Activiti Probe應(yīng)用程序中，觀看Activiti流程數(shù)據(jù)庫表中的流程實(shí)例，所以導(dǎo)航至http://localhost:8080/activiti-probe所以，并以kermit再次登錄。然后切換至“數(shù)據(jù)庫（Database）”和“ACT_HI_PROC_INST”數(shù)據(jù)庫表如圖1.13所示。

Figure 1.13 A screenshot of the Activiti Probe application showing the process instance database table, which contains the completed simple book order process.

圖 1.13 Activiti Probe應(yīng)用的屏幕截屏顯示了流程實(shí)例數(shù)據(jù)庫表，它包括了已完成的訂書流程。

Activiti Probe provides us with a web view on the database tables of the Activiti engine. In the process instance table you can see information like the start and end time of the process and the name of the last activity.

Activiti Probe為我們提供了Activiti引擎數(shù)據(jù)庫表的Web視圖。在流程實(shí)例數(shù)據(jù)庫中，您可以觀察流程的起止時(shí)間，以及最后活動(dòng)的名稱。

This completes our first journey of the Activiti toolstack. In the coming chapters we’ll take a more detailed look at the Activiti toolstack and how to use the Java API of Activiti to for example create processes or retrieve management information. So hold on tight as we are about to expose you to more powerful functionality of BPMN 2.0 and Activiti.

這就完成了我們Activiti工具棧的首次旅程。后續(xù)章節(jié)將詳細(xì)介紹Activiti工具棧，如何使用Activiti Java API創(chuàng)建流程，或者檢索管理信息。所以，我們將再接再厲，繼續(xù)介紹BPMN 2.0和Activiti強(qiáng)大功能。

1.6 Summary （小結(jié)）

This chapter was really packed with information! We started with a gentle introduction into business process management and BPM vocabulary. We also saw a bit of history when we talked about WS-BPEL, BPMN 1.x and eventually BPMN 2.0. At that point it was time to take a closer look at the way you can do modeling with BPMN 2.0 and we looked at different categorization strategies of WfMC and Bruce Silver to make BPMN 2.0 understandable and usable for different users.

本章真的是擠滿了太多的信息！從簡介到到業(yè)務(wù)流程到BPM詞匯。我們也了解了一點(diǎn)WS-BPEL,BPMN 1.x和 BPMN 2.x的歷史。仔細(xì)觀察了BPMN 2.0的建模方法，也了解了WfMC和Bruce Silver的分類策略。這些策略讓BPMN 2.0針對不同用戶更可理解，更可用。

And finally we got acquainted with the Activiti tool stack and we were able to implement a  simple book order process using a script and user task. And what’s even more interesting,  we were able to start the Activiti process engine, deploy our book order process, start a process instance and do some unit testing on it with just a couple lines of Java code. It’s obvious that Actviti provides us with a powerful API and toolset. In the next chapter you will be introduced in more detail into the different parts of the Activiti tool stack.

最后，我們熟悉了Activiti工具棧。通過使用腳本任務(wù)和用戶任務(wù)，我們能夠?qū)崿F(xiàn)簡單的訂書流程。最有意義的是，我們能夠啟動(dòng)Activiti流程引擎，部署訂書流程，啟動(dòng)一個(gè)簡單的流程實(shí)例，通過數(shù)行代碼完成單元測試。顯然，Activiti給我們提供了強(qiáng)大的API和工具集。下一章，將介紹Activiti工具棧不同部件的詳細(xì)細(xì)節(jié)。