Monthly Archives: March 2008

Determine FAST QRServer Port

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:



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




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

2. Use this code similar to the following to instantiate a connection to FAST:

     ISearchFactory searchFactory;
        NameValueCollection nameValueCollection = new 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. If you pick a wildly incorrect port, you get a helpful error message:


4. However, if you pick the port number listed on the overview (15102) you don’t get that helpful error message.  Instead, later when you try to access any data via a search or reference a FAST view, 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 Tags:

Subscribe to my blog.

Towards SharePoint Technical Design Patterns: SharePoint Designer Workflow + Event Receiver = High Potency Cocktail

One of the emerging patterns I find in crafting SharePoint solutions leverages SharePoint Designer workflow and an event receiver.

Here is a business scenario to put it in context:

  • I upload a document to a doc lib.
  • I kick off multi-step workflow created using SharePoint Designer.
  • At some point during that process, 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.  However, 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" action), 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.

In the end, 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.


Subscribe to my blog.

Observed Behavior: Moving SPD Workflows Within a Site Collection


UPDATE: I’ve been researching how to embed a SPD workflow into a site definition.  This MSDN forum chain has some interesting information.  It’s not conclusive, but points to path through the jungle.

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.

People are often asking / wondering / fretting over moving SPD workflows from one place to another.  Today, I followed these steps and made these observations:

  • I created a workflow using SharePoint Designer in a site attached to a document library.
  • The associated document library already housed several documents.
  • I saved the site as a template.
  • When I saved the site as a template, I saved the content as well.
  • I created a new site in the same site collection using that template.

At this point, 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.

This time, it worked fine.

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 me your SharePoint Designer migration story.  I’ll gladly update this posting with any insights thus offered.


Subscribe to my blog.

Technorati Tags:

Quick and Simple: Workflow-only 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. 

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

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


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

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


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


Subscribe to my blog.

Sunday Funny: “I Thought This Was Supposed to Be a Rich Town”

A little over three years ago, my wife and I signed my son up for a summer activity, 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.  So, in order to overcome his natural reluctance, we told him early and did our best to make it sound like fun, etc.  Even with a multi-month advertising campaign, he still wasn’t convinced.  We forced him to do, though, 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.  But, 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.  In the mean time, he’s finally convinced us he really 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, its schools offer more programs for the kids, etc.  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 prime nights for sleep overs!"  Stage Right was going to interfere with his weekend socials. 

The day comes, we bring him there and drop him off and as with everything else, his natural love of just being alive took over and he’s been having a good time with it.

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".  However, it turns out he was.


Subscribe to my blog.

Technorati Tags:

SharePoint Does Not Provide Calendar Roll-ups; Potential Solutions

UPDATE: An anonymous person in the comments posts this link:

Forum users often ask a question like this:

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

Is WSS 3.0 or MOSS 2007, it is not possible to directly configure a "roll-up" calendar.  Calendars exist on their own, independent of any other calendar.

To create a roll-up calendar, follow one of these paths:

  1. Use a Content Query Web Part.  This is the easiest solution for MOSS users (WSS does not provide CQWP).  CQWP, unfortunately, does not provide a calendar view of data out of the box.  It does provide enormous rendering flexibility (see here for one example) but by default, shows its results in simple list format.  In many cases, CQWP probably a good choice.
  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 and MOSS.

There are probably other clever solutions to this problem.  If you have one or know of one, please leave a comment or email me and I will update this post.


Technorati Tags: ,

Subscribe to my blog.

Create Sites (SPWeb) via SharePoint Designer Workflow

This blog entry is more of an "in the realm of the possible" entry vs. concrete 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 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.


 Subscribe to my blog.

Technorati Tags: ,

Quick and Simple: Provision a Web Site Using SharePoint Object Model In C#

I tried searching for a little snippet code that would show how I can create a new SPWeb in a site collection.  I didn’t find it as quickly or easily as I expected so I thought I’d slap together a little entry on the subject.

This code creates a new Wiki site:

 SPSite siteCollection;

    siteCollection = new SPSite("http://conchang-o9l8qi");

    SPWeb w = siteCollection.OpenWeb();

    w.Webs.Add("xyzzy", "xyzzy Title",
        "xyzzy description", 1033, SPWebTemplate.WebTemplateWIKI, false, false);

