You can set this up in Task Scheduler to run every x minutes and send you an email when there are any errors in the Application Event Log or the System Event Log. There is a section in the code where you can create more user-friendly messages for complex or confusing error messages. It also […]
One day, I hope to be able to fully understand and explain the “Ambient Transaction” true/false option in BizTalk WCF-SQL and WCF-Custom send and receive ports. Until then, I’m going to collect the most relevant info and blogs here: The official Microsoft BizTalk parameter definition (for the WCF Send or Receive Port): http://msdn.microsoft.com/en-us/library/dd787981.aspx Specifies whether […]
09/15/2014 14:46:28 Test 09/15/2014 14:47:02 Test 09/15/2014 14:48:02 Test 09/15/2014 14:49:02 Test cls $PSVersionTable $Action1 = New-ScheduledTaskAction -Execute "I:\Scripts\TestClusteredTaskRS.cmd" $Action2 = New-ScheduledTaskAction -Execute "E:\Scripts\TestClusteredTaskCW.cmd" $DurationTimeSpan = New-TimeSpan -Minutes 1 $DurationTimeSpanIndefinite = ([TimeSpan]::MaxValue) $DurationTempTest = New-TimeSpan -Days 1000 $Trigger = New-ScheduledTaskTrigger -Once -At "00:01" -RepetitionInterval $DurationTimeSpan -RepetitionDuration $DurationTimeSpanIndefinite #Register-ScheduledTask -TaskName "RegularCalcTest2" -Action $action #Register-ClusteredScheduledTask -TaskName "CalcTask01" -TaskType […]
Suppose you run this: Get-ClusteredScheduledTask and get this as a result: TaskName TaskType ——– ——– TestClusterWide ClusterWide TestResourceS… ResourceSpecific What a pain. So how do you see the value of the second TaskName above. One idea would be to use names under 12 characters. If you must or do use longer names, here’s one solution: cls […]
Function “IsActiveNode” function IsActiveNode { $activeClusterName = (Get-WMIObject Win32_ComputerSystem -ComputerName BIZTALK2013).Name $computerName = get-content env:computername $message = "ActiveCluster=$activeClusterName computerName=$computerName" $isSame = $false if ($activeClusterName -eq $computerName) { $isSame = $true } $message = $message + " IsSame=$isSame" #Write-Host $message return $isSame } cls $IsActiveNodeResult = IsActiveNode Write-Host "IsActiveNode=$IsActiveNodeResult" Sample test: . .\IsActiveNode.ps1 cls $IsActiveNodeResult […]
No, BizTalk 2013 (nor prior release of BizTalk) do NOT support IBM WebSphere MQ 8.0. We confirmed this with a ticket to Microsoft. What is confusing is the following on Microsoft page: http://msdn.microsoft.com/en-us/library/jj248684%28v=bts.80%29.aspx#BKMK_MQSeries According to current information, supported IBM WebSphere MQ versions in Microsoft BizTalk Server 2013 and 2013 R2 : IBM WebSphere MQ 6.0.2.12 […]