Microsoft Australia looking for Senior BizTalk Consultants

cjwalker — Mon, 11 Jul 2005 01:36:00 GMT

Mitch Denny puts it very nicely... in a nutsehell Microsoft Australia is after a couple of Senior Consultants with strong BizTalk experience for their Canberra and Sydney offices. Check out Mitch's post for details.

Brisbane, Australia - Brisbane BizTalk Community - BrizTalk.org

cjwalker — Sun, 05 Jun 2005 14:52:00 GMT

A new special interest group has been formed for BizTalk users, managers, developers.

If you are a Brisbane local and work with BizTalk please come and join in.

http://www.briztalk.org/

"To identify and unite the expanding community of Microsoft BizTalk Server designers, developers, administrators and users
in the Southeast Queensland area, providing a forum to share knowledge, information and experience."

What is BAM?

cjwalker — Wed, 25 May 2005 08:49:00 GMT

Business Activity Monitoring in BizTalk Server 2004

Basically BAM lets you expose orchestration events and message data for analysis by “information workers” - regular users. A business analyst uses their understanding of the business process to determine data they are interested in (in a spreadsheet). It is probably mostly useful where the orchestration is reasonably complex and/or has long running transactions (ie. a reasonable amount of time between significant business events or “milestones”, such as Received, Approved, Dispatched etc). The developer then “maps” the BA’s data/event items to actual steps in the orchestration and elements in messages. The output of the BA’s work and the developers work is deployed – one part to the Tracking Engine and the other to Analysis Services. You then fire up your system, put some messages through and open up a specially generated Excel spreadsheet (_LiveData.xls) and view the data exposed by the orchestrations & messages. Very cool. I'd encoruage anyone working with BizTalk to take a look at BAM.

A side note - initially I ran into an issue where the BM tool was not generating the <filename>_LiveData.xls file.

When you use a locale setting other than English (United States) while installing the English version of BizTalk Server, your deployment of the Bam.xls file generates an "fnGetString" or "Old format or invalid type library" error.

Solution
Change the computer locale to English (United States) and re-run the bm deploy command at the command prompt.

To change your computer locale to English (United States)
Click Start, click Control Panel, and then click Regional and Language Options.
In the Regional and Language Options dialog, on the Regional Options tab, choose the English (United States) locale from the drop down box, and click OK.

cjwalker's WebLog : BizTalk

Microsoft Australia looking for Senior BizTalk Consultants

Brisbane, Australia - Brisbane BizTalk Community - BrizTalk.org

What is BAM?