My initial searches failed because I was looking for phrases like "provision a web site using sharepoint object model" and the like. 

If you search for "Webs.Add()", you’ll find a number of very useful blog entries, MSDN articles and SDK documentation that go into depth on this subject.  I definitely recommend this site.


 Subscribe to my blog.

Technorati Tags:

Integrate SharePoint Designer Workflows with Web Services

I’ve been playing around with custom actions for SharePoint Designer for some time (see here for some detailed stuff, if that interests you).

In my current project, we need to do some fairly heavy lifting and we want to use declarative SPD workflow to manage the associated business process. 

Long story short, this is entirely possible.  I extended my Codeplex project to invoke a "helper service" and now we can invoke a web service directly from an SPD workflow. 

Here’s the signature:

 public string Dispatcher(
        Guid WebID, // Passed by the runtime environment
        Guid SiteID, // Passed by the runtime environment
        string ListID, // Passed by the RTE (don't know why this is a string, not a GUID)
        int ListItemID, // Passed by the RTE.
        string XmlMessage) // Passed by the user as declared in SPD.

This leverages the fact that we can get at important workflow information, like the site, list ID, etc.  This is well documented in several places for those of you interested in creating your own custom actions.  The idea is to extract the XML string as provided by the user to dispatch an appropriate procedure.  Fun stuff!

Sadly, this is obviously a one-way ticket down to "Loosey Goosey" anti-pattern land, but it’s better than hitting a brick wall 🙂

Is it an anti-pattern if you do it even though you know it’s an anti-pattern?

I hope to wrap this inside Codeplex in the near future.  If you’re interested in me doing so, give me poke (email or leave a comment) and I’ll be that more enthusiastic about doing it 🙂


 Subscribe to my blog.

Technorati Tags: ,

Sunday Funny: “I wonder if your password is …”

I recently bought lunch for my brother (as usual) and we ended up talking about funny things that we did at our respective colleges.  At my alma mater, Lafayette College, the academic support IT department had a very inclusive way about it.  We were given a LOT of rope and I took advantage of that at times.

Two my favorite memories relate to my good friend, Gabe.  He had made the terrible mistake of telling people his freshman year that "I’m a freshman, but I have Sophomore standing" due to the various advanced placement classes he had taken, etc.  Many of us were similarly situated but we didn’t talk about it so much.  His senior year, when we introduced him to people, we’d say "This is Gabe.  He’s a Senior, but he has Sophomore standing".

The college had some Sun workstation/servers running X-Window.  They had gigantic monitors and the engineers used them for CAD and other boring engineer stuff.  We CS people used them to learn programming and, of course, to play games.

We didn’t like the computer-helpless engineers to much so one of our favorite things to do would be to telnet to the box they were on and run X-eye on them.  This would pop up a pair of eyes that followed the mouse around on the screen.  You could pop up even more and have literally a dozen or more of the X-eye applications running.  Try not to laugh out loud when a hapless engineer is trying to close X-eye after X-eye and muttering under his breath about it 🙂

We also played X-trek on those boxes.  To do that, you had to download the source, get various dependencies wherever you could find them and build it.  I wasn’t a sophisticated C programmer, but I could read header files.  I was looking through these and found directives like "#DEFINE MAX_TORPEDO_DISTANCE 10".  I played around with that increase range and power for phases and torpedoes, re-built it and then destroyed Gabe the next time we played.

Gabe was also a huge fan of a TV show called Blake’s 7.  I had never seen it, but that didn’t prevent me from insisting that Dr. Who is the superior show.  The arguments would get heated at times 🙂

One day, it occurred to me that I could probably guess his UNIX password.  I sat down next to him one day and announced in a loud tone, "I’m going to guess your password right now, Gabe."  "Yeah, right" was his answer.  I then logged in, entered his user id, turned to face him, typed and said out loud, "I wonder if it’s B-L-A-K-E-7" ?  Touch typing has never paid off as handsomely as it did that day.

Next week (or soon): More computer room antics from college. 

Do you have any to share?  Leave a comment or email me and I’ll publish them here. 


Subscribe to my blog.

Technorati Tags: