Manfred wrote: > Hi, > > I'm trying to combine Xwiki products into an intranet collaboration solution > and would appreciate advice on good practices for this. We're talking a > manufacturing organisation, about 500 users, divided into a dozen production > departments with users working on various departmental and organisation-wide > projects. > > I was thinking one could have Xwiki Enterprise operating as the portal > containing all the common enterprise info, then have Workspaces for > departmental document use and Chronopolys for Project management. I'd love to > have a single install product but that doesnt seem to be possible as I > understand it. I also don't forsee any more wikis than the above 3 being > required. > > Using the 'quick links' shortcut menu on XE I can add the URLs to the XWS and > Chronopolys spaces and provided one saves login details its pretty seamless > to transition between the products while working. > > At the moment I have the 3 Xwiki products running on separate virtual machine > servers i.e. separate IP's, Tomcat6 or Jetty app server, Java6 and Postgresql > databases. > > I'd like to know how much of this can be practically integrated. I realise I > can most likely combine everything into a single VM, running a single app > server with different URL paths and separate databases but ... > > more importantly how can I get more synergy with the 3 products working > together? > > Q's like: > > 1. Could all 3 products run on the same Xwiki database in Postgres or would > there be conflict with users, tables, etc. If not all 3 how about just XE and > XWS on the same database? Is this possible or am I looking for problems?
It's possible in theory to do all this in one wiki (but never has been done for chrono + XWS + XE, AFAIK), but I would advise you to do this setup on a XEM (http://manager.xwiki.org) basis, with one wiki per product. Since it's for a large organization, you will probably use the LDAP authenticator (http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication#HLDAPAuthentication) or something similar, so you won't have issues managing users accross wikis. The way XEM currently work is that it create one database per wiki, so you would have something like 4 databases (or more) on your postgres instance, for example: - "xwiki" => the main wiki, hosting the manager interface (to create, manage wikis, access rights, etc) - "enterprise" => A XE instance - "workspaces" => A XWS instance - "chronopolys" => a Chrono instance Of course you can choose your own names to match the business behind, like "portal", "documents", "projects" or whatever names you find suitable. Note that you can do inter-wiki links and you can share users between wikis, so it's not like the wikis are totally isolated one from another. > > 2. I'm not sure where the user uploaded wiki attachments are stored, if in > the db then ignore this Q, but if they are stored in the OS file system then > is it possible to have a common uploaded file space for all 3 platforms? Inside the database. Regards, Jerome. > > 3. Also, there seems to be some sort of integration possible with Alfresco > CMS stored files - is this for XE or could XWS/Chronopolys also access > Alfresco docs? > > Thanks > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
