by community-syndication | May 8, 2014 | BizTalk Community Blogs via Syndication
Like any software development company we have identical challenges in managing a development, test and release process. As a growing company we experiment with different tools to improve our processes and delivery quality, for 7.2 we mainly used Asana as our project management tool. BizTalk360 7.2 is an important milestone for us in variety of […]
The post How do we use Asana, Balsamiq and Google Docs to manage BizTalk360 development, test and release process appeared first on BizTalk360 Blog.
Blog Post by: Saravana Kumar
by community-syndication | May 6, 2014 | BizTalk Community Blogs via Syndication
All the BizTalk database which is being backed up by the ‘Backup BizTalk Server’ job, so all databases with the exception of the BAM Star Schema database (BAMStarSchema), has one table called “MarkLog”. These tables are holding all the transaction marks (they are actually timestamps in a string format), set to a specific database, created […]
Blog Post by: Sandro Pereira
by community-syndication | May 5, 2014 | BizTalk Community Blogs via Syndication
We had issues where federated users were continually prompted from their username and password when trying to sync their OneDrive for Business account. Even if you typed the password correctly authentication still failed. We were directed to this KB Article
Our specific problem was resolved by disabling Extended Protection for Authentication, which can be completed via […]
Blog Post by: Dan Fluet
by community-syndication | May 5, 2014 | BizTalk Community Blogs via Syndication
The Web Application Proxy service in Windows Server 2012 can be used to provide pre-authentication and backend authorization to non-claims aware applications published with Integrated Windows Authentication (IWA) using Kerberos for external clients.
by community-syndication | May 2, 2014 | BizTalk Community Blogs via Syndication
The ESB Toolkit has been around for a while but for many BizTalk developers it’s still not entirely clear when you can use it and what the benefits are. The ESB Toolkit is designed to provide the right benefits to cope with complex and rapidly changing integration challenges. Of course, there are also disadvantages and not in every project it’s convenient to use it.
See the following sections to give you an overview of when to use it and what the disadvantages and benefits are.
When to use it
- In the project is a need for Reusable Components, SOA & Agile.
- Often in larger projects is there a need for it.
- The business processes in BizTalk can be divided in Reusable Components.
- It’s required to have NO Downtime when deploying a change.
- The complexity of the business processes that is going to be automated in BizTalk is relatively simple.
- To reduce the amount of Receive Ports or Send Ports in BizTalk.
- Low Latency scenarios.
- You want to expose web services with BizTalk.
Disadvantages
- ESB Toolkit adds complexity to a BizTalk project.
- Little documentation.
- Installation is difficult.
- BizTalk 2009 & BizTalk 2010.
- Management Portal can be difficult to install.
- It’s not fully functional out of the box.
- Instead it provides a base set of ESB components that must be extended.
- Management Portal is sample.
- Performance.
- Off Ramps are Dynamic Ports.
Benefits
- Reusing of services.
- Reusing Pipeline components & Orchestrations for multiple message types.
- Deployment of changes / new versions with less or NO downtime.
- Orchestrations are not bound anymore to a Map or a XSD.
- Out of the box BAM.
- Centralized Error Handling.
- Performance.
- Out of the box Cache.
- Low latency scenarios.
- Using Pipeline Components (Messaging Services) instead of Orchestrations.
- You want to expose web services with BizTalk.
Conclusion
In BizTalk 2013 are most drawbacks solved. The installation is no longer a separate download but is now integrated as part of the BizTalk Server setup. Also in previous BizTalk versions, a dynamic send port uses the adapter’s default host but in BizTalk 2013 an adapter Send Handler is configurable for every installed adapter. However, it is still true that the learning curve is high but there is now also a book about the ESB Toolkit and the ESB Survival Guide gives a good overview of wikis and blogs about it. Still, in a BizTalk project where the ESB Toolkit is used it’s better to have also an experienced developer that has real experience with the ESB Toolkit so it can really help you.
See Also
For more information see:
by community-syndication | May 1, 2014 | BizTalk Community Blogs via Syndication
Working with TFS automated builds for BizTalk I have started to run into the TFS / MSBuild file path length restrictions (no, I don’t understand in modern operating system why the build process has a file path limit) and have tried several ways to reduce the path length, with varying degrees of success, this week I discovered one way to help reduce the path length without compromising the TFS Automated build process and I would like to share it with you.
Example of the default location for the source on a build server, I have highlighted one of the longer examples:
In the TFS build Agent there is a variable that controls the start of the source location on the build server, it is called Working Directory
The default value for this is:
$(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionPath)
In the build server I have this is:
C:\Builds\5\Mexia\BizTalkDemo_buildv3
The last part of this is the source tree path and the name of the build, which are typically much longer than this example.
To reduce this I found that we can change $(BuildDefinitionPath) to $(BuildDefinitionId)
$(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionId)
This changes the starting path to:
C:\Builds\5\15
This is reduce the path by 13 characters, but if your source tree path and build definition name are a typical size this may reduce the path by almost 100 characters, without compromising any part of the build process.
The previous list of files now looks like this:
I hope this tip helps solve your automated build path lengths issues.
More …
by community-syndication | Apr 30, 2014 | BizTalk Community Blogs via Syndication
When we create certain sized VMs, the NICs associated with them are throttled for
Outbound traffic. Here’s some numbers that were originally published from a little
while ago (may have changed since, but these give you a guide):
|
Specifications
|
Extra Small
|
Small
|
Medium
|
Large
|
Extra Large
|
|
CPU
|
1.0 GHz
|
1.6 GHz
|
2 X 1.6 GHz
|
4 X 1.6 GHz
|
8 X 1.6 GHz
|
|
Memory
|
768 MB
|
1.75 GB
|
3.5 GB
|
7 GB
|
14 GB
|
|
VM Local Storage
|
20 GB
|
225 GB
|
490 GB
|
1,000 GB
|
2,040 GB
|
|
Network I/O Performance
|
Low
|
Moderate
|
High
|
High
|
High
|
|
Allocated Bandwidth
|
5 Mbps
|
100 Mbps
|
200 Mbps
|
400 Mbps
|
800 Mbps
|
Blog Post by: Mick Badran
by community-syndication | Apr 30, 2014 | BizTalk Community Blogs via Syndication
In a couple weeks, I’ll be invading Houston, TX to deliver a pair of sessions at Microsoft TechEd. This conference – one of the largest annual Microsoft events – focuses on technology available today for developers and IT professionals. I made a pair of proposals to this conference back in January (hoping to increase my […]
Blog Post by: Richard Seroter
by community-syndication | Apr 29, 2014 | BizTalk Community Blogs via Syndication
The BizTalk360 team had grown considerably in the past few months. When you grow so quickly, it’s inevitable you’ll face some challenges around the processes in the company, the company culture, bringing everyone up to speed etc., – known more as the classic scalability issues. We thought it will be a good opportunity to capitalize […]
The post How did we use our BizTalk360 7.2 release for team building activity? appeared first on BizTalk360 Blog.
Blog Post by: Gokul Dhamodaran
by community-syndication | Apr 29, 2014 | BizTalk Community Blogs via Syndication
This is a temporary post that was not deleted. Please delete this manually. (d96073bb-052b-4975-9da0-288f8bfe23e9 – 3bfe001a-32de-4114-a6b4-4005b770f6d7)
The post Temporary Post Used For Theme Detection (33d6cbe8-5e27-424d-a286-5fc92356d33f – 3bfe001a-32de-4114-a6b4-4005b770f6d7) appeared first on BizTalk360 Blog.
Blog Post by: Gokul Dhamodaran