扩展迁移逻辑

The migration logic is written in such a way, that it is easy to extend to suit your needs. The source code is available as a Maven 2 project in the srcsubfolder of the downloaded zip file. To build a new zip file, after having changed or extended the logic, simply execute a

迁移逻辑可以编写，以便轻松地满足你的需求。源代码在所下载zip文件里src子文件夹里作一个Maven 2项目来使用。为了构建一个新的zip文件，在已经改变或者扩展逻辑之后，简单执行下面指令

to produce a new zip file in the target folder.

在target文件下产生一个新的zip文件。

Following picture gives a high-level overview of the classes in the migration logic.

下图提供了在迁移逻辑里类的高层次概貌。

• Both the ProcessConversion and ProcessDataMigration classes have a main method that directly is called from the ant build script in the root of the migration zip.
• ProcessConversion and ProcessDataMigration 这两个类都有在迁移zip的根目录下的ant构建脚本里调用的main方法。
• These classes construct a ServiceFactory based on the two properties files, using a static factory method
• 通过使用静态的工厂方法，基于两个properties文件这些类构建一个ServiceFactory

ServiceFactory.configureFromProperties(jbpmDbProperties, activitiDbProperties);

• The services are constructed by the ServiceFactory (eg. getProcessConversionService()) and are used to execute the migration logic:
• 通过ServiceFactory (eg. getProcessConversionService())构建这些服务，这些服务被用来执行迁移逻辑：

 1 public void execute() throws IOException {

 2     

 3   // convert processes

 4   ServiceFactory serviceFactory = createServiceFactory();

 5   ProcessConversionService processConversionService = serviceFactory.getProcessConversionService();

 6   Map<String, Document> migratedProcesses = processConversionService.convertAllProcessDefinitions();

 7   

 8   // write results to bpmn20.xml files

 9   writeConvertedProcesses(migratedProcesses, workingDir);

10     

11   // Deploy processes to Activiti

12   ActivitiService activitiService = serviceFactory.getActivitiService();

13   activitiService.deployConvertedProcesses(migratedProcesses);

14     

15   // data migration

16   

17 }

• The ProcessConversionService is an interface that contains process conversion and process definition data retrievel operations. It uses an implementation of Jbpm3Dao. The default implementation of this class uses a Hibernate SessionFactory to retrieve all the data from jBPM 3 tables.

The ActivitiService offers operation needed to get the migrated data in the Activiti tables. For example, deploying the converted process definitions is such an operation

ProcessConversionService 是一个包含流程转换和数据检索的流程定义借口。它使用了 Jbpm3Dao.的实现。这个类的缺省实现使用了Hibernate的SessionFactory从jBPM 3的数据库表里检索所有的数据。

ActivitiService 提供需要从Activiti数据库表迁移数据的操作。例如，部署转换之后的流程定义就是如此的操作。

• All these dependencies, ProcessConversionService, Jbpm3Dao, Sessionfactory, ActivitiService and ProcessEngine, are interfaces and can be implemented by your own implementation. You can inject them into the ServiceFactory using regular JavaBean setters. When no such custom implementation is set, the ServiceFactory will fall back to creating the default implementation:
• 所有这些依赖， ProcessConversionService, Jbpm3Dao, Sessionfactory, ActivitiService 和 ProcessEngine都是接口，并能由你自己实现。采用正常的JavaBean设置器，能将它们注入到ServiceFactory。当没有设置这些实现，ServiceFactory将后退一步，建立缺省的实现：

    1 public ProcessConversionService getProcessConversionService() {
 2   if (processConversionService == null) {

 3     this.processConversionService = createDefaultProcessConversionService();

 4   } 

 5   return processConversionService;

 6 }

 7 

 8 protected ProcessConversionService createDefaultProcessConversionService() {

 9   ProcessConversionServiceImpl service = new ProcessConversionServiceImpl(getJbpm3Dao());

10   return service;

11 }
            

Table of Contents

目录表

Database migration

数据迁移

Process conversion

流程转换

Extend the migration logic

扩展迁移逻辑

The jBPM migration is considered [EXPERIMENTAL].

jBPM迁移仅作[EXPERIMENTAL]之用。

It is possible to migrate an existing installation of jBPM version 3 to Activiti. The migration includes both process definition conversion (ie. from JPDL 3 to BPMN 2.0) and data migration.

