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

Will IWOV fix the default event subsystem database or integrate MySql OOTB?

Frederik

Just curious if anyone knows whether Interwoven plans to fix the default event subsysten (flatfile) database... (which, if you lived on another planet, blows up in size in a matter of hours/days. Currently, one can either replace it with an RDBMS (add cost/time) or kill the event subsystem - not that they mention that in any doc, let alone pre-sales info (*) )

This poster suggests that he heard they'll integrate MySql out of the box. But that post is old by now, and 6.7 apparently hasn't fixed anything.
http://devnet.interwoven.com/forums_vb/showthread.php?t=13864&forumid=11&highlight=mysql+event+database

Any news?

(*) Just for fun, I looked it up in the 6.7 install manual... it's described as:
It is strongly recommended that you select a database instead
of default, so that event information can be stored and processed in a higher
performing and scalable manner making use of full database functionality. LOL :mad:

Find more posts tagged with

Comments

Valentine

I believe the only response was "Use a real RDBMS".
Even if IW ships mysql with TeamSite it is not any different from installing mysql yourself.

Migrateduser

I believe the only response was "Use a real RDBMS".
Even if IW ships mysql with TeamSite it is not any different from installing mysql yourself.

This is purely my opinion wrt mysql shipped with TeamSite install.

If IW ships mysql with TeamSite then any issues with the database support is part of the IW TeamSite support. If mysql is installed and configured separately then the only option is but the mysql support from 3rd party and not IW.

Adam Stoller

This is purely my opinion wrt mysql shipped with TeamSite install.

If IW ships mysql with TeamSite then any issues with the database support is part of the IW TeamSite support. If mysql is installed and configured separately then the only option is but the mysql support from 3rd party and not IW.

Are you saying this is why IWOV wouldn't include MySQL with TeamSite - because it's a 3rd-party product?
How does this fit with the logic of shipping:

get some support from IWOV, but will likely have to go somewhere else...

Frederik

I believe the only response was "Use a real RDBMS".
Even if IW ships mysql with TeamSite it is not any different from installing mysql yourself.

Well, it's different in the sense that

IWOV would actually deliver a system that has a change of being production-ready.
IWOV would be expected to support _their_ OOTB end-to-end solution, including the event subsystem (like they support the default db today - :cool: )
I wouldn't need to download, study, install, maintain, security-patch MySql myself. I wouldn't need to create an inhouse installation kit/script for it. (at my company, all installations should be scripted so they are easily reproduced without manual intervention - of course that's impossible with Teamsite itself as there is no support from unattended installation)
I wouldn't need to convince my management that they should allow me to install an "no-brand" (in their eyes - don't flame on this) open-source db

I'm sure there's more differences... /F.

RonaldV

I agree with Frederik.

When you pay the amount of money Iwov charges for Teamsite you should expect that either:

- a component like the Event Subsys works OOTB
- they clearly communicate that a DB is part of the system requirements (and thus warn you before hand in the release/upgrade-notes)

Neither is done.

Ronald

dtheimer

I was looking up some information on the Event Subsystem and came across this post and thought I would add a bit of detail.

The issue is with the HyperSonic database which has a java bug in it, causing the database flat file to 'explode' in size. If you want more detail you can look for a posting on this problem and for some potential short-term fixes.

As the manual indicates the "default" database is meant to be used only for demo purposes. I am not sure how many companies are installing TeamSite as a demo rather then as a application to solve an issue. So it might be best to add more robust open source database as a replacement for the HyperSonic DB or just require a Relational Database from the get go.

If you are using the "Default" database in production you should make plans to switch to a Relational Database - soon or later you will have an issue with a mega size file shutting down TeamSite and or the server, unless you are just demoing TeamSite for the fun of it...

Frederik

As the manual indicates the "default" database is meant to be used only for demo purposes.

I invite you to tell me where the manual says that... The only thing I found was the not very explicit "strong recommendation [... for] higher performing and scalable manner" note (quoted in my first post) buried somewhere in the install manual at step 20 of the installation. I nowhere found the word "demo" used to describe the default event subsystem db.