GRAVITER SharePoint Integration: Praesent Morbi Aliquam Codex GRAVITER Views

Hic views aliqua Codicis ostendit ex omnibus praesto INCITATUS server ex nomine QRServer (in qua communicamus cum nibh Vestibulum). I offer this up to give you all a taste of what it’s like to use the provided FAST API.

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


Spatium nominale Conchango
{
    genus EnumerateFASTViews
    {
        static Irrita Main(filum[] args)
        {

            ISearchFactory searchFactory;

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

            Consolandum.WriteLine("Total Views: [" + searchFactory.GetSearchViewList().Numera + "].");

            int i = 0;

            foreach (Obiectum O in searchFactory.GetSearchViewList())
            {
                Consolandum.WriteLine("View [" + i     + "]: [" + o.ToString() + "].");

            }

            Consolandum.ReadLine();

        }
    }
}

Nota quod vix videor a competenti C # programmer habeam et TUNICA, ita non aliquam viam meam raspberries, praesertim re: the "foreach (o in obiecto …)" construct 🙂

</finem>

Technorati Tags: ,

Scribet ad mea blog.

Et ieiunium, et respice primum SharePoint Integration

Felix occasio opus fui ieiunium <–> SharePoint integrationem project et cogitatio malim permanere participem experientia meo limitatum cum communitate.

Microsoft est in emendo processus INCITATUS. I don’t know anything about the schedule except that it should be finished in the "2nd quarter" per quod suppono 06/30/08.

Meo consilio project scriptor, at egregie,, invocet creando paucos telam dure idem partibus inviso, sentiant functionality ut vexillum MUSCUS quaero arca archa et core exitus texuerunt partem, 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, quamquam mihi manifestum est, quod aliqui ex jejunium veniam clare intelligimus MS tech (nec usi sunt Lorem mancipum).

INCITATUS:

Lorem servitore monstrum magnum est jejunium (quod in malo et non; MUSCUS est magnum, tam mihi monstrum productum). 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, consequitur ostendit, est magnus in relevancy (licet non videret quomodo manubria socialis relevancy). Autem, 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, ut mihi magis magísque.

MUSCUS:

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.

Videtur esse muneris interface tam telam.

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 tam certa, si productione parati-.

That’s it for now. As I progress through the project, Ego stipes magis.

</finem>

Technorati Tags: , ,

Scribet ad mea blog.

Determinare GRAVITER QRServer Port

Ut, per eius API communicábo cum ieiunium Quaerere, Scire oportet, quo ex portu currit QRServer.

