FAST SharePoint Comhtháthú: Cód Samplach chun Taispeáin Gach Fáil Views FAST

Seo roinnt cód a léiríonn go léir tuairimí ar fáil ó FAST freastalaí bunaithe ar an ainmnithe QRServer (an bpróiseas freastalaí lena ndéanaimid cumarsáid). I offer this up to give you all a taste of what it’s like to use the provided FAST API.

ag baint úsáide as Córas;
ag baint úsáide as System.Collections.Generic;
ag baint úsáide as System.Linq;
ag baint úsáide as System.Text;
ag baint úsáide as Com.FastSearch.Esp.Search;
ag baint úsáide as Com.FastSearch.Esp.Search.Http;
ag baint úsáide as Com.FastSearch.Esp.Search.Navigation;
ag baint úsáide as Com.FastSearch.Esp.Search.Query;
ag baint úsáide as Com.FastSearch.Esp.Search.Result;
ag baint úsáide as Com.FastSearch.Esp.Search.View;
ag baint úsáide as System.Collections.Specialized;
ag baint úsáide as System.Collections;


ainmspás Conchango
{
    ranga EnumerateFASTViews
    {
        statach neamhní Príomh-(teaghrán[] comhbhrí leis an rogha)
        {

            ISearchFactory searchFactory;

            NameValueCollection nameValueCollection = nua 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);

            Consól.WriteLine("Total Views: [" + searchFactory.GetSearchViewList().Líon + "].");

            int i = 0;

            foreach (réad o i searchFactory.GetSearchViewList())
            {
                Consól.WriteLine("View [" + i     + "]: [" + o.ToString() + "].");

            }

            Consól.ReadLine();

        }
    }
}

Tabhair faoi deara go mheas mé mé féin ar éigean inniúil C # Ríomhchláraitheoir agus tá mé craiceann tanaí, ní amhlaidh a dhéanamh a sheoladh ar aon sútha craobh mo bhealach, go háirithe maidir le: the "foreach (réad o i …)" construct 🙂

</deireadh>

Clibeanna Technorati: ,

Liostáil le mo bhlag.

FAST agus SharePoint Comhtháthú Féach Chéad

Bainim ádh go mbeadh an deis a bheith ag obair ar a FAST <–> Tionscadal comhtháthú SharePoint agus shíl mhaith liom leanúint ar aghaidh a roinnt mo thaithí theoranta leis an bpobal.

Microsoft Tá i an próiseas a bhaineann le ceannach FAST. I don’t know anything about the schedule except that it should be finished in the "2nd quarter" a glacadh mé bealaí 06/30/08.

Dearadh mo tionscadal ar, ag leibhéal an-ard, glaonna do chruthú codanna ghréasáin cúpla go bhfuil thart ar an cuma céanna, mothú agus feidhmiúlacht mar an bhosca cuardaigh caighdeánach MOSS agus croí-thorthaí chuid gréasáin, 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, cé go bhfuil sé soiléir dom go bhfuil cuid de na innealtóirí FAST thuiscint go soiléir MS ardteicneolaíochta (nó tá siad déanta úsáid a bhaint as conraitheoirí).

FAST:

FAST a táirge freastalaí mór ollphéist (agus ní féidir liom a chiallaíonn go bhfuil sa chiall dona; Is MOSS a táirge monster mór dom chomh maith). 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, Léiríonn torthaí, Is mór ar ábharthacht (cé nach féidir liom a fheiceáil conas plé é ábharthacht shóisialta). Mar sin féin, 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, mar a fhoghlaim mé níos mó.

CAONAIGH:

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.

Tá cosúil le bheith ina sheirbhís comhéadan gréasáin chomh maith.

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, nach bhfuil cinnte mar sin má tá sé a tháirgeadh-réidh.

That’s it for now. As I progress through the project, Feicfidh mé post níos mó.

</deireadh>

Clibeanna Technorati: , ,

Liostáil le mo bhlag.

Socraigh Port QRServer FAST

D'fhonn cumarsáid a dhéanamh le FAST Cuardaigh trína API, is gá dúinn a fhios ag an gcalafort ar a bhfuil an QRServer ag rith.

