Complete the tutorial Installing and Configuring Spatial Web Service for OC4J.

From your terminal window, enter the following commands:

cd $CLIENT_HOME/src/sql
sqlplus / as sysdba

Here, $CLIENT_HOME is the directory location where you extracted the wsclient.jar file.

To populate the relational feature type, enter the following SQL script:

@wfsrelmd.sql

The wfsrelmd.sql script creates users, tables, and indexes; grants privileges; and executes some PL/SQL procedures. The following screenshot shows only a part of the output.

To populate the document-based feature type, enter the following SQL script:

@wfsdocmd.sql

The wfsdocmd.sql script also creates users, tables, and indexes; grants privileges; and executes some PL/SQL procedures. The following screenshot shows only a part of the output.

Quit SQL Plus.

To create the feature type (java oracle.spatial.ws.admin demo.WFSAdminDemo SampleFeature ./data/datafeatures.xsd ./data/fd_sample.xml create), enter the following commands:

cd $CLIENT_DIR/src
./compileAndRunClient.sh runwfsct

Here, CLIENT_DIR is the path where you extracted the src folder.

In a new terminal, start the OC4J server. Enter the following commands:

cd <jdevhome directory>/bin
./oc4j -start

To run the relational WFS demo, enter the following commands (where $CLIENT_DIR is the client directory that has this demo's src/ content):

cd $CLIENT_DIR/src/data
cp wfsMapFile_rel.txt wfsMapFile.txt

cd $CLIENT_DIR/src
./compileAndRunClient.sh runwfsrel

The src/data/wfsrel_*.xml files will be accessed when you run the ./compileAndRunClient.sh runwfsrel command. The corresponding output files are generated in the src/data directory as the wfsrel_*.log files.

The following screenshots show the complete output in parts.

Examine the input XML, wfsrel_01.xml file, as shown in the following screenshot:

The corresponding output, wfsrel_01.log, is shown in the screenshot below:

To run the document-based WFS demo, enter the following commands (where $CLIENT_DIR is the client directory that has this demo's src/ content):

cd $CLIENT_DIR/src/data
cp wfsMapFile_doc.txt wfsMapFile.txt

Then, run the document-based demo (java oracle.spatial.ws.svrproxy.TestWFS wfs_doc_user wfs_doc_user) as follows:

cd $CLIENT_DIR/src
./compileAndRunClient.sh runwfsdoc

The following screenshots show the complete output in parts.

Examine the wfsdoc_06.xml input file. As mentioned, wfsdoc_06.xml is an example of the Transaction: Update request.

The following screenshot shows the response, the wfsdoc_06.log file.

To drop the relational feature type, enter the following commands:

cd $CLIENT_DIR/src/sql
sqlplus / AS SYSDBA

Run the SQL*Plus script: drprelmd.sql.

@drprelmd.sql

Quit SQL*Plus.

To drop the document-based feature type, enter the following commands:

cd $CLIENT_DIR/src
./compileAndRunClient.sh runwfsdt

Stop the OC4J server. Enter the following commands:

cd <Jdev directory>/bin
./oc4j -shutdown -port 23791 -password admin

Populate the record type for the CSW demo by entering the following commands (where $CLIENT_HOME is the client directory that has this demo's src/ content):

cd $CLIENT_HOMR/src/sql
sqlplus / as sysdba
@cswmd.sql

Quit SQL*Plus.

To create the type, use the Java class oracle.spatial.ws.admindemo.CSWAdminDemo createRecordType, as follows:

cd $CLIENT_HOME/src
./compileAndRunClient.sh runcswct

To run the CSW demo (java oracle.spatial.ws.svrproxy.TestCSW csw_user csw_user), enter the following commands (where $CLIENT_HOME is the client directory that has this demo's content):

cd $CLIENT_HOME/src
./compileAndRunClient.sh runcsw

Examine the csw_08.xml input file. As mentioned, csw_08.xml is an example of the GetRecordById request.

The corresponding output file, the csw_08.log file is shown below:

To drop the CSW record type (java oracle.spatial.ws.admindemo.CSWAdminDemo
dropRecordType), enter the following commands (where $CLIENT_DIR is the client directory that has this demo's src/ content):

cd $CLIENT_HOME/src
./compileAndRunClient.sh runcswdt

Stop the OC4J server. Enter the following commands.

cd <Jdev directory>\bin
./oc4j -shutdown -port 23791 -password admin

Locate the following files:

- src/sql/olslocut.dmp
- src/sql/olscreate.sql

Edit olscreate.sql. Enter the following commands:

cd $CLIENT_HOME/src/sql
gedit olscreate.sql

In the olscreate.sql file, change several occurrences of "connect user/password" to specify a desired username and password. For this tutorial, change the system and mdsys password to oracle.

Note: For Presentation Service and Route Service the insert(...) and assign_acl(...) statements need to be updated to point to the correct Route Server, and MapViewer URLs. If you have access to an Oracle Location Service, you can set up and access these URLs and then run the OpenLS SQL demos for the Presentation service and Route Service demos. Oracle Location Service will provide capability to process Routing and Mapping requests.

For more details about Oracle Route Server, refer to the chapter on Routing Engine in the Oracle Spatial Developer's Guide. For more details about Oracle MapViewer, click the following link:

http://www.oracle.com/technology/software/products/mapviewer/index.html

If you don't have access to Oracle Location Service, you cannot run the OpenLS SQL demos for Presentation Service and Route Service. So you need not make any changes to the insert into and assign_acl statements mentioned below.

But you can still run the OpenLS SQL demos for Directory service, and Geocoding service.

Change the following:

Server URL definitions in statements that INSERT INTO the mdsys.OpenLSServices table:

For Location Utility Service and Directory Service, you can keep the URL as http:localhost.

For Presentation Service and Route Service, the URL should point to the correct Route Server and MapViewer URLs. Therefore, change it only if you have access to Oracle Location Service.

In dbms_network_acl_admin.drop_acl('xxx.xml'), you can leave it as is for this tutorial.

Change the URL in access control list (ACL) definitions (the assign_acl statement)) to the URLs you chose in the INSERT INTO statements for the Presentation Service and Route Service. Change this only if you have access to Oracle Location Service.

In the $CLIENT_DIR/src/oracle/spatial/ws/svrproxy/Test.java file, do the following:

Change the URL (localhost, port) in:

myPort.setEndpoint("http://localhost:8888/SpatialWS-SpatialWS-context-root/SpatialWSSoapHttpPort");

Note: For the tutorial, you may keep it as "localhost:8888".

Edit occurrences of the following to specify an appropriate username and password:

myPort.setUsername(user);
myPort.setPassword("welcome");

Because you have already created users SpatialWsUser0 ... SpatialWsUser3, you might not need to make any changes. Also, note that some of the tests perform loops, for performance measurements.

Compile and run code.

For a sample YP request (Linux systems):

cd $CLIENT_HOME/src
./compileAndRunClient.sh runyp 

The following screenshot shows only a part of the output.

Enter the following commands:

cd $CLIENT_HOME/src/data
sqlplus mdsys/oracle

spool olsloc_01.log
@olsloc_01.sql
spool off

As mentioned in the table above, olsloc_01.sql is an example that requests from Geocode two addresses in San Francisco. You can view the spooled output log file, olsloc_01.log, from the $CLIENT_HOME/src/data directory. The screenshot shows only a part of the output.