Hi Kieran, thanks so much for this feedback. I will update that help topic to make things more clear. Note that your web app node and AE node can share a database, or they can use their own databases. We spec that out in the Hardware Requirements. Let me know if you have any questions about this. Thanks again for the feedback.
Thanks to you too. The following reply post from Jive (Shailesh Samant) suggests that EAE requires its own database.
I thought that pointing both at the same database was the reason for some errors I am seeing. Have I misunderstood something?
Also, if you navigate to admin: System > Settings > Activity Engine and scroll to the bottom the text reads:
Use the form below to connect your Activity Engine server(s) to a database used as their underlying storage. This database should be a different database instance than the database instance you've configured for the Jive platform.
I can confirm that whilst you can get Jive 5 up and running by pointing both the web app and eae at one database, errors crop up as you begin to use the system.
Perhaps the Hardware Requirements part of the documentation should not suggest a choice between shared and separate databases.
Hope this is helpful
Kieran Kelly - I got some clarity from our developers around this. You can physically share the same database between the Activity Engine and the core web app, but they must use different DB schemas. Also, for larger/heavy traffic communities, we strongly recommend using separate databases to account for the higher traffic loads and whatnot (spec'ed out reasonably well in our Deployment Sizing and Capacity Planning help topic). I will try to make this very clear in our docs moving forward. Thanks again for bringing this to our attention.