Differences between revisions 4 and 5
Revision 4 as of 2005-06-05 13:58:53
Size: 5095
Editor: PhilBurnside
Comment:
Revision 5 as of 2009-09-20 22:02:41
Size: 5095
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
To access the RDBMS store you will need an RDBMS configured, a database loaded with the correct schema (see ["MySQL41Schema.sql"]) and a suitable JDBC connector for the RDBMS. The example configuration given below is for a MySQL implementation. Other RDBMS support is available and I would recommend the SLIDE mail archive to get more details. To access the RDBMS store you will need an RDBMS configured, a database loaded with the correct schema (see [[MySQL41Schema.sql]]) and a suitable JDBC connector for the RDBMS. The example configuration given below is for a MySQL implementation. Other RDBMS support is available and I would recommend the SLIDE mail archive to get more details.
Line 18: Line 18:
The following configuration assumes you have a SLIDE respository already installed and running correctly. For more information on configuring SLIDE please see the ["Installation Guide"]. The following configuration assumes you have a SLIDE respository already installed and running correctly. For more information on configuring SLIDE please see the [[Installation Guide]].
Line 25: Line 25:
 1. Copy the web.xml from ["RDBMS Store Web.XML"] and replace the existing Web.xml file.
 1. Copy the code from ["RDBMS Domain.XML"] and replace the existing Domain.xml file.
 1. Copy the web.xml from [[RDBMS_Store_Web.XML]] and replace the existing Web.xml file.
 1. Copy the code from [[RDBMS_Domain.XML]] and replace the existing Domain.xml file.
Line 30: Line 30:
 1. Load the sql file ["MySQL41Schema.sql"]. This will create a database called "slide".  1. Load the sql file [[MySQL41Schema.sql]]. This will create a database called "slide".

Stores as RDBMS

In addition to storing the content within a file system you can configure SLIDE to use an RDBMS for content storage. To do this you will need access to an RDBMS and you will need to prepopulate a database instance with table definitions.

For more details please consult the following sites :

SLIDE RDBMS configurqation - http://jakarta.apache.org/slide/howto-j2eestore.html

SLIDE mail archives - http://www.mail-archive.com/slide-user@jakarta.apache.org/

Description

Within a SLIDE namespace you can define store's which use RDBMS to store the content. When storing content within these stores the files and all version information are kept within the database schema. This schema is pre-defined and a sample is included in the attached file.

Within the namespace you can define a combination of stores to utilise both the file system and different RDBMS databases. This is dependent on your architecture and the solution you are trying to implement.

To access the RDBMS store you will need an RDBMS configured, a database loaded with the correct schema (see MySQL41Schema.sql) and a suitable JDBC connector for the RDBMS. The example configuration given below is for a MySQL implementation. Other RDBMS support is available and I would recommend the SLIDE mail archive to get more details.

Configuration

The following configuration assumes you have a SLIDE respository already installed and running correctly. For more information on configuring SLIDE please see the Installation Guide.

This configuration guide is to run with MySQL 4.1. If you have a later version of the DBMS then please consult the SLIDE mail archive for more specific configuration details. For further information on configuring MySQL please consult the MySQL site - http://www.mysql.com/products/mysql/index.html

  1. Depending upon your Tomcat security you will need to register the following users and roles -
  2. If you have the Tomcat server running, then shut it down now.
  3. Take a copy of SLIDE web.xml and Domain.xml.
  4. Copy the web.xml from RDBMS_Store_Web.XML and replace the existing Web.xml file.

  5. Copy the code from RDBMS_Domain.XML and replace the existing Domain.xml file.

  6. You will need to find a copy of "mysql-connector-java-3.1.8-bin.jar" and copy it to the TOMCAT$/common/lib folder.
  7. If your MySQL database engine is not already loaded, start it now.
  8. Open an SQL session to the MySQL database.
  9. Load the sql file MySQL41Schema.sql. This will create a database called "slide".

  10. Copy the script and rename the database to "slide2".
  11. Launch your Tomcat server. If SLIDE is not automatically launched with the server, then enter the Tomcat manager and launch the servlet.
  12. Shutdown the Tomcat server.
  13. Delete the log files.
  14. Start the Tomcat server and the SLIDE servlet.
  15. Check the stdout Tomcat log. There should be no Java exceptions. If there are, then there is something wrong with the SLIDE installation. Please consult the SLIDE mail archives for further assistance.
  16. If the configuration has completed succesfully you can launch a WebDAV application (I suggest DAVExplorer) to access the repository.
  17. You can access the SLIDE respository with the following usernames "user1", "user2", "user3", "user4". Passwords are the same as usernames.
  18. Once in the SLIDE default repository you should see 4 folders - "data1", "data2", "rdbms1" and "rdbms2". Data 1 and 2 are file system stores, rdbms 1 and 2 are MySQL stores.

Your new SLIDE repository

If you have configured the SLIDE repository using the attached Domain.XML then you will have the following folder structure in place :

  • data1
  • data2
  • rdbms
  • rdbms2

RDBMS folder

User1 access

Can view all of the files in rdbms and it's sub folders. Has write access to rdbms and all sub folder except subfolderB. This has been explicitly denied.

User2 access

Is a member of the role "rdbms1" Can view all of the files in rdbms and its sub folders. Has write access to rdbms and all sub folders.

User3 access

Is a member of the role "rdbms1" Can view all of the files in rdbms and its sub folders. Has write access to rdbms and all sub folders.

User4 access

Can view all of the files in rdbms and its sub folders. Can only write to subfolderA. This has been explicitly granted.

RDBMS2 folder

User1 access

Can view all of the files in rdbms2 and it's sub folders. Has write access to rdbms and all sub folder except subfolderD. This has been explicitly denied.

User2 access

Is a member of the role "rdbms1" Can view all of the files in rdbms and its sub folders. Has write access to subfolderC. This has been granted explicitly.

User3 access

Is a member of the role "rdbms1" Can view all of the files in rdbms and its sub folders. Can not write to any folder.

User4 access

Can view all of the files in rdbms and its sub folders. Can not write to any folder.

RDBMS_StoresWithSamples (last edited 2009-09-20 22:02:41 by localhost)