Java workflow engine - mode code integration middleware

Keywords: workflow platform for rapid development of workflow business process management workflow design asp.net open source workflow bpm workflow system java workflow framework mainstream custom workflow engine Form Designer Process Designer

Front-end code integration steps:

  1. Ride integrated into BPM code, the code integrated with the rear end of the front end code integration.
  2. There are two front-end code directory is / DataUser / WF. Integrated front-end code is the need for these two directories into your development framework to go inside, to complete the integration of front-end code.
  3. DataUser data file can be modified, the file directory structure of these two please refer to the above described section.

The code-integration steps:

  1. For java version, we need to core code D: \ JFlow \ jflow-core \ src \ main \ java \ BP to put your schema in on it.
  2. For the .net version, you need to put into the three libraries in your solution BP.En30, BP.WF, BP.GPM three libraries, references to third-party dll, go to D: \ ccflow \ RefDLL go.

The advantages of this mode of call:

  1. Your team development framework code ccbpm code seamless integration to complete the API call ccbpm without resorting to micro and services, webservices interface to complete.
  2. After the code is actually two integrated framework for a run in the same app.
  3. You need to change your login method, after you verify the password for the user name, directly call ccbpm login API (BP.WF.Devinterfase.Port_Login (string userNo) static method) can be completed by value session session.
  4. After two frames login, you can directly call the ccbpm initiated, pending, in transit and other pages, you can directly call ccbpm the API to complete the operation.

Guess you like

Origin www.cnblogs.com/mengjuan/p/11996832.html