FAST SharePoint Pagsasama: Halimbawang Code upang Ipakita ang lahat ng mga magagamit na FAST Pananaw

Mag-iwan ng reply

Narito ang ilang mga code na nagpapakita ng lahat ng magagamit na tanawin mula sa isang FAST server batay sa mga pangalang QRServer (ang proseso ng server na kung saan namin makipag-usap). I offer this up to give you all a taste of what it’s like to use the provided FAST API.

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


namespace Conchango
{
    klase EnumerateFASTViews
    {
        statik walang bisa Pangunahin(pisi[] args)
        {

            ISearchFactory searchFactory;

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

            Mag-aliw.WriteLine("Total Views: [" + searchFactory.GetSearchViewList().Bilangin + "].");

            int i = 0;

            foreach (bagay o sa searchFactory.GetSearchViewList())
            {
                Mag-aliw.WriteLine("View [" + i     + "]: [" + o.ToString() + "].");

            }

            Mag-aliw.ReadLine();

        }
    }
}

Tandaan na isaalang-alang ko ang aking sarili ng bahagya karampatang C # programmer at mayroon akong manipis na balat, kaya huwag magpadala ng anumang mga raspberries aking paraan, lalo na muli: the "foreach (ang bagay at …)" construct 🙂

</dulo>

Technorati Tags: ,

Mag-subscribe sa aking blog.

FAST at SharePoint Pagsasama First Look

Mag-iwan ng reply

Ko pa masuwerteng upang magkaroon ng pagkakataon upang gumana sa isang FAST <–> SharePoint integration proyekto at naisip ko magpatuloy upang ibahagi aking limitadong karanasan sa komunidad.

Microsoft ay sa ang proseso ng pagbili FAST. I don’t know anything about the schedule except that it should be finished in the "2nd quarter" kung saan ipinapalagay ko paraan 06/30/08.

Aking disenyo proyekto, sa isang napakataas na antas, tawag para sa paglikha ng ilang mga bahagi ng web na may halos ang parehong hitsura, pakiramdam at pag-andar tulad ng karaniwang Moss kahon sa paghahanap at mga resulta ng core web bahagi, 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, bagaman ito ay kitang-kita sa akin na ang ilan sa FAST inhinyero malinaw na maunawaan MS tech (o ginawa nila paggamit ng mga kontratista).

FAST:

FAST ay isang malaking produkto halimaw server (at hindi ko ibig sabihin na sa isang masamang pakiramdam; Moss ay isang malaking produkto halimaw sa akin pati na rin). 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, mga palabas sa mga resulta, ay malaki sa kaugnayan (bagaman hindi ko makita kung paano nito pinangangasiwaan panlipunan kaugnayan). Gayunman, 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, bilang ko matuto nang higit pa.

Lumot:

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.

Mukhang isang web interface ng serbisyo pati na rin.

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, hindi kaya sigurado kung ito ay produksyon-handa na.

That’s it for now. As I progress through the project, Kukunin ko mag-post nang higit pa.

</dulo>

Technorati Tags: , ,

Mag-subscribe sa aking blog.

Tukuyin FAST QRServer Port

1 Sumagot

In order to communicate with FAST Search via its API, we need to know the port on which the QRServer is running.

