Although I have read the guide http://www.jivesoftware.org/builds/wildfire/docs/latest/documentation/db-integra tion-guide.html and tried to go over it with one of the daily builds the other week (which failed), I’‘ve tried it again with beta2 and frankly I’'m still having issues.
Wildfire, clean install, no conf. An existing db with use data exists.
Start fire, go into setup mode, select the a db, connection string, username and pass.
Profile selection - Only Default option is selectable… (why?)
my db gets populated with wildfire tables that I don’'t want in my db???
Is this the recommended integration path? I thought I’‘d only use my db just to read the user data nothing else, this seems invasive and doesn’'t feel like a good integration procedure.
I’‘d just like to be able to unzip wildfire, have an option in the setup profile selection to enter the jdbc auth provider settings and that’'s it.
If the server indeed needs more tables I’‘d feel more comfortable with that data outside my production database so I believe a hybrid aproach would be better where the wildfire server has it’'s own database for its own internal stuff and then allow the group/user providers to hook up to another existing db.
Is it just me that thinks the approach taken is brittle? Why should a production db have extra tables if jabber is secondary to the application’‘s real task? Wouldn’‘t the app’‘s be better off if they’'d be loosley coupled with wildfire?