About jBPM7 database table structure understanding problem

[Ripin Yan]

Dear All,
    

    Recently in the process of learning jBPM7 database tables, for the default table structure is very confused, is there any jBPM table structure documentation?

    

    For example, the table deploymentstore  when the data will be stored, what effect and so on.

    

    And table nodeinstancelog Stored node flow data process, why is StartNode> Join> HumanTaskNode> Join> StartNode, instead of StartNode> Join> HumanTaskNode, the purpose of such records? What do the values 0 and 1 of the 'type' field in the table mean?

[Maciej Swiderski]

On 12 Nov 2017, at 05:39, Ripin Yan <yanshui...@gmail.com> wrote:

Dear All,
    

    Recently in the process of learning jBPM7 database tables, for the default table structure is very confused, is there any jBPM table structure documentation?

https://docs.jboss.org/jbpm/release/7.4.1.Final/jbpm-docs/html_single/#_jbpmpersistence

    

    For example, the table deploymentstore  when the data will be stored, what effect and so on.

deployment store is mainly used with deployment synchronizer that allows to “remember” and sync between cluster members. It is used usually in embedded scenarios as in kie server this is not required.

    

    And table nodeinstancelog Stored node flow data process, why is StartNode> Join> HumanTaskNode> Join> StartNode, instead of StartNode> Join> HumanTaskNode, the purpose of such records?

this is because the engine executes activities in stack manner and thus they are ordered as such

What do the values 0 and 1 of the 'type' field in the table mean?

o represents entry of the activity and 1 represents exit of the activity.

Maciej

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/eec52268-2baa-4621-87b1-2d2525d4da17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ripin Yan]

Hi Maciej, 

    Thanks a lot!

    According to your guidelines, I saw in the document 14 table field explanation (SessionInfo、ProcessInstanceInfo 、EventTypes 、WorkItemInfo 、CorrelationKeyInfo 、CorrelationPropertyInfo 、ContextMappingInfo、ProcessInstanceLog 、NodeInstanceLog 、VariableInstanceLog 、AuditTaskImpl 、BAMTaskSummary 、TaskVariableImpl 、TaskEvent ) , the understanding of the database table deepened a lot, and there are three questions to ask:

    1. Are there any corresponding documents in the field interpretation of other tables?

    2. What is the time unit of the duration field in the BAMTaskSummary table?

    3. How to archive (migration data) of table data in a database for a process that has ended for several months? If the archive field in the task table is updated to 1, what will the jBPM engine do with the data when the task ends?

    

在 2017年11月13日星期一 UTC+8下午3:33:09，Maciej Swiderski写道：