将一个已安装的jBPM 版本3迁移到Activiti是有可能的。迁移包括流程定义转换（例如从JPDL3到BPMN 2.0）和数据迁移。

The migration tool is currently offered as a 'preview' only! The migration coverage is at this point in time not sufficient to be usable on production process definitions and databases. Also note that the migration is a 'best effort', which means that you may need to extend the migration logic to cover all your use cases.

迁移工具目前只作为‘预览’之用！当前迁移不能覆盖到产品的流程定义和数据。也要注意迁移是‘最大的努力’，这意味着你可以需要‘扩展迁移逻辑’来控制你所有的用例。

The migration tool is separately availbale as a zip file from the activiti.org download site. Once you have unzipped this file, you will see following files and folders:

迁移工具从activiti.org下载站点以zip文件方式分开下载。一旦加压这个文件，文件和文件夹如下所示：

• build.xml: This ant buildfile contains the targets to execute the process definition conversion and database migration.
• build.xml: 这个ant构建文件包含了执行流程定义转换和数据库迁移的目标。
• activiti.db.properties and jbpm3.db.properties: these properties files contain the database connection parameters for the jBPM 3 and Activiti database. These properties files must be changed when executing a database migration.
• activiti.db.properties and jbpm3.db.properties:这个特性文件包含了jBPM和Activiti数据库的数据库连接参数。当执行数据库迁移时，必须改变这些特性文件。
• processes: when running a process definition conversion, the jBPM 3 process definition files must be placed in this folder.
• processes:当运行流程定义转换时，jBPM3流程定义文件必须放置到这个文件夹。
• src: this folder contains the source code of the migration tool. Read the extension section if you want to tailor or extend the migration code to your needs.
• src:这个文件包含迁移工具的源代码。如果希望裁剪或者扩展迁移代码满足你自己的需求，请阅读扩展部分。
• lib: this folder contains all jars required to execute the migration logic.
• lib:这个文件夹包含执行迁移逻辑的全部jar包。

Database migration

数据库迁移

It is possible to migrate the data in the jBPM 3 database tables to the Activiti database schema. To do this, following properties files must be changed to point at the right database:

将jBPM3数据库表迁移到Activiti数据库schema是有可能的。为了完成这个任务，必须改变下面的properties文件，指向正确的数据库：

• jbpm3.db.properties: contains the parameters to connect to the jBPM 3 database. Also the Hibernate dialect must be provided.
• jbpm3.db.properties:包含了连接jBPM3数据库的参数。也必须提供Hibernate方言。
• activiti.db.properties: contains the parameters to connect to database to which the migrated data will be written. This can be the same database schema as the jBPM schema (ie. there are no name-clashes between jBPM and Activiti tables, indexes, foreign keyes, etc).
• activiti.db.properties: 包含了迁移将要写入数据库的连接参数。这个可能是和jBPM相同数据库schema（例如，在jBPM和Activiti数据库表名，索引名，外键名等等没有冲突）.

The database migration will use the data in the jBPM 3 tables to:

数据迁移将使用jBPM3数据库表的数据来做：

• Convert the process definition to the BPMN 2.0 counterpart. This means that the converted process definition will be deployed to the Activiti tables as part of the migration. As a side-effect, it will also produce the BPMN 2.0 XML files, similar to what happens when executing theprocess conversion.
• 转换流程定义为BPMN 2.0对应物。这意味着转换之后的流程定义将作为迁移的一部分被部署到Activiti的数据库表。作为副作用，它也产生BPMN 2.0 XML文件，这和当执行流程转换时所发生的事相似。
• Migrate runtime and history data of the processes to the Activiti tables. In this release, this is not yet implemented!
• 迁移流程的运行时和历史数据到Activiti数据库表。本次发布，这没有实现！

The data is retrieved from the jBPM 3 tables using Hibernate queries and the Hibernate mappings of jBPM itself.

使用Hibernate查询和jBPM自身的Hibernate映

射，可以从jBPM 3数据库表里检索到这些数据。

Process conversion

流程转换

