How could i avoid using content store?

Data Services
1

i’m updating an A12-project to the version 2023.06:
base = ‘27.0.0’
formEngine = ‘36.1.2’
kernel = ‘28.1.0’
uaa = ‘7.1.5’
dataservices = ‘36.0.1’
the project uses his own Database, and the Integration tests in the Project are using in memory database. the tests now are failing with an Error(see the attached log file):

i would like to know if it possible to get rid of new component “content store” in DS (in the project there is no use for attachments or thumbnails), or at least avoid processing or using when i run tests with in memory database.

logA12Test.txt (126.0 KB)

2

Hi,
could you please use our actuator endpoint (s.th. like http://localhost:8080/actuator) to inspect your current configuration (especially for content store) and add it to this post?

Also there is already a ticket that addresses this topic: A12-14918

Thanks, Hans.

3

Hi,
you may consider to share datasources of content store and data services (i.e. let content store use the same database as data services). Thus, only some (in your case unused) tables are added to the database.

Please be aware that this configuration setting is not tested thoroughly by Data Services.

4

Hello,

We allow to use same database for both DataServices and Content Store. To configure this you need to use configuration like this:

spring.datasources.dataservices.url=jdbc:h2:./databases/universal
spring.datasources.dataservices.username=sa
spring.datasources.dataservices.password=

Also content store should point to the same database:

spring.datasources.contentstore.url=jdbc:h2:./databases/universal
spring.datasources.contentstore.username=sa
spring.datasources.contentstore.password=
5

Hello @malek-linked-anchor .
Do you find the responses helpful or should the question remain open for more clarifications?

Thanks ahead for your feedback and have a nice rest of the day!

Katerina from the Discourse Team

6

i have solved the problem by no longer setting the name “persistence unit” explicitly for in memory-db. this might cause issues when tests run in parallel. Fortunately, we had no problems so far