http://openrdf.callimachus.net/sesame/2.7/docs/users.docbook?view
- Read the part
Configuring Workbench for UTF-8 Support
UTF-8 in the Request URI (GET)
There is another known issue (SES-1768) affecting the proper exploring of resources that use an extended character set. Workbench client-side code generates URI's assuming an ISO-8859-1 character encoding, and often Tomcat comes pre-configured to expect UTF-8 encoded URI's. It will be necessary to change the HTTP Connector configuration, or to add a separate HTTP Connector that uses ISO-8859-1. For details, see here for Tomcat 6 or here for Tomcat 7.
UTF-8 in the Request Body (POST)
To resolve issues where the request body is not getting properly interpreted as UTF-8 (see, for example, SES-1811), it is necessary to configure Tomcat to use its built in SetCharacterEncodingFilter. Some details are at https://wiki.apache.org/tomcat/FAQ/CharacterEncoding#Q3. With Tomcat 6, version 6.0.36 or later is required. On Tomcat 7, un-commenting the <filter> and <filter-mapping> elements for setCharacterEncodingFilter in $CATALINA_BASE/conf/web.xml, and restarting the server, were the only necessary steps.
- Put all Sesame libs in TOMCAT_HOME/lib
- Indexes: spoc,sopc,psoc,posc,opsc,ospc
- In TOMCAT_HOME/bin/setclasspath.bat, set the variable JAVA_HOME. For example, set "JAVA_HOME=C:\Program Files\Java\jre6"
- In TOMCAT_HOME/bin/catalina.bat, redirect the Sesame base directory like this: set JAVA_OPTS=%JAVA_OPTS% -Dinfo.aduna.platform.appdata.basedir=C:\Other\Directory\
- These jars should be in the project classpath: openrdf-sesame-2.7.3-onejar.jar, commons-codec-1.4.jar, commons-httpclient-3.1.jar, sl4j-api.1.6.1.jar, commons-logging-1.1.3.jar, sl4j-jdk14-1.7.5, jackson-core-2.2.1.jar
- These too (jena libs): jena-arq-2.10.1.jar, jena-core-2.10.1.jar, jena-iri-0.9.6.jar, xercesImpl-2.11.0.jar, xml-apis-1.4.01.jar