Sylvain Duford has a post where he describes K2.Net and his reaction to a demo of their recent stuff. I agree with Sylvain’s assumptions. I’ve been watching K2.Net for a while now, and I am also very impressed with their stuff. Thay are a very strong complement to BizTalk workflow.
There are other workflow providers who are good partners to Microsoft, such as Captaris-Teamplate. And for some projects, the Human Workflow Services provided within BizTalk is sufficient. Perhaps it is best to consider all three alternatives when determining the best fit for your implementation.
If you have experience with workflow and BizTalk and are looking for someone to talk to about it, send me a note or post a comment here…
David Chappell is the keynote speaker for a pair of events to be held in Bellevue and Portland.
David Chappell keynote in the morning and workshops on specific integration challenges and their solutions based on BizTalk Server 2004. This will be a good one-day introduction to BizTalk Server and its applications. The target audience is developers.
Use the links below to register.
Please don’t hesitate to contact me (firstname.lastname@example.org) if you have any questions about these events.
April 20 – Bellevue, WA
April 21 – Portland, OR
Today’s (March 23rd) issue of the MSDN Flash newsletter (A bi-weekly newsletter for developer news, events, and information) is chock-full of great information. More links to web content than I had noticed before. If you are a developer, you should be registered for this newsletter.
Use this link, (http://go.microsoft.com/?linkid=317027), log on using your Passport account, and then click on “Subscription Center” in the left-hand menu. You can then subscribe to a variety of MSFT newsletters, including MSDN Flash.
Jan Tielen, a .Net Guru from Belgium, has a great blog that has touched a lot on BizTalk Server lately. He posted an entry last month about macros that you can use in the File Send Handler with BizTalk. I wanted to update his list, and to remind you to mark April 2nd on your calendars. April 2nd is when the next revision of the BizTalk Server 2004 documentation will be released to the web. After April 2nd, please download the updated docs from this link. In the meantime, use this list of macros for the Send File Handler.
Coordinated Universal Time (UTC) date time in the format YYYY-MM-DDThhmmss (for example, 1997-07-12T103508).
UTC date time in the format YYYYMMDDhhmmsss, where sss means seconds and milliseconds (for example, 199707121035234 means 1997/07/12, 10:35:23 and 400 milliseconds).
Local date time plus time zone from GMT in the format YYYY-MM-DDThhmmssTZD, (for example, 1997-07-12T103508+800).
Name of the destination party. The value comes from message the context property BTS.DestinationParty.
Identifier of the destination party (GUID). The value comes from the message context property BTS.DestinationPartyID.
Qualifier of the destination party. The value comes from the message context property BTS.DestinationPartyQualifier.
Globally unique identifier (GUID) of the message in BizTalk Server. The value comes directly from the message context property BTS.MessageID.
Name of the file from where the File adapter read the message. The file name includes extension and excludes the file path, for example, foo.xml. When substituting this property, the File adapter extracts the file name from the absolute file path stored in the FILE.ReceivedFileName context property. If the context property does not have a value, for example, if message was received on an adapter other than File adapter, then the macro will not be substituted and will remain in the file name as is (for example, C:Drop%SourceFileName%).
Name of the source party from which the File adapter received the message.
Identifier of the source party (GUID). The value comes from the message context property BTS.SourcePartyID.
Qualifier of the source party from which the File adapter received the message.
UTC time in the format hhmmss.
Local time plus time zone from GMT in the format hhmmssTZD (for example, 124525+530).
Available on MS Downloads.
CMS 2002 actually has a pretty good story in regards to multiple language support. I’d be interested to hear your experiences with CMS and multiple languages. I’ve worked with a few customers on this, and the perception still remains that CMS 2002 is weak in this area. Here are a few items on the subject. Please feel free to comment about your experience or situation.
MCMS supports Unicode and UTF8. The site the end user sees and the web author console are completely localizable.
CMS 2002 SP1a supports English, French, German and Japanese for the core product. This means all documentation, administrative screens, etc. (sorry, no Spanish and no Chinese)
CMS 2002 SP1a authoring connector for word supports:
Simplified Chinese, Traditional Chinese, Dutch, English, French, German, Italian, Japanese, Korean, Portuguese (Brazil), Spanish, and Swedish