Now a days there are a lots of compression is going on for different kind of Integration tool. Here I am providing some information about BizTalk and MuleSoft. Both are popular and have a lots of confusion on choosing the tool for Integration. BizTalk: • BizTalk is the Integration tool developed by Microsoft • BizTalk … Continue reading Difference Between BizTalk and MuleSoft
I have created this presentation to show the concept of BizTalk server as Enterprise Application Integration. And about how does BizTalk fit in the Enterprise Application Integration concepts, How does BizTalk fulfill the Security criteria, Error Handling and Business Monitoring BizTalk_Interprise Application Integration
Enterprise Application Integration: In modern era, the concept of EAI is more relevant in IT industry. This is era of SAAS (Software as a system) and from large to small company everyone tries to create product and sell. And every organization cannot depend on one software or technologies. So, Enterprise integration becomes the vital part … Continue reading Enterprise Application Integration
Issue: The local MS DTC detected that the MS DTC on database has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC … Continue reading MSDTC issue while configuring BizTalk
SSO Application configuration requires to reduce burden on BizTalk Configuration file, because using BizTalk configuration file some time create problem if any one by mistake update some invalid data then it will not run any BizTalk application. Also, you cannot set up value from BTSConfig in custom pipeline. So, to overcome this issue, there is … Continue reading SSO Application configuration
Issue: Webhost failed to process a request. Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/33808916 Exception: System.ServiceModel.ServiceActivationException: The service ServiceName.svc cannot be activated due to an exception during compilation. The exception message is: Receive location for address ServiceName.svc not found. (The BizTalk receive location may be disabled.). ---> Microsoft.BizTalk.Adapter.Wcf.AdapterException: Receive location for address ServiceName.svc not found. (The BizTalk receive location … Continue reading Microsoft.BizTalk.Adapter.Wcf.AdapterException: Receive location for address ServiceName.svc not found
Issue: XML is missing in XMLDisassenbler stage: There was a failure executing the receive pipeline: Source: "XML disassembler" Receive Port URI Reason: Item has already been added. Key in dictionary: 'Request' Key being added: 'Request' Resolution: When we use ESB pipeline in BizTalk Receive location, this will happen when there is multiple schema in BizTalk … Continue reading XML is missing in XMLDisassenbler stage: There was a failure executing the receive pipeline: Source: XML disassembler
Issues: The type or namespace name does not exist in the namespace in orchestration. Reason: When we have start building solution and add orchestration. And after some time we change the name or design of the solution. And then if we create a new orchestration, that orchestration would have different namespace from older solution because solution … Continue reading The type or namespace name does not exist in the namespace.