Senior Application Specialist at Taqa Distribution
Real User
Top 20
Aug 13, 2025
Our usual use cases for BizTalk Server include mobile app integration with BizTalk Server, website integration with BizTalk Server, and other applications because we are from a utility company.
My customer's usual use cases for BizTalk Server are mainly for electronic data interchange, EDI. For example, they exchange documents such as orders and invoices in a structured way, sending invoices from SAP to customers using other systems. They use numerous standard formats such as EDIFACT or TRADACOMS in the UK. My main work is to implement the translations from one system to another or from one system to a standard message format.
The solution runs on-premise. It is a good middleware product that Microsoft has developed. It is used by the manufacturing, oil, and gas industries, as well as many other platforms. Many other products have evolved in the market, but BizTalk is still standing because of its performance. It is capable of pushing a maximum volume of data from a source system to a target system. It has a good capacity.
Recently, I migrated BizTalk applications into the Azure integration site, including Logic Apps, repair management, and some files. I implemented all of the DevOps setups, so I'm aware of BizTalk pipelines and development. If you're a client, you can use BizTalk as middleware. For instance, you can treat SalesForce as a destination if you want to communicate IDOCs to SalesForce subjects. In that case, BizTalk will be the middleware and will do the data transformation in the mapping or orchestration. If you want to use any policies or data transformations, you can implement it in the mapping level and implement some policies. We can apply some mapping and policies in BizTalk, like BAM policies or BRE policies. We can do all kinds of data resolution. The SalesForce objects will accept the same kind of format, and we can develop and do the data transformation in the same way. We can do the mapping and convert the data from the data center into XML. I used the 2016 version of BizTalk. The solution is deployed on-premises. The number of users is limited. We're able to restrict users. We created a security group and gave access to four to five members, so only those people can use the particular server.
BizTalk Server is used for system integration. Individuals convert different messages into different formats, which are transmitted through BizTalk. The solution is also used for some really brief orchestrations as well. Sophisticated workflows are really slow if they are managed with BizTalk.
The primary use cases for BizTalk Server involve logistic warehouse management for one of the business units.
Our usual use cases for BizTalk Server include mobile app integration with BizTalk Server, website integration with BizTalk Server, and other applications because we are from a utility company.
My customer's usual use cases for BizTalk Server are mainly for electronic data interchange, EDI. For example, they exchange documents such as orders and invoices in a structured way, sending invoices from SAP to customers using other systems. They use numerous standard formats such as EDIFACT or TRADACOMS in the UK. My main work is to implement the translations from one system to another or from one system to a standard message format.
The solution runs on-premise. It is a good middleware product that Microsoft has developed. It is used by the manufacturing, oil, and gas industries, as well as many other platforms. Many other products have evolved in the market, but BizTalk is still standing because of its performance. It is capable of pushing a maximum volume of data from a source system to a target system. It has a good capacity.
We use the product for verification with the bank.
Recently, I migrated BizTalk applications into the Azure integration site, including Logic Apps, repair management, and some files. I implemented all of the DevOps setups, so I'm aware of BizTalk pipelines and development. If you're a client, you can use BizTalk as middleware. For instance, you can treat SalesForce as a destination if you want to communicate IDOCs to SalesForce subjects. In that case, BizTalk will be the middleware and will do the data transformation in the mapping or orchestration. If you want to use any policies or data transformations, you can implement it in the mapping level and implement some policies. We can apply some mapping and policies in BizTalk, like BAM policies or BRE policies. We can do all kinds of data resolution. The SalesForce objects will accept the same kind of format, and we can develop and do the data transformation in the same way. We can do the mapping and convert the data from the data center into XML. I used the 2016 version of BizTalk. The solution is deployed on-premises. The number of users is limited. We're able to restrict users. We created a security group and gave access to four to five members, so only those people can use the particular server.
BizTalk Server is used for system integration. Individuals convert different messages into different formats, which are transmitted through BizTalk. The solution is also used for some really brief orchestrations as well. Sophisticated workflows are really slow if they are managed with BizTalk.