JBoss JBPM 3.1 User Guide Translation Program --- First Chapter

xiaoxiao2021-04-08  418

Chapter 1. Introduction

First chapter introduction

JBoss jBPM is a flexible, extensible workflow management system. JBoss jBPM has an intuitive process language to express business processes graphically in terms of tasks, wait states for asynchronous communication, timers, automated actions, ... To bind these operations together, JBoss jBPM Has The Most Powerful And Extensible Control Flow Mechanism.

JBoss JBMP is a flexible, scalable workflow management system. JBoss JBMP has an intuitive process language that can describe the task of business processes, the waiting state, timer and automation action of asynchronous communication in a graphical manner. To Bind these operations, JBoss JBPM has the most powerful and scalable control flow mechanism.

JBoss jBPM has minimal dependencies and can be used as easy as using a java library. But it can also be used in environments where extreme throughput is crucial by deploying it on a J2EE clustered application server.

JBoss JBMP has the smallest dependence, which can be used as using a Java library. Moreover, it can also be used by deploying on an environments that are critical to external throughput on the J2EE cluster application server.

JBoss JBPM CAN Be configured with any Database and it can be deployed on any application server.

JBoss JBMP can configure any database or deploy on any application server.

Overview

1.1 overview

.

The core workflow and BPM feature are packaged into a simple Java library, including the storage service, update, and retrieve the process information in the JBPM database.

Figure 1.1. Overview of the jboss jbpm components

Figure 1.1 JBoss JBPM Component Overview

1.2. The JBoss JBPM Starter Kit

1.2 JBoss JBPM Launch Kit

The Starter Kit Is A Download That Contains All The JBPM Components Bundled in One Easy Download. The Download Includes:

· JBPM-Server, A Preconfigured Jboss Application Server.

· JBPM-Designer, The Eclipse Plugin for Authoring JBPM Processes Graphically.

· JBPM-DB, THE JBPM Database Compatibility Package (see Below).

· JBPM, The Core JBPM Component Including the libs and this userguide. · JBPM-BPEL, A Reference to the jboss jbpm bpel excesis.

Toolbs include all JBPM components:

· JBPM-Server, a pre-configured JBoss application server.

· JBPM-Designer creates the Eclipse plugin for the JBPM process in graphical way.

· JBPM-DB, JBPM database compatible package (see below).

· JBPM, JBPM core components, including libraries and this user guide.

· JBPM-BPEL, JBoss JBPM BPEL extension reference.

The Preconfigured Jboss Application Server Has The Following Components Installed:

· The core jbpm company, packaged as a service archive

......................

· The JBPM Console Web Application That Can Be Used by Process Participants As Well AS JBPM Administrators.

................ ..

· The JBPM Command Executor for the Asynchronous Executation of Commands. The Command Executor is Also Configured As a servlet. The servlet will spawn a thread to monitor and execute the commists.

ONE EXAMPLE Process IS Already Deployed INTO The JBPM Database.

Pre-configured JBoss application servers include the following installation components:

· JBPM core components: packaged as a service memory (Archive).

· An integrated database containing JBPM tables: The default super (HyperSonic) database includes JBPM tables and a process.

· JBPM console web application: can be used by process participants and managers.

· JBPM schedule program: Used for timer execution. The Schedule Program is configured as a servlet in the kit. This servlet will generate a thread to monitor and perform timers (Timers).

· JBPM command executor: used for asynchronous execution of commands. The command executor is also a servlet. This servlet will generate a thread to monitor and execute the command.

One Example Process IS Already Deployed INTO The JBPM Database.

A process example has been deployed in the JBPM database.

1.3. The Jboss JBPM Graphical Process Designer

1.3 JBoss JBPM Graphics Process Designer

JBoss JBPM Also Includes a Graphical Designer Tool. The Designer IS A Graphical Tool for Authoring Business Processes.

JBoss JBPM also includes a graphic design tool. This designer is a graphical tool for creating business processes .The JBoss JBPM Graphical Process Designer is an Eclipse Plugin. A Standalone Installation of the Designer Tool Is on The RoadMap.

The JBoss JBPM Graphics Process Designer is an Eclipse plugin. One independent installation of the designer is still planned.

The most important feature of the graphical designer tool is that it includes support for both the tasks of the business analyst as well as the technical developer. This enables a smooth transition from business process modelling to the practical implementation.

The most important feature of graphics design tools is that it supports business analysts and support technology developers. This feature makes it possible to develop smooth transition from business processes to actual implementation.

The plugin is available as a local update site (plain zip file) for installation via the standard eclipse software updates mechanism. And there is also a feature package that you can unzip in your eclipse home directory.

With the installation of the standard Eclipse software update mechanism, the plugin is available locally update site (simple zip file). (It seems that it is not right, huh) and there is an Feature package that can decompress the HOME path of Eclipse.

