What does LS 3.0 need database for. Can it be used without?

Hi,

LS 3.0 (SitePub & RunTime) brings with it the new prerequisite of a Database. The docs are vague as to what is saved in the DB. It's annoying being dependent on the DB team and infrastructure, so I'm trying to check my options...

- So, what's saved in the DB?
- Can LS 3.0 be installed / used without a DB (with limited features available... - what would we lose)?

thx!

Find more posts tagged with

Comments

tec_iwov

The DB is used for OOTB user management and for Targeted content

niske

or to be a little more specific, it is used for OOTB runtime user management and pushing the taxonomy into production if you use targeted content.

It is not yet clear to me if you can install without it in case you don't use targetting.

Frederik

I've done an install today of SitePublisher 3.0 (a.k.a. LiveSite Development) without database, on Solaris. I did refresh my OD license to have DataDeploy Add-on module enabled before install.

During install, there's several mandatory prompts regarding the DB, for
- choice between MSSQL 2000, 2005 and Oracle (chose Oracle)
- folder where jdbc drivers are stored (answering blank was not allowed, I answered with a folder that did have some Oracle jdbc drivers... not sure if I could have answered with any random folder)
- database server name, listen port, database name, database admin user name and password for both the Development Database (I answered "unknown" to all of these) and Production Database (I answered "unknown2" to all of these).

I did *not* execute the post-install step to create db schema (./build.sh sql.execute)

Basic LiveSite operations seem ok.

I looked around, and found mention of the databases under OD-HOME/etc/livesite-database.xml which is used by datadeployment configs at OD-HOME/conf/LiveSite. From the first look at this, it seems that a few new LiveSite content types like blogs may also use the DB.

I'm still hoping to get this further specified...

shanon

All of the out of box DCTs use the database as does the Publish LiveSite Content workflow.

If you deploy any ootb DCT with this workflow, it will try and use the database. Also, it will try to create the database connections when the system starts up.

Please let us know what errors you get in the logs as I'd like to add this as an FR to flag the db enabled/disabled to support your configuration...

Thanks,
Shanon

Frederik

So far we've only installed SitePublisher, not the Runtime. So I don't think we'll use deployment WF soon. Also not quite sure I'll be doing much testing real soon. But if and when I find something relevant to the topic, I'll keep sharing