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; } } }

informations on the runtime (production) database

elenav

Hello,

we are migrating from Teamsite version 6.7 to version 7.3.

I have a question about livesite database used by the production runtime.

During the installation of the runtime environment on weblogic, we have to
add the information for connecting to the runtime (production) database
in the file database.properties.

I would like to know what kind of information does the runtime need from the database, because in the previous version I remember for example that in the IW_CONT_SITE table there must be the name of the sites deployed on the runtime, otherwise we couldn't see the .pages on the runtime. Now it is not anymore true, because I see pages also when the site is not deployed on the database.

Can anyone give me more informations?

And if we put the db.enabled=false what kind of functionality do we loose on the runtime?

Thanks in advance,
Elena

Find more posts tagged with

Comments

Faizi

By default runtime configured db.enabled=true, because OOTB ORM mapping files require database connection for segmentation/taxonomy/blog/content etc.

If you are not using any OOTB components then i don't think you need db.enabled=true, based on this flag runtime server load db connection at time of initialization.

You can see all the OOTB hbm mapping file in runtime's conf/livesite/orm location.

cecilb63

The runtime tables are still used for quite a bit of LSDS functionality.

You should be able to see the table DDL here: TeamSite\local\config\lib\content_center\livesite_customer_src\db

I think the most important tables are iw_asset, iw_site, iw_content, iwtax_node, and iwtax_node_type.

There are other table for optimization, login components (address, user), and other OOTB components

If it was me I'd want to be sure all tables are there and accessible so I can fully test all OOTB components and sites so I know the product is working correctly.

Faizi

The runtime tables are still used for quite a bit of LSDS functionality.

You should be able to see the table DDL here: TeamSite\local\config\lib\content_center\livesite_customer_src\db

I think the most important tables are iw_asset, iw_site, iw_content, iwtax_node, and iwtax_node_type.

There are other table for optimization, login components (address, user), and other OOTB components

If it was me I'd want to be sure all tables are there and accessible so I can fully test all OOTB components and sites so I know the product is working correctly.

You are correct if you are using OOTB component then obvious you should keep db.enabled=true.
But if you are not using OOTB db connection in anywhere then you can keep it false. There is no harm of this. That will boost your runtime performance.