http://restsql.org

Deployment

Structure and Distributions

restSQL source code is contained in three eclipse projects:
  1. restsql - service and core framework
  2. restsql-sdk - documentation, HTTP API explorer, javadoc, examples
  3. restsql-test - test framework, test cases
restSQL binary distributions contain three libraries:
  1. restsql-{version}.jar - core framework only
  2. restsql-{version}.war - service and core framework, 3rd party dependencies
  3. restsql-sdk-{version}.war - SDK
restSQL source distributions consist of one jar:
  1. restsql-{version}-src.jar - service and core framework

Deployment Modes

restSQL may be deployed in two modes:
  1. WAR - web application
    Clients use an HTTP service (web app) directly
  2. JAR - java library
    Clients use your service which uses the restSQL Java API

Configuring restSQL

restSQL requires two configuration files in both WAR and JAR modes:
  1. restsql.properties - general framework settings
  2. log4j.properties - logging settings
The files may be called anything you wish; these are only the suggested names. Two other properties files are optional: privileges (authorization) and trigger definitions. These are referenced in the main restsql.properties file

The general restsql.properties is set through a System Property, "org.restsql.properties". The value is an absolute path to your properties file, e.g. /etc/opt/business/restsql/restsql.properties. The WAR mode should use a context-param in the web.xml to set this (See Installation section later for details). The JAR mode will default to default-restsql.properties (source location: restsql/src/resources/properties) that is included in the jar.

The general restsql.properties contains the following configurations:

  1. Logging - required
  2. SQL Resource definition location - required
  3. Security - optional
  4. Triggers - optional
  5. XML - optional
  6. HTTP - optional
  7. Database - required
  8. Implementation classes - optional

Logging configuration example:

   # logging.facility=[log4j,java]
   # logging.config=relative/to/classpath
   # logging.dir=/absolute/path  - this is only used by the /log service method to find logs
   logging.facility=log4j
   logging.config=com/business/config/log4j.properties
   logging.dir=/var/log/restsql
Note that unlike all other locations, the logging.config location is RELATIVE to the classpath, not absolute. The default logging framework is log4j, using the default-log4j.properties included in the jar/war. This logs to the location /var/log/restsql. The logging levels are set for development, not production mode.

The location of SQL Resource definitions is critical. An example:

   # sqlresources.dir=/absolute/path
   sqlresources.dir=/etc/opt/business/restsql/sqlresources

The Security configuration is optional. Here is an example:

   # security.privileges=/absolute/path
   security.privileges=/etc/opt/business/restsql/privileges.properties

The Triggers configuration is optional. Here is an example:

   # triggers.classpath=/absolute/path
   # triggers.definition=/absolute/path
   triggers.classpath=/etc/opt/business/restsql/triggers
   triggers.definition=/etc/opt/business/restsql/triggers.properties

The XML configuration is optional. The defaults are:

   # request.useXmlSchema=[true, false]
   # response.useXmlDirective=[true, false]
   # response.useXmlSchema=[true, false]w
   request.useXmlSchema=false
   response.useXmlSchema=false
   response.useXmlDirective=false
The default settings indicate that request documents may be sent without schema references. Likewise response documents are sent without the xml directive (<?xml version="1.0" encoding="UTF-8"?>) and without schema references.

The HTTP configuration is optional. See HTTP Configuration for more detail. The defaults are:

   # http.response.cacheControl={cache-directive}, {cache-directive}, ...
   http.response.cacheControl=no-cache, no-transform

The Database configuration is required. for a database with built-in support:

   # database.driverClassName=x.x.x
   #	for MySQL use com.mysql.jdbc.Driver
   #    for PostgreSQL use org.postgresql.Driver
   # database.url=jdbc:etc:etc
   #    for MySQL use jdbc:mysql://hostname:3306/
   #    for PostgreSQL use jdbc:postgresql://hostname:5432/{database-name}
   # database.user=userName
   # database.password=password
   database.driverClassName=com.mysql.jdbc.Driver
   database.url=jdbc:mysql://localhost:3306/
   database.user=restsql
   database.password=Rest00sql#
	
   # MetaData implemenation class - match the implementation to your database
   # For MySQL:
   #	org.restsql.core.SqlResourceMetaData=org.restsql.core.impl.SqlResourceMetaDataMySql
   # For PostgreSQL:
   #	org.restsql.core.SqlResourceMetaData=org.restsql.core.impl.SqlResourceMetaDataPostgreSql
   org.restsql.core.SqlResourceMetaData=com.business.restsql.SqlResourceMetaDataMySql

