Rápido integración do SharePoint: Código de exemplo para amosar todos os dispoñibles Fast visto

Aquí está o código que mostra as vistas dispoñibles a partir dunha Rápido servidor baseado na chamada Qrserver (o proceso do servidor co cal nos comunicamos). I offer this up to give you all a taste of what it’s like to use the provided FAST API.

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


espazo de nomes Conchango
{
    clase EnumerateFASTViews
    {
        estático invalidar Principal(corda[] args)
        {

            ISearchFactory searchFactory;

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

            Consola.WriteLine("Total Views: [" + searchFactory.GetSearchViewList().Contar + "].");

            int i = 0;

            foreach (obxecto o en searchFactory.GetSearchViewList())
            {
                Consola.WriteLine("View [" + i     + "]: [" + o.ToString() + "].");

            }

            Consola.ReadLine();

        }
    }
}

Teña en conta que eu me considero un mal competente programador C # e eu teño a pel fina, polo que non envíe framboesas meu camiño, especialmente re: the "foreach (o obxecto e …)" construct 🙂

</final>

Technorati Tags: ,

Rexístrate para o meu blog.

Rápido e SharePoint Integración First Look

Eu teño a sorte de ter unha oportunidade de traballar nun rápido <–> Proxecto de integración do SharePoint e pensei en seguir a compartir miña limitada experiencia coa comunidade.

Microsoft está en o proceso de compra Rápido. I don’t know anything about the schedule except that it should be finished in the "2nd quarter" que eu asumo medio polo 06/30/08.

O proxecto do meu proxecto, nun nivel moi alto, chamadas para a creación de algunhas partes da web que teñen máis ou menos o mesmo aspecto, sentir e funcionalidade que a caixa de procura por defecto de Moss e núcleo resultados parte web, 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, pero é evidente para min que algúns dos enxeñeiros rápidas entender claramente MS tecnoloxía (ou que fixeron uso de contratistas).

Rápido:

FAST é un produto de servidor monstro grande (e eu non quero dicir que no mal sentido; Moss é un produto de gran monstro para min tamén). 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, amosa resultados, é grande en relevancia (a pesar de non ver como se encarga de relevancia social,). Con todo, 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, como eu aprender máis.

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.

Parece haber unha interface de servizo web así.

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, non teño tanta certeza se está listo para produción.

That’s it for now. As I progress through the project, Vou publicar máis.

</final>

Technorati Tags: , ,

Rexístrate para o meu blog.

Determinar Rápido qrserver Porto

Para comunicarse co FAST Search través da súa API, necesitamos saber a porta na que o qrserver funciona.

