Egiten egon naiz nire lehen inoiz online aurkezpena du EMC Abiega marketing makina anfitrioi at 12:00 eguerdi on Asteazkena EDT, 01/28. Ideia ez dago zer hau espero daukat, in terms of attendance. Hala eta guztiz ere, dut, baita punta-puntako, Esan ahal izango dut zer egin duzu denbora galtzen da espero.

I’m going to be describing what we here at EMC mean when we talk about "Enterprise Search." I’m distinguishing between regular old SharePoint Search (hau da, nahiko erabilgarria da berez) eta Enterprise Search, hau da, askoz ere handiagoa da, nastier, interesgarri eta perplexing arazoa konpontzeko.

Argumentua FAST ona duten tresna bat da, berriz, saiatzen Enterprise Search arazoa konpontzeko erabili egin dut (eta analogiak egin dut ubideak egiten naiz berriz,). This obviously ties into SharePoint and will be a part of the community’s fabric over the course of 2009 and beyond. That’s the hook for anyone reading my blog here.

Zu FAST interesa baduzu, Nahikoa informazio baliagarria aurkituko duzu denbora justifikatzeko gastatu niri entzuten horri buruz hitz egiteko, uste dut.

Marketing aurkezpen bat da, baina marketing gauza guztien amaieran, beraz, beti dezakezu jaregin off puntu horretan.

The mighty EMC marketing makina eman dit bat erregistratzeko esteka, beraz, mesedez erabili ezazu erregistratu.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

I had the good fortune of attending some partner training from FAST last spring. I was really impressed with the product and was looking forward to working with it. Zoritxarrez, one project fell through and then EMC acquired my company. Predictably, a certain amount of chaos ensued while we learned about EMC and EMC learned about us. FAST technology dropped a few points on the priority scale during that period. Hala eta guztiz ere, Galduko, inoiz ez dut nire interes produktua eta, are interesgarriagoa, handiagoa arazoa Lokalizatzeko.

Ez dut gustuko hitza, but I’m trying to get used to it 🙂 Despite it’s awkwardness, Lokalizatzeko benetako (edo, gutxienez,, azaleratzen ari diren) term. Do a Live Search Oraindik gehiago teknikoaren definizioak aurkitzeko interesa izanez gero, baina bidea azaldu nuen bulegoan inguruan hau bezalakoa da:

Kapital intelektuala ezin dela aurkitu ahal izango baita, ez da existitzen.

Ia egia da hau esatea:

Kapital intelektuala ezin dela aurkitu azkar eta erraz daiteke, bai eta ez da existitzen.

Kapital intelektuala (IC) starts as an idea in a person’s head and is then refined via collaboration with colleagues and interactions with various communities. To be truly useful, these resulting ideas must be recorded. This is where the trouble begins 🙂

Egun hauetan, Grabaketa normalean esan nahi du ideia hori beti MS Word Doc forma dokumentatua, Excel Workbook, etc. and eventually stuck in electronic format on a hard drive somewhere. IC obviously takes other forms like, irudi bezala, bideoak, oso informativo blogak, orokorra … it’s impossible to list them all. Aldi berean,, IC da leku ugaritan gordetako fitxategi sistema bezala, datu-base, enpresa-aplikazioen line (ERP, CRM, SharePoint, Documentum), etc.

Hau da, Lokalizatzeko arazoa: nola azkar eta erraz aurkituko IC hori dozenaka edo formatu ehunka dozenaka edo ehunka mila batean gordetzen dira, milaka (Lotsa ehunka mila diot) erakunde baten kokaleku?

It’s a difficult problem to solve. Bill English izan da Lokalizatzeko idazten from a very grand perspective in what I have come to think of as the Panama Canal approach. The history of the Panama Canal is amazing. In a nut shell, zoro bat frantziarrak (Ferdinand de Lesseps) hasi enpresa pribatu canal eraikitzeko, proiektua izan zen urte batzuk abandonatu, picked up again and finally finished by the American government under President Roosevelt. This reminds me of Bill’s approach because as he rightly points out, solving the findability is both hard and never stops. It took years and years of effort from the some of the hardest working humans on the planet to start, jarraitu, eta, azkenik, amaitzeko). And yet, it’s still not truly finished. Den neurrian ezagutzen dut, canal en bankuek ez dute inoiz ezagutu bere repose angelu, meaning that they have to be shored up and otherwise maintained even to this day. Solving findability is the same way. I definitely recommend that you read Bill’s series and subscribe to his blog for his point of view on findability, bereziki erlazionatzen SharePoint da.

