We are getting close to the end of another year and this is the right time to do a personal end-of-year review and make some work/life balance. To do some of your own personal planning for the year ahead. What personal goals do you want to achieve over the next 12 months? But also to look back and reflect on what you achieved in this last year. So in the following of one of my previous posts, this is the list of my contributions in the last six months on MSDN Code Gallery and TechNet Gallery.
MSDN Code Gallery is your destination for downloading sample applications and code snippets, as well as sharing your own resources.
List of contributions on MSDN Code Gallery:
- How to Call Orchestrations developed in a different Visual Studio Solution: In the past I developer a demo on “How to Call Orchestration from another project or from another BizTalk Application” (this demo is compose by one Visual Studio Solution with two different projects). However there were a few questions about how we can accomplished that using two different solutions… well is the exact same process, but to help clarify this topic and to better help the community members that placed the questions I decide to create a different demo.
- BizTalk Mapper Extensions UtilityPack for BizTalk Server 2013: New version of BizTalk Mapper Extensions UtilityPack with several useful functoids to include and use it in a map, which will provide an extension of BizTalk Mapper capabilities.
- BizTalk Mapper Extensions UtilityPack for BizTalk Server 2010: New version of BizTalk Mapper Extensions UtilityPack with several useful functoids to include and use it in a map, which will provide an extension of BizTalk Mapper capabilities.
- BizTalk Mapper Extensions UtilityPack for BizTalk Server 2006/2009: New version of BizTalk Mapper Extensions UtilityPack with several useful functoids to include and use it in a map, which will provide an extension of BizTalk Mapper capabilities.
- BizTalk Mapper Patterns: Working with Multiple input messages or joining message: When sending messages from one system to another it is common for the target system to require more information than the source system can provide. This is a common behavior that we all certainly come across in orchestrations.
- BizTalk Mapper Patterns: How to Send Orchestration Variables Into Maps: Basically this can be another example of Content Enricher Pattern that we explain here: BizTalk Mapper Patterns: Working with Multiple input messages or joining messages (Content Enricher Pattern), or you may need to pass orchestration variables into the map to make some transformation logic, in any of the ways, the best way we will accomplished this is to use the same technic explain in the previous demo, i.e., dragging a “Transform Shape” into the orchestration and setting multiple input messages under “Source Transform”.
- BizTalk Mapper Patterns: Working With Multiple Output Messages (Spliting Msgs): Another common pattern is working with multiple output messages or split messages. This technic can also called Content Filter.
- BizTalk Mapper Patterns: Working with Constant Values inside maps: Sometimes we would like to use constant values within a BizTalk map to suppress certain lack of “static” information in the source message which are required in the final message or to supply in elements that don’t change (or rarely change), such as a billing address or a company name. The best use of constant mapping depends on the situation and requirements you are developing against.
List of contributions on TechNet Gallery:
- BizTalk Infrastructure and Solution Overview Samples: Creating documentation is boring and it can be a challenging task. However documentation is an important part on every BizTalk Integration projects or for infrastructures operations management and administration. They will help you in many critical situation and will reduce the time needed to carry out different procedures like finding were the machines are hosted, how many machines your environment have, what are the actors (systems, protocols) in a given solution and so on. This contribution is a list of diagrams samples that you can use in your documentation describing Infrastructure, Solution and Technical overview of your BizTalk Solution/Environment.
- Monitoring Windows Updates and Pending Restarts on the servers using PowerShell: The script will monitor all the servers with Windows Updates ready to be installed, Windows Updates configured to be checked manually or servers that required a reboot. Servers that do not fall under these conditions will not be listed.
- PowerShell to Configure BizTalk Server Host and Host Instances: One of the task that we need to do in all our new BizTalk environment over and over again is creating and configuring the Host, Host Instances and of course the adapter handlers. This PowerShell script will help you to automate this process according to some of the Best Practices.
- Collection of Visio 2013 Stencil for BizTalk Server: New version of Visio 2013 Stencil for BizTalk Server with several modern flat Visio 2013 shapes for representing BizTalk Server physical architectures, Integration architectures or solutions diagrams in Visio 2013.
- Collection of Visio 2010 Stencil for BizTalk Server: New version of Visio 2010 Stencil for BizTalk Server with several modern flat Visio shapes for representing BizTalk Server physical architectures, Integration architectures or solutions diagrams in Visio 2010.
- Enable all the required IIS features for BizTalk Server with PowerShell: Microsoft Internet Information Services (IIS) provides a Web application infrastructure for many BizTalk Server features. BizTalk Server requires IIS for the following features: HTTP adapter, SOAP adapter, Windows SharePoint Services adapter, Secure Sockets Layer (SSL) encryption and BAM Portal. This PowerShell script to help you automate the process of configuring IIS with all the required features for BizTalk Server.