This content has been marked as final. Show 12 replies
We did the same steps you described. We get joseki to display and run using this URL:
http://localhost:7001/joseki/. Of course, substitute localhost for wherever you did the install.
Have you created the semantic network?
Yes, semantic network was created and an example ontology was loaded.
Good. Is there any suspicious server log on WLS side?
No suspicious logs....a thought just cxame to me that WLS admin console was up and running on same port....am thinking this may be why joseki page wouldn't display.
Actually they should be on the same port.
Could you cut & paste the actions you did for the following step? Which directory did you
copy all those files into?
7. Installed Joseki 3.4.0 IAW Oracle Semantic Technologies Developers guide.
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:
cp joseki-3.4.0.zip /tmp/joseki
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:
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:
cp /tmp/jena_adaptor/web/* /tmp/joseki.war/WEB-INF
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.
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
DATABASE USWER NAME: nciuser
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)
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/
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.
What domain name did you choose for these two steps you performed?
cp -rf /tmp/joseki.war <domain_name>/autodeploy
cp -rf /tmp/joseki.war /home/oracle/Oracle/Middleware/wlserver_10.3/samples/domains/wlserver/autodeploy
Please email me at alan dot wu at oracle dot com. I can then start a web conference to look at your configuration. It will be a lot easier that way.
I figured it out. Thank yall for the assists. Was a java problem. Was pointing to JDK 5 vs. JDK 6.
Hi everybody I have a problem with the configuration file joseki like you could send configured because I do not know,
I'm new at this please help me