I too am interested in this problem. Due to my exposure to FAST and on-going discussions on this subject with my brilliant EMC colleagues, I have some more ideas I plan to write about over the coming weeks and months. In my next article on this little series, Eta saiatu jarri kutxa bat arazoaren inguruan nola awful da benetan erakusteko noa (it’s more awful than you think 🙂 ). It’s awful, but at least it does fit inside a box.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Egunean hasten naiz 4 FAST bazkide prestakuntza buru sortu Larry Kaye hemen Needham-en, MA.

5 eguneko saio honetan hautsita behera klaseak sartu (3 eta 2 egun hurrenez hurren) entitled "FAST ESP: Bilaketa pertsonalizatuak Aliantza Bazkideak aplikazioak garatzen dut" and "FAST ESP: Developing Custom Search Applications for Alliance Partners II".

Hau da benetako boot camp mota klase da. Materiala sakon (Oso, oso sakona). Irakaslea (Larry) bere gauzak argi eta garbi daki. I highly recommend this training if you considering it.

</amaiera>

This is a continuation in my FAST coding mini-series for SharePoint folk. The bit of code below executes a search for the term "test" in FAST via a Console application. Obviously, hop-a da, jauzi egin eta salto kanpoan logika hori biltzeko zati bat web orri edo aplikazio barruan:

erabiliz Sistema;
erabiliz System.Collections.Generic;
erabiliz System.Linq;
erabiliz System.Text;
erabiliz System.Collections.Specialized;
erabiliz Com.FastSearch.Esp.Search;
erabiliz Com.FastSearch.Esp.Search.Http;
erabiliz Com.FastSearch.Esp.Search.Navigation;
erabiliz Com.FastSearch.Esp.Search.Query;
erabiliz Com.FastSearch.Esp.Search.Result;
erabiliz Com.FastSearch.Esp.Search.View;
erabiliz System.Collections;

namespace Conchango
{
    klasean InvokeSimpleFASTQuery
    {
        estatiko gal Nagusia(katea[] argumentuak)
        {

            #eskualde Hasieratu gure komunikazio FAST batera
            ISearchFactory searchFactory;

            NameValueCollection nameValueCollection = berria NameValueCollection();

            nameValueCollection.Add("fastsearchengine", "Com.FastSearch.Esp.Search.Http.HttpSearchFactory");
            nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.QRServers", "fastdemoback:15100");
            nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.RequestMethod", "GET");

            searchFactory = SearchFactory.NewInstance(nameValueCollection);

            #endregion

             Abiarazteko kontsulta bat

            katea queryString = "test";

            Kontsulta query = berria Kontsulta(queryString);

            query.SetParameter(BaseParameter.Multzokatzea, faltsuak);
            query.SetParameter(BaseParameter.NABIGAZIO, Egia);
            query.SetParameter(BaseParameter.NAVIGATION_DEEPHITS, 100);

            ISearchView searchView;
            searchView = searchFactory.GetSearchView("sharepointconn");

            IQueryResult emaitza = searchView.Search(kontsulta);

            Kontsolara.WriteLine("Total results from search: [" + result.DocCount + "].");

            int docCounter = 0;

            bitartean (docCounter < result.DocCount)
            {

                docCounter    ;

                IDocumentSummary thisDocSummary = result.GetDocument(docCounter);

                Kontsolara.WriteLine("[" + docCounter + "]: " + thisDocSummary.GetSummaryField("url").Balio katea);

            } // bitartean

            Kontsolara.ReadLine();
            #endregion

        }
    }
}

Honako emaitza sortzen:

</amaiera>

Nire blog Harpidetu.

Hemen kode batzuk erakusten batetik ikusia dago eskuragarri FAST zerbitzaria izeneko oinarritutako QRServer (zerbitzari prozesu dugu komunikatzeko). I offer this up to give you all a taste of what it’s like to use the provided FAST API.

erabiliz Sistema;
erabiliz System.Collections.Generic;
erabiliz System.Linq;
erabiliz System.Text;
erabiliz Com.FastSearch.Esp.Search;
erabiliz Com.FastSearch.Esp.Search.Http;
erabiliz Com.FastSearch.Esp.Search.Navigation;
erabiliz Com.FastSearch.Esp.Search.Query;
erabiliz Com.FastSearch.Esp.Search.Result;
erabiliz Com.FastSearch.Esp.Search.View;
erabiliz System.Collections.Specialized;
erabiliz System.Collections;


