UltraSearch - federated search

We want to make use of the federated search technology within UltraSearch, but there is a problem using the 'federator resource adapter'.
Deploying works, but the UltraSearch Administration cleaves on the JNDI location "eis/oracle", which does not exist:
There are no available resource adapter. Verify the configuration and deployment of your resource adapter.
javax.naming.NameNotFoundException: eis/oracle not found in admin
This error occures within UltraSearch Administration, if you click on the Tab 'Sources' -> Oracle Sources -> Create Source: Federated
Changing the federator JNDI location within the file '$PORTAL_HOME/j2ee/OC4J_Portal/application-deployments/default/FederatorSearchlet/oc4j-ra.xml'
(deployment descriptor for resource adapters) from "eis/Federator" to "eis/oracle" doesn't work, UltraSearch can't resolve the name.
oc4j.xml:
<?xml version="1.0"?>
<!DOCTYPE oc4j-connector-factories PUBLIC "-//Oracle//DTD Oracle Connector 9.04//EN" "http://xmlns.oracle.com/ias/dtds/oc4j-connector-factories-9_04.dtd">
<oc4j-connector-factories>
     <connector-factory location="eis/Federator" connector-name="Federator">
          <config-property name="connectionURL" value="jdbc:oracle:thin:@<db_host>:1521:<db_sid>"/>
          <config-property name="userName" value="wk_test"/>
          <config-property name="password" value="********"/>
          <config-property name="instanceName" value="wk_inst"/>
          <config-property name="verboseLog" value="false"/>
     </connector-factory>
</oc4j-connector-factories>
Mapping of the JNDI location within the file '$PORTAL_HOME/j2ee/OC4J_Portal/application-deployments/UltrasearchAdmin/admin/orion-web.xml' has no effect.
orion-web.xml:
<?xml version="1.0"?>
<!DOCTYPE orion-web-app PUBLIC "-//ORACLE//DTD OC4J Web Application 9.04//EN" "http://xmlns.oracle.com/ias/dtds/orion-web-9_04.dtd">
<orion-web-app
     deployment-version="9.0.4.1.0"
     jsp-cache-directory="./persistence"
     temporary-directory="./temp"
>

