There are many situations where we need to deploy WCF Services that we can use to interact with BizTalk, but if you’re constantly deploying to new systems, the process of manually creating and configuring them can become very time consuming and tedious. Leveraging the abilities of the BizTalk Deployment Framework (BTDF) we can automate this process along with your typical BTDF deployment.
In this guide we’ll step through how to configure BTDF to build the deployment of our existing WCF Services into the installer which BTDF creates for deployments.
In order to follow this guide it’s assumed that you have the following prerequisites:
A BizTalk solution and environment with BTDF installed
Already deployed WCF Services which you wish to replicate via deployment on the same machine
A basic knowledge of BizTalk, WCF, and IIS
First up we need to move our services into our solution folder. Simply…
The Dell Boomi AtomSphere provides users with the ability to create and configure trading partners for EDI transactions. Users can create trading partners to be used with the X12 Interchange format.
The X12 Interchange Format is a standard used for the sending and receiving of EDI files, it allows us to define different pieces of information about the file and communicate information about what is expected of the file between the respective trading partners. It uses the ISA and GS segment definition headers within sent EDI messages to set this information.
This post will cover how to create a basic X12 Trading Partner and the different configuration options available for them.
First we can create our trading partner by creating a new component and selecting “Trading Partner”, we can configure items such as the name and whether or not this is our company…
In our last post we were able to import an EDI Profile using Dell Boomi’s built in tools and we learned a little bit about how Boomi processes EDI. This time we will be modifying our 810 profile with some custom fields that our “business” requires.
From last time, the file we’re working with for this sample looks like this:
We already have a profile that can handle the input of this file, but let’s say one of our department heads just notified us they would like to keep track of the type of truck the order an invoice was for was driven on.
We’ll say that information in our file will look something like this:
Let’s add this segment below our N1 Loop in the Header Loop, we’ll say that this information is static for an entire invoice so it makes sense to…
Today we will be going over how to send a message from a Dell Boomi process to an Azure Service Bus queue, and then read that message off the queue, again in a Dell Boomi process.
In Boomi, we can interact with the Service Bus via simple HTTP Post. We will be calling these with the HTTP Connector shape in our Dell Boomi process, from there we will be able to construct our request in full. Then we will show that we can find the message in our queue.
Setting up the Process
Start off by creating a new process in the Atomsphere dashboard and give it an associated name, then click create:
This will bring up our blank process. It will prompt us to setup the Start Shape, select “No Data”, we will be manually creating a sample message for the time being….
Dell Boomi is a cloud-based integration platform with many capabilities, EDI being no exception.
EDI stands for Electronic Data Interchange, which is a method to communicate data across various platforms and technologies. It provides a very versatile way to send data such as order and healthcare information very quickly in a standardized way. This standardization comes from the many EDI file types which exist. These file types are denoted by their respective numbers. For example, an 810 file is used to represent an Invoice.
EDI Files can be intimidating at first glance, but once you understand some basic syntax they become logical to read. For example, here’s a very small 810 Invoice file below:
Each line in the file is called a “Segment”. Within each segment there are numerous “Elements”, each element is separated by an “Element Delimiter”. In the case of our…