Problems setting up Semantic tech in Orac le 11G running Linux.

Question

Hi Every1,
Am a novice at this Semantic Techno stuff and am trying to overcome that. Am trying to set up an 11G semantic tech baseline on a Linux box and am having difficulties getting everything loaded. Here is where I am at:
1.     Installed JDK V5.
2.     Installed Oracle 11Gr2 w/spatial and partitioning.
3.     Installed Jena V 2.6.2 (jena-2.6.2.zip) IAW Oracle Semantic Technologies Developers guide.
4.     Installed Jena Adaptor (jena_adaptor_for_release11-2.zip) IAW Oracle Semantic Technologies Developers guide.
5.     Installed Oracle WebLogic Server 11g Release 1(10.3.1).
6.     Installed Java 6.1.
7.     Installed Joseki 3.4.0 IAW Oracle Semantic Technologies Developers guide.
8.     Created J2EE data source in WebLogic Server admin console IAW Oracle Semantic Technologies Developers guide.
9.     Completed the autodeploy tasks IAW Oracle Semantic Technologies Developers guide.
10.     Restarted WebLogic Server.
11.     Attempted to verify the deployment via web browser (http://localhost.localdomain:7001/joseki) and received an Error 404—Not Found From RFC 2068 message vice the Oracle SPARQL Service Endpoint page as expected.
Am at a loss … can anyone identify where I went wrong and how to fix this problem?

Answer 1

Here are the steps I used loading Joseki.
1. Download and Install Oracle WebLogic Server 11g Release 1 (10.3.1). For details, see http://www.oracle.com/technology/products/weblogic/.
2. Ensure that you have Java 1.6 installed, because it is required by Joseki 3.4.0.
3. Download Joseki 3.4.0 (joseki-3.4.0.zip) from http://sourceforge.net/projects/joseki/files/Joseki-SPARQL/.
4. Unpack joseki-3.4.0.zip into a temporary directory. For example:
mkdir /tmp/joseki
cp joseki-3.4.0.zip /tmp/joseki
cd /tmp/joseki
unzip joseki-3.4.0.zip
5. Ensure that you have downloaded and unzipped the Jena Adaptor for Oracle Database, as explained in Section 7.1.
6. Create a directory named joseki.war at the same level as the jena_adaptor directory, and go to it. For example:
mkdir /tmp/joseki.war
cd /tmp/joseki.war
7. Copy necessary files into the directory created in the preceding step:
cp /tmp/jena_adaptor/joseki/* /tmp/joseki.war
cp -rf /tmp/joseki/Joseki-3.4.0/webapps/joseki/StyleSheets /tmp/joseki.war
8. Create directories and copy necessary files into them, as follows:
mkdir /tmp/joseki.war/WEB-INF
cp /tmp/jena_adaptor/web/* /tmp/joseki.war/WEB-INF
mkdir /tmp/joseki.war/WEB-INF/lib
cp /tmp/joseki/Joseki-3.4.0/lib/*.jar /tmp/joseki.war/WEB-INF/lib
cp /tmp/jena_adaptor/jar/*.jar /tmp/joseki.war/WEB-INF/lib
cp $ORACLE_HOME/md/jlib/sdordf.jar /tmp/joseki.war/WEB-INF/lib
cp $ORACLE_HOME/jdbc/lib/ojdbc6.jar /tmp/joseki.war/WEB-INF/lib
Note that in the last command, you can specify ojdbc6.jar instead of ojdbc5.jar if you are using JDK 6.
9. Using the WebLogic Server Administration console, create a J2EE data source named OracleSemDS. During the data source creation, you can specify a user and password for the database schema that contains the relevant semantic data against which SPARQL queries are to be executed.
If you need help in creating this data source, see Section 7.2.1, "Creating the
Required Data Source Using WebLogic Server".
7.2.1 Creating the Required Data Source Using WebLogic Server
If you need help creating the required J2EE data source using the WebLogic Server admin console, you can follow these steps:
1. Login to: http://<hostname>:7001/console
2. In the Domain Structure panel, click Services.
3. Click JDBC
4. Click Data Services.
5. In the Summary of JDBC Data Sources panel, click New under the Data Sources table.
6. In the Create a New JDBC Data Source panel, enter or select the following values.
Name: OracleSemDS
JNDI Name: OracleSemDS
Database Type: Oracle
Database Driver: Oracle's Driver (Thin) For Instance Connections Versions: 9.0.1,9.2.0,10,11
7. Click Next twice.
8. In the Connection Properties panel, enter the appropriate values for the Database Name, Host Name, Port, Database User Name (schema that contains semantic data), Password fields.
DATABASE NAME: orcl
HOST NAME: orcl.localdomain
PORT: 1521
DATABASE USWER NAME: nciuser
PASSWORD: <password>
CONFIRM PASSWORD: <password>
9. Click Next.
10. Select (check) the target server or servers) to which you want to deploy this OracleSemDS data source.
11. Click Finish.
You should see a message that all changes have been activated and no restart is necessary.
10. Go to the autodeploy directory of WebLogic Server and copy files, as follows.(For information about auto-deploying applications in development domains, see: http://download.oracle.com/docs/cd/E11035_01/wls100/deployment/autodeploy.html)
cd <domain_name>/autodeploy
cp -rf /tmp/joseki.war <domain_name>/autodeploy
In the preceding example, <domain_name> is the name of a WebLogic Server domain.
Note that while you can run a WebLogic Server domain in two different modes, development and production, only development mode allows you use the auto-deployment feature.
11. Check the files and the directory structure, as in the following example:
autodeploy/% ls -1R ./joseki.war/
./joseki.war:
application.xml
index.html
joseki-config.ttl
StyleSheets/
update.html
WEB-INF/
xml-to-html.xsl
./joseki.war/StyleSheets:
joseki.css
./joseki.war/WEB-INF:
lib/
web.xml
./joseki.war/WEB-INF/lib:
arq-2.8.0.jar
arq-2.8.0-tests.jar
icu4j-3.4.4.jar
iri-0.7.jar
jena-2.6.2.jar
jenatest-2.6.2.jar
jetty-6.1.10.jar
jetty-util-6.1.10.jar
joseki-3.4.0.jar
junit-4.5.jar
log4j-1.2.12.jar
lucene-core-2.3.1.jar
ojdbc5.jar
sdordfclient.jar
sdordf.jar
servlet-api-2.5-6.1.10.jar
servlet-api-2.5.jar
slf4j-api-1.5.6.jar
slf4j-log4j12-1.5.6.jar
stax-api-1.0.1.jar
wstx-asl-3.2.9.jar
xercesImpl-2.7.1.jar
12. Start or restart WebLogic Server.
13. Verify your deployment by using your Web browser to connect to a URL in the following format (assume that the Web application is deployed at port 7001): http://<hostname>:7001/joseki
You should see a page titled Oracle SPARQL Service Endpoint using Joseki, and the first text box should contain an example SPARQL query.
This is where I got the http error message instead of the Oracle SPARQL Service Endpoint using Joseki screen.