1.4. The JBoss JBPM CORE Component

1.4 JBoss JBPM core components

.............

JBoss JBPM Core Components is a simple Java (J2SE) software for managing process definitions and runtime environments for executing process instances.

JBoss jBPM is a java library. As a consequence, it can be used in any java environment like eg a webapplication, a swing application, an EJB, a webservice, ... The jBPM library can also be packaged and exposed as a stateless session EJB. This allows clustered deployment and scalability for extreme high throughput. The stateless session EJB will be written against the J2EE 1.3 specifications so that it is deployable on any application server.

JBoss JBPM is a Java library. So it can be applied in any Java environment, such as web applications, Swing applications, EJBs, and Web Service, etc. The JBPM library can also package and act as a stateless Session EJB. This allows cluster deployment and Scalable. This stateless session ejb is based on J2EE 1.3 specification, so you can deploy on any application server .The JBoss JBPM Core Component Is Package, AS A Simple Java Library Archive. Depending on the FunctionATIS That You Use, The Library JBPM-3.0 . Jar Has Some dependencies on Other Third Party Libraries Such As EG Hibernate, Dom4j and Others. Those dependencies area Clearly Document in Chapter 5, Deployment

JBoss JBPM core components are packaged as a simple Java library file. Given the features you use, library JBPM-3.0.jar depends on other third-party libraries such as Hibernate, Dom4j. These dependencies are described in detail in Chapter 5 "Deployment".

For its persistence, jBPM uses hibernate internally. Apart from traditional O / R mapping, hibernate also resolves the SQL dialect differences between the different databases, making jBPM portable across all current databases.

For persistence, Hibernate is used inside the JBPM. Unlike traditional O / R mappings, Hibernate also solves the difference in SQL dialects of different databases, so that JBPM can easily access all popular databases.

The JBoss jBPM API can be accessed from any custom java software in your project, like e.g. your web application, your EJB's, your web service components, your message driven beans or any other java component.

JBoss JBPM API can be accessed by any custom (Custom) Java software in your project, such as your web app, your EJB, your web service component, your message drives the bean or other Java components.

1.5. The JBoss JBPM Console Web Application

1.5 JBoss JBPM Console Web Application

The jBPM console web application serves two purposes. First, it serves as a central user interface for interacting with runtime tasks generated by the process executions. And secondly, it is an administration and monitoring console that allows to inspect and manipulate runtime instances.

The JBPM Console web application provides two services. First, as a central user interface for interaction with runtime tasks generated by the process executor. Second, act as an administrative and monitoring console, allowing an instance of the runtime.

1.6. The JBoss JBPM Identity Component

1.6 JBoss JBPM authentication components

JBoss jBPM can integrate with any company directory that contains users and other organisational information. But for projects where no organisational information component is readily available, JBoss jBPM includes this component. The model used in the identity component is richer then the traditional servlet-, ejb - And Portlet Models.Jboss JBPM can combine any company directory containing users and other organization information. Just for projects available for organizational information components, JBoss JBPM includes this component. The model used in identification components is very rich. For example, traditional servlets, ejb and portlet models.

For More Information, See Section 11.11, "The Identity Component"

See 11.11 "Identification Components" for more information.

1.7. The jboss jbpm scheduler

1.7 JBoss JBPM Schedule Procedure

The JBoss JBPM Scheduler Is A Component for Monitoring and Executing Timers That Are Scheduled During Process Executions.

The JBoss JBPM schedule is used to monitor and execute the timer, and the timer is scheduled during the process execution.

The timer component software is packaged in the core jbpm library, but it needs to be deployed in one of the following environments: either you have to configure the scheduler servlet to spawn the monitoring thread or you have to start up a separate JVM with the scheduler Main.

Timer component software is packaged in the core JBPM library, but it needs to be deployed in one of the following environments: You either configure the schedule (Schedule) servlet to generate monitoring threads, or start separate in schedule main program (Schedule main) JVM.

1.8. The JBoss JBPM Database Compatibility Package

1.8 JBoss JBPM Database Compatible Bag

The JBoss JBPM Database Compatibility Package Is A Download Package That Contains All The Information, Drivers and Scripts All The Information, Drivers and Scripts All the Information, Drivers and Scripts All the Information

The JBoss JBPM Database Compatible package is a download package, including all information, drivers, and scripts that make JBPM run on your selected database.

1.9. The JBoss JBPM BPEL EXTENSION

1.9 JBoss JBPM BPEL extension

The JBoss jBPM BPEL extension is a separatly packaged extension that extends jBPM with support for BPEL. The essence of BPEL is an xml scripting language for writing web services in terms of other web services.JBoss jBPM BPEL extension is a support for BPEL extends the JBPM, separate extensions. The essence of BPEL is a XML scripting language for writing Web Service.

转载请注明原文地址:https://www.9cbs.com/read-132809.html

New Post(0)