Introduction To K2 WorkFlow:

K2.com : K2 blackpoint Released
K2 have release their new product called blackpoint. This is a very well integrated solution with Microsoft SharePoint products and technologies (WSS 3 and MOSS).
Why might you look at K2 blackpoint over an above just the Workflow Foundation that you get with SharePoint?

• Fast creation and deployment of workflow processes using either the K2 Web Designer (built with Silverlight!) or K2 Studio. (No Code!)
• Amazing integration with SharePoint 2007 with numerous wizard based functions
• Rich options for forms (InfoPath, Form Server, ASP.Net, SharePoint)
• Great user experience for the business users (One task list for all tasks with rich functionality such as out of office, redirect, delegate, bulk actions)
• Data driven workflow (Use SmartObjects to wrap SharePoint data which can help drive your workflow)
• Integrated security model
• Delegated management of processes (Process portals for process managers to manage their processes)
• Reporting
• Enterprise grade server for process execution
Amazing price point! (In my opinion, the time saved building, deploying and managing processes will provide very fast ROI on the cost of K2)
K2.com : K2 blackpoint Overview

Enabling the K2 Features from Central Administration
After installing BlackPearl when I clicked any of the 'Feature' links from the K2 Administration tab in Central Admin, I was getting the following error;
"The site http://:/ could not be found in the Web application SPWebApplication Name=SharePoint - Parent=SPWebService."
I noticed that the reported site was my SSP Administration web application. Because I had this on a different port to MOSS, the only Site Collection is ssp/admin and there is no 'root' site collection. I tried deleting the SSP and web application, and the feature links then started working. I created a new SSP on a different port and it stopped working again. Then I tried adding a blank site collection at the root of the SSP Admin web application and they started working again.
I assume this means that there is an error when the BlackPearl link enumerates the site collections in all of the web applications and it expects there to be a site collection at the root of the web app.
So a work around is to create a blank site collection in the root of your SSP web application. (Or put your SSP in the same web application as your other sites)