Implementation classes configuration is optional. The defaults are:

   # Implementation classes - use these to customize the framework
   # org.restsql.core.RequestLogger=fully.qualified.class.name
   # org.restsql.core.SqlBuilder=fully.qualified.class.name
   # org.restsql.core.Factory.ConnectionFactory=fully.qualified.class.name
   # org.restsql.core.Factory.RequestFactory=fully.qualified.class.name
   # org.restsql.core.Factory.SqlResourceFactory=fully.qualified.class.name
   # org.restsql.security.Authorizer=fully.qualified.class.name
   org.restsql.core.RequestLogger=org.restsql.core.impl.RequestLoggerImpl
   org.restsql.core.SqlBuilder=org.restsql.core.impl.SqlBuilderImpl
   org.restsql.core.Factory.ConnectionFactory=org.restsql.core.impl.ConnectionFactoryImpl
   org.restsql.core.Factory.RequestFactory=org.restsql.core.impl.RequestFactoryImpl
   org.restsql.core.Factory.SqlResourceFactory=org.restsql.core.impl.SqlResourceFactoryImpl
   org.restsql.security.Authorizer=org.restsql.security.impl.AuthorizerImpl

See the SDK for more detail on Security, Logging and Trigger configuration.

Access http://yourhost:port/restsql for links to the effective runtime configuration.

Installing restSQL WAR mode

Requirements: JEE Container, RDBMS, JAR tool

