To BizTalk and Beyond! https://docs.microsoft.com/archive/blogs/mandi/feed.xml Findings, lessons learned and other stuff... Tue, 16 Jan 2018 20:00:59 GMT en-US hourly 1 BizTalk MSDN links: They're going away. This is your 'heads up' moment. https://docs.microsoft.com/archive/blogs/mandi/biztalk-msdn-links-theyre-going-away-this-is-your-heads-up-moment Tue, 16 Jan 2018 19:54:01 GMT https://blogs.msdn.microsoft.com/mandi/?p=345 Downloadable PDFs All BizTalk 2000 - BizTalk 2010 MSDN documentation links are going to redirect to a downloadable PDF. Meaning, when you click on a BizTalk 2009 link, it redirects to the BizTalk 2009 documentation that is a downloadable PDF on download.microsoft.com. The MSDN links are going away for the following versions:
  • BizTalk 2000
  • BizTalk 2002
  • BizTalk 2004
  • BizTalk 2006 and 2006 R2
  • BizTalk 2009
  • BizTalk 2010
Their content now exists in a PDF file for you to download, and optionally print to give as birthday and anniversary gifts. I know some of you are big fans of the BizTalk 2004 architecture topics. As an FYI, it was suggested to delete the older topics (I'm looking at you BizTalk 2004), but I know from my many conversations with you all that you still rely on these older versions.

Docs.Microsoft.com

All "current" topics are at docs.microsoft.com/BizTalk. The "core" of BizTalk is the same, as it has been since BizTalk 2004. Meaning, we have the same databases, same architecture, mostly the same tools, and so on. The topics that apply to specific versions (BizTalk 2013 and BizTalk 2016) state this in docs, such as Install BizTalk 2013 or BizTalk 2016 prerequisites. Most of the content on docs is in a public GitHub repository, and this includes the BizTalk Server documentation. So when you see something that needs updated, then update it. I review every Pull Request, so know that I got your back. I won't let a change get merged until I know it's fact. For those that embraced this change, I applaud you, and appreciate your pull requests.   Many thanks, Mandi Ohlinger]]> Integration Boot Camp 2017: September 21 - September 22, 2017 https://docs.microsoft.com/archive/blogs/mandi/integration-boot-camp-2017-september-21-september-22-2017 Tue, 18 Jul 2017 22:22:37 GMT https://blogs.msdn.microsoft.com/mandi/?p=325 Integration Boot Camp (formerly known as the BizTalk Boot Camp). As always, it's free, and open to anyone and everyone. With the new features and easier interaction with Azure Services, we have so many new and different things to show. The key technologies in this boot camp are BizTalk Server 2016 Feature Pack 1, Azure Logic Apps, Azure Functions, and much more.

Requirements

  • In-person event; Skype is not offered
  • Laptop: Many discussions include hands-on activities
  • Azure subscription: Azure virtual machines, Logic Apps, and other Azure services require an Azure subscription
  • Non-disclosure agreement (NDA): A non-disclosure agreement (NDA) is required; which is available to sign upon arrival. Many companies already have a NDA with Microsoft. When you register, we’ll confirm if one already exists.
  • Specific requirements will be emailed to all attendees the week of September 11-15, 2017.

Location

Microsoft Corporation 8050 Microsoft Way Charlotte, NC 28273 Bing map  Google map Note: This year's boot camp is in a different building than previous boot camps. When you arrive, check-in is required. If you are driving to the event, car registration is also required (download and complete Vehicle and Customer Registration). Event Time: 8 AM - 4:30 PM EST; The discussions and labs go the entire day, on both days.

Registration

We've had a couple of last minute cancellations. Register at https://www.microsoftevents.com/profile/form/index.cfm?PKformID=0x2347774843c. Attendance is limited. The event is targeted towards a technical audience, including administrators and developers. Registration includes:
  • Attendance both days
  • Breakfast and lunch both days
  • Access to the online Microsoft company store