Seguín estes pasos para localízase lo:

  1. Faga o login no sitio web de administración Rápido (http://server:port/admin).
  2. Desprácese ata Xeral do Sistema.
  3. Locate "Search Dispatcher" e prema na icona luneta:

    imaxe

  4. I utilizado con éxito o valor de, 15100 for "Info Name" = "http":

    imaxe

Notas:

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

2. Use este código similar ao seguinte para instanciar unha conexión co FAST:

     ISearchFactory searchFactory;
    
        NameValueCollection NameValueCollection = novo 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. Se incorporarse un porto incontrolado incorrecta, recibe unha mensaxe de erro útil:

imaxe

4. Con todo, se incorporarse o número do porto aparece na visión (15102) you don’t get that helpful error message. Pola, máis tarde, cando tentar acceder aos datos a través dunha busca ou facer referencia a unha visión Rápido, 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".

</final>

Technorati Tags:

Rexístrate para o meu blog.

Rumbo Design Patterns SharePoint técnicos: SharePoint Workflow Design + Receptor de eventos = Cocktail de alta potencia

Un dos patróns emerxentes que atopar na elaboración de solucións SharePoint emprega fluxo de traballo do SharePoint Design e un receptor de eventos.

Aquí está un escenario de negocios para colocar-lo no contexto:

  • Eu enviar un documento a unha biblioteca doc.
  • Eu ban fóra do fluxo de traballo multi-paso creado utilizando o SharePoint Design.
  • Nalgún momento, durante ese proceso, fluxo de traballo asigna unha tarefa a alguén (vía recoller datos de usuario ou asignar unha tarefa).
  • 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.
  • Aquí está o kicker: Quero que a data que impulsa que KPI ser festivo-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. Con todo, 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".
  • Arrincar a falsa.
  • No momento axeitado no fluxo de traballo (e.g. just before the "collect data" acción), asignar ese valor como True.
  • Un ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" adoita teito.
  • Cando o fluxo de traballo atribúe DoCalculateDueDate a verdade, o receptor de eventos calcula a data de caducidade de vacacións-aware.
  • Cando o receptor de eventos fai este cálculo, el define a bandeira DoCalculateDueDate a falsa.

A finais, 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.

</final>

Rexístrate para o meu blog.

Comportamento observado: Movendo fluxos de traballo SPD nunha colección web

Actualización: I’ve been researching how to embed a SPD workflow into a site definition. Esta cadea foro MSDN ten algunhas informacións interesantes. It’s not conclusive, pero apunta camiño a través da selva.

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.

A xente está sempre pregunta / pregunta / fretting over moving SPD workflows from one place to another. Hoxe, Seguín estes pasos e fixo estas observacións:

  • Eu creei un fluxo de traballo mediante o SharePoint Designer nun sitio conectado a unha biblioteca de documentos.
  • A biblioteca de documentos asociados xa abrigou varios documentos.
  • Salvei o sitio web como un modelo.
  • Cando eu salvo a web como un modelo, Salvei o contido ben.
  • Eu creei un novo sitio web no mesmo conxunto de sitios usando este modelo.

Neste punto, 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.

Eu continúe:

  • Inaugurado o sitio no SharePoint Deseño.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • Corre o fluxo de traballo.

Este tempo, funcionou moi ben.

I’ll add that this workflow used the "collect data from user" acción que é unha acción en concepto complexo baixo o capo.

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.

O que significa isto? 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, enteiras novas granxas (e.g. dev ao escenario para cutucar).

Se estás lendo isto e inclinado, por favor engada un comentario ou enviar correo-e me your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</final>

Rexístrate para o meu blog.

Rápido e sinxelo: Workflow-só de actualización campo

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.

Usar un tipo de contido do sitio web / columna para conseguir este efecto.

Crear un tipo de contido coa columna de estado, como se mostra:

imaxe

Note the "Status (a demostración)" campo na parte inferior.

Seguinte, click on the column name to access the column’s properties. Select "Hidden (Non aparecerá en formas)" na sección Configuración da Columna, como se mostra:

imaxe

This removes the field from the standard edit/update forms. Con todo, inda está dispoñible nas vistas, KPIs, o modelo de obxecto e en calquera outro lugar que quere usalo, including SPD workflow.

</final>

Rexístrate para o meu blog.

Domingo divertido: “Eu penso que este era quere que sexa unha cidade rica”

Un pouco máis de tres anos, miña muller e eu asinei o meu fillo de unha actividade de verán, 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.

Eu non sei se o neno de todo o mundo é así, 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. Así, a fin de superar a súa desgana natural, nós dixemos-lle cedo e fixemos o noso mellor para facelo soar como diversión, etc. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, aínda que, e, como é frecuentemente o caso, he had a great time.

No momento en que o segundo ano enroladas en torno, he had once again convinced himself that he didn’t want to participate. Pero, tiñamos o contratou e de día cero, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, estaba moi animado, todos os sorrisos e anunciadas, "O xogo é o Coello de peluche and I want to be the Rabbit". He had spent literally months carrying on (ás veces histericamente) sobre como el non quería ter nada que ver con xogadores do parque e despois do primeiro día, he wants to be the lead role in the play. We’ve seen this pattern before.

(Para a nosa sorpresa, conseguiu o papel de coello e foi sorprendente.)

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. Nese medio tempo, el finalmente convenceu-nos que realmente 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, súas escolas ofrecen máis programas para os nenos, etc. My wife grew up in that town and her parents live there, polo que estamos "viciado de" 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: "Noites de venres primeiro noites de sono Overseas!" Stage Right was going to interfere with his weekend socials.

O día vén, nós trae-lo alí e deixar lo e como todo, o seu amor natural de simplemente estar vivo asumiu e está tendo un bo tempo con el.

Este fin de semana pasado, a miña muller estaba falando con el e por primeira vez, 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: "Eu penso que este era quere que sexa unha cidade rica."

Todos estes anos, I never really thought that he was hearing or understanding anything as it related to the "rich town". Con todo, acontece que foi.

</final>

Rexístrate para o meu blog.

Technorati Tags:

SharePoint Non proporcionar Calendario Roll emerxentes; Solucións posibles

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

Os usuarios do foro moitas veces unha pregunta como esta:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, usuarios en subsites vai crear eventos de calendario, 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 ou Moss 2007, non é posible configurar directamente un "roll-up" calendar. Calendars exist on their own, independente de calquera outro calendario.

Para crear un calendario de roll-up, seguir un destes camiños:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS non ofrece CQWP). CQWP, por desgraza, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (Aquí tes un exemplo) pero por defecto, shows its results in simple list format. In many cases, CQWP probablemente unha boa opción.
  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 e Moss.

There are probably other clever solutions to this problem. If you have one or know of one, por favor, deixe un comentario ou enviar correo-e me e eu vou actualizar este post.

</final>

Rexístrate para o meu blog.

Crear sitios (SPWeb) vía SharePoint Workflow Design

Este blog é unha "no ámbito do posible" entrada vs. información concreta.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Basicamente, os usuarios insiran datos nun cliente novo "" lista personalizada e, a continuación, cando remate e validado o proceso de entrada de datos, necesitamos crear un sitio web para que o cliente.

Eu son un gran fan tanto de fluxo de traballo declarativa, así como un programador de fluxo de traballo feble Visual Studio, entón eu quería atender ao requisito usando o SharePoint Design.

Eu pretendo escribir sobre isto en maior detalle (e espero que presente a un grupo de usuarios ou dous o ano que vén), pero aquí está a solución global:

  • Crear unha acción personalizada que se integra con SPD.
  • A acción personalizada permite SPD para invocar un servizo web e pasalo a cadea XML.
  • Web situada a liña de servizos da lista personalizada e crea un novo sitio web de acordo cos datos para ese novo cliente, usando un personalizado definición web.
  • Servizo web, a continuación, actualiza a lista personalizada con algunhas informacións, como un enlace para o novo sitio web.

Foron consideradas outras abordaxes, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, hai unha morea de código C # con esta solución, pero é acondicionada dentro dun fluxo de traballo declarativa, entón temos algúns dos beneficios do fluxo de traballo declarativa, mentres chamando ao servizo local de creación de.

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.

</final>

Rexístrate para o meu blog.

Technorati Tags: ,