I followed these steps to locate it:

  1. Log into the FAST admin site (http://server:port/admin).
  2. Navigate to System Overview.
  3. Locate "Search Dispatcher" and click the spyglass icon:

    imahen

  4. I successfully used the value, 15100 for "Info Name" = "http":

    imahen

Mga Tala:

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

2. Gamitin ang code na kamukha ng mga sumusunod upang magbigay ng halimbawa ng koneksyon sa FAST:

     ISearchFactory searchFactory;

    NameValueCollection nameValueCollection = bago 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. Kung pumili ka ng isang wildly maling port, kumuha ka ng isang kapaki-pakinabang na mensahe ng error:

imahen

4. Gayunman, kung piliin mo ang port number na nakalista sa pangkalahatang-ideya (15102) you don’t get that helpful error message. Sa halip, mamaya kapag sinusubukan mong i-access ang anumang data sa pamamagitan ng isang paghahanap o banggitin ang isang view ng 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".

</dulo>

Technorati Tags:

Mag-subscribe sa aking blog.

Patungo sa SharePoint Technical Pattern Disenyo: SharePoint Designer workflow + Tatanggap ng Kaganapan = bagsik Cocktail

Mag-iwan ng reply

Ang isa sa mga umuusbong na mga pattern mahanap ako sa crafting solusyon sa SharePoint Pinakikinabangan SharePoint Designer workflow at isang kaganapan receiver.

Narito ang isang negosyo sitwasyon upang ilagay ito sa konteksto:

  • Ako mag-upload ng isang dokumento sa isang doc Lib.
  • Sipain ko off ang multi-hakbang na daloy ng trabaho na nilikha gamit ang SharePoint Designer.
  • Sa ilang mga punto sa panahon ng prosesong iyon, daloy ng trabaho ay nagtatalaga ng isang gawain sa isang tao (sa pamamagitan ng mangolekta ng data mula sa gumagamit o magtalaga ng isang gawain).
  • 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.
  • Narito ang kabayong naninipa: Gusto ko ang mga petsa na nag-mamaneho na KPI na maging 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. Gayunman, 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 ito upang hindi totoo.
  • Sa naaangkop na oras sa daloy ng trabaho (e.g. just before the "collect data" aksyon), magtalaga ng halagang iyon sa True.
  • Isang ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" ay karaniwang hindi totoo.
  • Kapag workflow nagtatalaga DoCalculateDueDate sa true, mga kaganapan receiver kinakalkula ang holiday-aware takdang petsa.
  • Kapag ang kaganapan receiver Ginagawa ito pagkalkula, Nagtatakda ito ang DoCalculateDueDate flag upang hindi totoo.

Sa katapusan, 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.

</dulo>

Mag-subscribe sa aking blog.

Napagmasdang Pag-uugali: Naglilipat ng daloy ng trabaho SPD Sa loob ng isang Collection Site

Mag-iwan ng reply

I-UPDATE: I’ve been researching how to embed a SPD workflow into a site definition. Ito chain MSDN forum ay may ilang mga kagiliw-giliw na impormasyon. It’s not conclusive, ngunit ang mga punto upang path sa loob ng gubat.

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 … maramdamin.

Ang mga tao ay madalas na nagtatanong / nagtataka / fretting over moving SPD workflows from one place to another. Ngayon, Sinundan ko ang mga hakbang na ito at ginawa ang mga obserbasyon:

  • Nilikha ko ang isang daloy ng trabaho gamit ang SharePoint Designer sa isang site na naka-attach sa isang library dokumento.
  • Ang mga kaugnay na library dokumento na matatagpuan ilang mga dokumento.
  • I-save ang site bilang isang template.
  • Kapag ako naka-save na mga site bilang isang template, I-save ang nilalaman pati na rin.
  • Lumikha ako ng bagong site sa parehong koleksyon site gamit ang na template.

Sa puntong ito, 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.

Nagpatuloy ako:

  • Binuksan ang site sa SharePoint Designer.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • Nagpatakbo ako ng workflow.

Oras na ito, ito ay nagtrabaho fine.

I’ll add that this workflow used the "collect data from user" pagkilos na kung saan ay isang medyo kumplikado pagkilos sa ilalim ng 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.

Ano ang ibig sabihin nito? 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, buong bagong mga sakahan (e.g. dev sa entablado upang mag-udyok).

Kung binabasa mo ito at may hilig, paki-post ng komento o email sa akin your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</dulo>

Mag-subscribe sa aking blog.

Technorati Tags:

Mabilis at simpleng: Workflow-lamang Update Field

1 Sumagot

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:

imahen

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

Susunod, 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:

imahen

This removes the field from the standard edit/update forms. Gayunman, ito ay magagamit pa rin sa mga pagtingin, KPI, ang bagay na modelo at kahit saan pa na gusto mong gamitin ito, including SPD workflow.

</dulo>

Mag-subscribe sa aking blog.

Linggo ng nakakatawang: “Naisip ko na ito ay dapat na Maging Rich Town”

1 Sumagot

Ang isang maliit na higit sa tatlong taon na ang nakalipas, aking asawa at ako naka-sign ang aking anak na lalaki up para sa isang aktibidad ng tag-init, 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.

Hindi ko alam kung ang bata sa lahat ng tao ay ganito, 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. Kaya, upang mapaglabanan ang kanyang natural na pag-aatubili, namin sinabi sa kanya ng maaga at ginawa ang aming pinakamahusay na upang gawin itong tunog tulad ng masaya, at iba pa. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, kahit na, at bilang ay madalas na ang kaso, he had a great time.

Sa pamamagitan ng mga oras ng ikalawang taon na pinagsama sa paligid, he had once again convinced himself that he didn’t want to participate. Pero, kami ay naka-sign up sa kanya at sa zero-araw, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, siya ay napaka nasasabik, lahat ng mga smiles at inihayag, "The play is the Velveteen Kuneho and I want to be the Rabbit". He had spent literally months carrying on (minsan hysterically) tungkol sa kung paano hindi niya nais na magkaroon ng kahit ano ang gagawin sa Player Park at pagkatapos ng unang araw, he wants to be the lead role in the play. We’ve seen this pattern before.

(Karamihan sa aming mga sorpresa, ginawa niya makuha ang Kuneho papel at siya ay kagulat-gulat.)

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. Sa Pansamantala, sa wakas siya ay naniwala sa amin siya talaga 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, nitong mga paaralan nag-aalok ng higit pang mga programa para sa mga bata, at iba pa. 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 magbigay-alam gabi para sa pagtulog overs!" Stage Right was going to interfere with his weekend socials.

Ang araw ay, dalhin namin siya doon at i-drop off sa kanya at katulad ng lahat ng iba pa, kanyang natural na pag-ibig ng pagiging lamang buhay kinuha sa ibabaw at siya ay pagkakaroon ng isang magandang panahon na may ito.

Ito nakaraang weekend ang aking asawa ay pakikipag-usap sa kanya at para sa unang pagkakataon, 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."

Lahat ng mga taon, I never really thought that he was hearing or understanding anything as it related to the "rich town". Gayunman, ito lumiliko out siya ay.

</dulo>

Mag-subscribe sa aking blog.

Technorati Tags:

SharePoint ba Hindi Magbigay ng Calendar Roll-ups; Potensyal Solutions

4 tugon

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

Forum mga gumagamit ay madalas na tinatanong ng tanong na tulad nito:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, mga gumagamit sa subsite ay gumawa ng mga kaganapan sa kalendaryo, 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."

Ay WSS 3.0 o Moss 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, independiyenteng ng anumang iba pang mga kalendaryo.

Upang lumikha ng isang roll-up ng kalendaryo, sundin ang isa sa mga path:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS ay hindi nagbibigay ng CQWP). CQWP, sa kasamaang-palad, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (tingnan ang dito para sa isang halimbawa) ngunit sa pamamagitan ng default, shows its results in simple list format. In many cases, CQWP marahil isang magandang pagpipilian.
  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 at Moss.

