Deploying a Federated Search Service (Java)

After implementing a federated search service, you must deploy your code.

Follow the instructions below to deploy a Java federated search service:

Compile the class that implements the Oracle WebCenter Interaction Development Kit (IDK) interface and copy the entire package structure to the appropriate location in your web application (usually the \WEB-INF\classes directory).
Update the web.xml file in the WEB-INF directory by adding the class to the appropriate *Impl keys. For example, add your class to SearchImpl as shown below. Note: The *Impl key in the web.xml file must reference the fully-qualified name of the class. If the service uses SCI, you must also enter the fully-qualified name of the appropriate implementation of the IAdminEditor interface. For a list of keys, see Web Service Class Names (*Impl).
```
...
<env-entry>
<env-entry-name>SearchImpl</env-entry-name>
<env-entry-value>com.plumtree.remote.search.helloworld.Search</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
...
```
Start your application server. (In most cases, you must restart your application server after copying a file.)
Test the directory by opening the following page in a web browser: http://<hostname:port>/idk/services/<servicetype>ProviderSoapBinding (for example, http://localhost:8080/idk/SearchSoapBinding). The browser should display the following message: "Hi there, this is an AXIS service! Perhaps there will be a form for invoking the service here..." When you configure the Web Service for the federated search service in the portal, enter this path as the Service Provider URL.
If the federated search service uses a SCI page to define settings, you must also deploy the SCI code. For details on using SCI pages, see Creating Service Configuration Pages for Content Crawlers.

Parent topic: About Oracle WebCenter Interaction Federated Search Services

Oracle WebCenter Interaction Web Service Development Guide

Deploying a Federated Search Service (Java)