FAST SharePoint Sameining: Dæmi Code til að sýna allar Laus FAST Views

Skildu eftir skilaboð

Here is some code that shows all available views from a HRATT server based on the named QRServer (the server process with which we communicate). I offer this up to give you all a taste of what it’s like to use the provided FAST API.

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


namespace Conchango
{
    flokki EnumerateFASTViews
    {
        truflanir ógilt Main(band[] args)
        {

            ISearchFactory searchFactory;

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

            Console.WriteLine("Total Views: [" + searchFactory.GetSearchViewList().Count + "].");

            INT i = 0;

            framhandleggur (mótmæla o í searchFactory.GetSearchViewList())
            {
                Console.WriteLine("View [" + i   + "]: [" + o.ToString() + "].");

            }

            Console.ReadLine();

        }
    }
}

Note that I consider myself a barely competent C# programmer and I have thin skin, so don’t send any raspberries my way, especially re: the "foreach (object o in …)" construct 🙂

</enda>

Technorati Tags: ,

Gerast áskrifandi að bloggið mitt.

Fljótur og SharePoint Sameining First Look

Skildu eftir skilaboð

Ég hef verið heppinn að hafa tækifæri til að vinna á FAST <–> SharePoint sameining verkefni og hélt ég myndi halda áfram að deila Takmörkuð reynsla mín við samfélagið.

Microsoft er í í því að kaupa HRATT. I don’t know anything about the schedule except that it should be finished in the "2nd quarter" sem ég geri ráð leið við 06/30/08.

Verkefnisins míns hönnun, á mjög háu stigi, kallar að búa til nokkrar hluta vefur sem hafa u.þ.b. sama útlit, finnst og virkni eins og the staðall mosa leita kassi og algerlega Niðurstöður 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, þó það er augljóst að mér að sumir af the fljótur verkfræðinga greinilega skilja MS tækni (eða þeir hafa nýtt sér verktaka).

HRATT:

FAST er stór skrímsli framreiðslumaður vara (og ég meina ekki að í vondu skilningi; MOSS er stór skrímsli vöru til mín og). 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, sýnir niðurstöður, er stór á mikilvægi (þó að ég sé ekki hvernig það annast félagslega gildi). Hins, 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, sem ég læri meira.

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.

Það virðist vera þjónusta vefur tengi eins og heilbrigður.

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, ekki svo viss um að ef það er framleiðslu-tilbúinn.

That’s it for now. As I progress through the project, Ég staða meira.

</enda>

Technorati Tags: , ,

Gerast áskrifandi að bloggið mitt.

Ákveða HRATT QRServer höfn

1 Svara

Til þess að samskipti við Fljótur Leita gegnum API, við þurfum að vita hafnar á tré QRServer er í gangi.

