HistoryLevel in Activiti 5.4

[frauke]

Hello everyone,

I got the problem "no historyLevel property specified" on starting the web server (Tomcat).
So I changed the spring  setting of processEngineConfiguration so it defines the historyLevel.
But now it expects an Integer instead of a String.

My question now is:
How does the "historyLevel" settings are related (if they indeed are!?) to the former "history" settings which had the values "audit", "full" etc.
What value do I have to set if formerly I used history="full"?

Frauke

[frauke]

Ok,

I can't get it working anyway.
This is my process engine Spring configuration:

    <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
        <property name="databaseType" value="h2" />
        <property name="dataSource" ref="dataSource" />
        <property name="transactionManager" ref="transactionManager" />
        <property name="databaseSchemaUpdate" value="false" />
        <property name="historyLevel" value="1" /> 
    </bean>
Is there anybody who can help me?
I am stuck.

Frauke

[frederikherema1]

Try this (from /activiti-engine/src/test/resources/org/activiti/standalone/history/fullhistory.activiti.cfg.xml)


<bean id="processEngineConfiguration" class="org.activiti.engine.impl.cfg.StandaloneInMemProcessEngineConfiguration">
 
    <!– Database configurations –>
    <property name="history" value="full" />
    <property name="databaseSchemaUpdate" value="true" />
   
    <!– job executor configurations –>
    <property name="jobExecutorActivate" value="false" />
   
  </bean>


[frauke]

Ok, this works, but I do not quite unterstand what the databaseSchemaUpdate and the jobExecutorActivate have to do with the history setting? Can you explain it to me?

Actually we had set these settings on purpose (see below) because we do the database schema update with Liquibase.
So we are not so happy with this solution….

        <property name="databaseSchemaUpdate" value="false" />
        <property name="jobExecutorActivate" value="true" />
Frauke

[frederikherema1]

Nothing, I just pasted an extract from the config-file, which contained the history setting. Sorry for the confusion

[frauke]

That confuses me completely now because it only works with your settings above.
And not, if I change one of them.

You see me quite puzzled  :?

[frauke]

Could it be that there is an coincidental relation between the historyLevel and the database setting?
<property name="databaseSchemaUpdate" value="true" />Something that I have not taken into account in my Liquibase update script?

Could you please check for me if the schema update writes something into the database that is related to the history level?
Actually it could also have been in the update from version 5.2 to 5.3 since we skipped the latter.

Thanks
Frauke

[frauke]

OK, I found something:

See topic
Activiti SQL for upgrading from 5.2 to 5.3…

http://forums.activiti.org/en/viewtopic.php?f=6&t=1246&start=0&hilit=HistoryLevel

Is that the answer?

[frederikherema1]

AFAIK, the update-strategy and jobexecuter does NOT infuence the history

[frauke]

The schema update obviously has something to do with the history level.
See
http://forums.activiti.org/en/viewtopic.php?f=6&t=1246&start=0&hilit=HistoryLevel
That's what I meant.

Frauke