Multiple Stores
Description
SLIDE allows multiple store's to be defined per namespace. In this way the stored files can be grouped and controlled according to logical containers.
Integrated within each store is the security model. It allows the SLIDE administrator to lock down the environment and to restrict areas of the namespace from different groups of users.
You must always define a default store within a namespace, otherwise the SLIDE servlet will be unable to correctly initiate a session.
The stores defined can be file server, RDBMS or LDAP repositories. You can also map multiple stores to the same file areas however issues with contention locking will cause problems on initiating the servlet and for the user.
To access the different stores you append the store name to the SLIDE servlet. For example,
To invoke the default store enter - "http://localhost:8080/slide"
To invoke the "Marketing" store enter - "http://localhost:8080/slide/marketing"
To invoke the "Technical" store enter - "http://localhost:8080/slide/technical"
Configuration
Wiki Markup |
---|
These instructions assume you already have a stable and working version of SLIDE running. For more details on how to configure SLIDE please refer to the \[Installation Guide\]. |
- Backup your Domain.xml, Web.xml (SLIDE implementation) files
- Replace the Web.xml file with this code - Multi_Store_Web.XML
- Replace the Domain.xml file with this code - Multi_Store_Domain.XML
- Register the following users in your Tomcat/SLIDE realm - user1 (role = admin), user2 (roles = data1, data2), user3 (roles = data1) and user4 (roles = data2)
- If you have Tomcat running shut it down.
- Start the Tomcat server.
- If SLIDE is not automatically started when you launch Tomcat, start the SLIDE servlet.
- Shutdown Tomcat.
- Start Tomcat and the SLIDE servlet. (You need to do this because of a problem with building the SLIDE repositories. It always needs a second start to finalise.)
- Check the Tomcat "stdout_*.log" and check that no Java errors have been thrown. (There should be none, but check none-the-less).
Wiki Markup Launch a DAV viewer (DAVExplorer is a good one - see \[Tips and Tricks\] for more details)
- Open the SLIDE repository with the following - http://localhost:8080/slide
- When prompted enter the username "user1" password "user1". This is the administrator for the respository. You should see two stores defined within the SLIDE root - "data1" and "data2".
Now you have established the namespace you can experiment with the repository. The following properties have been preset for each of the test users (user1 through 4)
In store "data1"
user1
- all rights
user2
- member of role "data1"
can write to "data1", "data1/accounts", "data1/accounts/balance"
no write to "data1/marketing", "data1/marketing/widgets", "data1/marketing/gadgets", "data1/accounts/p_and_l"
user3
- member of role "data1"
can write to "data1", "data1/accounts", "data1/accounts/balance", "data1/marketing/balance" (this is an explicit permission to user3
no write to "data1/marketing", "data1/marketing/widgets", "data1/accounts/p_and_l"
user4
- no write to any directory in data1
In store "data2"
user1
- all rights
user2
- member of role "data2"
can write to "data2", "data2/testing", "data2/testing/results"
no write to to all remaining folders.
user3
can write to "data2/development/graphics
no write to all remaining folders
user4
- member of role "data2"
as per user2.