Storing Strategies in DB

[Vic]

Hi,

I was wondering if someone could explain to me the reason for having DAP to store strategies into DB.

This is really confusing: IRD would be storing strategies directly into DB via DBServer but it still sends requests for loading and unloading scripts directly through config server?

From what I have seen, the compiled version of the strategy is stored under "scripts" folder in CME which means URS compiles the strategy and sends it to config server, which in turn saves the data into config db. It then proceeds to add ANNEX of every loaded RP via config server asll well. So, why in the world strategy needs to be stored DIRECTLY in DB if the rest is done through config server anyway?

[ecki]

Hi Vic,

The answer is simple, because you wont need anymore to have rbn stored on local or shared drive if you need edit strategy. IRD stores it in cfg DB via DAP. But prior to have this feature you have to run sql script to create special table for this purpose.

rgds..

[Vic]

Hi, Ecki,

thanks

But, I was wondering why IRD would not be able to store the strategies through the config server, since config server has access to the same DB! Having a DAP just for strategies makes the whole architecture absurd. The only reason why you would want to have a DAP is if you wanted to store strategies in a different DB from CME... And I doubt that many of us would want that.

Genesys: if you are reading this take note

[ecki]

Sorry Vic


Probably because this is not the main functionality of configserver. Configserver suppose to keep all cfg data in RAM and not supply db server functionality. However cfg would again use dbserver to store it to database, so why to bother cfgserver with this and have 3 applications involved in storing process?

[Vic]

Point well taken. Thanks, ecki! (As always)

[ecki]

No worries, ur welcome