BI4.0 and Derby database

[Former Member]

Hi expert

First of all: Happy new year!

I'm not sure to undertstand the role of the derby database trhough the differents tools in BI4 sp06

The monitoring is using Derby database by default!

Is the path of the DB looks like D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB\Derby ?

I read that it is possible to migrate the derby database to The Audit DB. But as i don't use monitoring i think there is no reason. I plan to monitore BI4 with a solution manger (Don't need BI4 monitoring)

What about Promotion management, Version management and visual difference? is that they use the same derby database or a other one. It is a little fuzzy for me.

What about this path: D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\LCM_repository\svn_repository

Is there any other tools who use Derby DB ?

I think i must extend my backup to derby database correct ?

Thank you for your help

Regards

Gil

[shiva_vishnubatla · Accepted solution]

Hello Gil,

The version management uses (subversion) svn repository for version management and it is an open version management system availble out there (not derby)

Promotion Management does use Apache derby database for overrides functionality. This is located in the <install>/data/lcm/lcmoverries location (or its equivalent) and configurable to different locations, but the derby usage is a limitation at the moment

As you already know, Monitoring uses derby by default - but is configurable and the db option can be changed.

There is an SAP Ideaplace request to "Remove Apache Derby from the SAP BI4 Platform" as applies to the application / configuration standpoing. Please sign up for that

Remove Apache Derby from the SAP BI4 Platform : View Idea

This thread already has several views and responses from SAP development.

Regards,

Shiva

[Former Member · Accepted solution]

Hi all

Thank you for your answers.

I understant much more now but i still have a question about what Shiva said.

SVN does use Derby DB ! (page 15: http://www.chiboug.org/CHIBOUG/NewsDoc/NewsDoc12462.pdf)

So there is 2 Derby database: One for Monitoring and one for LCM_using overrides ?  am i right ??

Regards

Gil

[Former Member · Accepted solution]

Yes, we have 2 Derby Database

1)LCM Connection Override settings are located in the LCM Derby Database.

The Derby Database is located in the location specified below.

Windows

<installation directory>\SAP BusinessObjects Enterprise XI 4.0\Data\LCM

Unix/Linux

<installation directory>/sap_bobj/enterprise_xi40/Data/LCM

2) Derby monitoring database, Which is used/configured in the monitoring application.

[former_member182521]

As others said Derby is a dedicated database for BI4 out-of-box monitoring capability which xml based rather than  relational.  Promotion/version management has their properietary  .ml based structure which is no where related to Derby database. I would still recommend you to use the BI4.x monitoring along with Solution manager integration. This is because of the fact that monitoring is capable of individual Businessobjects service/server metrics which you cannot get from solution manager. Metrics obtained from Solution manager would be on OS level such as CPU utilization, Individual process metrics and memory utilization. Hope this helps you. Regards Mani

[Former Member]

Hi Gil,

Derby DB is only utilized for the default monitoring database and no other functionality including auditing is using

this DB in BI 4. As you are leveraging Solution manager for monitoring I believe there is no need for this database in your scenario.

Check the Database release reference section in the link below..

[Former Member]

Only Monitoring uses Derby DB. If you want to switch to other DB which your company uses, you can do so.

Promotion Management/ Version Management/Visual Difference does not use any DB.

Version Management default comes with SVN. You can integrate the Version Management, if you have clearcase.

CMS and Audit DB- Default is either My SQL or Sysbase, depends on what version of the BO you are using.