Properties Files: Create your two required properties files (restsql.properties and log4j.properties (or logging.properties), as above. Create your two optional privileges and triggers definitions if required. The restsql.properties can exist outside the restSQL webapp, however the log4j.properties/logging.properties must exist within the classpath in WEB-INF/classes. Note that it will not load properly if you put the logging properties in WEB-INF/lib. You do not have to create the logging directory or directories, e.g. /var/log/restsql. The logging frameworks will do this automatically.

Abbreviated Deployment for Tomcat

You can use this shortcut if you are using Tomcat, do not want restSQL Authentication or Authorization and Java Security Manager is disabled (the default for Tomcat). Add a Parameter entry that indicates your absolute path to your restsql.properties in your $TOMCAT_HOME/conf/context.xml, as in: 

   <Parameter name="org.restsql.properties" value="/etc/opt/business/restsql/restsql.properties" override="false" />
That will override the default properties location in the web.xml of the WAR.

Place the unmodified WAR in the $TOMCAT/webapps directory and bounce the server, or deploy the webapp using your favorite method.

Complete Deployment

The restsql-{version}.war contains the service and framework classes as well as dependencies. Extract it's contents to some temp area, e.g. /tmp/restsql. Use the standard jar tool that comes with your JRE/JDK. The command is jar -xf war-file-name. It extracts all contents in the current directory. The contents looks like:

    restsql/
        META-INF/
        wadl/
        WEB-INF/
        index.html

web.xml: Change the restSQL WEB-INF/web.xml. The LifecycleManager needs to know where to load your restsql.properties. Here's an example:

    <context-param>
        <param-name>org.restsql.properties</param-name>
        <param-value>/etc/opt/business/restsql/restsql.properties</param-value>
    </context-param>

The default deployment descriptor (web.xml) contains login config (authentication method) and security constraints (authorization declarations). See the restSQL default deployment descriptor.

Disabling Authorization and Authentication: To disable authentication/authorization, simply remove or comment out the security-constraint and login-config elements in the web.xml. Security is disabled by default.

Enabling Authorization and Authentication: You may use the default security constraints and login config or change it to conform to your specific roles, realm and other requirements. More information on Web Application Security using deployment descriptors is available at http://java.sun.com/javaee/6/docs/tutorial/doc/bncbe.html. Or consult your container's documentation. Authentication mechanisms (credential management, user to role assigment) are typically container-specific/proprietary. You will also need to configure a privileges properties file and reference it in the restsql properties file. See the SDK's Security configuration for instructions.

Naming: You may deploy this as a single file or exploded war to your JEE container. Rename it from restsql-#.war to to restsql.war or webapps/restsql if you want the path to be http://yourhost:port/restsql. Containers generally use the war file name instead of the web.xml's id to name the web app. Additionally, the SDK's HTTP API Explorer will work without any customization.

Deploy: Copy your exploded war or war to your container's webapps dir and restart the container, or deploy the webapp in your preferred style. All third party dependencies are included in the war distribution in the WEB-INF/lib.

Java Security Manager: If Java Security is enabled in your container, permissions must be added to your container's policy file. restSQL requires:

However, restsql uses other libraries (jersey, jdbc, logging) which need some unknown combination of access permissions. The only configuration that has been demonstrated to work is to grant all permissions to restsql. For example for Tomcat, add this to the end of the ${TOMCAT_HOME}/conf/catalina.policy file: 
    grant codeBase "file:${catalina.base}/webapps/restsql/-" {
        permission java.security.AllPermission;
    };

Note: If you receive a 500 response to any res query with the text "No suitable driver found", then the container cannot find your jdbc driver. This can usually be fixed by placing the database driver in some common server library location. This also occurs after deploying the restSQL.war to WebLogic using the console when the container is running. After a container restart, the driver is found.

Installing restSQL JAR mode

Properties: Follow the instructions for Configuring restSQL.

Deploy: Copy jar to the classpath of your web app, e.g. WEB-INF/lib. The following third party dependencies also need to be in your classpath:

log4j is not necessary if your app uses Java Native Logging. restSQL has been tested with JRE 1.6 and Java Native Logging.

Additionally one of the following jdbc drivers is necessary for databases with built-in support:

Authorization and Authentication: restSQL will authorize SQL Resource operations. Your app will authenticate users and associate users with roles. You must provide a priviliges properties file and reference it in the restsql.properties. Your app will call restSQL's Authorizer and provide a SecurityContext implementation. See the SDK's Security configuration for more instructions.

Java Security Manager: If you run enable Java Security, restSQL requires read/write access (java.util.PropertyPermission) to the following system properties: org.restsql.properties, org.apache.commons.logging.Log and either log4j.configuration for log4j logging or java.util.logging.config.file for Java Native logging. Additionally it needs read access (java.io.FilePermission) to the various properties files, and SQL Resources and triggers directories.

Installing restSQL SDK

Requirements: JEE Container, JAR tool, MySQL or PostgreSQL, Web Browser

Install restsql WAR mode as above with one variation: the restsql.properties must be changed to reference the sdk's SQL Resources definition directory. Below is an example:

    # sqlresources.dir=/absolute/path
    sqlresources.dir=/opt/tomcat/webapps/restsql-sdk/examples/sqlresources

Deploy: Extract restsql-sdk-{version}.war to your container's webapps directory, e.g. /opt/tomcat/webapps/restsql-sdk. Restart the container or use your preferred deloyment method.

The SDK war contents are:

     restsql-sdk/
         api-explorer/
         database/
         defaults/
         doc/
         examples/
         javadoc/
         META-INF/
         wadl/
         WEB-INF/

Database: The HTTP API Explorer requires access to an extended sakila database. It is extended for the restsql-sdk with new tables and data. Bash and Windows batch scripts are provided to create the base and extended database for MySQL and for PostgreSQL. The bash script is restsql-sdk/database/<database>/create-sakila.sh and the Windows batch script is restsql-sdk/database/<database>/create-sakila.bat, where database is either mysql or postgresql. You will need to change the user and password variables in the beginning of the script to an account that has database and table creation privileges.

Troubleshooting: The HTTP API Explorer requires access to a restsql service instance. If you have not deployed restsql to the same host/port as the SDK and to the location /restsql, then you will need to make one small tweak. Change two Javascript variables in restsql-sdk/api-explorer/index.html. Here is an example: 

    var restsqlHost = "http://somehost:8080";
    var restsqlBaseUri = "/restsql-0.7";

Installing restSQL Test

Requirements: restSQL project or deployed restSQL, JDK, Ant

The test project contains component test code, artifacts and a harness that exercise the framework and the service using the Java and HTTP APIs, respectively. The Java API tests use straight JUnit tests. The HTTP API tests use an XML-driven test case harness built with JUnit. The Java API tests require the restsql project, since it relies on its build file and source code. The HTTP API tests only require a deployed restsql service.

Database: If you have not deployed the SDK yet, you will need to deploy the extended sakila database. Bash and Windows batch scripts are provided to create the base and extended database for MySQL and PostgreSQL. The bash script is restsql-test/database/<database>/create-sakila.sh and the Windows batch script is restsql-test/database/<database>/create-sakila.bat, where database is mysql or postgresql. You will need to change the user and password variables in the beginning of the script to an account that has database and table creation privileges.

Execution: The tests are executed using the Ant build file (restsql-test/build.xml). Executing the default target, all, will run everything, but you can also run test-api (Java API) or test-service (HTTP API) to run one or either half. If the service is not running in the default location, http://localhost:8080/restsql/, then the System Property, org.restsql.baseUri, must be set. For example:

    ant -Dorg.restsql.baseUri=http://somehost:8080/restsql-0.7/ test-service-http

Test results will appear on the console. Test detail is available in restsql-test/obj/test.