nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

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

Find more posts tagged with

Comments

frauke

Ok,

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

<br>&nbsp;&nbsp;&nbsp; <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="databaseType" value="h2" /><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="dataSource" ref="dataSource" /><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="transactionManager" ref="transactionManager" /><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="databaseSchemaUpdate" value="false" /><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="historyLevel" value="1" />&nbsp; <br>&nbsp;&nbsp;&nbsp; </bean><br>

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)

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

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….

<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="databaseSchemaUpdate" value="false" /><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="jobExecutorActivate" value="true" /><br>

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

frederikherema1

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…

frauke

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