Lean mé ar na céimeanna a aimsiú dó:

  1. Logáil isteach ar an suíomh admin FAST (http://server:port/admin).
  2. Nascleanúint a dhéanamh Forbhreathnú Córas.
  3. Locate "Search Dispatcher" agus cliceáil ar an deilbhín Spyglass:

    íomhá

  4. Bhain mé úsáid as go rathúil leis an luach, 15100 for "Info Name" = "http":

    íomhá

Nótaí:

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

2. Bain úsáid as an cód cosúil leis an méid seo a leanas le ceangal instantiate a FAST:

     ISearchFactory searchFactory;
    
        NameValueCollection nameValueCollection = nua 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. Má roghnaigh tú port wildly mícheart, fhaigheann tú teachtaireacht earráide cabhrach:

íomhá

4. Mar sin féin, má tá tú ag piocadh an uimhir phoirt atá liostaithe ar an forbhreathnú (15102) you don’t get that helpful error message. Ina áit sin, ina dhiaidh sin nuair iarracht tú a rochtain a fháil ar aon sonraí trí chuardach nó tagairt d'fhonn FAST, 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".

</deireadh>

Clibeanna Technorati:

Liostáil le mo bhlag.

I dTreo SharePoint Patrúin Dearadh Teicniúil: SharePoint Dearthóir Sreabhadh oibre + Glacadóir Teagmhas = Ard Cocktail Potency

Ceann de na patrúin ag teacht chun cinn a aimsiú mé i crafting réitigh SharePoint SharePoint ghiaráil Dearthóir sreabhadh oibre agus glacadóir ócáid.

Seo cás gnó a chur i gcomhthéacs:

  • Mé doiciméad a uaslódáil chuig lib doc.
  • Ciceáil mé amach sreabhadh oibre il-chéim a cruthaíodh ag baint úsáide as SharePoint Dearthóir.
  • Ag pointe éigin i rith an phróisis, sreabhadh oibre shannadh tasc le duine éigin (trí shonraí ó úsáideoirí a bhailiú nó tasc a shannadh).
  • We want to use a KPI to track how long that task is awaiting completion. The KPI shows green for tasks that are completed or due more than 3 days from now. It shows yellow if the task is due tomorrow or today. It shows red if the task is past due.
  • Seo an Kicker: Ba mhaith liom an dáta a thiomáineann an TFB a bheith ar saoire-eolas.

I can’t calculate a holiday-aware due date in SharePoint Designer workflow very easily. I would have to create a custom action or use a 3rd party tool. Mar sin féin, it’s easy enough to calculate such a date in an event receiver. Merge those two together and we get a pattern like this:

  • Define a hidden yes/no site column on the document library labeled "DoCalcualteDueDate".
  • Sé thúsú go bréagach.
  • Ag an am cuí sa sreabhadh oibre (e.g. just before the "collect data" gníomh), luach sin a shannadh do True.
  • An ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" Is é de ghnáth bréagach.
  • Nuair a shannadh sreabhadh oibre DoCalculateDueDate go fíor, Ríomhann an glacadóir ócáid ​​an dáta dlite saoire-eolas.
  • Nuair a dhéanann an glacadóir ócáid ​​seo a ríomh, Leagann sé an bhratach DoCalculateDueDate go bréagach.

Sa deireadh, SPD workflow is communicated with an event receiver via the DoCalculateDueDate semaphore and we have holiday-aware due dates that are assigned at the exactly correct moment in the workflow’s life. SharePoint Designer controls when the due date is assigned but the event receiver performs the actual calculation and assignment.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati: ,

Oibriú Bhreathnaithe: Bogadh sreabhadh oibre SPD Laistigh Bailiúchán Láithreán

Suas chun dáta: I’ve been researching how to embed a SPD workflow into a site definition. Tá roinnt eolais suimiúil an slabhra fóram MSDN. It’s not conclusive, ach pointí chun cosán tríd an jungle.

I’m giving this post a slightly oddball "Observed Behavior" lead since I’m a little leery of drawing conclusions from it. SPD workflows are … temperamental.

Daoine ag iarraidh go minic / wondering / fretting over moving SPD workflows from one place to another. Sa lá atá inniu, Lean mé ar na céimeanna seo agus rinneadh na tuairimí:

  • Chruthaigh mé ag baint úsáide as sreabhadh oibre SharePoint Dearthóir i suíomh gabháil le leabharlann doiciméad.
  • An leabharlann doiciméad gaolmhar lonnaithe cheana féin roinnt cáipéisí.
  • Shábháil mé an suíomh seo mar theimpléad.
  • Nuair a Shábháil mé an suíomh seo mar theimpléad, Shábháil mé an t-ábhar chomh maith.
  • Chruthaigh mé suíomh nua sa bhailiúchán suíomh céanna ag baint úsáide as an teimpléad.

Ag an bpointe seo, I tried to run the workflow. It promptly terminated itself with the log message, "Failed on start".

I expected this. I have low expectations when it comes to moving SPD workflows around.

Lean mé:

  • Osclaíodh an suíomh i SharePoint Dearthóir.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • Rith mé an sreabhadh oibre.

An uair seo, d'oibrigh sé fíneáil.

I’ll add that this workflow used the "collect data from user" ghníomhaíocht a bheadh ​​gníomh sách casta faoi na cochall.

I tentatively conclude that the process of "finishing" the workflow caused SPD to properly associate the SPD workflow with the new document library. I also conclude the XOML and other XML artifacts are reasonably "loose". They are not super tightly coupled to the document library.

Cad a chiallaíonn sé seo? Assuming it’s a reliable and reproducible process, there’s at least one rough method we can use to move them around. I don’t know if this would work if we crossed site collection boundaries or even more drastically, feirmeacha ar fad nua (e.g. dev chuig céim a dtáirgí).

Má tá tú ag léamh seo agus claonta, le do thoil post a comment nó ríomhphost chugam your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati:

Quick agus Simplí: Réimse Nuashonrú-Sreabhadh Oibre amháin

It’s often useful to store status information in a custom list such as an approval code which should never be directly manipulated by end users. This is a common business scenario. I have been working on a project this year that generates various status and reminder dates via SharePoint Designer workflows that then drive KPIs and generally support time-critical business processes.

Bain úsáid as cineál ábhar an tsuímh / colún a bhaint amach i bhfeidhm.

Cruthaigh cineál ábhar an tsuímh leis an gcolún ar stádas mar a thaispeántar:

íomhá

Note the "Status (le haghaidh Demo)" réimse ag bun an leathanaigh.

Ar Aghaidh, click on the column name to access the column’s properties. Select "Hidden (Ní bheidh le feiceáil i bhfoirmeacha)" sa Colún alt Socruithe mar a thaispeántar:

íomhá

This removes the field from the standard edit/update forms. Mar sin féin, Tá sé ar fáil i tuairimí fós, PTF, an tsamhail réad agus in aon áit eile ba mhaith leat é a úsáid, including SPD workflow.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati: ,

Dé Domhnaigh greannmhar: “Thought I seo bhí ceaptha chun bheith ina Baile Rich”

A beag os cionn trí bliana ó shin, mo bhean chéile agus mé ag síniú mo mhac suas ar feadh an tsamhraidh gníomhaíocht, The Midland Park Players. This is a drama group that spends about three or four weeks preparing for a play and then showing it to the parents, friends and relatives. It’s always been done very well.

Níl a fhios agam má tá gach duine leanbh mar seo, but my son is extremely reluctant to try new things. Knowing this, we signed him up for the program. We’ve found that it’s best to alert him to these kinds of things early and often. Mar sin,, d'fhonn a shárú a drogall nádúrtha, dúradh linn dó luath agus rinne ár ndícheall a dhéanamh fuaime sé cosúil le spraoi, etc. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, cé go, agus mar is minic an cás, he had a great time.

Faoin am an dara bliain rollta timpeall, he had once again convinced himself that he didn’t want to participate. Ach, Bhí sínithe againn air suas agus ar náid-lá, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, bhí sé an-tógtha, gach smiles agus d'fhógair, "The play is the Bheilbhéidín Coinín and I want to be the Rabbit". He had spent literally months carrying on (uaireanta hysterically) faoi ​​conas nach raibh sé ag iarraidh go mbeadh rud ar bith a dhéanamh leis Rannpháirtithe Páirc agus tar éis an chéad lá, he wants to be the lead role in the play. We’ve seen this pattern before.

(I bhfad chun ár n-iontas, rinne sé an ról Coinín a fháil agus bhí sé iontach.)

Fast forward a few years. He’s been in Park Players three times now, so he’s something of a veteran. This summer (2008), Players starts up again. Idir an dá linn, tá sé cinnte ar deireadh dúinn sé i ndáiríre doesn’t want to play soccer and he never liked basketball. That left him with no extra-curricular activities for late Winter / early Spring. A client with whom I was working mentioned that his daughter was in a program called Stage Right. Stage right is a slightly more expensive version of Park Players and it’s not in my town, but adjacent to it. Perfect.

The thing to know about that town is that it’s practically another country in terms of wealth. It has a high-frequency train right to Wall Street and NYC in general. It’s just a wealthy place. One of the on-going family discussion themes is whether we should have moved to that town instead of where we live now. It’s a bigger town, ar fáil dá scoileanna cláir níos mó do na páistí, etc. My wife grew up in that town and her parents live there, so we are "hooked in" despite not living there. I personally grew up in different circumstances in Massachusetts, so I don’t have a lot to say about this during family dinner conversation. This isn’t to say that we aren’t very happy where we live. We just know that that town is a level above our town economically.

Stage Right’s next program started too soon for us to launch our normal advertising campaign to overcome my son’s reluctance. This is when he came up with one my personal favorite arguments against doing something: "Friday nights are príomh- oíche Táthcheangail codlata!" Stage Right was going to interfere with his weekend socials.

Tagann an lá, a thabhairt dúinn chuige ann dó titim amach agus mar atá le gach rud eile, a ghrá nádúrtha díreach a bheith beo agus ghlac sé ar a bhfuil dea-am a bhfuil sé.

An deireadh seachtaine seo caite bhí mo bhean ag caint dó agus don chéad uair, I think he’s tailoring his discussions very precisely for his audience. She had asked him how Stage Right compares to Midland Park Players. He tells her that "In Park Players, we have teenagers that help us out. There aren’t any in in Stage Right. In Park Players, teenagers make all props. In Stage Right, we have to bring our own props. We have to do everything. And then he twists the knife: "I thought this was supposed to be a rich town."

Gach na bliana, I never really thought that he was hearing or understanding anything as it related to the "rich town". Mar sin féin, casadh sé amach go raibh sé.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati:

SharePoint nach soláthraíonn Féilire Roll-ups; Solutions Féideartha

Suas chun dáta: An anonymous person in the comments posts this link: http://www.atidan.com/atidan-collaboration-kit.php

Fóram úsáideoirí a iarraidh go minic ceist mar seo:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, Beidh úsáideoirí in subsites chruthú imeachtaí féilire, and will have the option of marking them as ‘public.’ Events marked as public will dynamically appear in the shared site calendar. Thus the shared site calendar is a roll-up of all public events from all subsite calendars."

An bhfuil SSU 3.0 nó CAONAIGH 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, neamhspleách ar aon féilire eile.

Chun a chruthú féilire rolla-suas, leanúint ar cheann de na cosáin:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (Ní SSU a chur ar fáil CQWP). CQWP, ar an drochuair, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (féach anseo le haghaidh sampla amháin) ach de réir réamhshocraithe, shows its results in simple list format. In many cases, CQWP is dócha go bhfuil rogha maith.
  2. A more programming-oriented solution would be to use event receivers. Implement event receivers on the subsite calendars that keep their public events in sync with the master calendar. As a given subsite calendar is modified, reach out to the master calendar and update it as needed. This option is available in both WSS 3.0 agus CAONAIGH.

There are probably other clever solutions to this problem. If you have one or know of one, fág nóta nó thoil ríomhphost chugam agus beidh mé cothrom le dáta an bpost.

</deireadh>

Liostáil le mo bhlag.

Láithreáin Cruthaigh (SPWeb) via Sreabhadh Oibre Dearthóir SharePoint

This blog entry is more of an "in the realm of the possible" iontráil vs. info coincréite.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Go bunúsach, users enter data into a "new customer" liosta saincheaptha agus ansin nuair a bhí siad an próiseas iontrála sonraí críochnaithe agus bailíochtaithe, ní mór dúinn a chruthú suíomh don chustaiméir.

Tá mé an dá lucht leanúna mór de sreabhadh oibre declarative chomh maith mar ríomhchláraitheoir sreabhadh oibre stiúideo amhairc lag, mar sin bhí mé chun freastal ar an riachtanas ag baint úsáide as SharePoint Dearthóir.

Intinn agam a scríobh faoi seo go mion (agus tá súil againn i láthair do ghrúpa úsáideora nó dhó sa bhliain atá romhainn), ach anseo tá an réiteach foriomlán:

  • Cruthaigh gníomh saincheaptha a chomhtháthaíonn leis an SPD.
  • Ceadaíonn an gníomh saincheaptha SPD chun seirbhís gréasáin a agairt agus é a chur ar shraith de XML.
  • Locates seirbhís Gréasáin an tsraith ar an liosta saincheaptha agus go gcruthaíonn sé suíomh nua de réir na sonraí don chliant nua ag baint úsáide as sainmhíniú láithreán saincheaptha.
  • Seirbhís Gréasáin nuashonrú ansin an liosta saincheaptha le roinnt eolais cosúil le nasc go dtí an suíomh nua.

Mheas againn cur chuige eile, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, níl a lán de C # ZIP sa réiteach seo, ach tá sé fillte taobh istigh de sreabhadh oibre declarative, mar sin a fháil againn roinnt de na buntáistí a bhaineann le sreabhadh oibre declarative agus hooking isteach sa tseirbhís site-cruthú.

All we need now is an easy tool to automatically migrate SPD workflows around as easily as we can for visual studio workflows and we’ll really be cooking with gas 🙂 I understand that some folk are out there working on this problem and I hope they have some good success with it soon.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati: ,