Agenda

Mandi Ohlinger, Microsoft Welcome & What's coming Discussion & hands-on lab: BizTalk Server 2016, and using some of the new features in Feature Pack 1. Jeff Hollan, Microsoft Discussion & hands-on lab: Introduction to serverless and Azure Event Grid. Build a serverless app end-to-end using Azure Logic Apps, Azure Functions, and Azure Event Grid. Stephen Thomas, Azure MVP Discussion & hands-on lab: Use Logic Apps, and Cognitive Services to monitor for company sentiment. Ashish Bhambani, Microsoft & Gautam Gyanendra, Synegrate Discussion & hands-on lab: B2B message handling using the Enterprise Integration Account. Create an end-to-end B2B supply chain scenario. Sidney Andrews, Azure MVP Discussion & hands-on lab: Logic App automation/deployment with Azure Resource Manager (ARM) templates. Nicholas Hauenstein, Azure MVP Discussion & hands-on lab: Real-world look at enabling Logic Apps connectivity to external services + things. Create a real-world custom connector. Jeff Hollan & Kevin Lam, Microsoft Discussion & hands-on lab: Advanced patterns with Azure Logic Apps, including parallel execution and exception handling.

Hotel

See Hotels_2017 (downloadable word doc) for some recommendations.

Questions

Ask in this post or contact me: mandi dot ohlinger at microsoft dot com.

Integrate 2017 - Redmond