It is possible to only convert the process definitions xml from JPDL to BPMN 2.0 that can be executed on the Activiti engine. To do this, place the jBPM 3 processes inside the processes folder. There can be any number of (nested) subfolders, the tool will scan every (sub)folder inside processes to discover processdefinition.xml files (file name must be processdefinition.xml!).

只将JPDL的流程定义xml转换为能在Activiti引擎执行的BPMN 2.0是有可能的。为了完成这个任务，请将jBPM 3放置到process 文件夹。可以有任何数量（内置）子文件夹，工具将扫描process每个（子）文件夹，来发现processdefinition.xml文件（文件名必须是processfinition.xml!）。

The discovered processes will be parsed and deployed to an in-memory databse, such that the logic of reverse engineering the process definition from the jBPM deployment tables contained in the database migration is used for both cases.

被发现的流程将被解析并部署到一个内存数据库，以便对包含在数据库迁移的jBPM部署数据库表的流程定义进行反向工程，以为解析和部署之用。

Once the jBPM 3 processes are placed in the processes folder, execute the convert.processes target in the root of the unzipped migration tool folder:

一旦jBPM 3流程被放置到process文件夹，那么执行在解压之后的迁移工具文件夹根目录下的convert.processes目标。

ant convert.processes

During conversion, you will see plenty logging passing by describing where and how the process conversion is being executed. At the end of the conversion, you will see following logging appear:

在转换过程中，通过描述流程转换执行是何地和何时转换的方式，可以观察到大量的日志。在转换的末尾，将观察到下列日志出现：

As shown in the logging, the resulting BPMN 2.0 processes can be find in the converted-process-xxxx folder, where the xxxx is the timestamp of the conversion.

正如日志所示，BPMN 2.0流程的结果可以在converted-process-xxxx文件夹里找到，这里xxxx是转换的时间戳。

In this release, only limited support for start, end, wait state and task-nodes is implemented. In the future, this coverage will expand.

在本次发布里，只实现了对开始，结束，等待和任务节点的有限支持。在将来，这个覆盖范围将要扩充。

Grails is a dynamic web application framework built on Java and Groovy, leveraging best of breed APIs from the Java EE sphere including Spring, Hibernate and SiteMesh. Grails brings to Java and Groovy developers the joys of convention-based rapid development while allowing them to leverage their existing knowledge and capitalize on the proven and performant APIs Java developers have been using for years.

• Changelog: See JIRA
• Download: http://grails.org/Download .
• Documentation: http://grails.org/doc/1.3.x

New Features & Improvements

Updated Groovy

Grails 1.3.7 now bundles Groovy 1.7.8.

Masking Request Parameters From Stacktrace Logs

When Grails logs a stacktrace, the log message may include the names and values of all of the request parameters for the current request. To mask out the values of secure request parameters, specify the parameter names in the grails.exceptionresolver.params.excludeconfig property:

grails.exceptionresolver.params.exclude = ['password', 'creditCard']

Request parameter logging may be turned off altogether by setting thegrails.exceptionresolver.logRequestParameters config property to false . The default value is true when the application is running in DEVELOPMENT mode and false for all other modes.

grails.exceptionresolver.logRequestParameters = false

Table of Contents

Overview（概述）

Changing the database（变更数据库）

Overview（概述）

Activiti KickStart is a webbased tool to quickly create 'adhoc' business processes using a subset of constructs available to the Activiti engine. KickStart provides a simple UI that doesn't require to learn BPMN or any modeling environment, as it works with concepts that are familiar to every business user. However, the processes that are created using KickStart, are fully BPMN 2.0 compliant and can be used as a starting point for more complex BPM endeavours.

Activiti KickStart的是一个基于Web的工具，用Activiti引擎可用的构件（constructs）的子集提供给快速创建“即席（adhoc）”的业务流程。Kickstart提供了不必学习BPMN或者任何建模环境的简单UI，因为它树立了每个业务用户都熟悉的概念。但是，通过KickStart创建的的流程，是和BPMN 2.0兼容，并可作为更为复杂BPM努力的起点。

KickStart integrates perfectly with the Activiti engine. As such, processes created with KickStart are immediataly usable in Activiti Explorer and are visible in Probe.

KickStart能和Activiti引擎完美集成。因此，采用KickStart创建的流程在Activiti Explorer立即可用，并在Probe里面可见。

KickStart serves many business cases, but the following three are probably the most common:

