ફાસ્ટ શેરપોઈન્ટ એકત્રિકરણ: બધા ઉપલબ્ધ ફાસ્ટ જોવાઈ પ્રદર્શિત કરવા નમૂના કોડ

Here is some code that shows all available views from a ફાસ્ટ 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.

નો ઉપયોગ પદ્ધતિ;
નો ઉપયોગ System.Collections.Generic;
નો ઉપયોગ System.Linq;
નો ઉપયોગ System.Text;
નો ઉપયોગ Com.FastSearch.Esp.Search;
નો ઉપયોગ Com.FastSearch.Esp.Search.Http;
નો ઉપયોગ Com.FastSearch.Esp.Search.Navigation;
નો ઉપયોગ Com.FastSearch.Esp.Search.Query;
નો ઉપયોગ Com.FastSearch.Esp.Search.Result;
નો ઉપયોગ Com.FastSearch.Esp.Search.View;
નો ઉપયોગ System.Collections.Specialized;
નો ઉપયોગ System.Collections;


નામસ્થળ Conchango
{
    વર્ગ EnumerateFASTViews
    {
        સ્થિર ગેરમાન્ય મુખ્ય(સ્ટ્રિંગ[] વિકલ્પોલેછે)
        {

            ISearchFactory searchFactory;

            NameValueCollection nameValueCollection = નવું 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);

            કન્સોલ.WriteLine("Total Views: [" + searchFactory.GetSearchViewList().Count + "].");

            ઈન્ i = 0;

            foreach (પદાર્થ શૂન્ય અથવા કશું નહિ માં searchFactory.GetSearchViewList())
            {
                કન્સોલ.WriteLine("View [" + i   + "]: [" + o.ToString() + "].");

            }

            કન્સોલ.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 🙂

</અંત>

Technorati ટૅગ્સ: ,

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

ઝડપી અને શેરપોઈન્ટ એકત્રિકરણ પ્રથમ દૃષ્ટિ

I’ve been lucky to have an opportunity to work on a FAST <–> SharePoint integration project and thought I’d continue to share my limited experience with the community.

Microsoft is in the process of purchasing ફાસ્ટ. 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 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). તેમ છતાં, 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.

શેવાળ:

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.

</અંત>

Technorati ટૅગ્સ: , ,

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

ફાસ્ટ QRServer પોર્ટ નક્કી

તેના API દ્વારા ઝડપી શોધો સાથે વાતચીત કરવા માટે, અમે QRServer ચાલી રહ્યું છે જેના પર પોર્ટ જાણવાની જરૂર છે.

હું તે સ્થિત કરવા માટે આ પગલાંઓ અનુસરીને:

  1. ઝડપી એડમિન સાઇટ પ્રવેશ કરો (http://server:port/admin).
  2. સિસ્ટમ ઝાંખી શોધખોળ.
  3. Locate "Search Dispatcher" અને spyglass ચિહ્ન પર ક્લિક કરો:

    છબી

  4. હું સફળતાપૂર્વક કિંમત ઉપયોગ, 15100 for "Info Name" = "http":

    છબી

નોંધો:

1. બંદર 15100 appears to be the default out-of-the-box port number for the QRServer.

2. ફાસ્ટ માટે જોડાણ instantiate કરવા નીચેના જેવી જ આ કોડનો ઉપયોગ કરો:

     ISearchFactory searchFactory;
    
        NameValueCollection nameValueCollection = નવું 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. જો તમે જંગલીની જેમ ખોટો પોર્ટ પસંદ નહિં, તમે મદદરૂપ ભૂલ સંદેશો વિચાર:

છબી

4. તેમ છતાં, તમે ઝાંખી પર યાદી થયેલ પોર્ટ નંબર પસંદ જો (15102) you don’t get that helpful error message. ને બદલે, તમે એક શોધ દ્વારા કોઈપણ માહિતી ઍક્સેસ અથવા એક ઝડપી દ્રશ્ય સંદર્ભ પ્રયાસ પછી, 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".

</અંત>

Technorati ટૅગ્સ:

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

શેરપોઈન્ટ ટેકનિકલ ડિઝાઇન પેટર્નસ તરફ: શેરપોઈન્ટ ડિઝાઈનર વર્કફ્લો + ઇવેન્ટ રીસીવર = હાઇ સામર્થ્ય કોકટેલ

હું શેરપોઈન્ટ ઉકેલો કળાનો શોધી ઊભરતાં દાખલાની એક શેરપોઈન્ટ ડિઝાઈનર વર્કફ્લો અને એક ઇવેન્ટ રીસીવર સિંગાપોર.

અહીં સંદર્ભમાં તે મૂકવા માટે એક બિઝનેસ દૃશ્ય છે:

  • હું એક દસ્તાવેજ lib કરવા એક દસ્તાવેજ અપલોડ.
  • શેરપોઈન્ટ ડિઝાઈનર ઉપયોગ કરીને બનાવવામાં હું બંધ જવું બહુ પગલું વર્કફ્લો.
  • તે પ્રક્રિયા દરમિયાન કેટલાક તબક્કે, વર્કફ્લો કોઇ એક કાર્ય સોંપે (વપરાશકર્તા પાસેથી માહિતી એકત્રિત અથવા કાર્ય સોંપવા મારફતે).
  • 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.
  • અહીં આ રીતે Kicker છે: હું KPI રજા-પરિચિત હોવું કે નહીં કે તારીખ માંગો છો.

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. તેમ છતાં, 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".
  • ખોટા તે પ્રારંભ.
  • વર્કફ્લો યોગ્ય સમયે (e.g. just before the "collect data" ક્રિયા), સાચું છે કે કિંમત સોંપી.
  • એક ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" સામાન્ય રીતે ખોટું છે.
  • વર્કફ્લો સાચું DoCalculateDueDate સોંપે છે જ્યારે, ઘટના રીસીવર રજા-પરિચિત કારણે તારીખ ગણતરી.
  • ઘટના રીસીવર આ ગણતરી કરે ત્યારે, તે ખોટા માટે DoCalculateDueDate ધ્વજ સુયોજિત કરે છે.

અંતે, 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.

</અંત>

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

Technorati ટૅગ્સ: ,

નિરિક્ષણ કર્યું બિહેવિયર: એક સાઇટ સંગ્રહ અંદર એસપીડી વર્કફ્લો ખસેડવું

અપડેટ: I’ve been researching how to embed a SPD workflow into a site definition. આ એમએસડીએન ફોરમ સાંકળ કેટલીક રસપ્રદ માહિતી છે. It’s not conclusive, પરંતુ જંગલ મારફતે પાથ નિર્દેશ.

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 … સ્વભાવગત.

લોકો ઘણી વાર કહેતી હોય છે / આશ્ચર્ય / fretting over moving SPD workflows from one place to another. આજ, હું આ પગલાંઓ અનુસરીને અને આ અવલોકનો કરવામાં:

  • હું એક દસ્તાવેજ લાઇબ્રેરી સાથે જોડાયેલ સાઇટ શેરપોઈન્ટ ડિઝાઈનર મદદથી વર્કફ્લો બનાવનાર.
  • સંકળાયેલ દસ્તાવેજ લાઇબ્રેરી પહેલેથી જ કેટલાક દસ્તાવેજો રાખવામાં.
  • હું એક નમૂના તરીકે આ સાઇટ સાચવવામાં.
  • હું એક નમૂના તરીકે આ સાઇટ સાચવવામાં ત્યારે, હું તેમજ સામગ્રી સાચવી.
  • હું કે નમૂનાનો ઉપયોગ કરી સમાન સાઇટ સંગ્રહ એક નવી સાઇટ બનાવનાર.

આ બિંદુએ, 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.

હું ચાલુ રાખ્યું:

  • શેરપોઈન્ટ ડિઝાઈનર માં સાઇટ ખૂલેલા.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • હું વર્કફ્લો ચાલી હતી.

આ સમય, તે દંડ કામ કર્યું.

I’ll add that this workflow used the "collect data from user" હૂડ હેઠળ પ્રમાણમાં જટિલ ક્રિયા છે કે જે ક્રિયા.

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.

આ શું અર્થ છે? 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, સમગ્ર નવા ફાર્મ (e.g. હાંકી કાઢવા માટે યોજવાનો dev).

તમે આ વાંચી અને વળેલું રહ્યાં છો, અથવા એક ટિપ્પણી પોસ્ટ કરો મને ઇમેઇલ your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</અંત>

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

Technorati ટૅગ્સ:

ઝડપી અને સરળ: વર્કફ્લો માત્ર સુધારા ક્ષેત્ર

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.

એક સાઇટ સામગ્રી પ્રકાર વાપરો / આ અસર હાંસલ કરવા માટે સ્તંભ.

બતાવ્યા પ્રમાણે સ્થિતિ સ્તંભ સાથે એક સાઇટ સામગ્રી પ્રકાર બનાવો:

છબી

Note the "Status (ડેમો માટે)" તળિયે ક્ષેત્ર.

આગામી, click on the column name to access the column’s properties. Select "Hidden (સ્વરૂપોમાં દેખાશે નહીં)" બતાવ્યા પ્રમાણે કૉલમ સેટિંગ્સ વિભાગમાં:

છબી

This removes the field from the standard edit/update forms. તેમ છતાં, તે હજુ પણ જોવાયું માં ઉપલબ્ધ છે, KPIs, ઓબ્જેક્ટ મોડેલ અને ક્યાંય તમે તેને વાપરવા માંગો છો, including SPD workflow.

</અંત>

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

Technorati ટૅગ્સ: ,

રવિવાર ફની: “મને લાગ્યું આ શ્રીમંત ટાઉન રહો રહેવા ત્યારે”

પહેલાં એક ઓછી ત્રણ વર્ષો, મારી પત્ની મને અને ઉનાળામાં પ્રવૃત્તિ માટે મારા પુત્ર સાઇન અપ, 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.

I don’t know if everyone’s child is like this, 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. તેથી, in order to overcome his natural reluctance, we told him early and did our best to make it sound like fun, વગેરે. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, છતાં, and as is often the case, he had a great time.

By the time the second year rolled around, he had once again convinced himself that he didn’t want to participate. પરંતુ, we had signed him up and on zero-day, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, he was very excited, all smiles and announced, "The play is the Velveteen Rabbit and I want to be the Rabbit". He had spent literally months carrying on (sometimes hysterically) about how he didn’t want to have anything to do with Park Players and after the first day, he wants to be the lead role in the play. We’ve seen this pattern before.

(Much to our surprise, he did get the Rabbit role and he was amazing.)

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. સરેરાશ સમય, he’s finally convinced us he ખરેખર 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, તેના શાળાઓ બાળકો માટે વધુ કાર્યક્રમો પ્રદાન કરે છે, વગેરે. 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 મૂળ ઊંઘ ઓવરમાં રાત!" Stage Right was going to interfere with his weekend socials.

આ દિવસે આવે છે, આપણે ત્યાં તેને લાવવા અને તેને બંધ મૂકવા અને બીજું બધું સાથે, માત્ર જીવંત છે તેના કુદરતી પ્રેમ સંભાળ્યો અને તે સાથે સારો સમય આવી રહી ગયેલ છે.

This past weekend my wife was talking to him and for the first time, 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."

All these years, I never really thought that he was hearing or understanding anything as it related to the "rich town". તેમ છતાં, it turns out he was.

</અંત>

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

Technorati ટૅગ્સ:

શેરપોઈન્ટ કૅલેન્ડર રોલ અપ્સ પૂરું પાડતું નથી; સંભવિત સોલ્યુશન્સ

અપડેટ: An anonymous person in the comments posts this link: http://www.atidan.com/atidan-collaboration-kit.php

ફોરમ વપરાશકર્તાઓ વારંવાર આ જેમ એક પ્રશ્ન પૂછો:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, subsites વપરાશકર્તાઓ કૅલેન્ડર ઘટનાઓ બનાવશે, 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."

WSS છે 3.0 અથવા MOSS 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, અન્ય કોઈપણ કૅલેન્ડર સ્વતંત્ર.

એક રોલ અપ કૅલેન્ડર બનાવવા માટે, આ પાથ એક અનુસરો:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS CQWP પૂરું પાડતું નથી). CQWP, કમનસીબે, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (એક ઉદાહરણ તરીકે અહીં જુઓ) પરંતુ મૂળભૂત રીતે, shows its results in simple list format. In many cases, કદાચ સારી પસંદગી CQWP.
  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 અને MOSS.

There are probably other clever solutions to this problem. If you have one or know of one, અથવા એક ટિપ્પણી છોડી કૃપા કરીને મને ઇમેઇલ અને હું આ પોસ્ટને અપડેટ કરશે.

</અંત>

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

સાઇટ્સ બનાવો (SPWeb) શેરપોઈન્ટ ડિઝાઈનર વર્કફ્લો મારફતે

This blog entry is more of an "in the realm of the possible" પ્રવેશ vs. કોંક્રિટ માહિતી.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. મૂળભૂત રીતે, users enter data into a "new customer" custom list and then when they have finished and validated the data entry process, we need to create a site for that customer.

I’m both a big fan of declarative workflow as well as a weak visual studio workflow programmer, so I wanted to meet the requirement using SharePoint Designer.

I plan to write about this in greater detail (and hopefully present to a user group or two in the coming year), but here’s the overall solution:

  • Create a custom action that integrates with SPD.
  • The custom action allows SPD to invoke a web service and pass it a string of XML.
  • Web service locates the row in the custom list and creates a new site as per the data for that new client using a custom site definition.
  • Web service then updates the custom list with some information such as a link to the new site.

We considered other approaches, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, there’s a lot of C# code in this solution, but it’s wrapped inside a declarative workflow, so we get some of the benefits of declarative workflow while hooking into the site-creation service.

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.

</અંત>

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

Technorati ટૅગ્સ: ,