There are probably other clever solutions to this problem. If you have one or know of one, mangyaring mag-iwan ng komento o email sa akin at ako ay i-update ang post na ito.

</dulo>

Technorati Tags: ,

Mag-subscribe sa aking blog.

Lumikha ng Site (SPWeb) sa pamamagitan ng SharePoint Designer workflow

Mag-iwan ng reply

This blog entry is more of an "in the realm of the possible" entry vs. kongkreto info.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Talaga, users enter data into a "new customer" custom na listahan at pagkatapos ay kapag sila ay tapos na at napatunayan ang proseso ng data entry, kailangan naming gumawa ng isang site na para sa customer.

Ako ay kapwa isang malaking fan ng paturol daloy ng trabaho pati na rin ang isang mahinang visual studio workflow programmer, kaya Nais kong upang matugunan ang mga kinakailangan sa paggamit ng SharePoint Designer.

Plano ko na magsulat tungkol sa mga ito nang mas detalyado (at sana ay naroroon sa isang user group o dalawa sa mga darating na taon), ngunit narito ang pangkalahatang solusyon:

  • Lumikha ng isang pasadyang aksyon na integrates sa SPD.
  • Ang custom action na nagbibigay-daan sa SPD ang magpatakbo ng isang web service at pumasa ito sa isang string ng mga XML.
  • Web serbisyo locates ang hilera sa custom na listahan at lumilikha ng isang bagong site bilang bawat ang data para sa na ang mga bagong client gamit ang custom na kahulugan site.
  • Web serbisyo pagkatapos ay ina-update ng mga custom na listahan ng ilang impormasyon tulad ng isang link sa bagong site.

Namin itinuturing na iba pang mga approach na ito, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, mayroong isang pulutong ng mga C # code na ito sa solusyon, ngunit ito ay nakabalot sa loob ng isang paturol workflow, kaya namin makuha ang ilan sa mga pakinabang ng paturol workflow habang hooking in sa site ng paglikha-serbisyo.

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.

</dulo>

Mag-subscribe sa aking blog.

Technorati Tags: ,