topic Re: HistoryLevel in Activiti 5.4 in Alfresco Archive

HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 07:45:46 GMT

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" se

Re: HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 07:58:24 GMT

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

Re: HistoryLevel in Activiti 5.4

frederikherema1 — Mon, 11 Apr 2011 08:00:17 GMT

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>

Re: HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 09:19:41 GMT

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

Re: HistoryLevel in Activiti 5.4

frederikherema1 — Mon, 11 Apr 2011 09:49:54 GMT

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

Re: HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 09:54:28 GMT

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 :?

Re: HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 10:50:33 GMT

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

Re: HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 11:24:54 GMT

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?

Re: HistoryLevel in Activiti 5.4

frederikherema1 — Mon, 11 Apr 2011 11:40:33 GMT

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

Re: HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 11:53:26 GMT

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

Re: HistoryLevel in Activiti 5.4

frederikherema1 — Mon, 11 Apr 2011 13:14:05 GMT

Right… Forgot about that (it's my comment on the other topic, woops). That's why the java-steps in the upgrade-process are introduced. But other than that, the properties are completely unrelated.

The history-level is now stored in the DB, the first time the engine starts on a schema (or upgrades) to prevent changing the history-level and messing up engine assumptions done about history (eg. expecting certain entities to exist when level=full). I thought you were migrating from 5.3 to 5.4, which contains no java-steps, only SQL.

I guess, since you use liquibase, you will have to check all java-steps in the upgrade-process and do that stuff manually…

Re: HistoryLevel in Activiti 5.4

frauke — Mon, 11 Apr 2011 13:35:47 GMT

Well yes, it was your comment - I forgot to mention in my post
but still it was a very good one and helpful too.

We are thinking about calling the DbUpgradeStep classes from Liquibase using some kind of wrapper class, there is a possibility to do that.
I will try that and if it works, I will post it here. May be it will be interesting for other users too.

And by the way: I didn't really believe those properties where related directly in any way

Frauke