namespace Conchango
{
    klasean EnumerateFASTViews
    {
        estatiko gal Nagusia(katea[] argumentuak)
        {

            ISearchFactory searchFactory;

            NameValueCollection nameValueCollection = berria NameValueCollection();

            nameValueCollection.Add("fastsearchengine", "Com.FastSearch.Esp.Search.Http.HttpSearchFactory");
            nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.QRServers", "fastdemoback:15100");
            nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.RequestMethod", "GET");

            searchFactory = SearchFactory.NewInstance(nameValueCollection);

            Kontsolara.WriteLine("Total Views: [" + searchFactory.GetSearchViewList().Diruz + "].");

            int i = 0;

            foreach (objektu o urtean searchFactory.GetSearchViewList())
            {
                Kontsolara.WriteLine("View [" + i     + "]: [" + o.ToString() + "].");

            }

            Kontsolara.ReadLine();

        }
    }
}

Kontuan uste nuen neure burua bat ozta-ozta eskudunak C # programatzaile eta azal daukat, beraz, ez bidali mugurdi edozein nire bidea, batez ere, berriro: the "foreach (objektuaren eta …)" construct 🙂

</amaiera>

Nire blog Harpidetu.

Izan dut zortea aukera bat azkar batean lan egiteko <–> SharePoint integration project and thought I’d continue to share my limited experience with the community.

Microsoft is in the process of purchasing FAST. I don’t know anything about the schedule except that it should be finished in the "2nd quarter" which I assume means by 06/30/08.

My project’s design, at a very high level, calls for creating a few web parts that have roughly the same look, feel and functionality as the standard MOSS search box and core results web part, but pulling from FAST. I’ve made some baby steps in that direction.

FAST is a dedicated search engine. It’s not based on Microsoft technology, though it’s obvious to me that some of the FAST engineers clearly understand MS tech (or they’ve made use of contractors).

FAST:

FAST is a big monster server product (and I don’t mean that in a bad sense; MOSS is a big monster product to me as well). It appears to be based on Java and I noticed some apache stuff and maybe some PHP. I wouldn’t be surprised if there were other bits of tech mixed in here and there. It definitely runs on windows server and is working fine in the virtual environment which I’ve been using.

It makes use of a facade web service that crawls SharePoint content for indexing in its special FAST way.

A SharePoint end user would be pretty much at home with FAST’s user interface. It has simple/advance search, shows results, is big on relevancy (though I don’t see how it handles social relevancy). Hala eta guztiz ere, it does go further. Its stemming seems better. I really can’t articulate it well but I’ll just say "it’s better." You can take my word for it, or not 🙂 I may elaborate on this point in the future, as I learn more.

Moss:

FAST provides a .NET-friendly DLL that provides an interface to the FAST engine. This makes it possible for us to create web parts or application pages or whatever we want to query FAST and present the results.

There seems to be a web service interface as well.

I also have access to a FAST-provided web part that does integrate MOSS and FAST. I don’t know if this is a POC, something that was whipped up as a demo or what. It’s definitely a good learning tool, not so sure if it’s production-ready.

That’s it for now. As I progress through the project, I’ll post more.

</amaiera>

Nire blog Harpidetu.

Ahal izateko, bere API bidez bilatu FAST komunikatu, portuan duen QRServer abian dagoen jakin behar dugu.

Urrats hauek jarraitu nuen hura aurkitu ahal izateko:

1. Admin FAST gune sartu (http://server:port/admin).
2. Sistema Orokorra nabigatu.
3. Locate "Search Dispatcher" eta klik spyglass ikonoa:

   

4. Zuzen erabili dut balioa, 15100 for "Info Name" = "http":

   

Oharrak:

1. Portu 15100 appears to be the default out-of-the-box port number for the QRServer.

2. Erabili kode hau ondorengo antzeko konexio bat instantziatu to FAST:

 ISearchFactory searchFactory;

    NameValueCollection nameValueCollection = berria NameValueCollection();

    nameValueCollection.Add("fastsearchengine", "Com.FastSearch.Esp.Search.Http.HttpSearchFactory");
    nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.QRServers", "fastdemoback:15102");
    nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.RequestMethod", "GET");

    searchFactory = SearchFactory.NewInstance(nameValueCollection);

3. Hautatzen erabateko okerra portu bat bada, bat lagungarria errore mezua lortuko duzu:

4. Hala eta guztiz ere, hautatzen Orokorra zerrendatzen ataka zenbakia bada (15102) you don’t get that helpful error message. Horren ordez, geroago bilaketa baten bidez datuak sartzeko edo FAST ikuspegi erreferentzia saiatu duzu, you get an error. Debugging shows that the searchFactory’s view count is zero. You’ll be given the message "Failed to fetch Search View List".

</amaiera>

Nire blog Harpidetu.