In this blog we are going to discuss how we can use Boomi API to overcome some of the limitations of using Web Service Server connectors.
Here are some of the limitations we discussed in our previous blog.
In REST service, how do we restrict the process to support specific REST verbs, for example say the process should accept only the GET/POST and reject DELETE/PUT.
Passing queries/parameter in the URL itself
Something like this http://SERVER:9090/ws/simple/getBlogs/blogid/1 or this http://SERVER:9090/ws/simple/getBlogs?blogid=1
Managing or assigning multiple web services end point to a Boomi process
This blog post will discuss ways to work with the Boomi AtomSphere API to work around these limitations
Before we begin using Boomi API, we need to verify access to the Boomi API.
Login into Boomi portal, In the top right menu, select API Management.
If you are able to see below screen then you have the access to…
While testing an integration it is always important to perform a series of negative test cases to ensure the process can fail gracefully through error handling. It is not always possible for endpoint environments to be set up for quick and easy testing. For this reason, a useful step in the development process is to create test harnesses. These can act as the implementation of abstract test cases beyond simple shape-to-shape testing. Test harnesses are also incredibly useful for regression testing.
There are some instances where you may wish to package a set of processes that ready for installation by managed accounts. Dell Boomi offers a solution to this problem with the use of Integration packs. Integrations packs allow you to offer a pre-packaged solution to your end users.
There are however a few things to consider before using integration packs:
You can only have a maximum of 100 processes in a single integration pack.
There are several components that cannot be added to an integration pack. Those elements included
Process Route Components
Processes that contain Process Route Components
Processes must first be published to a process library before being added to an integration pack. For more information about how to use process libraries in Dell Boomi, see this link
Integration pack management and multi-install integration packs are optional Dell Boomi AtomSphere features that must first be…
There are a wide range of scheduling options that are made available to a Boomi application once it is deployed. Depending on the inbound connector used in the application, once deployed the process can run on a schedule or it can continuously poll some existing data source. How the process runs is dependent on if the inbound connector being a “Get” operation or a “Listen” operation.
A “Get” operation allows the process to get a set of inbound records from a data source. Upon deployment this process can either be triggered manually or can have a schedule set up so that it runs on set intervals, for example perhaps it is desired that the process runs every Tuesday and Thursday of every week.
A “Listen” operation allows a data source to be continuously polled and will retrieve data as it comes in. An…
A common operation in Dell Boomi is to copy processes from one account to another. These processes can often be used as templates for new processes. One way to accomplish this task is to copy the process to the other account choosing the account and the folder.
While this method does move the process that we need to the correct account, there are a few drawbacks to this method.
It is difficult to determine which version of the process you are using when copying the process in this manner.
Copying a new version of the process is often messy process which involves first deleting the old version of the process before copying over the new version.
In many instances there are better and less painful alternatives to the above mentioned method.
Dell Boomi offers a feature called Process Library Management that fixes these issues….
While the Dell Boomi user interface is highly robust and user friendly there are times when using the user interface can prove to be quite tedious. One example that we have discovered to be an example of this are process deployments. In order to deploy a set of Boomi processes one must search for each individual process and deploy. This may not seem overly tedious if AtomSphere only has a few processes. But in some cases AtomSphere could have numerous applications each consisting of many processes. It is easy to see given the scenario how frequent deployments could prove to be very time consuming.
Luckily, there is an alternative to using the AtomSphere user interface. Dell Boomi offers a set of APIs (both REST and SOAP) that can be used for various sets of tasks and that includes deploying Boomi processes….
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…
Through the use of Atom Queues and Listeners a single process can spawn many iterations of a listening process. Each process spawned from a listener will execute asynchronously, independent of any other executions. By default, an Atom Queue listener will spawn an instance of the listening process every time a document is written to the queue. While this will work fine in cases with a low throughput, larger numbers of documents being processed will cause a large number of executions to get kicked off.
Many times when working with Microsoft Azure, it is necessary to read and write information to Microsoft Azure File Storage. Unfortunately, at this time Dell Boomi currently only supports a Microsoft Blob Storage Connector; one possible solution to this problem is to use Microsoft’s AzCopy utility to read and write information to Microsoft Azure File Storage.
AzCopy is a command-line Utility designed for copy data to and from Microsoft Azure Blob, File, and Table storage; but our purposes we will be using it to write data to Microsoft Azure File Storage.
AzCopy can be downloaded from this link (http://aka.ms/downloadazcopy). To install, simply follow the installation instructions.
One possible use of AzCopy is to upload newly created data files to Microsoft Azure File Storage. By doing so we can call AzCopy to upload the data files after we have finished creating them all rather…
Many times when a document cache is created for use in a lookup function, only a few values are actually needed. A typical approach to document caching would write an entire document to the cache, including unneeded values. This approach works fine when caching a small number of documents, but will perform worse as more documents need to be cached. A much more efficient approach is to only cache the elements of a document that are actually used.