Integration Basics

Issue: I encountered a strange problem today. When I attempted to open a solution I had developed a few days ago in Visual Studio 2019, it kept crashing. Resolution: Repair Visual Studio. Restart the server or your development box.

 1. Check Active connections Check Active connections by running the below command. If there are any active connections then you need to terminate those connections USE master; SELECT * FROM sys.sysprocesses WHERE dbid = DB_ID('TestDB'); 2. Disconnect users You need to disconnect users. If you run the below statement, it will set the database to single-user mode USE master; ALTER DATABASE TestDB SET SINGLE_USER WITH ROLLBACK IMMEDIATE; 3. After doing this, try to drop the database by running the below command. DROP DATABASE TestDB;

Issue In some cases when you deploy the changes using CI CD pipeline in BizTalk the changes might not be visible. Root cause CI CD might have skipped the undeploy. Hence you need to manually uninstall by going to the control panel and uninstalling it. Please go ahead and delete the .msi from the back up and the main folder as well

Steps  Let's remove the connection and redeploy the process But you can see that the connection is available under the environment extensions. This is working as expected. If you need to roll back to a previous version, the process will work properly if the extension is in place. In some cases, you might want to use the connection at a later point in time. It helps in such scenarios. Let us now see how we can remove it from the environment extensions in case this is causing confusion for you. Re-add the connection that we have removed. There is no need to hook up the connection. Just place it on the canvas. Now click on Extensions Uncheck the extended properties and click OK and save the process Now remove the connection, save it, create a new packaged component, and deploy the process.

 Undeploying a Boomi Application Deploy --> Deployments Add Filter --> Component You will find the process. Now click on Undeploy . Click on Undeploy

Document Flow in Boomi Each document may contain one or multiple records. Groups of documents move in a batch in Boomi. Boomi automatically loops through records and documents. Each path processes to completion before the next path begins. Different Shapes in Boomi Branch Processes entire deck of documents in each branch shape It executes each path sequentially. The documents flow down the subsequent paths only if the documents flowing down the preceding path succeed in completing the path A branch can have up to 25 paths Decision Sort the documents into 2 piles. The one which matches true is executed first and the other which matches false is executed last. Try-Catch This is used for error handling. All documents flow through the Try path. Failed document flow to the catch path Flow Control Batching Documents are batched into the specified size + remainder. For example you are batching by 5 documents and you receive 21 documents in that shape. It will be processed in batches in the ma...

Basics of Process Route Shape Use case : Suppose you have a route shape that directs documents to different execution paths. For example, if the company value is "Company A," the document follows the Company A execution path. If the value is "Company B," it takes the Company B execution path. Now, imagine that changes are required in the business logic for both execution paths. The team handling the Company A execution has already completed their changes. However, the team working on Company B's changes has not finished their updates, creating a dependency for the entire application deployment. By utilizing a process route shape, you can decouple the application. Replace the route shape with a process route shape, allowing you to deploy the process route component separately from the sub-processes. This approach enables you to decouple the application, providing flexibility in managing dependencies Process Route shape By using the process route shape, yo...