Secutus est illos gradus collocare:

  1. Log in situ ieiunium admin (http://server:port/admin).
  2. Some Overview System.
  3. Locate "Search Dispatcher" click in icon spyglass:

    imaginem

  4. Ego feliciter usus valor, 15100 for "Info Name" = "http":

    imaginem

Notes:

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

2. Uti huius Codicis similis ad sequentes ad instantiate connexionem ad ieiunium:

     ISearchFactory searchFactory;
    
        NameValueCollection nameValueCollection = novum 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. Si recte colligunt a portu bacchatur, vos adepto a benevolens erroris nuntius:

imaginem

4. Autem, si colligunt prodigium numerus recensentur in overview (15102) you don’t get that helpful error message. Pro, postea cum conantur ut obvius ullus notitia inquisitionem vel per visum Pomponius jejunium, 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".

</finem>

Technorati Tags:

Scribet ad mea blog.

Technical consilium exemplaria ad SharePoint: SharePoint amet Workflow + Maximum eventus Receptor = potentia Cocktail

Unus de emergentes exemplaria invenio in innectis SharePoint solutiones leverages SharePoint Designer workflow, et opus Receptorem.

Hic est a negotio missionis ponerent in context:

  • Ego upload a tabellae ut a doc lib.
  • Ego calcitrare off multi-step usura workflow creavit SharePoint Designer.
  • Ad punctum in quod processus, workflow assignat officium alicui (per colligere notitia de user negotium vel assignare).
  • 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.
  • Hic 'CALCITRO: Volo diem festum esse qui pellit quod KPI-Conscius.

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. Autem, 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".
  • Ut falsum illud Initialize.
  • In tempore opportuno workflow (e.g. just before the "collect data" Actio), quod ad verum valorem assignaret.
  • An ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" falsum est normaliter.
  • Cum workflow assignat veram DoCalculateDueDate, Receptorem Supputat eventus feriae-date debitum conscia.
  • Ubi ad rem facit accipientis Calculo, Nuntium ad hoc ponit falsam DoCalculateDueDate.

In finem, 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.

</finem>

Scribet ad mea blog.

Moribus observatum: Movens SPD Workflows intra Collection Site

UPDATE: I’ve been researching how to embed a SPD workflow into a site definition. Haec forum MSDN catenam notitia aliqua interesting. It’s not conclusive, sed puncta ad viam per truncatis.

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.

Populus saepe interrogat / Mirantes / fretting over moving SPD workflows from one place to another. Hodie, Et ego post hos gradus facti, haec observamus:

  • Workflow creata sum usura a SharePoint Designer in situ attachiatus ad documentum bibliotheca.
  • Bibliothecam jam socius tabellae est tere pluribus documenta.
  • Lorem ipsum dolor sit amet, ut servatum a me.
  • Cum ego, ut salvos situm template, Tam contentus sim salvus.
  • Ego novum situ in eodem collection site usura id template.

Ad hoc, 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.

Dixique:

  • Aperuit in situ SharePoint Designer.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • Cucúrri in workflow.

Hoc tempore, id operato simila.

I’ll add that this workflow used the "collect data from user" Sed actio quae est multiplex secundum actionem sub cucullo.

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.

Quid hoc? 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, Novus omnis firmis (e.g. Dev ad scaenam FODICO).

Si hoc legere scis inclinatus, consectetur adipiscing elit velit vel email me your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</finem>

Scribet ad mea blog.

Technorati Tags:

Vivos et Simplex: Workflow tantum Update Field

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.

Uti typus euismod / agmine consequi effectum.

Partum a situ contentus cum status column type ut ostensum:

imaginem

Note the "Status (nam Demo)" agro ad imum.

Postero, click on the column name to access the column’s properties. Select "Hidden (Non apparent in formis,)" Column Occasus ut ostendo in sectione:

imaginem

This removes the field from the standard edit/update forms. Autem, tamen est available in views, KPIs, et id quod alibi uti velis, including SPD workflow.

</finem>

Scribet ad mea blog.

Dominica Funny: “Suspendisse lacus supponitur esse putabam”

Paulo super tres annos, uxorem et signati mea filius pro a aestate actio, 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.

Nescio si cuivis puero hoc, 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. Ita, ut naturam ipsam vinceret invitus, nos ei mane et fecit optimum ut sonus fun, etc. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, licet, et ut est saepe causa, he had a great time.

Tempus per annum secundum volutabatur, he had once again convinced himself that he didn’t want to participate. Sed, nos signati eum et in nulla hodie, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, erat ipsum excitatur, omnes rident et nuntiatum, "Est fabula in Velveteen Rabbit and I want to be the Rabbit". He had spent literally months carrying on (aliquando hysterically) Quomodo noluit habere cum dies et justo Players, he wants to be the lead role in the play. We’ve seen this pattern before.

(Nostra admiratio, fecit adepto Rabbit munus et erat miris.)

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. Interea, ipse suus tandem persuasum nobis vere 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, eius scholis offerre magis progressio pro haedos, etc. My wife grew up in that town and her parents live there, sic sunt "aduncum 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: "Veneris noctibus sunt prima noctes somno overs!" Stage Right was going to interfere with his weekend socials.

Die venit, ferimus, et ibi eum cædere, et cetera, Amor naturalis est vivere sed valere eros et accepit eam cum tempus.

Volutpat vestibulum dixisset praeterita et primum uxorem, 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: "Ego hanc urbem opulentam ponebatur."

Omnibus annis, I never really thought that he was hearing or understanding anything as it related to the "rich town". Autem, vertit ex erat.

</finem>

Scribet ad mea blog.

Technorati Tags:

SharePoint Non providentes Calendar rotulo-ups; Potentia Solutions

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

Forum users saepe interrogare sicut hoc:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, users in subsites erit creare calendarium eventus, 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."

Est WSS 3.0 vel MUSCUS 2007, est non posse directe configurare a "volumen-usque" calendar. Calendars exist on their own, independens alterius calendarium.

Creare volumen-usque calendarium, sequitur ex his semitas:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS non providere CQWP). CQWP, infeliciter, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (hic enim uno) sed per default, shows its results in simple list format. In many cases, CQWP probabiliter bonum electio.
  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 et MUSCUS.

There are probably other clever solutions to this problem. If you have one or know of one, placere relinquat comment vel email me et update hoc post.

</finem>

Technorati Tags: ,

Scribet ad mea blog.

Creare Sites (SPWeb) per SharePoint amet Workflow

Vestibulum turpis est de "in regnum posset" introitu nobis. concretum info.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Basically, users intrare notitia in "novum Lorem" consuetudinem album et cum consummavi et convalidatur notitia introitu processus, opus ad partum a site quod Lorem.

Sum tam a magnus fan de enuntiativum workflow ut a infirmus visivae Studio workflow programmator, sic voluit ad exigentiam usura SharePoint amet.

EGO intentio scribo hic uberius (Morbi convallis neque et spe praesens annus duo), sed hic altiore solutio:

  • Creare consuetudo actio quod integrates cum SPD.
  • Consuetudinem actio permittit SPD invocare telam ministerium et transire filo XML.
  • Meaning ministerium locat versu in consuetudinem album et creat novum site ut per notitia quod novum client usura consuetudo site definitio.
  • Meaning ministerium ergo updates consuetudinem album cum notitia ut a link ad novum site.

Nos considerari alia aditus, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, Solutio in C # augue mattis wisi, sed suus involvit intus enuntiativum workflow, ita nos aliquam de beneficia enuntiativum workflow dum hooking in site-creationis ministerium.

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.

</finem>

Scribet ad mea blog.

Technorati Tags: ,