<resource-ref-mapping name="eis/oracle" location="eis/Federator"/>
</orion-web-app>
The UltraSearch documentation (UltraSearch User's Guide) regarding federated search and federated sources is pretty inadequate.
Is there any document describing this topic?
System:
UltraSearch: 9.2.0 (API version 9.0.4)
Oracle Portal: 9.0.2.5
Operation System: Sun Solaris 5.9 (Sparc)
Oracle Aplication Server: 10g (Patchset 9.0.4.1)
Database: Oracle9i Enterprise Edition Release 9.0.1.5.0

Dorian,
I realize that this post is a year old, but I am also trying to utilitze the federated search in UltraSearch. I have read that the capability exists but have not found any documentation on how to implement. From this post, it looks like you made progress. How did you find info on how to use this capability?
Thanks,
Amy

Similar Messages

How to get the SharePoint user context available in custom federated search connector?

Hi,
I'm investigating the possibilities for developing a federated search connector for SharePoint 2013 Online. This should allow us to search a customer's database through our custom developed application (both on premise). We intend to develop
an remote federated search connector (using OpenSearch protocol) and configure a result source in SharePoint for that connector.
The problem I'm struggling with is that I want different search results from this ressult source based on the permissions of the user that is executing the search. The admin should find a lot because he has permissions on certain items in the custom
application. The employee should find just a few because he has no permissions on certain items in the custom application. We developed the custom application ourselveds and the search in that application is taking permissions into account: it doesn't
return results if a user doesn't have sufficient permissions. That part works just fine.
However, to be able to use that, the remote federated search connector must be able to identify the user that is executing the search in SharePoint Online. So: how do I get the SharePoint user context in the remote federated search connector?
I know I can configure the replacement token {User.Name} in the result source configuration, but that gives me the name of the user only. This is insufficient to get an identity, principal, token or whatever, that let's me log in into our custom
application.
I also know that in a provider hosted app, user context is passed through from SharePoint and is known within the remote app. But since result sources need fixed (or anonymous) credentials configuration for connecting to the remote federated search connector,
all users will be using the same credentials. This makes me assume these credentials are for securing communication and cannot be used within the execution of the search within the remote federated search connector.
At the moment, I'm stuck. Any help will be greatly appreciated.
Cheers,
Ruud.

Hi,
Per my knowledge, we cannot get the SharePoint user context available in custom federated search connector with other methods.
Here is a similar thread for your reference:
https://answers.atlassian.com/questions/263735/atlassian-sharepoint-connector-federated-search-authentication-and-authorization
Thanks,
Linda Li
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

Federated search - specifying the service configuration page

I've built an interface (web service) to the Portal federated search specification so users can search libraries in our company's document management system (Panagon).
I want to specify an administration page, where an administrator can set a property which is the name of the library to be searched by an instance of the federated search web service. To do this, I've set a valid URL for the Service Configuration URL parameter when I configure the web service.
However, when I try to administer the Federated Search object corresponding to the web service, then I get the following message, even if the admin page has been built to just print a "Hello World" message:
<i>The Server Configuration Interface for this Outgoing Federated Search is unavailable. Check the URL configuration in the Web Service associated with this object.</i>
If I use the Administration Configuration URL, then I'm creating a rod for my own back, as we have 20 + libraries which we want to incorporate into the federated search interface. Each one of these would then have it's own entry in the "Select Utility" drop down box.
Has anyone successfully used the service configuration page option?
Thanks for any advice you can offer,
Charles

I've used SCI elsewhere, but never in Federated Search. The best way to test SCI is to download the Service Station from http://portal.plumtree.com. That can show you the entire SOAP trace so you can see exactly what's going on.
HTH,
Chris Bucchere | bdg | [email protected] | http://www.bdg-online.com

Error in Federated Search

Hi,
I have writte a federated search to search for external search engine (Verity). When i run the search it is calling the basicSearch method implemented in the remote server but after that it is throwing SAXParserException (Pasted the exception down). What can be the problem..
Thanks in advance..
Vikas G
Oct 4, 2004 2:14:07 PM org.apache.axis.client.Call invokeINFO: Mapping Exception to AxisFaultAxisFault faultCode: {http://xml.apache.org/axis/}Server.userException faultString: org.xml.sax.SAXParseException: The declaration for the entity "HTML.Version" must end with '>'. faultActor: null faultDetail: stackTrace: org.xml.sax.SAXParseException: The declaration for the entity "HTML.Version" must end with '>'. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanEntityDecl(XMLDTDScannerImpl.java:1561) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDecls(XMLDTDScannerImpl.java:1971) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDTDExternalSubset(XMLDTDScannerImpl.java:319) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1030) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:232) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:546) at org.apache.axis.Message.getSOAPEnvelope(Message.java:377) at org.apache.axis.client.Call.invokeEngine(Call.java:2132) at org.apache.axis.client.Call.invoke(Call.java:2102) at org.apache.axis.client.Call.invoke(Call.java:1851) at org.apache.axis.client.Call.invoke(Call.java:1777) at org.apache.axis.client.Call.invoke(Call.java:1315) at com.verity.UltraseekBindingStub.search(UltraseekBindingStub.java:356)
at com.search.VeritySearch.basicSearch(VeritySearch.java:119) at com.plumtree.remote.search.RemoteSearch.BasicSearch(RemoteSearch.java:70) at com.plumtree.remote.search.xp.XPRemoteSearch.BasicSearch(XPRemoteSearch.java:56) at com.plumtree.remote.search.soap.SearchSoapBindingImpl.BasicSearch(SearchSoapBindingImpl.java:87) at com.plumtree.remote.search.soap.SearchSoapBindingSkeleton.BasicSearch(SearchSoapBindingSkeleton.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:372) at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:292) at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:276) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:437) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:316) at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:701) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:106) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:576) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)

Do you have any view object and attribute mapped to the Emp. No. Criteria Message Text Input...?
Is yes, please remove it.

Federated Search without Query String?

I need to configure Federated Search for a URL having search text box & button. It does not provide a query string.
Can I configure Result Source without Query String?
(www.domain.com)

No, you cannot do it OOTB. SharePoint supports OpenSearch 1.1 which doesn't contain other nethods except GET

Simple Federated Search

