10.3 Deploying and Configuring Spatial Web Services

Preparing WebLogic Server (Version 12.1.3 or Later)

Before you deploy the web service engine, it is recommended that you create a managed server in WebLogic Server.

For the Web Service Engine to be successfully deployed on a managed server, a WebLogic ___domain must be created.

Creating a Domain on WebLogic Server

You must ensure that a ___domain exists for web services on WebLogic Server. To create a spatial ___domain, follow these steps.

1. Log in to the WebLogic Server console.

2. Select Create a New WebLogic Domain, and click Next.

3. Select Domain Source: Generate a Domain Configured Automatically, and click Next.

4. Configure the Administrator Username and Password, and click Next.

5. For Server Start Mode, select Development or Production.

6. For JDK, select one of the available JDKs.

7. For Customize Environment and Service Settings, either accept the default values or specify any customizations.

8. On the Create WebLogic Domain page, click Create, then Next.

9. On the Creating Domain page, click Done.

For more information about creating and configuring a ___domain, see the WebLogic Server documentation.

Unpacking the sdows.ear.zip File (WFS, WCS, CSW)

Before anyone can use Spatial and Graph WFS, WCS, and CSW services, you, as an administrator with the DBA role, must ensure that the sdows.ear.zip file, found in $ORACLE_HOME/md/jlib, is unzipped into a desired directory before deployment. The resulting path should end with an sdows.ear directory, which is sometimes referred to as the sdows exploded directory.

Deploying Spatial Web Services on WebLogic Server and Editing the web.xml File

Spatial web services should be deployed as an exploded directory because log files are generated inside this directory.

For backward compatibility for WFS service only (because WCS 2.0.1 and CSW 2.0.2 are newly added services as of Release 12.2), if you prefer SpatialWS-SpatialWS-context-root (or any other preferred root name), then in the web.xml file, for the <env-entry-name>oracle/spatial/ws/publish_url_as/contextPath</env-entry-name> element, specify the desired value in its <env-entry-value> element. In this case, also modify these other files to reflect a root other than the default oraclespatial: application.xml, context.xml, weblogic.xml, wfs.wsdl and csw202.wsdl.

Similarly, if you need to change the servlet path for WFS, WCS, or CSW, all relevant <env-entry-name> and <env-entry-type> elements in the web.xml file must specify the desired values. For example:

<env-entry-name>oracle/spatial/ws/publish_url_as/servletPath/wfs</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>

<env-entry-name>oracle/spatial/ws/publish_url_as/servletPath/csw</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>

<env-entry-name>oracle/spatial/ws/publish_url_as/servletPath/wcs</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>

If a proxy server is used as an intermediary for requests from clients, the following env-entry elements in the web.xml file should be edited.

• oracle/spatial/ws/publish_url_as/host

• oracle/spatial/ws/publish_url_as/port

• oracle/spatial/ws/publish_url_as/protocol

• oracle/spatial/ws/publish_url_as/contextPath

• oracle/spatial/ws/publish_url_as/servletPath/ws

• oracle/spatial/ws/publish_url_as/servletPath/wfs

• oracle/spatial/ws/publish_url_as/servletPath/csw

• oracle/spatial/ws/publish_url_as/servletPath/wcs

• oracle/spatial/ws/publish_url_as/xmlservletPath/ws

• oracle/spatial/ws/publish_url_as/xmlservletPath/wfs

• oracle/spatial/ws/publish_url_as/xmlservletPath/csw

• oracle/spatial/ws/publish_url_as/xmlservletPath/wcs

To deploy a spatial web service on WebLogic Server, follow these steps.

1. Log in to the WLS console

2. Click Deployments, then Install.

3. Ensure that Path is set to the application deployment (Exploded Archive) directory.

4. Select sdows.ear (a directory), and click Next.

5. Ensure that the Install this deployment as an application targeting style is selected, and click Next.

6. In the list of potential servers to which to deploy the WFS Engine, select the name of the managed server that you created, select I will make the deployment accessible from the following ___location, enter the Exploded Archive (Application deployment) Directory, and click Next.

7. Ensure that the deployment name is sdows, and click Finish.

Ensuring the Web Service Web Project is in the Active State

After completing the necessary steps for a spatial web service, check on the Deployments page that the application is in the Active state.

If it is in the Prepared state, click Start to start the application.

Configuring Each Spatial Web Service

The next step is to configure each spatial web service that you will use (such as WFS, WCS, or CSW) independently. You must perform specific tasks that depend on which web services you will be supporting for use in your environment. You will probably need to create and grant privileges to database users. You may need to download and load special data (such as for geocoding), modify configuration files or create data sources in WebLogic Server.

See the chapter for each relevant spatial web service for instructions specific to that service.