Dell Boomi continues to lead the iPaaS platform with leading edge features and cloud specific tools to help you succeed with your integration implementation. For the month of October Tallan is excited to announce AtomSphere’s latest feature set:
Java 8 Support
Atom Cloud upgraders and installers (for Windows and Linux) for Java 8 are available.
For new Molecule and Cloud installations on Java 8, the default cluster library is JGroups 3.
Additionally, if a non-Atom folder is selected during an upgrade to Java 8, clicking OK returns to the previous screen to select a different installation folder.
Test Atom Cloud
The following observations come from the NYC SQL Server Meetup 9/1/2015 presented by Devin Knight of Pragmatic Works, augmented with my own discoveries. They assume the reader has basic familiarity with the prior PowerPivot, PowerQuery and PowerView products.
• This release debuts PowerBI Desktop (PBID). The significance of this is that PowerBI is no longer tied to Excel or Sharepoint, thus it no longer requires IT involvement (aside from giving access to data sources). It is a stand-alone app ala (but not part of) Office 365. It is basically a bundling, divorced from Excel, of the prior PowerQuery, PowerPivot and PowerView products. Look and feel is very similar to these. It can be downloaded for free from www.powerbi.com
• The disconnect from Excel means it can have its own release cycle and not be constrained by having to render through Excel. There have reportedly…
In the September release for Dell Boomi’s Atomsphere the platform now offers a Google Apps Connector!
The Google Apps connector uses the Google Drive API for spreadsheet file management as the Google Document List API has been deprecated.
Dell Boomi has added the following improvements to the September 2015 release of Dell Boomi AtomSphere. For more information, please see the September Release Notes in the AtomSphere Reference Guide.
A Dell Boomi administrator can create a series of API Roles and associate specific users to each API Role. By associating a group of users to a single API Role, the administrator can grant access all the users associated with that API Role for specific APIs, groups of APIs, or web service components at once without needing to set the permissions individually.
Also, the administrator can define specific IP addresses or IP address ranges…
We thought we’d post some of the recent changes and new functionality added to the Del Boomi Platform. Some of these are additional features to the API Stack while others are new functionality in existing shapes (as in the try/catch shape) and the New proxy settings for Atom, HTTP, SOCKS4, and SOCKS5 protocols provide the ability to add a userID and password to key-based authentications. Overall some really really cool stuff and we hope that you will find them useful in your project or implementation!!!!!!
Please read on and see if one of these enhancements or new features will work for you!
In the last post, I wrote about the overall structure of 837P claim messages. 837I and 837D messages have similar structures, though with some differences – for example, the 837I has many more diagnosis code options, and the 837D has more specific nodes for tooth identification, etc. One important thing to note is that 837P, 837I, and 837D files are very similar, but not the same. It’s not enough to simply change the version numbers in the GS and ST segments and then try to process one the same as the other! If it were that easy, we wouldn’t need separate schemas for them in BizTalk!
BizTalk provides out of the box functionality to support these message types, with well developed functionality to translate the X12 EDI to XML and vice versa. The schema nodes also have friendly names, translating something like this:
Muenchian Grouping is a powerful technique for to allow grouping by common values among looping/repeating nodes in an XML document. BizTalk does not have out of the box support for this, but it can be achieved by adding custom XSLT to a map. Chris Romp wrote a post about this years ago that serves as an excellent example of the idea in BizTalk: http://blogs.msdn.com/b/chrisromp/archive/2008/07/31/muenchian-grouping-and-sorting-in-biztalk-maps.aspx. The drawback of his method is that you lose all other Mapper functionality by using completely custom XSLT, and custom XSLT is more difficult to maintain than a BizTalk map.
Enter Sandro Periera’s phenomenal tutorial on Muenchian Grouping in BizTalk maps (https://code.msdn.microsoft.com/windowsdesktop/Muenchian-Grouping-and-790347d2). His solution is particularly powerful because it allows you to maintain the functionality and simplicity of the BizTalk Mapping engine while extending it to allow for the Muenchian Grouping technique as well. However, there is still…
Recently, I presented a webinar “Secure Integration Messaging with BizTalk and Windows Azure Service Bus (formerly known as AppFabric Service Bus).
I’d like to take some time and walk through creating the solution. In this webinar, I demonstrated how to process inbound orders from external trading partners into our on-premise middle-ware platform (which routes orders to the fulfillment order processing systems). One of the key components to solving this integration problem was Windows Azure Service Bus. The Windows Azure Service Bus exposes an endpoint and acts as a relay service to external endpoints. BizTalk 2010 can now natively connect to the Service Bus using the AppFabric Connect feature. This feature can be installed from the BizTalk 2010 installation media.
Here is the overall architecture:
Below illustrates the integrated external B2B partners into our internal LOB systems flow…
I’ll walk you through how I created this simple solution:
I Just returned from TechEd 2012 and one of my favorite sessions was ‘Application Integration Futures – The Road Map and What’s Next in Windows Azure‘. It was refreshing to see the first slide’s title “Key takeaways: we are innovating in BizTalk”.
Here is the abbreviated message from the slide deck:
Continued investment in BizTalk – take your investment forward
BizTalk Server: releasing 6 months after Windows 8
Enabling new Azure based BizTalk scenarios in IaaS & PaaS
Bringing together BizTalk on-premises and Azure
Bet on BizTalk and continue to buy
BizTalk on IaaS coming soon – reduce hardware procurement lead time; reduce time & cost setup and configuration (expect “base BizTalk images”; move apps to Azure and back easily
BizTalk on PaaS – we are already seeing EAI & EDI on Service Bus using Bridges, Transforms, and trading partner management
Here is the timeline (taken from the presentation slide deck)
A challenge we have at Tallan is keeping our training up-to-date with the latest and greatest of technologies. We are constantly re-evaluating our lessons to keep up with ever changing technologies. In recent months, we have seen a shift in our client work from using traditional ASP.NET to using ASP.NET MVC 2. This has challenged our .NET developers to learn and create MVC best practices and ensure high quality deliverables. As you may know, MVC to a .NET developer can take time to understand and learn.
As an organization, we approach training from a mentor/mentee concept. This allows our trainees to have a dedicated training partner to guide him/her through the module and it allows for the mentor to learn communication and management skills. We have begun reviewing our training process, in particular our .Net training modules. With this in mind…
Recently, a company in the process of implementing BT 2006 within their enterprise asked me for a recommendation regarding best practices for a pre-existing usage scenario they were seeking to accommodate using BizTalk. This company receives, on a reoccurring basis, a variety of disparate inbound flat file business documents which, at present, are processed into their suite of business applications using SQL Server DTS. While the interchange with this company in question has CERTAINLY inspired folks at BlogBizTalk and Tallan to start developing a whitepaper comparing and defining best-practice usage and design considerations for implementing SSIS (or equivalent ETL tool) and BizTalk both in scenarios of consonance or autonomy, a few much more immediate considerations arose for my address.
One such very much more low level consideration was that for the handling of the disparity of received file formats. My understanding…