Does anyone have sample code for running a simple federated search query (e.g., http://search.yahoo.com/search?p=, http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=, etc.) ? I would like to add several of these simple searches to the list of federated search engines.
Thanks.

We currently have a field where a user can enter a search term and select the data source from a drop-down list like the following:
<select name="SearchEngines"><option value="http://www.jtbaker.com/asp/catalog.asp?searchdata=">MSDS</option><option value="http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=">Dictionary</option><option value="http://www.m-w.com/cgi-bin/thesaurus?book=Thesaurus&va=">Thesaurus</option><option value="http://www.google.com/search?q=">Google</option><option value="http://search.yahoo.com/search?p=">Yahoo!</option><option value="http://www.altavista.com/web/results?q=">Alta Vista</option></select>
What we would like is to have this list of data sources on the "Search Locations" section with check boxes when you click on the Federated Search icon.

Portal to Portal Federated Search

Hi All,
There is probably a really simple answer to this but I'm having difficulties seeing it at the moment. As you can see from the title I'm trying to configure a federated search to search for documents within another portal instance. I've read the admin guide, online help & various discussion and yet I'm still none the wiser.
I understand that when you install the portal (v5.0.4) you get an incoming federated search for free. This allows someobdy to search as guest user. What I also assume is that on the portal which will be doing the search I need to set up a Outgoing federated search. Is this correct? If so then no problem but the question is that this needs to be based on a Web service. The documentation points to the EDK search API to develope this and hence the problem. I'm not familar with search web services so not sure what I should be aiming to return? Or infact anything that should be contained.
I'm developing in Java and have looked at the 2 examples but still feel lost. Can anyone point me in the right direction or further explain what I should be trying to achieve and how to get there.
Many thanks, Adam

Hi Rani,
see my answers bellow:
1. You mean you are in the Room Maintenance iView and add a new room member, and you can give him any role but the owner role? That's strange. Could you send me a screenshot?
2. By default, the search for rooms, for example, in the room directory, in the room list, in room administration, or in the room relations manager, is performed using the SAP search engine Search and Classification (TREX). If you deactivate the TREX search for rooms or you have not installed TREX with the portal, the system switches automatically to the Content Management search function (CM search).
Here the link for more info: http://help.sap.com/saphelp_nw04s/helpdata/en/6b/4e9442c22d1131e10000000a1550b0/content.htm
3. Here the definition from SAPHelp: "A federated portal network allows organizations with distributed portal installations, both SAP and non-SAP, to provide a single portal access point per user to portal information, services and applications distributed on portals throughout the entire organizational network. This implementation allows existing content and configurations to be utilized, and to minimize necessary administration efforts". So you were right about your assumptions. Here you find more information: http://help.sap.com/saphelp_nw04s/helpdata/en/67/7e70424edcc553e10000000a1550b0/content.htm
Hope this helps,
Robert

Extending the Federated Search Results

Federated Search
I am looking on how to extend the Search Results in the Federated Search. Right now there is Rank Application icon, title and summary. The search service I have has 4 more columns. What would be the easiest way to extend the number of columns for the search datasource I have.
Anthony Chestnut

Prabhu,
There's no specific docs on this page, but you should be able to customize the federated search results page in the same way as any other portal page. Look for the general documentation on UI customization. You'll probably need to look over the code for the federated search page to see how the search is invoked. The Activityspace you want to customize is called "NetworkSearchAS", and the code is in com.plumtree.portalpages.browsing.search.network (in the portalpages DLL or jar).
Craig

Federated Search Error

Hi, I have developed a few federated search agents against our document management system. The search agents work great, etc, EXCEPT for one glitch. When the search is invoked, the portal contacts the search agent and the search builds the document result set and sends it back, all basic stuff. So, if i get 150 results the page display would show display 1-20 of 150. The problem arises when i click next to get the next set of data. The portal shows me the same 20 dsocuments i was looking at but says 21-40 of 150. Now if I click next and then previous or previous and then next it shows me the correct 21-40 documents and all others are fine. Upon investigsting the issue, I found that the portal was contacting the search agent once to get the search result, but when the user hit next for the first time the portal contacted the search agent again and reran the federated search, but everyother next or previous click after that it did not. Any ideas? it's almost like it forgot that it contacted the search agent the first time. Has anyone experienced this problem or know of a bug. The search agent was built verbatum from Plumtree documentation and even reviewed by Plumtree to no avail :(

What is the soap request saying for the following values? If the number to return is set to 10, for the second request, it should be:
<NumberToSkip >10</NumberToSkip> <MaximumReturn >10</MaximumReturn>
The only (non-bug) reason that NumberToSkip should not be set is if the TotalNumberOfHits was set to less than 10 (or whatever you have set for the number returned).

Federated Search for Documentum

Hi. Has anybody implemented a federated search for Documentum? I think Documentum uses Verity internally for full text indexing, but Verity is tightly integrated with Documentum's own metadata search - does Documentum expose the search functionality as a web service - is there any customization required on this web service (meaning, is it already a SOAP web service that Plumtree understands readily or do we have to write any custom code). Any inputs on implementing federated search for remote search repositories such as Verity, FAST, Autonomy would be helpful?

Hi Bbelko, as Raji mentioned,
Lync Desktop Client cannot search any external source outside your organization.
Nevertheless, Lync Full Client can search against your local Outlook contact lists (only your personal contact and linked contact lists like LinkedIn or Facebook). Additionally, Lync is generating its own Address Book (ABS) which it can search against. You
can modify in Lync how the service should generate the address book, based on the GAL. GAL here does NOT mean the Exchange GAL, instead it is the Active Directory. It only queries information based on Exchange attributes.
http://technet.microsoft.com/en-us/library/gg429711.aspx
How this helps understanding how the service is working via the User Replicator.
Federated contacts can be therefor also only maintained in AD.
Thomas
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Federated Searches from the Basic Search Box

Is there a way to have the portal's basic search facility perform a federated search without having to visit the federated search page? We would like our users to be able to search any location from the simple search box.

Is there a way to have the portal's basic search facility perform a federated search without having to visit the federated search page? We would like our users to be able to search any location from the simple search box.

Federated Search Error - Hello World Sample

Hello,
I am trying to setup a Federated Search using the example HelloWorldSearch.war (java version). I am relatively new to the Portal Technology, but have extensive experience in web app development.
I am getting an error when I try to run my Federated Search. "Error - Error executing search on Test Federated Search : Federated search of federated portal object 200 could not be executed. The federated portal may be configured incorrectly." Any Ideas?
I have created 3 Portal Objects:
1) Remote Server - this points to my Tomcat instance - http://msc_tesposito1:8080/
2) Search Web Service - which points to app/service. I have specified "HelloWorldSearch/services/SearchProviderSoapBinding" and linked it to my Remote Server Instance.
3) Federated Search - linked this to my Search Web Service.
I then took the HelloWorldSearch-Java.war file from the samples provided, renamed it to HelloWorldSearch.war and dropped it in my Tomcat webapps directory. I can hit the web service just fine by executing "http://msc_tesposito1:8080/HelloWorldSearch/services/SearchProviderSoapBinding".
Does anyone have any ideas as to what I might be able to do to get this working?
Tom Esposito
Manheim, Inc.
www.manheim.com

