Package com.plumtree.remote.search

Provides interfaces for searching remote systems from the portal.

See:
          Description

Interface Summary
IRemoteSearch Interface to enable the portal to execute searches on remote systems.
ISearchContext Interface that provides a way to connect with the portal via the PRC.
ISearchQuery Interface that provides the input information to execute the search.
ISearchRecord Bean-type interface for an individual search record.
ISearchResult Interface that represents search results.
ISearchUser Interface that provides user-related information to enable the retrieval of results authorized and personalized for the user.
 

Class Summary
RemoteSearchRecord Bean class that implements ISearchRecord.
SearchConstants Constants for error codes.
TypeSearchError Type-safe enumeration of error types.
 

Exception Summary
SearchException Exception class to communicate known exceptions and user-defined errors to the search interface in the portal.
 

Package com.plumtree.remote.search Description

Provides interfaces for searching remote systems from the portal.

Search services provide access to external repositories without adding documents to the portal Knowledge Directory. Search services are especially useful for content that changes frequently or is only accessed by a small number of portal users. Search services are a way to make content accessible to portal users without adding documents to your portal Knowledge Directory.

Using the IDK, you can create remote search services that access a range of backend systems.

See Search Example

To view the SOAP endpoint required in the Profile Web Service Settings of the Profile Web Service, open a browser and point it to http://<my_server>:<my_port>/<war_name>/services. For example, http://express-job1.devnet.plumtree.com:8080/HelloWorldSearch/services. The page should display "And now...Some Services." with a list of all defined services. The default endpoint for Search URL is http://<my_server>:<my_port>/<war_name>/services/SearchProviderSoapBinding, and for Service Configuration URL (if used) is http://<my_server>:<my_port>/<war_name>/services/SciProviderSoapBinding. If the DeployServlet was used to create the services, you will see the services with a developer-supplied prefix.



For additional information on the Oracle® WebCenter Interaction Development Kit, including tutorials, blogs, code samples and more, see the Oracle Technology Network (http://www.oracle.com/technology/index.html).

Copyright ©2010 Oracle® Corporation. All Rights Reserved.