After the Integration Boot Camp, your Microsoft team will be at Integrate 2017 - Redmond. Many thanks, Mandi Ohlinger]]> BizTalk Boot Camp 2016: September 22 - September 23, 2016 https://docs.microsoft.com/archive/blogs/mandi/biztalk-boot-camp-2016 Fri, 29 Jul 2016 18:38:58 GMT https://blogs.msdn.microsoft.com/mandi/?p=265
  • BizTalk Server 2016, what's new, and using the new Logic Apps adapter
  • See how Microsoft Supply Chain is using BizTalk Server and Logic Apps together
  • Creating Logic Apps using commonly-used connectors
  • Using the Logic Apps Tools in Visual Studio
  • Using the Enterprise Integration Pack (EIP) with Logic Apps
  • Connecting to on-prem resources using the Gateway
  • Create a Microsoft Flow
  • API Management
    • The itinerary and hands-on sessions are being created. More specific details will be added as they are finalized.

    Requirements

    • In-person event; Skype is not offered
    • Laptop: Many discussions include hands-on activities
    • Azure subscription: Logic Apps requires an Azure subscription
    • Non-disclosure agreement (NDA): A non-disclosure agreement (NDA) is required; which is available to sign upon arrival. Many companies already have a NDA with Microsoft. When you register, we’ll confirm if one already exists.

    Location

    Microsoft Corporation 8055 Microsoft Way Charlotte, NC 28273 Bing map  Google map Check-in is required. If you are driving to the event, car registration is also required (download and complete Vehicle and Customer Registration). Event Time: 8 AM - 5 PM EST

    Registration

    Register here. Attendance is limited. The event is targeted towards a technical audience, including administrators and developers. Registration includes:
    • Attendance both days
    • Breakfast and lunch both days
    • Access to the Microsoft company store

    Hotel

    Discounted hotel options listed in Hotels (downloadable word doc).

    Questions

    Ask in this post or contact me: mandi dot ohlinger at microsoft dot com. We hope to see you here! Mandi Ohlinger]]>         What's the deal with all these Microsoft "apps" https://docs.microsoft.com/archive/blogs/mandi/whats-the-deal-with-all-these-microsoft-apps Wed, 01 Jun 2016 01:44:15 GMT https://blogs.msdn.microsoft.com/mandi/?p=235 Here's my attempt.

    PowerApps

    Geared toward business analysts and specialists to create apps for mobile devices (excluding Windows phones) using an Office-like experience. No writing code.


    PowerApps has two parts: client (also known internally as Studio) and the service (also known internally as the 'portal'). You install the client on your computer, and use it to create apps. The service (web.powerapps.com) is where you can also create apps, and you create any connections. These "connections" / "data sources" connect to different services, like SalesForce, Wunderlist, GitHub, OneDrive, Office 365, yada yada yada. See this list.


    The client tool is similar to PowerPoint (imo), and has a function bar for expressions similar to Excel. When you go to add a connection, web.powerapps.com automatically opens, and shows you the list of all the connections.


    PowerApps has no direct relationship to Azure or the Azure portal. If you're good with Excel or app creation in general (notice I didn't say app development), you need to checkout PowerApps.


    App Service

    A suite that includes platform services geared toward developers to create web apps, mobile apps, and API apps using different languages, like .Net, NodeJS, and more. App Service is an Azure offering, and therefore uses an Azure subscription and the Azure portal.


    If you previously used Azure websites and mobile services, this is where you belong.


    Logic Apps

    Part of the App Service offering kinda. Geared toward developers and IT pro users.


    It uses the Azure portal to create logic apps using a designer. You create a flow-like experience starting at the top, add different connectors for your "message", and then end your flow at the bottom. Logic apps uses triggers to get a message (to give you an example), and actions to do something with the message (e.g. save to OneDrive).


    If you're a BizTalk user and want to connect your systems or services, this is where you belong. If you want to start creating business-like flows and don't consider yourself a BizTalk person, I encourage you to try logic apps. The user experience is much improved and easier to use compared to previous versions.


    API apps

    Geared toward developers that need to create their own APIs using ASP.Net, C#, Java, Python, and more. Your custom API apps can be consumed by Logic Apps. Go here for more specifics.


    Connectors / Connections / API apps

    Where to begin...  They were originally called "API apps; not be confused with API Apps in App Service. Well, we're now calling these "connectors", even the ones that don't actually "connect", like the BizTalk* connectors (Transform, XML Validator, ...).


    These connectors are based off swagger files. PowerApps, Logic apps, Flow, and soon to be others all use the same swagger file. For example, if you're using the Salesforce connector in Logic apps, and the Salesforce connection in PowerApps, then you are using the exact same Salesforce swagger file. The difference is how the client (Logic apps vs PowerApps vs Flow) exposes the information in the swagger file. In logic apps, we use Triggers and Actions. In PowerApps, we use Functions. They are the same - just different naming.


    Connectors use OAUTH, so you'll need an account and a password to connect.


    BizTalk Services (MABS)

    It was called AppFabric Integration, then it was Service Bus EAI & EDI Labs, then it was called Windows Azure BizTalk Services, and now it's called Microsoft Azure BizTalk Services. If you are considering an Azure solution for your BizTalk applications, then look at Logic Apps.
    ]]>         BizTalk 2010 is officially in Extended Support https://docs.microsoft.com/archive/blogs/mandi/biztalk-2010-is-officially-in-extended-support Wed, 13 Jan 2016 09:14:00 GMT https://blogs.msdn.microsoft.com/mandi/2016/01/13/biztalk-2010-is-officially-in-extended-support/ So what does this mean? I'll tell you.

    If you need help, our support teams are here and will continue to help, until January 2021. So, continue to open those support cases. Here's the 'but'. Cumulative Update 9 is the last update; there are no more bug fixes or updates. There will continue to be security fixes, which are rare in our BizTalk world. Here's some online reading:

    Microsoft Support Lifecycle

    BizTalk Server Product Lifecycle on the TechNet Wiki

     

    For those still using BizTalk Server 2006 and 2006 R2, it's time to upgrade. Extended support ends July 2016. BizTalk Server supported upgrade paths lists the upgrade paths and more.

     

    ]]>         SSIS scripts to help manage BizTalk Server https://docs.microsoft.com/archive/blogs/mandi/ssis-scripts-to-help-manage-biztalk-server Tue, 12 May 2015 14:48:00 GMT https://blogs.msdn.microsoft.com/mandi/2015/05/12/ssis-scripts-to-help-manage-biztalk-server/  

    SSIS package generator for archiving BizTalk BAM activity tables
    When you deploy a BAM activity, the BAM archive SSIS packages are automatically generated. If the activities have millions of row, deploying the BAM activity is slow. This SSIS package replaces the script tasks that create and execute the insert scripts. It replaces them with a data flow task; which improves the performance.

      

    Delete Backup History And Files
    When the Backup BizTalk Server job executes, it creates two files in the backup folder. These folders are not maintained by BizTalk. This SSIS package deletes the backup history and the backup files using parameters you enter.

     

    Run All BAM SSIS Packages
    Looks at all the deployed BAM Activities. Then, it runs the associated packages to ensure the BAMPrimaryImport table is archived.

     

    Got another one? Add it to the comments and I'll add it the blog post.

    ]]>         BizTalk Boot Camp 2015: April 29 – April 30, 2015 https://docs.microsoft.com/archive/blogs/mandi/biztalk-boot-camp-2015-april-29-april-30-2015 Tue, 27 Jan 2015 18:04:00 GMT https://blogs.msdn.microsoft.com/mandi/2015/01/27/biztalk-boot-camp-2015-april-29-april-30-2015/ The BizTalk Boot Camp is a free public technical event that provides a deep-dive into our offerings, including BizTalk Server, Hybrid Solutions with Microsoft Azure, and Azure App Service. In these two days, we demonstrate and discuss advanced topics, including: 

    • Introduce Azure App Service, including creating and consuming existing connectors and API Apps.
    • Show and demonstrate connectors and API Apps in Azure that focus on integration, including the concepts we know (and love) in BizTalk Server.
    • Use SSIS package to help manage BizTalk Server.
    • Automate BizTalk Server build and testing with TFS and/or Team City & Octopus.
    • Show and demonstrate API management with BizTalk Server 2013 R2 using WebHTTP and JSON.
    • Meet, ask questions, and discuss issues/scenarios with some of the Charlotte-based experts in SQL, Azure, SharePoint, IIS and ASP.Net, Windows Azure Pack, TFS, and other Microsoft services.
    • Additional hybrid solutions/projects focusing on BizTalk Server and the cloud.

     

    This is a great opportunity to learn about the BizTalk family of products and services while also learning about common BizTalk issues from the experts.

    The event is targeted towards a BizTalk technical audience, including administrators and developers. 

    Requirements

    • In-Person Event: Lync and Skype are not offered.
    • Laptop: Many discussions include hands-on activities.
    • Non-Disclosure Agreement: To attend, a non-disclosure agreement (NDA) is required; which is available to sign upon arrival. Many companies already have a NDA with Microsoft. When you register, we'll confirm if one already exists.

     

    Location

    Microsoft Corporation

    8055 Microsoft Way

    Charlotte, NC 28273

    Bing Map

    Check-in is required. If you are driving to the event, car registration is also required (download and complete attached form).

     

    Registration

    Registration is now closed. Attendance is Full. To be on the Wait List, register HERE for the BizTalk Boot Camp 2015. Registration includes:

    • Attendance to all discussions
    • Access to the Microsoft company store
    • Breakfast and lunch on Wednesday April 29 and Thursday April 30
    • Welcome dinner at Salsa's on Wednesday April 29

     

    Hotel

    Hampton Inn & Suites Charlotte-Arrowood Rd

    9110 Southern Pine Blvd

    Charlotte, NC 28273

    +1 704-525-3333

    $89 USD per night

    Reservations: https://hamptoninn3.hilton.com/en/hotels/north-carolina/hampton-inn-and-suites-charlotte-arrowood-rd-CLTHSHX/index.html
    Arrival: April 28
    Departure: May 1
    Group Code: LOL

    If making reservation by phone, use code CHXLOL.

    Complimentary shuttle service to/from Microsoft campus, to/from the Charlotte Douglas International Airport (CLT), and anywhere within a 5-mile radius.

    Hilton Garden Inn Charlotte/Ayrsley

    1920 Ayrsley Town Blvd

    Charlotte, NC  28273

    +1 704-970-5000

    $139 USD per night

    Reservations: https://hiltongardeninn.hilton.com/en/gi/groups/personalized/C/CLTAYGI-MIC-20150428/index.jhtml?WT.mc_id=POG

    Complimentary shuttle service to/from Microsoft campus. Hotel is in an area with restaurants within walking distance.

     

     

    Questions 

    Ask in this post or contact me: mandi dot ohlinger at microsoft dot com.

     

    Additional agenda items will be added to this blog as they are finalized. Attendance is limited.

     

    We hope to see you there!

    Mandi Ohlinger

    Vehicle Registration Template.dotx

    ]]>         Integration User Group Webcasts? Sign me up. https://docs.microsoft.com/archive/blogs/mandi/integration-user-group-webcasts-sign-me-up Wed, 07 Jan 2015 15:00:27 GMT https://blogs.msdn.microsoft.com/mandi/2015/01/07/integration-user-group-webcasts-sign-me-up/ When: Starting Monday January 19

    What: https://www.integrationusergroup.com/

    Sign-up: https://www.eventbrite.com/o/integration-user-group-160636640

    The plan is for a one hour webcast covering Microsoft integration content. There are different community speakers, including Microsoft MVPs, leading and participating in these webcasts.

    ]]>         BizTalk Services: Dear MessageSender.exe, we're breaking up https://docs.microsoft.com/archive/blogs/mandi/biztalk-services-dear-messagesender-exe-were-breaking-up Tue, 02 Dec 2014 17:04:00 GMT https://blogs.msdn.microsoft.com/mandi/2014/12/02/biztalk-services-dear-messagesender-exe-were-breaking-up/ While in Redmond for the Integrate 2014 Summit, I took the opportunity to politely ask Sameer to help me with a MessageSender.exe problem. Here's the scenario:

    I created an Azure BizTalk Services project with an XML Bridge and a SQL Server LOB Target. The project built and deployed successfully to my BizTalk Service. When sending a test message with MessageSender.exe, the following error occurred:

    Webexception received while sending the data
    An exception occured: Object reference not set to an instance of an object.

    I used Azure Storage Explorer to connect to my Storage account and review the logs. Now that the problem is fixed (more on that later), these errors may not be relevant. Either way, here are the errors:

    The System event log shows a ServiceBus error that repeats about every 30 seconds:

    PreciseTimeStamp:              11/17/2014 8:35:08 PM
    EventRecordID:                    33465
    Event Data:                            <Trc Code="ServiceBusManagementUnspecified" Cmp="PipelineManagementAsyncResult" Call="PipelineManagementAsyncResult" Prj="Send" TID="479bb845-bde3-401d-97a9-1ae7f38043d0" Msg="Unauthorized request. Token required" Ex="" UTC="2014-11-17T20:35:08.483Z" />

    PreciseTimeStamp:              11/17/2014 8:35:08 PM
    EventRecordID:                    33466
    Event Data:                            ControlEndpoint. RequestId=479bb845-bde3-401d-97a9-1ae7f38043d0_G1. Error=Unauthorized User.

    PreciseTimeStamp:              11/17/2014 8:35:08 PM
    EventRecordID:                    33467
    Event Data:                            <Trc Code="ServiceRegistryProtocolHandlerEndProcessMessageFailure" Cmp="" Call="" Prj="" TID="" Msg="" Ex="Microsoft.Cloud.ServiceBus.Common.Management.Exceptions.ManagementException : Unauthorized request. Token required&#xD;&#xA;&#xD;&#xA;Server stack trace: &#xD;&#xA;  

     

    The Application log shows the same error about every 2 minutes:

    <Trc Code="ServiceBusManagementUnspecified" Cmp="PipelineManagementAsyncResult" Call="PipelineManagementAsyncResult" Prj="Send" TID="a228615c-6724-4438-85d6-0739f942003c" Msg="Unauthorized request. Token required" Ex="" UTC="2014-11-17T22:20:09.079Z" />

     

    And the following error every hour:

    <Trc Code="UsageFailedToInitialize" Cmp="" Call="" Prj="" TID="" Msg="Couldn't download DatacenterInfo.xml from Blob." Ex="Microsoft.Cloud.Common.AzureStorage.StorageClientException : The specified container does not exist.
    ---&gt; System.Net.WebException : The remote server returned an error: (404) Not Found.&#xD;&#xA

     

    So Sameer says, install this:

    1. In my Visual Studio project, go to the Tools menu, and select Extensions and Updates.
    2. Select Online.
    3. In Search, type BizTalk.
    4. Select BizTalk Service Explorer from the list and download/install.

    In Server Explorer, Windows Azure BizTalk Services is listed. You may have to close/reopen Visual Studio for it to display:

     

    Right-click Windows Azure BizTalk Services and click Add BizTalk Service. Enter your deployment name and Access Control values:

     

    Now, send a test message:

    1. Right-click the bridge and select Send Test Message.
    2. In the window, Load your message, and select Send.

    The test message was successfully sent and the SQL table was updated.

     

    Using this tool, you can also debug your message flow:

    1. Right-click the bridge and select Debug.

    2. Enter your Service Bus relay values to open the tool:

    3. Click Load Message and then click Send Message.

    4. The tool steps through the different stages and when a stage completes successfully, green displays:

    5. Click Continue to move through the next stages, reviewing your status and message body as you go. If a stage or pipeline fails, red is displayed. The Tracking events are also listed in Server Explorer:

     

    I don't know why MessageSender returned the error (and continues to error) but BizTalk Service Explorer has my vote. 

     

    ]]>         How to create a Windows Firewall Inbound Rule https://docs.microsoft.com/archive/blogs/mandi/how-to-create-a-windows-firewall-inbound-rule Mon, 03 Nov 2014 15:32:00 GMT https://blogs.msdn.microsoft.com/mandi/2014/11/03/how-to-create-a-windows-firewall-inbound-rule/ When you install the BizTalk Adapter Service (BAS) Runtime, it creates an IIS web site that is bound to TCP port 8080. In most computers, port 8080 isn't opened on the firewall. When you install BAS, you can set any port you like but keep in mind that port 80 is reserved for the default web site. So, don't enter port 80.

    These steps show how to allow connections on TCP port 8080 using Windows Firewall on Windows 7 and Windows 8.

    1. Confirm port 8080 is opened/not opened. Open a command prompt and type: netstat -aon | more. In my sample output, you see that port 8080 is listed in the Local Address column. This means the port is opened:

    2. To open the port, open Windows Firewall:

    • Windows 7: In Start, Search, you can type Windows Firewall. Select Windows Firewall with Advanced Security.
    • Windows 8: In Start, you can type Windows Firewall; which opens the Control Panel -> System and Security -> Windows Firewall. Click Advanced Settings:

    3. In Advanced Settings in the left-hand pane, click Inbound Rules. In the Actions pane on the right, click New Rule:

    4. In the wizard, select Port and click Next:

    5. Check TCP, check Specific local ports, enter 8080, and click Next:

    6. Click Allow the connection and click Next:

    7. Check your networks. In my environment, I checked all options. Click Next:

    8. Enter a rule name and click Finish. My rule name is 8080:

     

    Enjoy!

     

    ]]>