It works fine on my local tomcat. All this search returns is - "Place holder" string, it's harcoded there.
It seems you have registered exemple by manual. Try use migration tool - ...\plumtree\ptportal\5.0\bin\native\ptmigration.bat
As soon as migration(import) is done all you need to do is change url to your actual remote server

Federated Search

Hi
Any one have idea, how federated search can be implemented.
I have searched in SDN and SAP help.
If any one have screen shots or code samples please send me.
regards,
Bala

hi bala
u cn refer to this links
Configuration of Federated Search
http://help.sap.com/saphelp_nw70/helpdata/en/44/5802b4a1293673e10000000a114a6b/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/44/64a254b9da4ddee10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/44/58bd7ab6684ddee10000000a1553f7/frameset.htm
regards
bhargava

Analytic and federated search

Is there anyway to get analytic server to collect data on federated searches? We have a custom search that uses federated search and we need to collect search terms...
Ray

1-cost should be determined by your license
2-read everything about TREX here:
https://websmp205.sap-ag.de/EP60HOWTOGUIDES (you'll need your SAP service market place ID and password)
if you don't have one, try this resource:
http://help.sap.com/bestpractices/crossindustry/enterpriseportal/v160/html/how-to_guides.htm
hope this helps

Federated Search - Native Exception: Access is denied

Hi,
I created a Search Web Service and the corresponding Search web service and Outgoing Federated Object to use it. The service works as long as I'm logged into the Portal, but it fails for the Guest user, displaying the following error:
Error executing search on Part Search : Native exception: Access is denied. (0x80070005): [Permission to open object with ID 1 and class ID 3 denied.] (428,PTDispatch.cpp)
I've searched the Discussion Forum and Support center, but I can't find the cause of this problem, nor a solution.
Does anyone know what this error may be referring to and how to fix it?
Thanks,
Jose

Shawn,
Even though you map a network drive, it still remains as a logical drive(accessed using NETBEIU protocol) and you may not be able to use File commands on the network based drives. So I would suggest u to use a BufferedInputStream.

UltraSearch - federated search

Similar Messages

Maybe you are looking for