KickStart服务许多商业案例，但以下三个可能是最常见：

• Simple business processes: some processes are just simple by nature, and every company has them. Think about an expense process, a holiday leave process, a hiring process, etc... These kind of processes are probably already being done using paper or e-mail. KickStart allows to model these processes quickly and change them whenever it is needed. As such, KickStart really lowers the threshold to automate these business processes.
• 简单的业务流程：一些流程天然简单，并且每个公司都有。考虑到付费流程，请假流程，雇佣流程，等等…这些流程用书面或者e-mail的方式已经完成。Kickstart运行快速对这些流程建模，每当需要时改变它们。因此，Kickstart真正地降低了门槛，并让这些业务流程自动化。
• Prototyping: before diving into complex BPMN 2.0 modeling and thinking about the corner cases of the process, it is often wise to get all people involved aligned and work out a prototype that shows the vision of what needs to be done. KickStart allows to do exatcly that: create a business process prototype on the fly, to get your ideas visible for everyone.
• 原型：在钻研复杂的BPMN 2.0建模和考虑流程的偏例之前，它往往是明智的，让所有参与的人平等，制定一个原型来展示所要完成的愿景。KickStart的允许恰恰如此：创建一个业务流程的原型，让大家看到你的想法。
• Adhoc work: in some cases, coordination is required between different people or groups in a company. You know how it normally goes: sending an email here, doing a telephone there ... which often ends up in a tar pit of nobody knowing what or when something needs to be done. However, a business process management platform such as Activiti is an excellent way of distributing and follow-up everything, as it is intended to track exactly such things. KickStart allows you to create processes for adhoc work in a matter of minutes, and distribute and coordinate tasks between people easily.
• 即席工作：在一些情况，在一个公司里，不同的人员或组之间的协作是必要的。您知道正常时如何运作的：在这里发送邮件，在那里打电话…这经常终止于没有人知道需要完成什么或者何时完成这样的焦油坑。但是，诸如Activiti这样的业务流程管理平台是解决分发和后续事情的卓越解决之道，因为它的目的是准确跟踪这些事情。Kickstart允许您在数分钟之内创建即席工作的流程，并在人们之间分发和协调任务。

Following screenshots show the capabilities of Activiti KickStart. Take for example the next picture. It shows how an expense process is created in a matter of a few minutes.

下列屏幕截图展示了Activiti KickStart的能力。下图作为示例。它展示如何在几分钟之内创建一个付费流程。

After clicking the save button, the process is immediately usable in Activiti Explorer:

在点击“保存”按钮之后，这个流程立即在Activiti Explorer可用。

KickStart also allows to define forms for every task:

KickStart也允许为每个任务定义表单：

Which are obviously directly usable in Activiti Explorer:

这些明显直接在Activiti Explorer可用：

At any time during process creation, it is possible to view the corresponding BPMN 2.0 diagram of the business process:

在流程建立的任意时间，它可以查看相应的BPMN2.0业务流程图。

Whenever it is required, the processes defined with KickStart can be opened up and modified:

每当它是必需，与KickStart的定义的流程可被打开和修改：

Processes created with KickStart are fully compliant with the BPMN 2.0 XML, which means that the process can be imported into any BPMN 2.0 editor:

用KickStart的创建的流程是完全符合BPMN2.0的XML，这意味着该流程可以由任何兼容的BPMN2.0编辑器输入：

Changing the database（变更数据库）

Activiti KickStart is currently not yet using the REST API, but uses the service API by including the Activiti engine as a library. While Explorer, Probe and Cycle use the same mechanism for changing the database (see here), the same does not yet apply for KickStart.

Activiti KickStart当前还没有使用REST API，而是通过包括了Activiti引擎作为类库使用服务API。虽然Explorer，Probe和Cycle使用相同的机制改变数据（参见这里），但这不适于KickStart。

To change the database that KickStart uses in the demo setup, generate a new activiti.cfg.jar, and place it in the apps/apache-tomcat-6.x/webapps/activiti-kickstart/WEB-INF/lib folder.

为了改变演示安装里KickStart使用的数据库，产生一个新的activiti.cfg.jar,并将它放置到apps/apache-tomcat-6.x/webapps/activiti-kickstart/WEB-INF/lib文件夹。