Ég fylgdi þessum leiðbeiningum til að finna það:

  1. Skráðu þig inn á the fljótur admin síðuna (http://server:port/admin).
  2. Sigla til System Overview.
  3. Locate "Search Dispatcher" og smelltu á Spyglass táknið:

    mynd

  4. Ég notaði tókst gildi, 15100 for "Info Name" = "http":

    mynd

Skýringar:

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

2. Notaðu þennan kóða svipaðar eftirfarandi að ræst tengingu við FAST:

     ISearchFactory searchFactory;

    NameValueCollection nameValueCollection = ný 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. Ef þú velja stórlega rangt höfn, þú færð gagnlegar villuboð:

mynd

4. Hins, ef þú velur gátt skráð á yfirlitinu (15102) you don’t get that helpful error message. Staðinn, síðar þegar þú reynir að fá aðgang að þeim gögnum um leit eða vísa a fljótur útsýni, 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".

</enda>

Technorati Tags:

Gerast áskrifandi að bloggið mitt.

Undir SharePoint Tæknilegar Patterns Design: SharePoint Designer Vinnuflæði + Atburður Receiver = High Virkni hanastél

Skildu eftir skilaboð

Einn af vaxandi mynstur ég finna í föndur SharePoint lausnir notar SharePoint Designer workflow og atburð móttökutæki.

Hér er fyrirtæki atburðarás tvö setja það í samhengi:

  • Ég senda skjal til læknir lib.
  • Ég sparka burt multi-skref workflow búin til með SharePoint Designer.
  • Á einhverjum tímapunkti á því ferli, workflow assigns a task to someone (via collect data from user or assign a task).
  • 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.
  • Here’s the kicker: I want the date that drives that KPI to be holiday-aware.

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. Hins, 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".
  • Initialize it to false.
  • At the appropriate time in the workflow (e.g. just before the "collect data" aðgerð), assign that value to True.
  • An ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" is normally false.
  • When workflow assigns DoCalculateDueDate to true, the event receiver calculates the holiday-aware due date.
  • When the event receiver does this calculation, it sets the DoCalculateDueDate flag to false.

Í lok, 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.

</enda>

Gerast áskrifandi að bloggið mitt.

Mæld Hegðun: Færa SPD Verkferlar innan vefsvæðis Collection

Skildu eftir skilaboð

UPDATE: I’ve been researching how to embed a SPD workflow into a site definition. Þetta MSDN vettvangur keðja hefur nokkrar áhugaverðar upplýsingar. It’s not conclusive, en bendir á leið í gegnum frumskóginn.

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 … skapstór.

Fólk er oft að spyrja / spá / fretting over moving SPD workflows from one place to another. Í dag, Ég fylgdi þessum leiðbeiningum og gert þessar athuganir:

  • Ég bjó til Workflow nota SharePoint Designer í síðuna fylgir skjal bókasafn.
  • Tilheyrandi skjal bókasafn húsa þegar nokkur skjöl.
  • Ég bjargaði síðuna sem sniðmát.
  • Þegar ég vistað á síðuna sem sniðmát, Ég spara efni og.
  • Ég bjó til nýja síðu í sama staður safn með að sniðmát.

Á þessum tímapunkti, 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.

I continued:

  • Opened the site in SharePoint Designer.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • I ran the workflow.

Í þetta sinn, það í uppnámi fínn.

I’ll add that this workflow used the "collect data from user" action which is a relatively complex action under the hood.

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.

What does this mean? 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, entire new farms (e.g. dev to stage to prod).

If you’re reading this and inclined, please post a comment or email mig your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags:

Fljótleg og einföld: Workflow aðeins Update Field

1 Svara

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.

Use a site content type / column to achieve this effect.

Create a site content type with the status column as shown:

mynd

Note the "Status (for Demo)" field at the bottom.

Næsta, click on the column name to access the column’s properties. Select "Hidden (Will not appear in forms)" in the Column Settings section as shown:

mynd

This removes the field from the standard edit/update forms. Hins, it is still available in views, KPIs, the object model and anywhere else you want to use it, including SPD workflow.

</enda>

Gerast áskrifandi að bloggið mitt.

Sunnudagur Fyndið: “Ég hélt að þetta átti að vera ríkur Town”

1 Svara

Rúmlega þrjú ár síðan, konan mín og ég skráði son minn upp í sumar starfsemi, 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.

Ég veit ekki hvort barn allra er eins og þetta, 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. Svo, í því skyni að sigrast á náttúrulega tregðu hans, Við sögðum honum snemma og gerði okkar besta til að gera það hljóð eins og gaman, o.fl.. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, þó, og eins og er oft raunin, he had a great time.

Með því að næsta ár velti um, he had once again convinced himself that he didn’t want to participate. En, við höfðum skrifað undir hann og á núll-dagur, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, hann var mjög spenntur, allar brosir og tilkynnt, "The play is the Velveteen Kanína and I want to be the Rabbit". He had spent literally months carrying on (stundum hysterically) um hvernig hann vildi ekki hafa neitt að gera með leikmenn Park og eftir fyrsta dag, he wants to be the lead role in the play. We’ve seen this pattern before.

(Mikið að koma á óvart okkar, Hann gerði fá Kanína hlutverk og hann var ótrúlegt.)

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. Í the meðalvegur tími, hann er loksins sannfærður okkur að hann í raun 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, skóla bjóða fleiri forrit fyrir börn, o.fl.. 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 blómi nætur fyrir utanríkis sofa!" Stage Right was going to interfere with his weekend socials.

Í dag kemur, við að koma honum þangað og sleppa honum burt og eins og með allt annað, eðlilegt ást hans bara að vera á lífi tók og hann hefur verið að hafa góðan tíma með það.

Þetta síðasta helgi konan mín var að tala við hann og í fyrsta sinn, 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."

Öll þessi ár, I never really thought that he was hearing or understanding anything as it related to the "rich town". Hins, það kemur í ljós að hann var.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags:

SharePoint veitir ekki Dagatal Roll-ups; Mögulegum lausnum

4 Svör

UPDATE: An anonymous person in the comments posts this link: http://www.atidan.com/atidan-collaboration-kit.php

Spjallborð notendur spyrja oft með spurningu eins og þessa:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, notendur í undirvefsvæðum mun skapa Dagskrá, 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."

Er WSS 3.0 eða Moss 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, óháð öðrum dagbók.

Til að búa til rúlla-upp dagbókina, fylgja eina af þessum leiðum:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS veitir ekki CQWP). CQWP, því miður, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (sjá hér fyrir eitt dæmi) en sjálfgefið, shows its results in simple list format. In many cases, CQWP sennilega gott val.
  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 og Moss.

There are probably other clever solutions to this problem. If you have one or know of one, vinsamlegast eftir umsögn eða email mig og ég mun uppfæra þessa færslu.

</enda>

Gerast áskrifandi að bloggið mitt.

Búa Síður (SPWeb) með SharePoint Designer Workflow

Skildu eftir skilaboð

This blog entry is more of an "in the realm of the possible" færslu vs. steypu upplýsingar.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Grundvallaratriðum, users enter data into a "new customer" Custom lista og svo þegar þeir hafa lokið og staðfest á færslu gögn ferli, við þurfum að búa til síðu fyrir að viðskiptavinur.

Ég er bæði stór aðdáandi af skilgreiningarþekkingar workflow og veikur Visual Studio workflow forritari, svo ég vildi til að mæta kröfum með SharePoint Designer.

Ég ætla að skrifa um þetta í meiri smáatriðum (og vonandi til staðar til notenda hóp eða tveimur á komandi ári), en hér er almennt lausn:

  • Búa til sérsniðnar aðgerðir sem sameinar með SPD.
  • The siðvenja aðgerð gerir SPD að beita vefur þjónustu og gefa það a band af XML.
  • Vefur þjónusta staðsetur róður í sérsniðnum lista og skapar nýja síðu eins og á gögnum um þessi nýju viðskiptavini með sérsniðna síða skilgreiningu.
  • Vefur þjónusta endurnýja þá sérsniðin lista með einhverjum upplýsingum eins og tengil á nýju síðuna.

Við talin önnur aðferðir, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, það er mikið af C # kóða í þessa lausn, en það er vafinn inn í skilgreiningarþekkingar workflow, þannig að við fá sumir af the hagur af skilgreiningarþekkingar workflow en krókur inn á síðuna-sköpun þjónustu.

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.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags: ,